The nine steps of the methodology look like a project plan: intake, stakeholder mapping, architecture, pre-mortem, roadmap, operating model, change management, rollout, handoff. But the nine steps are a designed emotional experience. Each step produces a deliverable and a feeling, and the feelings are as deliberate as the deliverables. A methodology that ignores the emotional layer produces technically correct plans that the organization does not own; what the team remembers about the process determines whether the plan survives.
Vulnerability establishes the emotional contract
Step 1 (intake) compiles what already exists: plans, decks, status reports, roadmaps. The deliverable is a baseline, but the emotional experience is vulnerability. The program team is showing us the real situation, including the contradictions and the gaps, including documents that haven’t been updated since last quarter. Step 2 (stakeholder mapping) deepens that vulnerability. One-on-ones surface what plans leave out: political dynamics and resource conflicts, plus private doubts about the timeline. People say things in a one-on-one that they will not say in a room. These first two steps set the emotional contract for the engagement. If the client team experiences vulnerability and receives it back as organized clarity, trust is established. If honesty is handled carelessly, the engagement never recovers.
The productive dip reveals real complexity
Step 3 (architecture) defines the program’s structure, ownership, and dependencies; step 4 (pre-mortem) identifies the ways the program is most likely to fail. Designing for failure is the core discipline of this phase. The emotional experience is discomfort. The architecture session reveals overlapping workstreams nobody had mapped. The pre-mortem forces the team to name failure modes everyone has been avoiding. The constraints calendar shows that execution windows are smaller than the approved timeline assumed. This is the first valley of the W-curve, and it’s by design. The client team is seeing their program’s real complexity, often for the first time. Our job during this phase is to name the discomfort in advance so the team experiences it as progress rather than as evidence that the engagement is failing. When the dip is expected, it builds credibility; when it’s a surprise, it erodes confidence.
Generative energy produces ownership
Step 5 (roadmap sessions) shifts from diagnosis to construction. The energy shifts; people are building together. The integrated roadmap visual comes together, and for the first time the entire program is visible on a single page; workstream leads who’ve been working in silos see how their piece connects to every other piece. That’s when ownership kicks in. The plan is built from their constraints and their risks, shaped by their input. The consulting team shaped the process, but the content belongs to the people who generated it. The risk during this phase is scope expansion, since generative energy tends to produce expanding ambition. We manage this through the conflict log, which captures ideas and concerns without letting them derail the session.
Governance connects back to owned risks
Steps 6 through 8 (operating model, change management, and rollout) design the infrastructure that makes the plan executable: governance structures, decision rights, communication plans, and wave sequencing. The emotional experience is impatience. The client team has just experienced the high of building an integrated plan, and now the facilitators are asking them to design meeting structures. This is the second valley of the W-curve. The consulting team connects each governance element directly to the risks identified during the pre-mortem. The escalation path exists because the pre-mortem identified cross-functional decisions that will stall without a clear resolution mechanism. When the operating model is connected to specific risks the team already owns, it registers as insurance rather than overhead.
The readout demonstrates independence
Step 9 (readouts and handoff) is graduation. The client team presents the integrated plan to the executive sponsor and steering committee:
- The program lead walks through the architecture while workstream leads present their scopes, milestones, and dependencies
- The risk register, now evolved into a decision log, shows the tradeoffs the team has already resolved
When the engagement builds genuine ownership along the way, the readout demonstrates that the team can run the program independently. When it does not, the readout is a handoff of artifacts the team doesn’t feel connected to, and the program reverts to its pre-engagement state within weeks. A predictable emotional arc shapes every engagement, and one program’s full journey illustrates how the W-curve plays out in practice.
