Every manager eventually faces the same situation: you set the quarter's priorities two months ago, and now nothing looks like what you planned. The urgent has eaten the important. A new initiative from leadership derailed two projects. Three things that were supposed to happen in parallel are all behind.
This is not a planning failure. It's a structural problem that most teams never fix. Priorities collapse when the manager treats the list as a communication artifact instead of an operating instrument: owned, reviewed, defended, and changed only with visible tradeoffs.
The Fix: Make Priorities Real
Name a single owner for the priority list
Will Larson's advice for technical roadmaps applies here: the roadmap is not a document, it's a conversation — but someone has to own it. Same with priorities. One person is accountable for the current state of priorities, for maintaining them, and for communicating when they change.
When priorities shift — and they will — that person explains why and what the tradeoffs are. This is a governance question, not a planning question.
Define what "done" means before you start
John Doerr's OKR framework is useful here, but the specific useful practice is: before a priority is added, define success criteria. Not just "ship the feature" but "ship the feature and see X% improvement in Y metric within Z timeframe." Without this, you never know if the priority was achieved — so you never know if it was the right priority.
Create explicit triage criteria
The question "is this more important than what we're currently doing?" needs an explicit answer, not just intuition. Some teams use impact vs. effort matrices. Others use traffic light systems. What matters is not the specific framework — it's that the same framework is applied consistently, and that someone with authority is applying it. Good criteria usually include customer impact, revenue/risk exposure, reversibility, deadline reality, and what existing commitment would move.
The Problem with "Everything is Priority"
Many managers respond to priority conflicts by declaring everything a priority. This is a failure of leadership communication. It might feel safe ("I'm not choosing favorites") but it's actually negligent — because it gives the team no way to make the tradeoffs that will inevitably need to be made.
When everything is priority, nothing is priority. And the team knows it — they just quietly make the decisions themselves, without telling you.
What to Do When Leadership Changes Priorities
This is the hardest case, because the pressure is real and the answer isn't "just say no."
When a leadership request collides with an existing priority list:
- Make the tradeoffs explicit. Don't just absorb it silently. Show what the new priority displaces and for how long.
- Agree on the new list together. You're not refusing — you're updating the shared map.
- Communicate to the team why. Not "leadership said so" but "here's the reasoning and here's what we're shifting."
The script is simple and uncomfortable:
"We can take this on. It means the onboarding cleanup moves from May to June, or the reporting work loses two engineers this sprint. Which tradeoff do you want?"
This is managing up without becoming a messenger. You are not carrying executive churn down to the team as weather. You are translating it into choices, costs, and consequences — then bringing the actual decision back cleanly.
Bad version: "Leadership changed priorities. Sorry, everyone."
Better version: "The company needs the enterprise demo sooner because it unblocks the renewal. We are pausing the internal dashboard for two weeks. The cost is slower finance reporting this month; leadership has accepted that tradeoff."
The teams that handle priority changes best are the ones where everyone understands why things were prioritized in the first place — so that when things shift, the team can reason about it rather than just following the latest instruction.
Priorities that collapse at the first crisis aren't priorities. They're wish lists. Priorities are the ones you defend — or consciously trade away. The expert manager's job is not to make the team immune to change; it is to make change legible, costed, and deliberate.
