When Everything Is a Priority, Your Team Decides Which Ones Are Not

Refusing to rank the list does not stop the ranking. It moves the ranking to the people with the least information about what actually matters.

You gave the unit five things for the term. All five are real, all five were promised to someone outside your team, and you did not put them in order because you could not think of one you were willing to lose. Two months in, three of them have moved and two have not. Nobody chose that in a meeting. There was no conversation where a person said the words we are going to let this one slip. It simply happened, distributed across a hundred small decisions about what to do next on an ordinary Tuesday, and you found out about it late enough that the recovery cost more than the choice would have.

The ranking got made. You just were not the one who made it, and you were not in the room.

Ranking is not optional, it is only ever delegated

Any list longer than the hours available gets sorted. That is not a cultural problem or a discipline problem, it is arithmetic, and it happens whether or not anyone has been given the authority to do it. When a leader declines to sort the list, the sorting moves to whoever is holding the work at the moment the week goes sideways, which is usually the person with the narrowest view of what the institution is going to care about in June.

That person is not making a bad decision. They are making a decision with the information they have, and the information they have is local. They know who called them this morning. They know which of the five things has someone attached to it who will follow up. They do not know that the third item is the one your dean has already mentioned twice, because you have never said so.

What people sort by when you have not

Whoever asked most recently. Recency is the cheapest available signal and it works well enough often enough that people trust it. The consequence is that your list gets reordered by the communication habits of everyone outside your unit, and the colleagues who send the most email end up setting your team's quarter.

Whatever has a person attached to it. A commitment with a name on the other end will beat a commitment to a deadline every time, because the first one produces an awkward conversation and the second one produces a line in a report. Work that matters institutionally but has no impatient human behind it is the work that quietly does not get done.

Whatever can be closed. Under pressure people finish things. Closing something small returns a measure of control, and an important task that cannot be finished this week loses to three unimportant ones that can. This is the one that hurts most, because the person doing it is working hard, visibly, on the wrong things, and nothing about their effort looks like a problem.

Sorting it yourself

Rank to a number, out loud, and put it in writing. First, second, third. If two of them genuinely cannot be separated, then say what happens when they collide at four o'clock on a Thursday, because that is the only form of ranking that survives contact with a real week. A list of five things marked as equally important is not a plan, it is a decision you have decided not to make.

Name what comes off, specifically. When something new arrives midterm, the question is not whether the team can take it on. The question is which of the five it displaces, and the answer has to be one of them by name. Adding work without naming what it pushes out is how a unit ends up with eleven priorities by April and no capacity to explain why any of them slipped.

Tell them when to reorder without you. Give the conditions. If a student issue arrives, it goes first, and I do not need to be asked. If the request comes from that office, it waits until we have talked. Then ask to hear about it afterward rather than beforehand. Most leaders who complain that their teams cannot prioritize have never told anyone what to do when the stated order stops matching the situation, which happens most weeks.

The part that is about you

Refusing to rank is often not indecision. It is a way of avoiding a conversation upward. If you put the list in order, you are saying out loud which promise you are prepared to break, and someone above you will eventually ask about the one at the bottom. Leaving the list flat keeps you from having to answer that question in advance. It also transfers the answer to a coordinator who will be the one explaining, in June, why the thing at the bottom did not happen.

The other possibility is worth sitting with. You may not actually know the order. That is a legitimate position, and it happens when direction above you has been changing faster than anyone can absorb. It is also a very different problem, and the response to it is not silence. It is to say to your team that you are working on the order, to give them a rule to use until you have one, and to go get the answer from the person who owes it to you.

Three questions

Which of your current commitments would you let slip if you had to choose one today? If you cannot answer that in a sentence, your team is answering it for you every week, and their answer is being set by whoever emailed most recently.

When something new landed on the unit this term, what came off? Name it. If nothing came off, the work did not disappear, it went into someone's evenings, and you will find out which someone when they leave.

If your newest hire had to choose between two of your priorities tomorrow afternoon with nobody available to ask, what would they pick, and would that be the choice you wanted? That question tells you whether you have communicated an order or only a list.