Strategic shift (board)
When the board needs to bless or block.
Strategic shifts brought to a board are prone to a specific failure: the board defers to the founder's narrative in the room, then second-guesses it over email afterward. Asking each director to commit privately to their validating and invalidating metric first turns a blessing ceremony into a real decision with a falsifier attached.
Should the board approve the proposed strategic shift?
Each board member: the one metric that, if it moved as expected over 18 months, would validate this decision; the one that would invalidate it; and the named alternative path you would prefer if we don't take this one.
What each contributor weighs
Ask everyone to put these on the table privately, before they see another contributor's position.
- The one metric that, if it moves as projected over 18 months, validates this shift.
- The one metric that would invalidate it — your early warning.
- The named alternative path you would back if the board does not take this one.
- The governance or capital implication you are most uneasy about.
- Market expansion
- Major product reset
- M&A approach
How this decision usually goes wrong
- Rubber-stamping the founder's story without anyone naming a falsifier.
- Anchoring on the most senior director's first reaction.
- Approving the direction without agreeing on what would prove it wrong.
- Confusing enthusiasm for the founder with conviction in the plan.
How to run this decision in 48 hours
- Open a room seeded with the question above. Set a 48-hour deadline.
- Paste the opening context — keep it short. Engineers will not read more than 300 words.
- Invite by email. Each contributor submits position + reasoning + risks privately, before seeing anyone else.
- Read the synthesis. Claude maps consensus, dissent, blind spots, and confidence.
- Decide and log. The synthesis is the decision-log entry — no separate write-up.
A synthesis that records each director's validating and invalidating metric, the alternative paths considered, and a clear read on whether the board is genuinely aligned or politely acquiescing.
Related reading
- Why every distributed engineering team needs a decision log
- Async vs sync engineering decisions: how to choose