Why Your Leadership Team Can't Agree on Priorities
You held the planning meeting. You walked through the list. Everyone nodded.
Six weeks later, your operations lead is deep in a scheduling software rollout. Your sales lead is building a customer referral program. Someone else is quietly rewriting job descriptions. Each of them believes they're working on the top priority. Nothing on the list is actually finished.
It's tempting to call this a discipline problem, or a too-many-projects problem. Usually it's neither. Your team agreed on the list. They never agreed on what the list was for.
A priority list hides the decision that matters
Most priority lists are built from projects: buy the software, hire the manager, launch the program. A list of projects tells people what to do. It doesn't tell them which goal wins when two of those projects compete for the same people, money, or month.
That decision lives one level up, in the goals. And goals almost always get agreed to in a way that skips the hard part. "Grow revenue from existing customers" and "get the owner out of day-to-day operations" both sound right. Nobody argues. Nobody says which one matters more.
So each leader fills in the answer from where they sit. Sales weights revenue. Operations weights getting the owner out of scheduling. The owner weights whatever kept them up last night. Every one of them can look at the same list and come away with a different top priority, and every one of them is being reasonable.
This is a clarity gap: the team doesn't share a specific understanding of what matters most and why. It's the first of five gaps that cause change initiatives to lose momentum, and it's the one that shows up earliest. You can't own, sponsor, or reinforce a priority your team never actually agreed on.
Signs the disagreement is upstream
The arguments sound like they're about projects. They're really about goals. Watch for these:
Every goal is "important." If your goals are weighted equally, you don't have priorities. You have a list.
The same debate keeps coming back. If you've argued about the order of two projects three times, the real disagreement is about the goals behind them.
Your most important goal has nothing pushing it. It happens more often than you'd think: the goal leadership cares about most has no project that strongly moves it, while a lower-stakes goal has three.
Some projects can't be tied to any goal. They're on the list because someone started them, not because they move anything.
How to surface it before it costs you a quarter
You don't need a planning retreat. You need the trade-offs out in the open. Four steps:
1. Separate goals from projects. A goal is something that has to be true a year from now: a result, not an activity. "Reduce overtime costs" is a goal. "Buy scheduling software" is a project. Mixed lists are where most priority confusion starts.
2. Force the trade-off. Split 100 points across no more than five goals. Not evenly. If you could only hit one goal this year, it gets the most points. Two goals can tie, but spreading points evenly to be fair defeats the purpose.
3. Score every project against every goal. Ask one question each time: if we finished this project, how much closer would this goal be? Use a simple scale: no effect, some, strong, or critical. Critical means the goal fails without it, and most goals have one at most.
4. Find out whether your team would score it the same way. This is the step that matters. Your ranking is one person's view. The differences between your view and your team's are more useful. Where two leaders weight a goal 40 points apart, you've found the conversation you've been having indirectly for months.
What the scores can't tell you
A scored ranking is a starting point, not a verdict. Two limits worth naming:
It ignores capacity. Your top three projects may not fit in the same quarter, or rely on the same two people.
It can't break a close tie. If your top projects score within a few points of each other, more math won't settle it. A direct conversation with your team will.
That's the point. The goal isn't a perfect ranked list. It's making the disagreement visible while it's still cheap to resolve.
Try it on your own list
The free Project Priority Ranker walks you through all four steps in about 15 minutes. You'll get your projects ranked against your goals, a view of which goals are covered and which are exposed, and three questions to take to your team.
Once you have your results, do one of two things:
Share them with your leadership team. Ask whether they'd weight the goals the same way. Their answer tells you more than the ranking does.
Bring them to Office Hours. Bring your results, or bring two or three leaders' results, and we'll work through where they differ and what that means for your next 90 days.
