If something isn’t done done — finished, usable, delivering value — it has no commercial return yet.

You may have spent weeks on it.

You may have spent serious money on it.

You may be 80% complete.

Until it’s finished and usable, it’s worth nothing.

As you approach a release, you might deliberately reduce new feature work and focus on finishing and stabilising.
If features are largely done, you might stop pulling new work entirely and focus on security, performance, or hardening.

The important part is that the selection can change, without needing to change the underlying priorities.
That’s almost impossible when everything is forced into a single ranked list across very different demand streams.

With a clear selection policy, you can adapt what you pull into the team based on proximity, risk, and context, while keeping strategic intent stable.

Most teams don’t struggle because they can’t prioritise.

They struggle because they’re trying to prioritise everything against everything else.

New features.
Fixes.
Technical debt.
Security.
Operational work.
Support.

Instead of loading a fixed amount of work because the calendar says so, I encourage teams to decide how much work makes sense right now. That might be an hour’s worth, a few days, or sometimes longer. The point is that it’s value bound and flow bound, not time boxed.

When that work finishes, you pull in more.
If it takes longer than expected, you wait.
The system adapts without panic.

Most teams don’t have a capacity problem.

They have an intake problem.

Too much work is pulled in, too far ahead, and delivery starts to feel jumpy and reactive.

Capacity isn’t about how busy everyone is.
It’s about how much work the system can absorb and finish without choking.

Saying no isn’t difficult because people don’t understand priority. It’s difficult because saying no forces trade offs into the open. It makes assumptions visible and exposes the fact that not all demands can be honoured at the same time.

When teams struggle to say no, it’s often because those trade offs haven’t been made explicit.

Most teams don’t have a prioritisation problem.
They have a problem making decisions.

Now, most interaction is intentional. Meetings are scheduled. Conversations have agendas. Decisions are discussed in neat, focused slots. On paper, that looks like progress.

But what I see again and again is teams losing their shared sense of what’s really going on. People are aligned in meetings, yet surprised by outcomes. Leaders feel informed, but still feel that something is off. Misunderstandings don’t show up immediately, they surface later as friction, rework, or tension between roles.

Post Covid work became more deliberate.
Delivery quietly became harder.

Teams gained focus.
They lost signal.

Less overhearing.
Less informal alignment.
Less catching problems while they were still small.

Over the last few weeks I’ve written about a few recurring delivery patterns.

Interruptions that derail focus.
Work that hangs around and starts to smell.
Teams stretched thin because too much is in play.
Leaders struggling to say no, even when they know they should.

Working with leaders, one of the hardest things they struggle with is saying no.

No to their bosses.
No to customers.
No to the next “urgent” thing that lands mid-flow.

Saying no feels uncomfortable.
It can feel like you’re blocking progress, being difficult, or letting someone down.

All teams have capacity problems.

But not because they’re under staffed.
Because they don’t control their focus.

Most teams are trying to do far more than they have the capacity for, at the same time.

Part of the problem is how we think about roles.

I often describe work that’s been hanging around too long as “smelly tickets”.

You know the ones.They’ve been open for weeks. Sometimes months.
No one quite owns them anymore, but everyone’s aware of them.

They start to go off.

Whatever company I work in, I see the same kind of interruptions.

I call them “drive-bys”.

Someone walks past your desk, metaphorically shoots you, and carries on.
You stop.
You lose the thread.
The thing you were trying to finish just got harder.

Before you start anything new, it’s worth asking a simpler question:

How much work do we already have in play?

I often see teams come back in January with good intent and clear priorities, but far too much already happening. The problem isn’t effort. It’s overload.

January always starts with good intent.

Clear goals. Fresh plans. A sense that “this year will be different”.

And then, somehow, everything starts to feel busy again.

January is already hard enough. Cold, dark, money spent, routine back with a thud. There’s a reason “Blue Monday” gets talked about this time of year, even if the science is shaky. People feel it.