Most stuck product teams are stuck for the same few reasons. Not exotic ones. The team usually blames “capacity” or “tech debt”, buys more of both, and stays stuck. The real cause is normally one of five things, and once you name it, the fix is usually clear.
Here are the five, what each looks like from the inside, and the first move to unstick it.
1. No one actually owns the decision.
Work piles up behind a choice nobody is allowed to make. Three people each hold a third of the answer, the meeting ends with “let’s align next week”, and the build waits. This is the most common stall, and the cheapest to fix. Name a single decision-maker for the thing that is stuck. Give them the context and a deadline. A decision made on Thursday beats a better one made never.
2. The brief is too vague to build.
If the brief is “improve the dashboard” or “use the data we collect”, the team cannot start, so they stall politely. A good brief names the problem, the user, and what “done” looks like. We wrote a whole post on this: how to write a brief that actually gets built. One of our own engagements began as “find the leaks” and only moved once it became “predict the leaks before they happen”. Same data. A buildable sentence, and the reframe that went on to unlock £1.75 million of funding.
3. Too much is in flight at once.
Five half-finished things ship nothing. One finished thing ships. Teams stall because everything is “in progress” and nothing is “done”, so momentum never compounds. Cut the work in progress hard. Pick the one outcome that matters most this month, finish it, then take the next. Slower on paper, faster in practice.
4. The roadmap is one nobody reads.
A roadmap that needs a meeting to explain is not doing its job. If a busy, non-technical reader cannot understand it on a Friday afternoon, the team cannot align around it, so they drift back to whatever is loudest. Rewrite it in plain English, one line per item, ordered by what matters. If you cannot, that is the signal: the thinking is not finished yet.
5. Senior attention shows up once a week.
Plenty of teams have a senior product person on a call every Monday and then alone all week. The hard calls land between calls, so they wait, or get made by whoever is nearest. This is the layered-consultancy model, and it stalls real work. The fix is senior help that sits in the team and does the work, not one that reviews it from a distance. That is the whole idea behind Help.
How to tell which one you have.
Ask the team one question: “What are we waiting on?” The answer points straight at the pattern:
- “A decision” points to 1, no one owns the decision.
- “Clarity on what they want” points to 2, the brief is too vague.
- “We’re spread thin” points to 3, too much in flight.
- “We’re not sure what’s next” points to 4, the roadmap nobody reads.
- “Someone senior to just call it” points to 5, senior attention only weekly.
The team almost always knows. They are rarely asked plainly.
Honest caveat, because we always give one. Sometimes delivery is slow for a real, unglamorous reason: the work is genuinely hard, the system is genuinely old, the team is genuinely too small. No reframing fixes that, and anyone who says otherwise is selling something. But in our experience that is the minority. Most stalls are one of the five above, hiding behind a story about capacity.
If you are not sure which one you have, that is a fine place to start. Naming the pattern is most of the fix.
Stuck is a position, not a personality. Most teams get moving again faster than they expect, once they stop fixing the wrong thing.
Want a read on what is actually stuck? Talk to us.