Every stuck project I've walked into had the same thing in common. Not a lack of budget, talent or effort. Everyone in the room was sure the goal was clear. And everyone had a slightly different goal in mind.
The sponsor wanted it faster. IT wanted it stable. The business wanted it to stop getting in the way. All three said "yes" in the same meeting, and all three meant something else.
The idea feels finished. It isn't.
An idea that lives in your head feels complete, because your head fills in the gaps for you. The moment you have to write it down, you discover the gaps. That's not a failure. That's the point. Writing forces decisions, and decisions are what move a project forward.
Three questions, one page
Before anything gets designed, specified or built, I ask a team to answer three questions. One sentence each.
1. The action. What do we actually want to do? Replace, simplify, comply, automate, stop? Pick one verb. If you need three, you have three projects.
2. The subject. Whose work changes? Not "the organisation". Name the people: the claims handler, the account manager, the screener at the counter. If nobody's day changes, nothing will.
3. The outcome. What does better look like, in a way you could check? Faster, cheaper, fewer errors, compliant by a date. "Improved experience" doesn't count. "From 45 to 20 minutes per file" does.
Do it on paper, in ten minutes
Step away from the laptop. A screen invites you to polish slides and open more tabs. A pen and a blank page force you to choose. Give it ten minutes, no more. If it takes longer, you've found exactly what's stuck.
The explain-back test
Then hand the page to someone outside the project, ideally from a different department, and ask them to explain it back to you in their own words. Don't help them.
If they get it right, you have a shared goal. If they don't, you just saved yourself months of building the wrong thing. Fix the page, not the person.
Why this works
Most projects don't stall on technology. They stall on shared understanding. Three sentences on one page won't solve everything, but they make the disagreements visible early, while they're still cheap. That's usually the moment a stuck project starts moving again.
Want to try it with your team? I run this as the first hour of every Clarity Sprint. Tell me what's stuck.