A Goal Is Not a Priority

A list of outcomes tells people what to hit. It does not tell them what to choose. That is the job a priority does.

Pull up your enterprise priorities and read them the way a new leader would.

Grow revenue. Expand margin. Improve customer retention. Rebuild the platform.

Every one of those matters. The first three are goals. The fourth sounds more like an initiative. None of them is yet a priority, because none tells the organization what it is choosing or what it will give up.

The difference

A goal is a result you intend to reach. It can be measured, and it should be.

A priority is the choice you make to reach it, including what you will not do along the way.

“Expand margin” is a goal. “Exit the two lowest-margin product lines and move their engineering capacity to the platform rebuild” is a priority. The first tells the organization where to end up. The second tells it how to get there and what it is giving up.

Goals are not the problem. They define the result. The scoreboard tells you whether you are getting there. The problem is a priority list made only of goals.

The distinction sounds academic until you watch what happens without it. Hand a leadership team a list of goals and every function writes its own route. Sales expands margin through pricing. Operations cuts cost. Product pushes premium features. Each route is reasonable. They compete for the same people, the same capital, and the same leadership attention, and nobody has made the call between them.

That is one way three stated priorities become nineteen in practice. The list stayed short. The choices underneath it multiplied.

Why repeating them does not help

When priorities are not landing, the natural response is to communicate them more.

In one large study of strategy execution, only 55 percent of middle managers could name even one of their company's top five priorities (Sull, Homkes and Sull, Harvard Business Review, 2015).

Repetition is not the fix. A list that forces no choices is hard to hold onto, however often it is repeated. A choice that moved people and money is harder to miss, because everyone felt it.

What it looks like when it works

The test is not whether the priorities are written down. It has two parts.

Same words. Ask five leaders, separately, to name the enterprise priorities. If you hear five versions, you do not yet have enterprise priorities. You have five interpretations.

A visible consequence. Then ask each of them to point to one thing that happened because of a priority: a decision made, a budget moved, an initiative stopped. If they name the same priorities and can point to nothing, the priorities are on display rather than in use.

When both parts hold, something else changes. Trade-offs stop being settled by whoever escalates hardest. They get settled against the priority, and people can see why.

Enterprise first, then function

Enterprise priorities are not a menu for each function to choose from. They are the frame every function works inside.

That does not mean every function carries the same list. Functions may carry different priorities, or contribute differently to the same one. What each must be able to show is which enterprise priority its own choices serve. A functional priority that serves none of them is local optimization, however well it is executed.

Think of it as translation, not replication. The enterprise sets the direction. Each function works out what that direction requires of it, and where it will need something from another function to get there.

Locked, not frozen

Priorities that change every time pressure arrives are not priorities. They are the latest urgent thing.

Locked means the list holds between defined review points. New work does not get added alongside it. It replaces something, or it waits. A quarterly review is a common starting point for revisiting the list, adjusted to the business cycle.

Frozen would be a mistake. Performance data and the frictions that keep resurfacing are exactly the evidence that should reopen a priority. The discipline is not refusing to change. It is changing on purpose, at a set point, for a stated reason.

The working number is still no more than three, as a default rather than a rule. A simpler business may need fewer, and a more complex one may justify a fourth. Never add a priority to avoid making a trade-off.

Why this comes first

Focus is the first of the five disciplines because the other four are built on it.

Without locked priorities, decision rights can default to functional interest. The scoreboard can fill with whatever is easiest to report. Meetings lose a basis for deciding what deserves attention. Frictions pile up with no enterprise filter to sort them.

Priorities alone do not execute, though. Focus without Decide produces debate without resolution. The team agrees on what matters and still has no one who makes the call when two priorities compete for the same resources. That is the subject of the next article.

Try this now

Take your current enterprise priority list. Next to each item, write G or P.

• G if it is a result: something you will measure.

• P if it is a choice: something you will do, with something given up to do it.

For every G, write the choice underneath it. What will we do to get there? What will we stop, delay, or do less well to fund it?

If you cannot write the second half, the choice has not been made yet. Someone further down the organization is making it for you.

A goal tells the organization where to go. A priority tells it what to give up to get there.

Roger Young is the founder of Excel Leadership Group, which develops leaders and builds the systems that help leadership teams execute.