7 min read · 1,432 words
At a glance
- The first Decision Review carries three decisions, not eight. Each one shows up as a three-path model with a dollar number, a named defender, and a date.
- The meeting resolves; it does not discuss. If a decision cannot resolve in the room, the math was not ready, and it goes back to the function with a date.
- Expect a surprise in meeting one: half the decisions you thought were live are already made, unsigned. The third meeting is the one that compounds.
Who is in the room?
Sixty minutes, five people or fewer, three decisions, three resolutions. That is the whole spec for the first Decision Review, and most of the ways to blow it up are ways of violating one of those four numbers.
Start with the five people. The room is the CEO, the finance lead, and the named defenders of the paths on the table. That is it. Not the whole exec team, not the chief of staff taking notes, not the VP who would like context. The Decision Review is not a leadership meeting; presence is earned by owning a number. If the mid-market GTM call is on the agenda, the person defending the Keep math is in the room. If the head of product has no number on any of the three decisions, the head of product gets the register afterward, not a chair.
This feels harsh the first time and turns out to be the kindest rule in the system. Meetings where attendance signals status produce discussion. Meetings where attendance means defending a dollar figure produce resolution. Everyone invited knows exactly why they are there, and everyone not invited knows exactly what would earn the seat: a name next to a number.
What are the three things to get right?
The first meeting succeeds or fails on three disciplines. Each one has a failure shadow, and the failure shadow is always more comfortable than the discipline.
- Bring three decisions to the room, not eight. Pick the three the company cannot push past this quarter. Everything else gets scheduled, not solved. The instinct is to load the backlog, because the backlog is real and the stall has been accumulating unresolved calls for a year. Resist it. Eight decisions in sixty minutes is a status meeting wearing a new name; each call gets seven minutes of reaction instead of fifteen minutes of math. Three is not a starter quantity you graduate from. Three is the operating capacity of a room that actually resolves things.
- Bring the math, not the slide. Every decision shows up as a three-path model: Keep, Kill, Restructure. Each path has a dollar number. Each number has a defender (a name) and a date. No narrative deck, no context section, no appendix. The model is the artifact, and it is one page per decision, in the shape we laid out in the one-page decision slide every board should see. If a path’s number is soft, the page says whose it is and when it firms up. A named soft number is workable. An anonymous confident number is how meetings get blown up.
- Bring the resolution, not the discussion. Walk out with three resolved decisions. If a decision cannot resolve in the meeting, the math was not ready. Send it back to the function. This is the discipline that feels most brutal and matters most: the meeting is not where thinking happens, it is where finished thinking gets ratified. Sending a decision back is not a failure of the meeting. It is the system catching unfinished math before the company spends real dollars on it, and the defender knows exactly what to bring next time.
How do the sixty minutes run?
The agenda is fixed, and the chair (the CEO, in the first few meetings) defends the clock more than the content.
- Minutes 0 to 5: register check. Prior resolutions get read, not reopened. In meeting one this takes ninety seconds because the register is empty.
- Minutes 5 to 50: three decision blocks of fifteen minutes each. The defender states the three paths and the dollars in three minutes, flat. Seven minutes of pressure on the math: what breaks each number, what was assumed, what firms up when. Five minutes to resolve: the room picks a path, or the chair sends it back with a named gap and a return date.
- Minutes 50 to 60: write it down. The register entries get drafted in the room, out loud, before anyone leaves. What gets written in the last ten minutes is the entire output of the meeting.
The three-minute statement is worth rehearsing. Defenders want to narrate context; the model already is the context. The chair’s most used sentence in meeting one is “what’s the number on that path?”
What gets written down?
One Decision Register entry per resolved call, six lines: the decision in one sentence, the path chosen, the dollar consequence, the owner, the date the result gets checked, and the condition that would reopen it. That last line does the most work over time. “Reopen if enterprise pipeline is below $2M on August 1” means the decision is closed against moods and open to facts, which is the entire point of the register.
Sent-back decisions get an entry too: the named gap, who owes the math, and the meeting it returns to. Nothing leaves the room unwritten. A Decision Review without a register is a conversation, and conversations are what the company was already having.
What are the two failure modes?
The first is drift into status update. By week two, a defender opens with progress: the pipeline review went well, the team is energized, the analysis is under way. The chair has to cut this in the first meeting or it becomes the format. The fix is the same sentence every time: what are the three paths and the numbers? Status is what the rest of the calendar is for.
The second is relitigating a resolved decision. Someone arrives at meeting two wanting to reopen the GTM call because the weekend felt bad. The register is the defense: the entry names the one condition that reopens the decision, and a new mood is not a new fact. The chair reads the reopen condition out loud and moves on. Hold this line twice and it stops being tested; lose it once and every resolution the system produces becomes provisional.
What changes by meeting three?
Meeting one teaches you something almost every time: half the decisions you thought were live are actually already made, unsigned. The company decided months ago; nobody wrote it down or attached a dollar figure, so the call kept circling the leadership meeting as if it were open. The other half are blocked on math that does not exist yet, which is why they never resolved, no matter how many times they were discussed. Meeting one mostly converts ghost decisions into signed ones and unbuilt math into assignments.
Meeting two is mechanical. The sent-back math comes home, the register gets its first real check, and the room starts pre-building three-path models without being asked, because everyone now knows what the chair will request.
The third meeting is the one that compounds. Decisions start arriving smaller and earlier, before they calcify into quarter-blocking stalls. The register starts doing the remembering, so resolved calls stay resolved and the meeting spends zero minutes on the past. We don’t audit the past. We justify each next call. By meeting three that sentence is no longer a slogan; it is the standing agenda.
What is the Decisive Finance role in this?
The hard part of meeting one is not the format. It is the math, because the three-path models on the stuck calls usually do not exist yet. The 14-day Decision Diagnostic builds them: the three decisions that matter, modeled as Keep, Kill, Restructure with dollars under each path, ready to defend. Guaranteed 3x your Diagnostic fee in recoverable value, in 14 days. Typical 5x to 10x. Most clients run their first Decision Review in the same week the Diagnostic lands.
Where to go from here
If three decisions have circled your leadership meeting for more than a quarter, the first Decision Review is overdue.
Read the guarantee Book the call
Related reading: