The method

Five moves.
One direction.

Each move has a job. Each job creates an output you can point at. No output means you haven’t moved — you’ve had another chat. Most stuck situations need one or two, done properly. The rest follows.

V
Move one
Visualise & Align

Make the decision visible enough that everyone is arguing about the same thing.

Not harmony. Not a mission statement. A sentence that would still make sense outside the meeting. Big, safe-sounding words — customer, strategy, value, risk — let everyone sound serious without becoming specific. This is the move that stops those words doing the hiding.

You’re forcing the room to choose a sentence with edges. One that has a subject, a boundary, and a purpose that could be forwarded to someone who wasn’t there.

“What are we actually deciding today? If we leave without a decision, what are we choosing by default?”
→ Output: Decision Sentence
Try this on Monday
In your next meeting going in circles: ask what you’re deciding, specifically. Write the answer in one sentence. If three people give three different answers, you haven’t aligned — you’ve politely misunderstood.
O
Move two
Own the Obstacles

Surface what’s making this feel unsafe. Turn blockers into conditions.

The obstacles are rarely technical. They are usually pride, scar tissue, fear of blame, or a need to win. This is not therapy. It’s the practical act of surfacing what’s making this feel unsafe and turning it into something the room can work with.

Constraints become conditions. Conditions are workable. Fog is not. Once a blocker is named as a condition — “if we cover off X properly, we’re good to move” — the room shifts from defence to design.

“When you say risk — which risk, specifically? If we handled that properly, we’d be good to move. Yes?”
→ Output: Conditions to Proceed
Try this on Monday
Next time someone says “we can’t”: ask which constraint, specifically. Then: if we met that condition properly, could we proceed? You’re not looking for enthusiasm. You’re looking for a nod that carries responsibility.
L
Move three
Launch & Learn

The smallest step that creates real evidence. Not a pilot programme. A proof point.

A decision without a proof plan is still only half-born. It exists socially, not operationally. It survives only as long as the attendees remember it the same way — which, as experience shows, is not long.

Launch means starting something real enough to create evidence. Learn means not mistaking enthusiasm for proof. The proof plan has four parts: what you’re producing, who owns it, when it’s due, and what decision the room makes when it sees it.

“What’s the smallest thing we can produce this week that proves the approach is real? One name on it, one date.”
→ Output: Proof Plan
Try this on Monday
Before the meeting ends: what are we leaving with? One proof step, one owner, one date. If nobody owns it, it doesn’t exist. It’s just atmosphere.
T
Move four
Track & Tune

A cadence that keeps momentum without heroics. Without it, every meeting starts from scratch.

Track & Tune is not status theatre. It is a rhythm that turns proof points into momentum — and makes relitigation harder, because there is always a visible loop coming where decisions land.

The cadence runs on three questions, weekly: what shipped, what did we learn, what decision do we need? Not what was worked on. Not what was progressed. Shipped. Evidence the room can see.

“What shipped since last time? What are we shipping next? What decision do we need to protect momentum?”
→ Output: Decision Cadence
Try this on Monday
Set one weekly question with your team. Not a status update — a decision loop. Three questions, thirty minutes. If someone answers “what shipped?” with “we had loads of meetings” — stop and diagnose.
S
Move five
Story & Spark

Give the decision a shape it can survive in. The meeting after the meeting is coming.

A decision made in a room is not the same as a decision that holds. Once the meeting ends, the story starts mutating. Someone says “they’ve cut scope.” Someone else says “it’s a delay.” A third forwards a note starting with “concerns were raised” — technically true, completely wrong in spirit.

Story & Spark is not performance. It is narrative control. The test: can someone explain the decision accurately to their boss after the meeting, without improvising? If not, you’re in trouble. Improvisation is where programmes go to die.

“We’re doing this so we can ship the core outcome, prove it works, and protect the value. If we try to carry everything at once, we’ll ship complexity instead of value.”
→ Output: Story That Travels
Try this on Monday
After your next key meeting: send a five-line note within an hour. Decision. Why. What’s parked. Next proof and date. The ask. That note is cheaper insurance than any governance process you’ll ever run.

Want to run this?

Training, facilitation, and delivery support for teams who need the work to move.

Work with Matthew →