There is a point in every technology team's journey when the number of “urgent” things starts exceeding the number of hours available in the day.
A production issue needs attention. A business team needs a new feature. A campaign is approaching. A vendor needs a decision. Security has an observation. Someone wants a report. A senior stakeholder has another request.
And somehow, everything is labelled priority.
I have experienced this many times in technology leadership.
The difficult part is not necessarily the volume of work. The real challenge is deciding what deserves attention first.
Because when everything becomes a priority, the team eventually loses the ability to distinguish between what is important, what is urgent, and what is simply demanding attention.
The priority trap
Early in my career, I often believed that being a good technology professional meant trying to accommodate as many requests as possible.
A stakeholder asks → we respond.
A business requirement comes → we start working.
An issue is escalated → we immediately shift focus.
It feels productive.
But there is a hidden cost.
Every time a team changes direction, there is context switching. When several priorities compete simultaneously, people may be working hard but making very little meaningful progress.
The team becomes busy.
But the business outcome doesn't necessarily improve.
That is when I started looking at prioritisation differently.
Prioritisation is not only about deciding what we will do. It is also about deciding what we will not do right now.
Not every urgent request is a business priority
One of the most useful questions I have learned to ask is:
“What happens to the business if we don't do this now?”
The answer often changes the conversation.
If a production issue is affecting customers or revenue, it may need immediate attention.
If a regulatory or security requirement has a deadline, it may have a clear priority.
If a campaign is approaching and a particular technology dependency can directly affect its success, that deserves attention.
But a request that has simply been marked urgent does not automatically become the highest priority.
There is a difference between urgency and impact.
A loud request is not necessarily an important request.
Priority should have a reason
When I discuss priorities with teams or stakeholders, I try to connect the request to a business outcome.
- Does it protect revenue?
- Does it affect customers?
- Does it reduce significant operational risk?
- Does it support an important business commitment?
- Does it unblock other critical work?
- Is there a genuine deadline?
- What happens if we postpone it?
These questions help move the conversation from “Who asked first?” to “What creates the greatest business impact?”
That is a much healthier way to manage technology delivery.
Technology teams need permission to say “not now”
This is perhaps one of the hardest lessons in technology leadership.
Saying “no” is difficult.
But sometimes the correct answer isn't “no”. It is:
“Not now. Here is why, and here is when we can take it up.”
There is a big difference.
A technology leader should not create unnecessary barriers between technology and business. At the same time, continuously accepting new priorities without considering existing commitments eventually hurts both sides.
A team that says yes to everything may initially look highly responsive. Over time, it may become unpredictable.
A team that clearly communicates its priorities can become much more dependable.
The role of a technology leader
As technology leaders, our responsibility is not simply to distribute tasks among people.
It is to create clarity.
When the team has ten things competing for attention, someone needs to help answer:
What are the three things that matter most right now?
That doesn't mean the remaining seven things are unimportant. It means they have to wait.
This requires understanding the business context, technical dependencies, risks, available capacity and expected outcomes.
It also requires communicating the decision clearly.
Because prioritisation without communication creates confusion.
Priorities also change
A priority list is not a permanent document.
Business conditions change. A production incident can suddenly become the highest priority. A campaign can move dates. A dependency can get delayed. A new business requirement can emerge. A security concern can change the risk equation.
Good prioritisation therefore requires continuous reassessment, not just creating a list at the beginning of a sprint or project.
The question should regularly be:
“Is this still the most important thing for us to be working on?”
Sometimes the right leadership decision is to continue. Sometimes it is to stop. And sometimes it is to change direction.
The team needs focus more than pressure
Technology teams generally don't need another person reminding them that everything is urgent.
They need clarity.
They need to understand:
- What are we trying to achieve?
- Why does it matter?
- What comes first?
- What can wait?
- What does success look like?
- Who owns the decision?
When these things are clear, teams can work with much greater confidence.
And when priorities are constantly changing without explanation, even highly capable teams can struggle.
Focus is a productivity tool.
What I believe today
I have come to believe that one of the most valuable things a technology leader can provide is clarity of priorities.
Not more meetings.
Not more dashboards.
Not more escalation.
Not more pressure.
Clarity.
Because technology delivery is ultimately not about how many tickets a team closes or how many features it releases.
It is about whether the technology work is helping the organisation move toward the outcomes that matter.
So when the next request arrives and someone says, “This is urgent.”
It may be worth asking one more question:
“What makes this more important than the things we have already committed to?”
That question may not always make the decision easier.
But it can make the decision clearer.
And sometimes, leadership is simply having the discipline to say:
“Yes, it is important. But it is not the priority right now.”← BACK TO LEADERSHIP INSIGHTS