Pull up this year’s plan. The one from the January offsite, the one everyone nodded at. Now count the priorities.
If it’s like most plans I see, you’ll need both hands. Growth, but also margin. The new market, but also the core product. Hiring, but also culture. Each one defensible. Each one genuinely important. The document reads like ambition, which is why it survived the meeting.
Here’s the uncomfortable part. A list of ten priorities isn’t a strategy. It’s a to-do list wearing ambition’s clothes. And you won’t see the cost at the offsite. You’ll see it on an ordinary Tuesday.
Where the list goes to collide
Priorities don’t fail in planning. They fail in small collisions nobody sees. A customer escalation lands the same afternoon the roadmap work was supposed to start. Your best engineer can serve the launch or the reliability push, not both. The budget has room for one more hire, and two teams have a case.
At each of those moments, someone has to choose. And because the plan lists ten things without ranking them, the plan goes silent exactly when it’s needed. So the choosing slides downhill. It lands on whoever is standing closest to the collision, usually the person under the most pressure that day, usually with the least context and the least authority to decide. They pick whatever is loudest, or safest, or whoever asked last. Then they brace for the follow-up question.
Multiply that by every team, every week. That’s the invisible system. I keep seeing the same scene: the plan is on the wall, and the real deciding happens three levels below it, made by tired people, on instinct, in the moment. You never decided not to choose. You just deferred the choice, and it got made anyway, hundreds of times, by people who never wanted the job.
This is why goal problems are almost never ambition problems. Your ten priorities are plenty ambitious. They’re choice problems, deferred. The list is where a decision went to hide.
The tie-break is the strategy
Here’s the move, and it’s smaller than you’d like. Pick one team. Leave their list alone. Then answer one question in writing: when two of these goals collide on a Tuesday afternoon, which one wins?
Not “which is most important.” Importance is abstract, and everything on your list clears that bar. The question is about collisions. When the launch and the reliability work want the same person in the same week, which one gets her? When a deal wants a discount that hurts margin, which goal bends? Write the answer down before the collision, not during it.
Every time I sit with a leadership team and ask this, the room goes quiet. Ten priorities were easy to agree on. One winner is hard. That difficulty is the tell. You’re finally doing the choosing the list was built to avoid.
The written tie-break is the actual strategy. The list describes everything you’d love to see happen. The tie-break describes what you’re willing to give up, and that’s the only part that steers. A goal that never wins a tie isn’t a goal. It’s a hope with a font size.
What changes on Tuesday
The first thing you’ll notice is speed. Collisions that used to escalate, or sit in a channel for two days, resolve in minutes, because the rule already exists. People stop booking meetings whose real agenda is “which thing do you actually want.”
The second thing is quieter and matters more. The pressure comes off your people. When the choosing was informal, every collision was personal risk: pick wrong and it reads as bad judgment. With the tie-break written down, picking becomes execution instead of exposure. Your team can commit hard to one thing without privately hedging against the other nine. That’s where the energy comes back. Not from a bigger vision. From a smaller doubt.
Performance follows the same line. Work compounds when it points one way for a while. Ten priorities pointing everywhere means every week is a fresh negotiation, and negotiation is the most expensive thing your company does invisibly.
You’ll be tempted to soften it. To add “it depends” or “use judgment.” Notice what that does: it takes the choice you just made and hands it straight back to the Tuesday. The tie-break doesn’t replace judgment. It protects it, by spending it on the rare exception instead of the weekly collision. Exceptions can still come to you. They should. That’s how you find out whether you named the right winner.
A list is what you want. A tie-break is what you’ve decided. Your company runs on the second one whether you write it down or not. So write it down, for one team, this week. If you can’t name the goal that wins, you haven’t set ten priorities. You’ve set zero, and hired everyone else to discover that one collision at a time.