The methodology has nine steps, each producing a deliverable alongside an emotional dynamic in the room that is as important as the artifact it generates. This is the overview.
Intake builds from what already exists
Intake compiles what already exists: decks presented to the board, roadmaps built by individual workstreams, status reports from earlier phases, vendor proposals, org charts, and project plans. The deliverable is a compiled view of the current state. The emotional dynamic is vulnerability. The program team is showing the consulting team the real situation, including the contradictions between documents and gaps nobody has addressed. Our job is to receive that information with clarity, not judgment.
Stakeholder mapping surfaces what people actually think
We conduct one-on-one interviews with twelve to twenty stakeholders across the functions involved, eliciting what people think privately but have not said in group settings. The deliverable is a stakeholder map capturing each person’s role, influence, concerns, and alignment. It also produces the first dependency signals: constraints and conflicts that live in individual knowledge rather than shared documentation. The emotional dynamic is relief; for many stakeholders, this is the first time someone has asked what they actually think.
Program architecture reveals hidden complexity
Architecture defines the program’s structure: how many workstreams, who owns each one, what the boundaries are, and where the dependencies sit. The deliverable is a program architecture diagram with workstream definitions, ownership assignments, and a dependency map. The emotional dynamic is the first dip of the W-curve. The architecture session reveals complexity the organization had not seen in one place before: overlapping scopes and unowned gaps, plus dependencies requiring coordination mechanisms nobody has built.
Pre-mortems give permission to name real risks
The pre-mortem asks the team to assume the program has failed and name the most likely reasons. This gives permission to be pessimistic in a structured way, producing risks that standard risk logs rarely capture (i.e., political dynamics and resource conflicts, plus vendor relationships weaker than the contract implies). The deliverable is a risk register plus a constraints calendar mapping the windows when the organization cannot execute: code freezes, budget cycles, seasonal peaks, and annual planning processes. The team leaves this step with a clear-eyed view of the obstacles ahead, and that clarity makes the next step productive.
Roadmap sessions turn constraints into a shared plan
The team builds the integrated plan together. We bring the architecture, dependency map, risk register, and constraints calendar into the room; the team sequences milestones, resolves timing conflicts, and designs around the constraints surfaced in the pre-mortem. The deliverable is the integrated roadmap: a single view of every workstream’s milestones, dependencies, and critical path. The emotional dynamic is the creative peak. We use co-creation with a 70/30 split (i.e., the client generates 70% of the content while the consulting team provides 30% as structure and facilitation). The plan belongs to the people who built it.
The operating model connects governance to real risks
The operating model designs the governance infrastructure: decision rights, meeting cadences, escalation paths, and coordination mechanisms. The deliverable specifies who makes which decisions, how often cross-functional coordination happens, and what the escalation path looks like. The emotional dynamic is the second dip. After the creative peak of roadmapping, governance design feels bureaucratic. The consulting team connects each governance element to specific risks and dependencies the team already identified, so the operating model registers as insurance rather than overhead.
Change management plans for the people not in the room
Change management plans for the people affected by the program’s outcomes: end users, store partners, field teams, patients, clinicians, or customers whose work will change. The deliverable maps affected populations, communication sequences, training requirements, and adoption metrics. Programs that skip this step produce plans the program team owns but the organization cannot absorb.
Rollout makes abstract dependencies concrete
Rollout sequences waves of execution and defines success criteria for each wave. The deliverable includes wave definitions and go/no-go criteria with contingency protocols. Dependencies that were abstract during roadmapping become concrete: this workstream delivers to that workstream in this window, and the gate checks whether the handoff is clean.
Readouts demonstrate that ownership has transferred
The team presents the integrated plan, operating model, risk register, and rollout plan to the executive sponsor and steering committee. The program lead walks through the architecture; workstream leads present their scopes. The risk register, now evolved into a decision log, shows the tradeoffs the team has already resolved. The emotional arc is graduation. The team built this plan, and they present it. When the engagement has built genuine ownership along the way, the readout demonstrates that the team can run the program independently. Each step carries its own facilitation techniques, artifacts, and emotional design, and the book explores them in depth.
