Starting a workshop from a blank page asks participants to generate ideas from nothing, which is cognitively hard and socially risky. The result is predictable: the most senior or most confident person offers a direction, and the rest of the room orients around it without engaging critically. A strawman changes the room’s task from generating to reacting, and that shift changes everything about the output.
Why Blank Pages Produce Bad Output
Proposing a workstream structure from scratch requires synthesizing the program’s scope, dependencies, and constraints into a coherent proposal in real time. That’s cognitively demanding. It also means attaching your name to an idea that others may disagree with, which carries social cost in rooms where hierarchy or cross-functional politics are in play.
The rational response is to wait for someone else to go first. The person who waits risks nothing; the person who volunteers risks being wrong in front of peers and senior leaders. In most rooms, waiting wins, which is why the blank page produces either silence or dominance by the most confident voice.
What a Strawman Changes
A strawman is a deliberately imperfect draft of whatever the session is designed to produce: a program architecture, a workstream charter, a set of milestones, a governance framework. We build it from intake interviews and stakeholder conversations. It’s informed but intentionally incomplete.
The strawman changes the room’s cognitive task. Reacting to a concrete artifact is easier than generating from nothing; the participant evaluates what’s in front of them, which takes less effort than assembling a proposal on the spot. “This workstream boundary is wrong because it splits a capability that should be managed together” is a specific, bounded critique that requires less effort than “here is how I would structure the program.”
The strawman also reduces social risk. Criticizing a document is safer than criticizing a person. When a VP marks up a strawman and says “this dependency is missing,” the critique is directed at the artifact. The same insight offered as an original proposal (e.g., “I think we have a dependency nobody has accounted for”) feels like a personal claim that can be challenged. The strawman gives the room permission to be critical without requiring anyone to stake personal credibility on an original position.
How Strawmen Level the Room
In an open-ended discussion, the people who speak are the ones with the most confidence, organizational power, or comfort with public speaking. A strawman invites a different kind of participation. Junior participants who would never volunteer an original idea in front of their VP will mark up a draft. They’ll circle a workstream boundary and write “this doesn’t reflect how our team operates” or flag a missing dependency. Designing for the quiet room means structuring exercises so every voice gets captured.
When we combine the strawman with silent writing (i.e., three minutes of individual markup before verbal discussion), the room’s full intelligence gets captured regardless of hierarchy. Every person’s annotations exist before the first word is spoken. We synthesize the markup into themes and present the range of the room’s thinking, giving equal weight to the disease area head who flagged a resource constraint and the SVP of R&D who questioned the timeline. Done well, this process turns skeptics into coauthors.
Building a Good Strawman
The quality of the strawman determines the quality of the critique it produces. A strawman that’s too polished discourages markup because the room assumes it’s been validated. A strawman that’s too rough produces confusion because the room can’t tell what it’s reacting to.
The right calibration is a draft that’s clearly structured and specifically wrong in places we expect the room to catch. The workstream boundaries should be close enough to realistic that the room engages seriously, but imperfect enough that the room has real work to do. The dependencies should include some obvious ones and miss some important ones that the room’s operational knowledge will surface.
The output of a strawman session is never the original draft. It’s the room’s version, organized by our structure, and owned by the participants because they built it through their corrections and additions. The same principle applies to content before slides and to building together in roadmap sessions: the facilitator’s structure enables the room’s substance.
