Everything Is Priority One: Leading a Team That Has Stopped Choosing

Eleven active workstreams. A team of nine. Every Monday the status board is green, every Friday something slips, and when you ask which of the eleven actually matters most, the room goes quiet — or worse, everyone answers differently.

Priority sprawl rarely announces itself as a crisis. It looks like a hardworking, agreeable team that keeps missing dates for reasons that all sound legitimate. Nobody is loafing. Nobody is fighting. The work is simply spread so thin that everything is most of the way done and nothing is finished — and the people carrying it are starting to feel like they are failing at a job they are actually doing well.

The instinct is to treat this as an execution problem: better project tracking, tighter standups, a new tool. In my experience, it is almost always a leadership problem wearing an execution costume. The team stopped choosing because choosing was never really theirs to do—and because it wasn't being done above them either.

Start with what you actually said yes to

The first move in the Rawe Adaptive Leadership Framework is diagnosis before prescription, and here the diagnosis is unusually concrete. Before anyone re-prioritizes anything, we build a single inventory of every commitment currently in flight: what it is, who owns the outcome, who asked for it, and what it is supposed to change. Not a status report. A commitment audit.

Three things usually surface. A meaningful share of the list is orphaned — work that outlived the reason it started. Another share has an owner for the tasks but nobody who owns whether it succeeds. And a surprising number of items were never formally added at all; they entered through a hallway conversation, a client escalation, or a well-meant yes in a meeting where the cost was invisible.

That last category matters most. You cannot ask a team to prioritize a list they have never seen in full, and until that list exists on one page, every prioritization conversation is really several people arguing about different lists.

Change the leadership habit that keeps growing the list

Re-ranking the work feels productive, but if nothing changes about how items get added, the list regrows within a quarter. The habit that has to change is almost always the leader's, and it is a small one: saying yes without saying what moves.

"Yes, and" is how sprawl happens. "Yes, instead of" is how focus happens. It is one word of difference, and it is uncomfortable, because instead of means naming the thing that will now be late, thin, or not done at all — and naming it to someone who will be disappointed.

This is where the adaptive part of the framework earns its name. Some teams need the tradeoff written down — a visible ranking everyone can point to. Others need something blunter: the leader publicly retiring three initiatives and absorbing the fallout without asking the team to justify it first. Which approach fits depends on how your team already makes decisions, not on what a framework prefers. But the underlying mechanic is constant. People do not learn that no is allowed from a policy. They learn it by watching a leader pay the price of one, once, in the open.

Give focus somewhere to live

The final step is the least glamorous, and it determines whether any of this survives contact with a busy quarter. Focus needs a home inside the operating rhythm you already run, not a new ceremony bolted on beside it.

Usually that means one standing slot — monthly is enough for most teams — where the commitment list is re-ranked and the bottom of it is retired rather than quietly carried forward. And one rule governing entry: nothing joins the list without naming what it displaces. Not a debate every time. Just a sentence.

The second-order effect is the one leaders tend to appreciate most: escalation gets cheaper. When the tradeoff is a normal, expected part of adding work, a manager who is underwater no longer has to build a case or risk looking uncommitted. They point at the list. That is a much easier conversation to have early — which is the only time it is genuinely useful.

If your team is busy and stuck

If the scene at the top of this post felt uncomfortably familiar — green boards, slipping dates, capable people working hard and finishing little — the problem is probably not capacity, and it is almost certainly not commitment. Nobody has been given the authority, visibility, or example required to choose.

That is fixable, and it usually moves faster than leaders expect once the list is on one page. If you would like to talk through what this would look like inside your organization, I would welcome the conversation. Reach out through the contact page and we can start with what is actually on your team's list today.