Roadmap sessions work when the room does the building. In a recent engagement, we brought three pre-built strawman roadmaps into a session with workstream leads who had already sat through two planning efforts that produced documents no one referenced again. Rather than presenting slides or starting from a blank page, we gave each lead a printed draft and three colored pens, and the session turned skepticism into ownership in ninety minutes.
Strawman drafts give the room a concrete starting point
We constructed one strawman roadmap per workstream from intake interviews and stakeholder sessions conducted earlier in the planning process. Each reflected our best understanding of the workstream’s scope, key milestones, dependencies, and sequencing. The drafts were printed on large-format paper, taped to the wall, and clearly labeled as works in progress. Each workstream lead received three pens:
- Red for marking what was wrong
- Green for adding what was missing
- Blue for flagging what was in the wrong sequence
The instruction was simple: take twenty minutes, review the strawman for your workstream, and mark it up. We did not present the strawman or walk the room through it; the workstream leads engaged with it directly.
Reactive exercises produce stronger output than generative ones
Within twenty minutes, all three drafts were covered in markup. The leads had crossed out milestones and added activities the intake interviews had not captured, rearranging sequencing based on operational constraints only they knew about. They were talking to each other, negotiating dependency timing and debating which milestones had to happen first. The skepticism had not disappeared; it had been redirected away from the planning process and toward the content of the plan itself. The strawman accomplished what a blank page and a finished plan cannot: it gave the room a format designed to be challenged and a concrete starting point. Reacting to a specific proposal is a task experienced operators can do quickly and with specificity; generating a roadmap from scratch is not. The full framework for why strawmen beat blank pages starts with this principle.
Ownership follows from doing the substantive work
The exercise was designed so the workstream leads did the substantive work. We provided roughly 30% of the content (i.e., the strawman drafts and the pen framework with a structured walkthrough); the room provided the remaining 70% (i.e., corrections, additions, sequencing arguments, dependency negotiations, and operational knowledge no outside consulting team could have brought). This is how facilitation design works at the exercise level. After the markup, we led a structured walkthrough. Each workstream lead presented their changes to the room, and the cross-workstream dependencies that surfaced during the markup were captured on a separate board for the second half of the session. Two workstreams had milestone conflicts: one needed an integration environment by March, while the other had a code freeze that blocked environment setup until April. The leads negotiated a resolution with us managing the process.
The investment in preparation pays off in commitment
Building the strawman drafts from intake data took roughly four hours of preparation; the session itself took ninety minutes. The return was a roadmap with three committed owners who had challenged and rebuilt it before execution began. When the program lead referenced it in subsequent weeks, the workstream leads engaged with it because they recognized their own work. The red-pen corrections were in the final version, and the sequencing they had argued about was the sequencing the program followed. For any consulting team facilitating cross-functional planning, the lesson is straightforward: bring something concrete enough to challenge and let the room do the rebuilding.
