Getting Unstuck

Every team gets stuck. It's not a failure - it's information. The question isn't whether you'll get stuck, but how fast you recognize it and what you do next.

After coaching 50+ teams through stalled deliveries, blocked decisions, and that vague "something is off" feeling, I've found that most stuck teams are solving the comfortable problem instead of the real one. This framework helps you orient honestly and get to the right intervention fast.

Before anything else: orient honestly

Stop and answer one question - not the version you'd tell a stakeholder, but the one you'd share with a trusted peer at 5pm on a Friday.

What's actually happening right now?

Write down two things:

• Point A - Where we actually are. Describe the honest current state.
• Point B - What "unstuck" looks like. Not a deliverable - an outcome. Not "ship the feature" but "users can complete the workflow without calling support."

If you can't articulate Point B as an outcome rather than an output, that's diagnostic. You may be stuck because the team hasn't agreed on what success actually means.

Four kinds of stuck

Most stuck teams fall into one of four categories. The intervention for each is different, and applying the wrong one wastes time.

1. Decision paralysis

What it looks like: The team can't converge on a direction. Stakeholders won't commit. Everything is priority number one. Meetings end without resolution.

What to try:

• Time-box the decision. "We're deciding by Thursday. The default if we don't decide is Option B." Deadlines with defaults force commitment.
• Separate reversible from irreversible. Most decisions are two-way doors. Ask: "What would it take to undo this?" If the answer is reasonable, just pick one and learn.
• Make the cost of indecision visible. Calculate what a week of delay costs in team time, opportunity cost, or customer impact. Put a dollar figure on it.

2. Delivery slowdown

What it looks like: Stories linger. Standups feel repetitive. "Almost done" is the default status. The team is busy but not shipping.

What to try:

• Walk the board right to left. Start from "done" and work backward. What's closest to shipping? Focus there first. Starting from the left creates new work-in-progress without finishing anything. (For a deeper investigation, run a full delivery diagnostic.)
• Look for hidden dependencies. Ask each person with a stuck story: "What's the one thing that would unblock you right now?" Often it's a 15-minute conversation that hasn't happened.
• Check story quality. If stories keep growing mid-iteration, acceptance criteria may be vague. Tighten the stories and the delivery tightens with them.

3. Organizational blockers

What it looks like: The team keeps hitting the same wall despite fixing everything within their control. Approvals take weeks. Other teams aren't available. Processes are in the way.

What to try:

• Name the system, not the symptoms. "We're blocked because the security review process takes three weeks and has no escalation path" is actionable. "We're slow" is not.
• Find the smallest escalation. Who is one level above the blocker? What would they need to hear to prioritize your request? Write that down and send it.
• Protect the team's energy. Organizational blockers erode morale fast. Be transparent about what the team controls and what they don't. Celebrate the work that's moving, even if the blocker persists.

4. The unnamed feeling

What it looks like: Nobody can point to a specific problem, but the energy is off. Retros feel flat. People are going through the motions.

What to try:

• Run a "what's weighing on you?" round. In a 1:1 or small group, ask everyone to name one thing that's taking up mental bandwidth - work or otherwise. Often the real blocker is something nobody has said out loud.
• Check for misaligned expectations. Ask each discipline (product, design, engineering) what they think the team's top priority is. If the answers diverge, that's your problem - you may not be operating as a balanced team.
• Look at sustainable pace. Teams that have been sprinting for too long lose the ability to self-diagnose. Sometimes the intervention is simply protecting space to breathe.

A real example: the wall that wasn't theirs

At the U.S. Space Force, I coached a software division stuck in the textbook "organizational blocker" pattern. Every team was diligently fixing what it controlled, cleaner backlogs, tighter stories, faster standups, and still nothing reached production. MVPs took six months. The honest Point A was bleak. Point B was simple to say and felt impossible: an app reaches production on a predictable cadence.

The intervention that worked was the unglamorous one from the list above: name the system, not the symptoms. The real blocker was a single production-approval gate, Operational Acceptance, that no app had ever passed. Every team optimizing its own velocity was polishing a car with no road out of the garage. So instead of speeding up a dozen teams, we found the smallest escalation, coached one app all the way through that gate to set a precedent, and the wall came down for everyone behind it. Cycle time went from six months to two weeks. (Full case study.)

The lesson generalizes past that team. When a group keeps hitting the same wall despite doing everything right, the answer is almost never more effort. Stop optimizing inside the wall and go name the one constraint everyone has quietly been working around. Fix that once, and a dozen "stuck" teams turn out to have been stuck on the same single thing.

Try this today

Pick the category that feels closest to your situation and try one intervention this week. You can also run through the interactive Get Unstuck tool for a guided version. If nothing quite fits, start with the honest orientation exercise. Writing down Point A and Point B takes five minutes and often reveals more than a two-hour retro.

The goal isn't to solve everything at once - it's to move from "we're stuck" to "we're stuck on this specific thing, and here's what we're trying next."