~ 500 words | ~ 3 minute read
Early in a project’s life, when priorities are still forming and the path forward isn’t fully clear, there’s a quiet temptation to treat everything as equally important.
It’s an understandable instinct. Leaders want to demonstrate momentum. Teams want to show they’re moving. And in the absence of clear signals about what matters most, the safest move often feels like treating all work with the same urgency.
The logic is reasonable: we don’t yet know what will matter later, so we’ll treat everything as if it might.
But this approach quietly undermines itself. When nothing is allowed to be more important than anything else, the capacity to focus dissolves.
When everything carries equal urgency, attention fragments. Teams spread thin. The work that genuinely needs deep thinking, careful sequencing, or early resolution gets the same shallow treatment as everything else.
Over time, this creates a kind of strategic exhaustion. The team is working hard, but without direction.
How priorities get flattened early
Priority flattening doesn’t usually happen through a single decision. It accumulates gradually, often under pressure that feels entirely reasonable at the time.
A project kicks off with high visibility. Leadership wants confidence that things are moving. So the team starts multiple workstreams at once, not because sequencing doesn’t matter, but because starting everything feels safer than choosing.
Dependencies get acknowledged but not prioritized. Risks are identified but not ranked. Decisions that could clarify the path forward get deferred because leadership doesn’t yet feel pressure to choose.
The result is a portfolio of work where everything is “important” and nothing is clearly more important than anything else.
For a while, this can feel manageable. Teams are busy. Status updates show progress across the board. Leadership sees activity and interprets it as momentum.
But underneath, something costly is happening.
Why “everything matters” is a dangerous default
When all work carries the same weight, a few quiet problems begin to emerge.
First, work that genuinely requires early focus gets treated the same as work that could wait. Clarifying ownership, resolving design decisions, and aligning on tradeoffs don’t receive the attention they need—even though these are the items that determine whether everything else can move forward.
Second, teams lose the ability to sequence intelligently. Without clear priority signals, starting order becomes arbitrary. But in complex work, sequence almost always matters. Some decisions unlock others. Some workstreams depend on clarity that hasn’t been built yet. When urgency is flattened, those dependencies remain hidden.
Third, capacity becomes a constraint faster than it should. When teams try to move everything forward simultaneously, they spread effort across too many fronts. Progress slows. Coordination overhead increases. The work that could have moved quickly with focus instead drags because attention is divided.
What started as an attempt to keep options open quietly becomes a barrier to making progress.
The downstream cost
The real cost of treating all work as equally urgent shows up later, often weeks or months into execution, when the team realizes they’ve been moving without a center of gravity.
Risks that should have been addressed early remain unresolved because they didn’t feel more urgent than anything else. Decisions that could have been made months ago now feel late. Work that could have been sequenced deliberately is now being renegotiated under time pressure.
By the time urgency becomes real, the team has already spent down much of its capacity, credibility, and slack. The ability to maneuver has narrowed. What could have been managed calmly now feels reactive.
This is the hidden cost of flattening priorities early: the team consumes the time and capacity it would have needed to address problems calmly.
What strong leaders do differently
Strong leaders resist the urge to treat all work as equally urgent, even when clarity is still forming.
They don’t wait for perfect information to decide what deserves focus. They make early calls about sequencing, knowing those calls can be adjusted as the work evolves.
They clarify (early and often) which decisions need to be made now versus which can wait. They protect their teams’ capacity to focus by refusing to start everything at once.
This doesn’t mean ignoring important work. It means recognizing that treating everything as urgent is itself a choice—and often the wrong one.
The discipline is in choosing what matters most before urgency makes that choice for you.
Want more like this?
If you’re responsible for guiding complex work, setting direction, and being accountable for outcomes, you can subscribe to receive occasional insights on project leadership and delivery.
Thoughtful notes. Practical ideas. Unsubscribe anytime.
Interested in taking this further?
If you’re responsible for the success of critical initiatives — or you’re developing the project leadership skills to support them — I’d be glad to connect.