The Good
You start without the baggage that slows other programs down: no legacy architecture to work around and no half-built systems constraining what’s possible. Building right from the start means sequencing properly, with every artifact connecting to the next. Programs that inherit broken infrastructure spend months untangling it; this one starts clean, and that’s a bigger advantage than most people realize.
Diagnosis
Either a new program that hasn’t built any planning infrastructure, or an inherited program where nothing was documented. The Blank Slate hasn’t failed; it hasn’t started yet. The real risk is the temptation to do everything at once.
What Typically Breaks
Everything, eventually, but the direct cause is usually paralysis: the scope is overwhelming and the team doesn’t know where to begin. Somebody starts a risk register while somebody else builds a roadmap, and nothing connects.
Risk Narrative
Overwhelming scope with no foundation creates the danger of starting everywhere and finishing nowhere.
Highest-Leverage Moves
1. Landscape Brief: Start here. Baseline what exists and document constraints. 2. Stakeholder Map + Architecture Blueprint: Know who matters before you start designing anything, then define the workstream structure. Phase 1 first, always. Do not touch Phase 2 or Phase 3 until Phase 1 is solid. The intervention should be sequenced, not launched in parallel.
Content to Surface
“What a [Artifact] Is” foundational pages for all 9 dimensions, the full method overview, blog posts on why programs fail