How to tell whether your growth team has a prioritisation problem or a capability problem

When growth stalls, the instinct is usually to add more: more channels, more experiments, more headcount, more vendors. Under pressure, it is hard to tell whether the core issue is prioritisation — doing the wrong things — or capability — not being set up to do the right things well. Getting that distinction wrong is expensive.

A prioritisation problem looks busy from the outside. Backlogs are full, standups are active, and the team can point to a long list of experiments and campaigns. Yet the work feels fragmented. There is no clear thesis about what actually moves the number. Every week introduces another “quick win” that quietly displaces the less glamorous, compounding work that never seems to get done.

Common signs:

• No shared definition of the single metric that matters for the next quarter.
• Initiatives launched because they are interesting, not because they clearly map to a constraint.
• Frequent context-switching across channels without closing the loop on what was learned.

A capability problem looks different. Here, the team may have a sensible plan but struggle to execute at the level needed. Experiments are slow to ship. Core hygiene tasks — like maintaining information architecture, content standards, or analytics quality — keep getting deferred. When new ideas arrive, there is no spare capacity to test them properly, so they are either rushed or never started.

Signs here include:

• Chronic bottlenecks in design, engineering, or content creation.
• Work that is theoretically “done” but hard to roll out at scale because standards are weak.
• Single points of failure where one person's bandwidth quietly caps what is possible.

The diagnostic move is simple but often skipped: before changing the plan or adding new inputs, sit down with the team and map work against constraints. List out the most important levers for growth over the next six to twelve months. Then mark, honestly, whether each lever is blocked primarily by confusion (we don't know what to do) or by capacity/skill (we know, but can't do it reliably yet).

If most levers are blocked by confusion, the solution is to do less — fewer bets, clearer standards, a narrower focus on the work that matters. If most are blocked by capability, the solution is to reinforce the system: better processes, clearer responsibilities, different hiring, or more deliberate use of external support.

The point is not to label a team as “good” or “bad”. It is to respect the operating model. A team with a prioritisation problem doesn't need more tools or more people. A team with a capability problem doesn't need yet another strategy workshop. Untangling the two is where calmer growth starts.