The challenge
Traditional governance is built for consensus, not challenge.
None of this is a failure of the people in the room. It is what happens when a small group, short of time, is asked to judge something one of them proposed.
Cognitive bias
A board of people who think alike reaches agreement quickly and confidently, and the confidence is the problem. Homogeneous teams build echo chambers, and conviction starts to stand in for evidence.
Variable rigour
Papers arrive late and the agenda runs long, so the scrutiny a proposal gets depends on when it was taken. Dissent voiced in the room rarely survives into the minutes.
Hidden conflicts
Generalists assess specialist domains, and the person who championed the last strategy is asked to weigh the alternative to it fairly.
The difference
Scrutiny that works the same way every time.
The value is not that it is quick. It is that the same rigour is applied to the ninth proposal of the quarter as to the first.
Independent first, adversarial second
Every member forms a position in isolation, before seeing anyone else’s. Only then do they argue, and the challenge stage presses hardest on the positions held most confidently with the least evidence behind them. Consensus reached in that order means something; consensus reached in a room rarely does.
The whole submission, every time
A board pack too long for a single prompt is read in passes until all of it has been read, and the record says how many parts it took and how many were covered. Not a summary of a summary: every page reaches the board, and the meeting can prove it.
The world outside the organisation
A brief on current conditions is fetched each day from named sources, dated to the day each figure was observed, and put in front of the board alongside your own context. Anything more than a week old is withheld rather than presented as current.
A record that can be defended
Every position, every change of mind and every point of dissent is kept, with the models, papers and prompts that produced them. A year from now the report can still say what informed it.
The board
Perspectives, chosen for the question.
Each member is built from a corpus of what that person has actually written, said and decided, so they argue from principles rather than from a caricature. Seat the ones the decision needs, or add your own.
Business
- Warren Buffett
- Jeff Bezos
- Indra Nooyi
- Mary Barra
Strategy
- Ray Dalio
- Christine Lagarde
- Jacinda Ardern
Technology
- Sheryl Sandberg
- Fei-Fei Li
How a meeting runs
Nine stages, in an order that matters.
You can watch it happen, and step in when the board asks you something. Or leave it and read the report.
- 01PutThe submission. Papers, a question, and what your organisation is for.
- 02PutThe questions. A long proposal is broken into the decisions inside it. You confirm them before anything runs.
- 03PutThe board. Choose who sits. Each member brings a corpus, not a caricature.
- 04ScrutiniseIndependent review. Every member forms a position alone, with reasoning and a stated confidence.
- 05ScrutiniseDebate. Positions meet each other. Members say plainly what would change their minds.
- 06ScrutiniseChallenge. The weakest and most contested positions are pressed hardest.
- 07ConcludeThe floor. The board asks you what it could not work out. You answer, or skip.
- 08ConcludeThe decision. Recommendations, dissent, assumptions, and the evidence still missing.
- 09ConcludeThe record. A chair’s report, minutes and the full transcript, as PDF, Word or Markdown.
Your material
It stays yours.
Separated at the database
One organisation cannot reach another’s meetings, papers or board knowledge. That is enforced by the database itself, not by the application asking politely.
Private by default
A meeting is yours until you share it with a colleague or your organisation. Papers are encrypted with a key held for your organisation alone.
We cannot read it either
Our own administrators can see that a meeting ran and what it cost. They cannot open it, and no setting on our side changes that.