The book started as a pattern library. After enough cross-functional planning engagements in retail and life sciences, the same problems kept appearing in the same sequence: the charter that described scope in language broad enough to mean anything; the roadmap that was a Gantt chart with color-coded bars and no dependencies mapped; the governance structure that existed as a recurring meeting series with no decision rights defined; the change management plan that would be built “once we get further along,” which meant too late or not at all. These were structural failures, and organizations with different industries and sophistication levels kept producing the same gaps in the same places. That pattern was too consistent to be coincidental and too consequential to leave undocumented.
Patterns Became a Methodology
The first version was a set of session designs and templates that worked across engagements. If the intake step kept revealing the same types of gaps, the intake process could be standardized around surfacing them; if the 70/30 facilitation structure kept producing stronger ownership, it could become a design principle. Over several years and dozens of engagements, those session designs became a nine-step methodology. Each step exists because a specific engagement proved it was necessary. Step 4 was added after an engagement where the team skipped risk assessment and paid for it during execution; the constraints calendar was added after a deployment got scheduled into an operational blackout window everyone knew about but nobody surfaced; the operating model step was refined after a strong roadmap fell apart because the team had no governance rhythm to maintain it. The methodology was extracted from engagements, and every step exists because something went wrong in an engagement that didn’t have it.
A Book Transfers What Decks Cannot
A VP who is about to lead a cross-functional program cannot learn what she needs from a ten-slide overview. She needs to understand the reasoning behind each step, the emotional dynamics of each session, the design decisions that make exercises work, and the failure modes that emerge when steps are skipped or sequenced incorrectly. That level of depth requires a book, which allows us to explain why the methodology works the way it does: why intake comes before stakeholder mapping, why the pre-mortem sits between architecture and roadmapping, why the operating model step matters more than most clients expect, why facilitation design is experience design, and why the engagement itself is what the client evaluates.
The Reader We Wrote For
The book is written for the VP or senior director who has been asked to lead a cross-functional program and who has been through enough consulting engagements to be skeptical of frameworks that sound polished in a pitch and break down in execution. This reader does not need to be convinced that cross-functional planning is hard; she has lived through programs where the plan looked solid on paper and fell apart when it hit the organization’s actual constraints and capacity limits. What she needs is a practical, tested approach she can evaluate before deciding whether to engage a firm, and one she can use as a reference during execution regardless of which firm she engages. The book is designed to be that reference, and it is designed to be adaptable. The nine steps are a recommended order because each step produces inputs the next step requires, but an organization with a strong baseline might move through intake in two days, and an organization with a mature risk culture might run a lighter pre-mortem. Each chapter explains what the step needs to accomplish, giving the reader the judgment to adapt rather than follow mechanically.
Transparency Builds Trust
Publishing a methodology is a risk for a consulting firm, but our bet is that transparency builds trust. The VP who reads the book and finds it useful is more likely to engage us than the VP who sat through a pitch and has to take the methodology on faith. The book lets her evaluate the approach on her own terms and test it against her experience before she signs anything. Knowing the steps does not replicate the ability to run them well. Our value is the facilitation skill and the pattern recognition from dozens of engagements: the experience design that makes each session land with a room full of senior leaders. If the methodology cannot withstand scrutiny when published in full, it was not strong enough to begin with. The question of what stays after you leave applies to the book itself: if the methodology can sustain without the consulting team in the room, the book will have served its purpose. The book is here.
