Week 48 Day 5: Running the 90-Minute Roadmap Session

Three facilitation rules. First: silent brainstorming before discussion. Have the team write their priority candidates individually before any group discussion. This prevents anchoring bias -- the first idea spoken aloud becomes the reference point for all subsequent ideas. Second: the leader speaks last. Your opinion carries outsized weight. If you speak first, the team aligns to your perspective rather than thinking independently. Third: time-box ruthlessly. When the discussion drifts, bring it back: 'We have 8 minutes left for milestones. Let us focus.'

Here is the complete facilitation guide. Before the session: send the strategic context document to the team 24 hours in advance. This gives everyone time to think about the quarter ahead rather than hearing the context for the first time in the meeting. Also send this prompt: 'Come prepared with your top 2-3 priorities for the quarter. What are the most important things for us to accomplish in the next 12 weeks? Think about business impact, technical risk, and team health.' During context setting (minutes 1-10): present the context crisply. Do not read a document aloud. Hit the key points: what did we achieve last quarter, what does the business need this quarter, what constraints are we working within, and what does success look like in 12 weeks? The most common mistake is spending too long on context and eating into the priority discussion. Set a timer. During priority identification (minutes 11-30): use silent brainstorming. Give the team 3 minutes to write their priorities individually. Then go around the room -- each person shares their priorities in 60 seconds. Post them all. Then group similar items. This typically reduces 12-15 items to 6-8 clusters. Now the discussion starts. For each cluster, ask: 'What is the business impact if we accomplish this? What is the risk if we defer it?' The team discusses. Then force-rank using the 'if we could only do one thing' protocol. Watch for these failure modes during the discussion. The HiPPO effect (highest-paid person's opinion): if a senior leader or stakeholder is present, their preferences can dominate. Mitigate by having them speak last. The recency effect: the team defaults to priorities based on last week's fire rather than the quarter's most important work. Mitigate by reframing: 'Set aside what happened this week. If you are looking at the whole quarter, what matters most?' The consensus trap: the team gravitates toward priorities everyone agrees on, which are often the least controversial rather than the most important. The hardest decisions -- the ones where the team disagrees -- are usually the most valuable to resolve. During milestone definition (minutes 31-50): for each priority, ask: 'What are the checkpoints that tell us we are on track? What should be true at the 4-week mark? At the 8-week mark? At 12 weeks?' Make milestones observable and date-specific. Not 'make progress on the migration' but 'migration framework is deployed to production by week 4, 30% of services migrated by week 8, and 100% of services migrated by week 12.' During trade-off documentation (minutes 51-70): this section requires the most courage. Ask: 'What are the things we know are important but are choosing not to do this quarter?' The team will resist this question because explicitly not-doing something feels like failure. Reframe: 'The trade-off list is not a failure list. It is a strategic clarity list. It shows that we are making deliberate choices about where to invest our limited time rather than pretending we can do everything.' During review and commit (minutes 71-90): read the roadmap aloud. The act of reading it aloud catches ambiguity that silent reading misses. Ask each team member: 'Do you commit to this plan?' Commitment is not unanimous enthusiasm. It is willingness to execute: 'Even if this was not my top choice, I understand the reasoning and I will execute against this plan fully.'

The silent brainstorming technique implements what brainstorming researchers call 'nominal group technique' (Delbecq, Van de Ven, and Gustafson, 1975) -- a method where individuals generate ideas independently before group discussion. Meta-analytic research by Mullen, Johnson, and Salas (1991) found that nominal groups (independent idea generation followed by group discussion) consistently outperformed interactive groups (traditional brainstorming) on both quantity and quality of ideas, because independent generation eliminates production blocking (waiting for others to finish speaking), evaluation apprehension (fear of judgment), and social loafing (letting others generate ideas). The leader-speaks-last rule addresses what organizational behavior researchers call 'authority gradient' (Torrance, 1955) -- the phenomenon where the opinion of the highest-status person in a discussion disproportionately influences the group's conclusions, even when the highest-status person's opinion is objectively less well-informed than lower-status members'. Research on airline cockpit communication (Helmreich, Merritt, and Wilhelm, 1999) found that reducing the authority gradient -- encouraging lower-status members to speak first -- reduced decision errors by 40% because it ensured that all available information was surfaced before the highest-status opinion anchored the discussion. The 'commit' ritual at the end implements what management researchers call 'disagree and commit' (a principle often attributed to Bezos, 2016, but rooted in Eisenhardt, Kahwajy, and Bourgeois, 1997, research on 'how management teams can have a good fight'). Their research found that high-performing teams maintained both high conflict (during the decision process) and high commitment (after the decision was made), because the explicit commitment ritual converted debate energy into execution energy.