Portrait of Asbjorn Bjaanes
Asbjorn Bjaanes

Articles ·

If You Keep Prioritizing the Urgent, You Will Never Get to the Important

Transforming from a feature factory to resilience and scale

Many of you will recognize the story of the teacher and the jar. He filled it with sand, then pebbles, then tried to force in big marbles, and of course they wouldn’t fit. So she started over, marbles first, then pebbles, then sand, and everything settled into place perfectly. The marbles are the important things. The sand and pebbles are the urgent, lower value things that expand to fill whatever space we give them.

This is exactly what happens in software and product development. Most teams I’ve worked with start from a place where urgent work consumes everything, and more urgent work keeps arriving. Ask why, and the answer is always the same, we don’t have time, we need more resources. But if you only ever serve the urgent, you never reach the important, the genuinely value adding work. The problem is, more resources rarely fix this, because urgent work has a way of expanding to consume whatever capacity you give it. The problem usually isn’t a lack of hands, it’s a lack of protected space.

Start with honest allocation

Start with deliberate capacity allocation. Split your team’s time into three buckets: value added work, housekeeping (things like refactoring, maintenance, and performance improvements), and genuinely urgent work (critical defects and time sensitive fixes).

But don’t assume some ideal ratio, like eighty percent value and twenty percent everything else, is where you should start. If an organization is carrying heavy technical debt or a large backlog of urgent commitments, treat this like a financial recovery plan. Just as someone in debt might need a larger down payment for a while before they can increase spending again, a team may need to allocate more capacity to urgent work and debt burn down at first, gradually shifting the balance toward value as the pressure eases.

Action point: before you touch your backlog, get honest about how deep the hole is, and set your starting ratio accordingly, not aspirationally.

Making it stick requires courage

Leaders need to be told upfront, before the work even begins, that there will be a painful period where the urgent pile hasn’t shrunk yet even though you’ve already pulled capacity away from it. That’s precisely the moment discipline matters most, because the instinct will be to abandon the plan and go back to firefighting.

Action point: agree on the plan and the expected pain, before you start, so that when the dip comes, everyone can point back to what was agreed rather than negotiating fresh in a moment of panic.

Build a shield

This is also why strong middle management, or Scrum Masters if you’re using that framework, matter so much. They act as a shield, absorbing pressure from stakeholders and customers so engineers aren’t pulled directly into the chaos and pushed off the plan. If leadership or customers have direct, unfiltered access to engineers during this period, the whole thing tends to collapse.

Action point: invest deliberately in that middle layer, train them, back them publicly, and make it clear that redirecting urgent requests through the process is their job, not a failure of responsiveness.

But be honest about the precondition here. This shield only holds if senior leadership has visibly committed to defending it in the specific moment someone tries to go around it, not just in principle, in the room, when a VP escalates past the Scrum Master to lean on an engineer directly. In organizations without much cross departmental trust, this is often the hardest part of the whole approach, harder than the framework, harder than the math. If a Scrum Master says no once and gets overruled, everyone learns instantly that the shield was theater, and the old habits come rushing back. So this isn’t a one time investment, it’s a standing commitment that has to be tested and honored repeatedly before people believe it’s real.

Two audiences, two kinds of proof

Belief doesn’t change through good intentions alone, especially among executives who are measured quarter to quarter. When the pain hits, and it will, customer satisfaction or delivery numbers may dip for a period, and the people closest to that pain, team leads, engineers, need real coaching and change management support to hold steady. Senior leadership, further from daily operations, needs something different, constant transparency and a steady stream of small, tangible wins translated into language they trust, reduced churn, cost savings, measurable delivery gains.

Action point: set up a lightweight, recurring update, weekly or biweekly, that shows leadership one or two hard numbers moving in the right direction, even if they’re small. Momentum, made visible, is what buys you the runway to keep going.

Nest your frameworks inside the allocation

Underneath all of this sits a simple mechanical truth, the eighty-twenty rule. Most value comes from a small fraction of effort, so protecting that fraction is what allows the marbles story to compound over time into genuinely excellent products and durable customer loyalty.

Once you have your buckets, nest your prioritization frameworks inside each one rather than applying one framework across everything. Use something like RICE or weighted shortest job first within the value bucket, and a simpler, lighter framework within the housekeeping and urgent buckets. This way nothing urgent can sneak into the value lane just because it shouted the loudest, everything has to compete on its own turf, within its own allocation.

Action point: this is a very practical thing any team can implement this quarter, without waiting for organizational buy-in on the whole philosophy first.

What success actually looks like

The payoff, when it finally arrives, shows up in two places at once. In the numbers: rising velocity, falling defect rates, faster time to resolution. And in the people, a spark returning in teams who had lost motivation, now rediscovering the satisfaction of building something properly instead of endlessly patching what’s broken.

A few questions worth sitting with

Consider these questions instead:

How much technical debt is your organization actually carrying, honestly, not optimistically?

Who in your organization is currently absorbing the pressure that should be hitting a process instead?

What’s the one small, visible win you could surface to leadership this month to buy yourself a little more runway?

Put the marbles in first. The sand will always find a way to fit around them.


Written by Asbjorn Bjaanes. Also published on Substack.

Reach out