Moving from concept to execution when the team is stuck.
There's a specific kind of stuck that doesn't look like stuck.
The team is busy. The meetings are happening. The decks are being updated. On paper, the project is moving.
But if you asked anyone in the room what are we actually building this quarter, and why, you'd get four different answers. Politely worded, all reasonable, none the same.
That's the version of stuck I get called into most often. Not paralysis. Motion without direction.
Why teams get here
It's rarely about capability. The people are usually good. What tends to happen is one of three things:
· The concept was agreed at the wrong altitude. Everyone signed off on a one-liner that sounded right in the room, but no one pressure-tested what it actually meant when you tried to build it. Two months in, execution reveals the ambiguity.
· The people who agreed aren't the people executing. Leadership aligned. The team who has to do the work wasn't in the conversation, so they're now interpreting a decision they didn't help make.
· The concept quietly evolved and no one re-anchored. Every meeting nudged it slightly. Six weeks later, the version people are executing against isn't the version anyone would defend if asked.
All three feel like execution problems. None of them are. They're clarity problems that only show up at execution time.
The move that actually unblocks it
The instinct, when a team is stuck, is to add process. More stand-ups. More project management. A new tool. Sometimes a reorg.
Almost none of that helps, because the problem isn't coordination. It's that the thing being coordinated has never been made concrete enough to point at.
The move that works is smaller and slower than it looks:
Get the team in one room. Put the concept on a wall. Draw it.
Not describe it. Not deck it. Draw it — as a diagram, a flow, a picture, a scaffolding on a board. Something everyone can walk up to and edit.
Two things happen when you do this:
The disagreements that were hiding in the language surface immediately, because you can't draw an ambiguous line. Someone has to say "wait, that arrow doesn't go there", and now the misalignment is on the wall instead of in people's heads.
Once the picture is agreed, everyone leaves with the same reference. Not a doc that gets skimmed. A picture they can recall. That shared reference is what execution actually runs on.
This isn't a workshop trick. It's the mechanism. Ideas that stay in words stay negotiable. Ideas that get drawn become load-bearing.
What "drawing it" actually looks like
You don't need a designer for this. You need a wall, a marker, and someone willing to hold the pen while the team argues.
A few shapes that tend to work:
· A flow — for anything with a before, during, and after. Useful when the team disagrees on sequence.
· A map — for anything with parts that relate to each other. Useful when the team disagrees on scope.
· A stack — for anything with layers of abstraction (goal → strategy → tactic → task). Useful when leadership and execution are talking past each other.
· A theory of change — for anything trying to produce an outcome in the world. Useful when the team can't agree on what "done" looks like.
The specific shape matters less than the act of drawing it together. The moment the picture is on the wall, the team stops arguing about the concept and starts working on the same thing.
What you don't need to do
You don't need to redo strategy. You don't need to bring in a new consultant to re-analyse the market. You don't need a new deck.
The strategy is almost always fine. The team is almost always capable. The gap is the picture in between — the scaffolding that lets everyone see the same thing when they look up from their own screen.
Build that once, and the execution unclogs on its own.
When it's worth bringing in someone external
If the team has been stuck for more than a few weeks, it's often hard to draw the picture from inside — because everyone in the room is part of why it hasn't been drawn yet. That's usually when I get the call.
A neutral facilitator doesn't bring more strategy. They bring a pen, a structure, and enough distance to ask the questions no one internal can ask without stepping on someone.
If that sounds like your team right now, let's talk.