The List of Ten Priorities

Ask almost any leadership team what their priorities are and you will get a list. Usually somewhere between eight and twelve items, formatted in a slide or a document, occasionally color-coded by quarter. It is presented with conviction, and everyone nods along, because the list feels like evidence of alignment. It is not.

A list of ten things is not a set of priorities. It is a backlog with better formatting.

The word priority is singular by nature. It comes from the Latin prior, meaning first. For most of history it had no plural form, because the concept resisted one — you cannot have multiple firsts. The business world invented "priorities" as a convenience, and in doing so created one of the most reliable mechanisms for organizational drift that I have encountered.

Here is where most teams get confused, though, and where the conversation needs more precision than it usually gets. The argument against long priority lists is not an argument against complexity. A company has many functions, and those functions often run simultaneously. Sales is running plays. Recruiting is filling roles. Product is shipping. Each of those is a distinct motion, and each motion can carry its own singular priority without contradiction. If your top sales priority this quarter is closing one million dollars in net new business, that is where every sales-focused action should point. At the same time, recruiting a senior finance leader can be the priority for your people operations motion. These coexist without conflict because they operate in different lanes.

What you cannot do is give an individual, or a team operating within a single motion, a priority list of their own. A salesperson who is simultaneously responsible for closing a million dollars in SMB revenue, adding three new enterprise logos, and rebuilding the enterprise pricing strategy does not have three priorities. She has a backlog, and she is being asked to manage the triage herself because leadership has not done it for her. That is where execution breaks, quietly and consistently, until someone notices the results and wonders why.

Real prioritization is an act of subtraction, and subtraction requires courage. Every item on a priority list represents something someone cares about, and removing it means telling that person their thing matters less than someone else's thing. Most teams would rather keep the list long than have that conversation. The cost is paid downstream, by the people doing the work, who resolve the conflicts themselves in real time with incomplete information and no institutional cover.

The structure that actually works is simple: one priority per motion, clearly owned, fixed for a defined window, and protected from scope creep until that window closes. Across motions, you can have as many concurrent priorities as you have distinct functions running well. Within any single motion, if you have more than one, you have none.