How I close a high-stakes decision in one session
One session sounds like a gimmick. Right up until you see what we refuse to leave the room without.
When I tell founders we close brand, product and growth decisions in a single session, I get a very polite version of "sure you do, mate." Fair enough. It does sound like the kind of promise that evaporates the second a real, messy, six-figure decision walks in.
Well here's the actual method. Not the ‘magic’. The mechanics. And why the one-session rule is the thing that makes it work, not the thing that breaks it.
The instinct with a big decision is to give it room. A discovery phase. A few weeks of research. A tasteful series of workshops. More time, better answer, surely?
Except that's almost never what happens. The time doesn't get spent deciding. It gets spent re-litigating, waiting on calendars, and letting the loudest opinion sneak back in between sessions. A decision left open over weeks doesn't mature like a fine wine. It goes off like milk. Yuck.
The single session format means forcing function. It says: the people who need to be here are here, the information we've got is the information we're deciding with, and we are not leaving with the question still open. That constraint does most of the heavy lifting, because deferral suddenly has nowhere to hide.
A good session is mostly won before it starts. It comes down to two things.
The right people, and only the right people. Everyone who can veto the decision needs to be in the room. Everyone who can't needs to not be. The fastest way to guarantee a decision reopens is to make it without someone who has the power to overturn it. The fastest way to stall one is to stuff the room with people whose job is to have opinions, but not to own the outcome. Sometimes this means a small group, sometimes it’s just me and you (the Decider).
The real question, written down. Most decisions turn up fuzzy. "What do we do about positioning?" That's not a decision, that's a topic. Before the session, we sharpen it into aquestion you can actually answer, with a choice at the end of it. Something like: "Do we commit to the SMB segment as our primary market for the next 12 months, or stay horizontal?" That, you can decide. A topic, you can only discuss. Forever.
Three things, in order. Theorder matters.
First, we agree what we're optimising for. This is the step everyone wants to skip, and the one that really decides everything. Until the room agrees on the single thing this call is meant to serve, every option looks defensible, because everyone's secretly scoring against a different goal. Most arguments that look like they're about the options are actually about the criteria.
Before: "We need this to feel more premium."
After: "We're optimising for winning enterprise clients, not retention. That's the only thing this redesign needs to do."
Surface the criteria, and half the row just evaporates.
Second, we put the real trade-offs on the table. Not a tidy list of options with the "right" one pre-baked and lightly disguised. The honest version: what each path costs, what it kills off, what has to be true for it to work, and what you'd be betting your ISA on.
Before: "Option B is the stronger long-term play."
After: "Option B buys us scale. It also costs us four months of feature freeze, and it only works if our lead engineer stays through the migration."
A decision made without seeing the cost of the road not taken isn't a decision. It's a preference that hasn't met reality yet.
Third, we make the call. Out loud. With an owner. Not "we're leaning towards." Not "let's go away and mull it over."
Before: "I think we're all roughly aligned on pushing the date back."
After: "We're delaying to the 15th. Sarah owns it. If we're not ready, we ship as-is."
The room has to feel that small, healthy flicker of discomfort that comes with commitment. If everyone leaves comfortable, you didn't decide anything. You had a lovely chat about deciding.
This is the part that makes it stick.
You don't leave with notes and good intentions. You leave with a Decision Proof™: a single, bespoke artefact that captures the call, the reasoning behind it, the trade-offs you weighed, and what happens next. It's built to be defensible to the person who wasn't incthe room. The board member. The new hire. The agency partner. The stakeholder who'll inevitably appear three months later asking "remind me why we decided this?"
That artefact is the whole game. A decision that only exists in people's heads reopens the moment results dip or a louder voice arrives. A decision that exists as a thing you can point at can't quietly drift. Someone has to deliberately reopen it, in the open, with a reason. That's the difference between advice (easy to ignore) and proof (you have to actually argue with it).
Depending on the decision, the Proof takes different shapes. A Direction Snapshot that brings rival strategies to life. An Experience Blueprint showing how the call reshapes the product. A Risk Map exposing the assumptions you're betting on. A Growth Path showing how it compounds. Different decision, different artefact, same job every time: make the choice real, visible, and properly hard to unpick.
The alternative isn't "a better decision, made more slowly." The alternative is the same decision made never. Circled for a quarter. Half-made in a Slack thread at 11pm. Reopened every time someone senior missed the meeting.
One good session beats ten of those, at a fraction of the cost. Not because fast is the goal, but because the speed is a symptom of having a frame, the right people, and a flat refusal toleave with the question open.
That's it. No magic. A sharp question, the right room, agreed criteria, honest trade-offs, a call with anowner, and an artefact that makes it stick. The hard part was never the method. The hard part is committing to a process that won't let you wriggle out. Which is precisely why most decisions never get one.
