One Goal Tomorrow

The word priority is five hundred years old, and for most of that time it was only ever used in the singular.

A priority. One thing. The thing that comes before the others, from the Latin prior: before. You could not have multiple priorities any more than you could have multiple firsts. The concept itself contained a discipline: if everything matters, nothing comes first.

Somewhere in the twentieth century, organizations began pluralizing the word. Priorities became standard usage: not in the sense that multiple things matter, which is obviously true, but in the sense that multiple things can simultaneously occupy the first position. This is a logical impossibility that most organizations treat as ordinary management practice.

What we lost when we pluralized the word was the discipline the word contained.

The Calendar Test

I have asked the same question in leadership teams for fifteen years. It is a simple question, and the answers it produces are reliably revealing: if I reviewed your calendar for the last ninety days, what would it tell me was your actual top priority?

Most leaders pause at this question. Some of them laugh. A few look genuinely uncomfortable, which is usually the sign that the question has landed where: it was meant to.

Because the calendar does not lie. The calendar is what actually happened. And in most organizations, what actually happened bears a modest resemblance at best to what was said to matter most.

I look for what is scheduled at eleven in the morning on a Tuesday or Wednesday. Not eight o'clock, when obligation fills the calendar. Not four o'clock, when the day is winding down. The middle of a working day, when discretion still exists and the leader has some choice about where their attention goes.

What I find, almost universally, is that eleven in the morning belongs to operations. Status reviews. Updates on what happened last week. The urgent work of the existing business. What I almost never find is protected time for the work that the leader said mattered most.

A full calendar is not a measure of productivity. In most organizations, it is a measure of the opposite.

The Exercise

I use an exercise with leadership teams that I call One Goal Tomorrow.

The exercise is simple and the conversation it produces is almost never simple. I ask each person in the room to write down, privately, the single most important thing, not the top three, not the top five, that the organization needs to advance tomorrow. One thing. Write it down. Don't share yet.

Then I ask them to share.

In organizations with genuine alignment, the answers cluster. Not identically people describe the same thing in different language, from different angles, with different detail. But they are pointing at the same thing. When this happens, it is visible immediately, and the relief in the room is palpable. People did not realize, until that moment, that they had been carrying the same answer independently: that the shared understanding they hoped existed actually existed.

In organizations without genuine alignment: which is most organizations: the answers are distributed across four or five different things, sometimes, more. Each answer reflects a real priority in someone's domain. Each answer is defensible. And the aggregate of all of them is an organization: that cannot act with concentration on anything.

At that point, there is a choice. You can let the room negotiate toward a list: three priorities, or five, or whatever number makes everyone feel included. Or you can hold the question until the team produces a single answer.

Most groups, without facilitation, retreat to the list. The discomfort of naming a hierarchy is too immediate. The relationship cost of saying this matters more than that is too visible. A leader who is serious about organizational performance does not let the room off the hook. They hold: the question. They name what they are seeing. They say: we have just demonstrated that we do not share a common understanding of what comes first. That is the problem we are here to solve. Then they make the choice because that is what leaders are for.

Priority Theater

There is a pattern I call Priority Theater.

Priority Theater is what happens when an organization has done the prioritization work: the offsite, the OKR process, the strategic planning cycle, and produced a document that says what the priorities are. But the calendar, the budget, and the daily behavior of the senior team reflect a different set of commitments entirely.

The document says innovation is a top priority. The calendar shows that the innovation team gets an hour a month with the CEO, while operational reviews get four hours a week. The document says that the organization is committed to developing its next generation of leaders. The budget shows that the leadership development program was the first thing cut when revenue softened.

No one is lying. No one decided to make the stated priorities irrelevant. The stated priorities simply did not displace the existing commitments with enough force to actually change behavior. The old patterns persisted. The new priorities were layered on top of them. And the organization continued doing what organizations do: allocating time and money to whatever had the, most established claim on both.

Priority without cost is not priority. It is aspiration. Aspiration does not move organizations.

Priority Theater is more dangerous than having no priorities at all. When you have no stated priorities, at least everyone knows the allocation decisions are being made on the fly. When you have stated priorities that do not match actual behavior, you have added confusion to the problem, and created a performance review system that will evaluate people against goals that the organization's own calendar did not support.

Why Organizations Accumulate Instead of Discipline

There is a reason organizations accumulate priorities rather than discipline them. Choosing one thing: really choosing it, in the sense that you are naming it as what comes before the others: requires you to name what does, not come first. And naming what does not come first is politically costly.

Every item on the priority list has a sponsor. Someone fought for it in the planning process, argued for its importance, tied their credibility to its inclusion. To say this thing is the priority is, implicitly, to say that other things are not. And the people whose things are not will feel it.

So what happens, in most organizations, is a negotiation toward inclusion. Everyone's priority stays on the list. The list grows. And the discipline of genuine prioritization, which requires genuine choice, gets replaced by a document that is more a record of what the organization cares about than a commitment to what it will do first.

The most important word in a senior leader's vocabulary is not yes. It is not yet.

Not yet means: I see what you are bringing, I believe it matters, and I am asking you to hold it while we finish what we are currently doing. Not yet is honest. It is specific. It leaves the door open while protecting the threshold. Leaders who build have learned to use it.

What Genuine Priority Looks Like

An organization that has genuine priority does not look like an organization: that has stopped caring about everything else. It looks like an organization: that has identified the constraint: the thing that, if resolved, would make: the most other things easier or unnecessary.

It looks like a senior leader who can, without looking at a document, name: the one thing their organization is concentrating on this quarter and explain exactly why that thing was chosen over the alternatives. Not a prepared answer. A real answer, grounded in understanding of what is actually limiting performance.

It looks like a team that is not overwhelmed: not because the work is light, but because the work is legible. People know what matters. They know how to make tradeoffs without escalating every decision to the top. They know what comes first, which means they know what can wait.

And it looks like progress that is visible. Not immediately, and not dramatically, but measurably. When a team that was dispersed across seventeen initiatives concentrates on one, the movement on that one is different in kind, not just degree. Problems get resolved rather than managed. The team develops in the specific area that the priority requires. The organization builds something: that will still be standing when the priority is done.

Sometimes leaders are not wrong. They are early. And sometimes the right response to an initiative that keeps failing is to prepare the soil and wait for the season that can support it.

The Discipline, Maintained Over Time

One goal tomorrow. Not forever. Not to the exclusion of everything else that matters. But tomorrow, and the day after, and the quarter that follows until the thing that most needed to move has moved.

Choosing one goal: actually choosing it, in the sense that you concentrate your organization's best attention on it and protect it from displacement is not a comfortable experience. Not at first. Perhaps not ever.

The discomfort comes from several directions. From the things you said no to. From the concentration of risk: when you disperse effort across many initiatives, the failure of any single one is manageable. When you concentrate on one, what you are building is visible and the stakes of not building it well are real. And from the pace: concentrated effort on a single important goal produces, first, the disorientation of being able to see clearly what is not yet done.

Leaders who build have learned that this discomfort is the price of clarity. And clarity is the price of progress. And progress is the thing they are actually trying to produce.

The hardest leadership skill is not vision. It is not communication, or talent development, or strategic thinking. The hardest leadership skill is the willingness to choose: to say: of everything we could pursue, this is what comes first, and I am willing to say so, and to protect it, and to be accountable for the choice.

My father had a phrase he used when he was managing multiple construction projects: a site with two foundations drying simultaneously is a site where both are at risk. He broke ground on one thing at a time.

That is the discipline. And the discipline, maintained over time, is what separates the organizations that build from the organizations that merely intend to.