Most consulting deliverables fail at adoption, not analysis. A roadmap we build is our roadmap; the client will review it, request changes, and approve it, but they won’t feel ownership the way they would if they’d built it themselves. The productive ratio is close to 30/70: we provide 30% of the content (i.e., frameworks and a process for working through the material) and the room provides 70% (i.e., the constraints, decisions, local knowledge, and commitments that only the people in the room can contribute). Because the experience is the product, how the output gets created matters as much as what it contains.
Ownership Through Structured Contribution
The 30/70 split addresses this by structuring the exercise so the room does the substantive work. We bring the template for a workstream charter; the room fills in the scope, names the dependencies, and defines the success criteria. We bring a draft program architecture based on intake interviews; the room marks it up, moves the boundaries, and resolves the overlaps. We bring a pre-mortem framework; the room generates the failure modes from their own experience.
In each case, our contribution is structural; the room’s contribution is substantive. The output belongs to the room because they built the parts that matter.
What the 30% and 70% Look Like in Practice
The 30% we bring is the scaffolding that makes the 70% productive. Without structure, a room of senior leaders will default to their most comfortable mode: status updates or political positioning. Our 30% prevents this by providing a specific format for the work. A good 30% includes:
- A clear question the exercise answers (e.g., “what are the most likely failure modes for this program?”) with a framework that constrains the response (e.g., “each failure mode must include a trigger, an impact, and a mitigation”)
- A process for collecting input (e.g., “independent writing, then round-robin sharing, then group prioritization”)
The structure is opinionated: this is the question, this is the format, this is how the room will work through it. That opinion is what the room is paying for. The content that fills the structure comes from the people who know the business, the constraints, and the politics.
The 70% the room generates is the material that no outside consulting team can bring. It includes the specific constraints that affect this program in this organization at this time: the migration blackouts, the political dynamics between a VP of Data Engineering and a VP of Merchandising who don’t trust each other’s numbers. It also includes commitment. When a workstream lead writes their own success criteria instead of reviewing criteria someone else wrote, they’re making a commitment. When a VP names a failure mode in a pre-mortem, they’re publicly acknowledging a risk they’re now responsible for mitigating. Generating content creates accountability that reviewing someone else’s content does not, and giving the room permission to be critical is what unlocks the 70%.
Calibrating the Split
The ratio breaks when we bring too much. Walking into a roadmapping session with a completed roadmap and asking the room “does this look right?” reduces their job from building to approving, and approval doesn’t produce ownership. It also breaks when we bring too little. A session that starts with “let’s brainstorm the program architecture” without a draft structure or a clear process will produce unstructured output; the room needs scaffolding.
The 30/70 split is a design discipline. Each exercise is built to answer a specific question, using a specific structure, with the room doing the substantive work inside that structure. The facilitator’s job is to design the 30% so precisely that the 70% is productive, specific, and owned by the people who generated it. When the team is building together in a roadmap session, that calibration is what makes the difference between output that gets used and output that gets filed.
