The Prioritisation Problem: How to Decide What Your Team Stops Doing

The way to decide what your team stops doing is to test every active piece of work against one explicit outcome for the quarter, then formally retire anything that cannot earn its place. That decision has to be made out loud, recorded and communicated, because work that is quietly deprioritised does not actually stop. It carries on consuming attention in the background while everyone politely pretends it has gone away.

Most teams are not short of priorities. They are short of subtractions. Every reorganisation, every new stakeholder and every well-intentioned initiative adds something to the pile, and almost nothing is ever taken off it. The result is a team running at full capacity that is still somehow missing the things that matter most.

Prioritisation, done honestly, is a subtraction exercise. Ranking work from one to twenty is comfortable because nothing has to be given up. Deciding that items eleven to twenty will not happen this quarter is uncomfortable, and it is the only version that changes anything. Here is how to run that decision without wrecking morale or your stakeholder relationships.

1. Recognise That Adding Work Is a Decision Too

Most leaders treat adding a project as a low-stakes act and stopping one as a high-stakes act. It is the wrong way round. Adding work commits your team’s finite hours to something new, and those hours have to come from somewhere. The cost is entirely real. It is just invisible, because it shows up as slippage on things that were already agreed rather than as a line item in a meeting.

Watch how new work usually enters a team. Someone senior asks a question, a manager offers to look into it, and three weeks later two people are quietly building something nobody formally approved. No decision was recorded. No trade-off was named. The team simply absorbed it, and the capacity came out of work that had already been promised elsewhere.

The fix is to treat intake with the same seriousness as spend. When something new arrives, ask what it displaces. Not rhetorically, but specifically: which named piece of work moves back, and who tells the person expecting it. If nobody can answer that, the new work is not ready to start.

This single habit changes the culture faster than any framework. Once people see that saying yes carries a visible cost, they become far more careful about what they say yes to, and far more willing to back you when you decide to stop something.

2. Make the Outcome Explicit Before You Rank Anything

You cannot decide what to stop until you know what you are trying to achieve. That sounds obvious, but most teams operate with a list of objectives rather than a single outcome, and a list gives you no way to choose. If everything is a priority, every piece of work can be defended and nothing ever gets cut.

Pick one outcome for the period ahead. Not a theme and not a value, but something you could point at in twelve weeks and say clearly whether it happened. Reduce the time to onboard a new client from six weeks to three. Halve the escalation rate. Land the migration without an outage.

Then write it where the team can see it and use exactly the same wording every time you refer to it. Wording drift is how outcomes lose their teeth. Once one person says improve onboarding and another says reduce onboarding time, the two are no longer testing their work against the same standard, and both can claim to be aligned.

With one outcome in place, ranking becomes far less political. You are no longer asking whose project matters more, which is a question about people. You are asking which piece of work moves this specific number, which is a question about evidence. Those two conversations feel completely different in the room.

3. Run a Stop Review, Not a Priority Call

Book ninety minutes and list every active piece of work your team touches. Not the roadmap, the reality: the recurring reports, the standing meetings, the half-finished tooling project, the favour someone agreed to in March. Most leaders are genuinely surprised by the length of this list, because a good third of it never appeared in a plan.

Against each item, record three things. The outcome it serves, the hours it consumes in a typical month, and who would notice if it disappeared. That third column does the heavy lifting. A striking amount of recurring work has no identifiable consumer at all, because the person who originally requested it has since changed role or left.

Sort the list by hours consumed and start at the top. The instinct is to cut small things because they feel painless, but dropping five two-hour tasks buys you almost nothing. Stopping one report that quietly eats three days a month buys you real capacity, and that is what makes the exercise worth running at all.

Aim to stop something meaningful rather than several trivial things. A review that ends with the team dropping a handful of minor tasks has not changed anyone’s week. If you come out of the session without at least one uncomfortable decision, you have run a priority call, not a stop review.

4. Retire Work Properly So It Does Not Come Back

Stopped work has a habit of resurrecting itself. Somebody asks after the report, an interim manager restarts it, and within two months the team is producing it again without anyone having decided they should. Retirement needs a process, or it is just a pause with better branding.

Tell the people affected directly, before they notice. A short message naming what is stopping, why, and what they should do instead is enough. The reason matters more than the decision itself. People accept losing something when they understand the trade-off, and quietly resent it when it simply vanishes.

Record the decision somewhere durable, with the date and the rationale. When the question comes back in five months, and it will, you want to point at the reasoning rather than relitigate it from memory. This is also the best protection available when a new manager arrives and starts asking why obvious things are not being done.

Then genuinely stop. Half-stopping is the worst outcome on offer: the team still carries the mental load and the maintenance, but nobody gets the benefit of the output. If the decision is to stop, delete the calendar invite, archive the dashboard and switch off the automation.

5. Protect the Decision When Pressure Returns

The hard part is not making the decision. It is holding it three weeks later when a senior stakeholder asks why their thing is not moving. That moment is where most prioritisation quietly collapses, because the leader concedes in the room and the team absorbs the work anyway.

Prepare for it. Have the outcome, the list and the trade-off ready, and answer with a swap rather than a refusal. We can pick that up, and to do it we would move the migration back three weeks. Are you happy for me to do that? This is a far stronger position than no, because it puts the cost back where the request came from.

Most requests do not survive that question, which tells you something useful about how they were made in the first place. The ones that do survive were genuinely important, and now you have explicit cover to reorder the plan. Either way, you have avoided the silent capacity leak that makes teams unreliable.

Do this consistently for a quarter and something shifts in how your team is treated. People start pre-filtering what they bring you. Your commitments start landing when you said they would. That reliability is worth more to your standing as a leader than any individual project you might have squeezed in.

If your team is running at capacity and still missing the things that matter, the problem is usually structural rather than personal. Fully Bossed works with leaders on exactly this kind of decision-making. Take a look at our services, or get in touch to talk it through.

Frequently Asked Questions

How do I decide what my team should stop doing?

List every piece of work your team currently touches, including recurring reports and standing meetings, then record the outcome each one serves, the hours it consumes monthly, and who would notice if it disappeared. Sort by hours consumed and start at the top. Anything that does not serve your single stated outcome, and has no identifiable consumer, should be retired formally rather than quietly deprioritised.

What should I say when a stakeholder objects to work being stopped?

Answer with a trade-off rather than a refusal. Explain what the team is prioritising, say what stopping this particular work buys you, then offer the swap explicitly: you can pick their request up, and here is the named piece of work that would move back to make room. Most requests do not survive that question, and the ones that do arrive with genuine cover to reorder your plan.

How often should a team review what it is doing?

Once a quarter is enough for a full stop review, provided you also handle intake properly in between. Every time new work arrives, name what it displaces before agreeing to it. The quarterly session then catches the slow accumulation of recurring tasks that never entered a plan, which is usually where a third of a team’s hidden capacity is sitting.