A ranking rebuilt every morning is a ranking that was never built
Asked for their order of priorities, most executives will show a list. It is tidy, numbered, sometimes colour-coded. Ask the same executive a fortnight later and the order has moved. A third item has dropped off, another has climbed to the top, and nobody remembers the change as a decision. The ranking is described as something done once; in practice it is redone every morning.
The cause is not a lack of discipline. The executive rebuilds the order each day around whichever request arrives loudest, because nothing fixes it in place. What is on the list is work. What orders the list is an unwritten feeling. A feeling gives a reasonable result on a quiet day, and on a pressured day it picks whatever is closest.
The difference between a list and a rule
A list says what will be done. A rule says which of two good tasks goes first when they compete. The two are routinely confused, and an executive with a list and no rule believes they have a set of priorities. A priority order is not a to-do list; it is a sentence that says why one good task outranks another. Where that sentence has not been written, the order is renegotiated every day, and the person negotiating across the desk is usually the most persistent one.
The rule actually applied is often not the rule that gets stated
There is a plain way into this in the coaching room: we ask the executive to look back over the yeses given in the last three months. First we ask what they rank by. The answer is usually ready: customer impact, strategic fit, revenue. Then we look at the work they actually accepted.
Stated against applied
Set side by side, the two lists are often surprising. The stated rule is revenue, but most of the accepted work was accepted to protect a relationship with whoever brought it. The stated rule is strategic fit, but what moved forward was whatever could be finished fastest. None of this is a flaw. Each is a reasonable rule; the executive simply did not choose it, and applied it without noticing.
That distinction decides the next step. Once they see the rule they have been applying, there are two paths: own it and say it aloud, or decide to change it. Either way, it is the first time they have had a rule. What existed before was not a rule but the consequences of having none. Every yes is a no placed somewhere else, and here the sentence becomes something that can be analysed: the logic behind the noes can finally be read.
A priority order is not a list. It is a sentence that says why one good task outranks another.
A good rule is short, testable, and usable under pressure
The properties of a workable rule are specific, and few of them have to do with eloquence. A long rule is not remembered under pressure. An abstract rule turns, when two tasks collide, into a sentence whose beneficiary is unclear. A rule that cannot be tested is an intention, not a rule.
- It is short: one sentence, small enough to fit in a note on a phone.
- It is testable: applied to two concrete tasks, the winner is clear without argument.
- It names the cost: it says in advance who will wait, and for how long, when a task does not win.
Writing down the cost
The third property is the one most often skipped, because writing the rule is easy and writing its cost is uncomfortable. "Work that protects a customer comes before work that wins one" is a sound principle; "so the sales team's deck will wait this quarter" disappoints a particular person. A rule that names its cost becomes a choice; one that does not stays a wish.
This piece completes a point from the executive asking what to focus on. There the question was whose list it is. Here the question is what rule that list will be ordered by. The second question follows the first, and cannot be answered without it.
The rule is chosen before the pressure arrives and changes only on a schedule
The time to choose a rule is not the time it is most needed. A rule chosen under pressure becomes the justification for the loudest request of the day. A rule written on a quiet morning, with no request waiting, is an actual rule, because it has not yet worked for or against anyone.
The rule for changing the rule
Holding a rule steady does not mean it never changes. The company's situation shifts; one quarter calls for protecting, the next for growing. What matters is that when the rule may change has also been stated in advance: every three months, or after a specific event that changes the company's position. Without that, the rule bends whenever it is tested, and a rule that bends gives way under the first real pressure.
The interval also gives the executive some relief. A new request arriving mid-week no longer reopens the rule. The request is applied to it, the result is stated, and the rule itself waits for the next review. The mechanism we described in direction is not a document exercise works here at small scale: the rule exists less on paper than as a behaviour repeated every day.
From the field
Nearly every executive who comes to work on prioritisation asks for a method: a matrix, a scoring model, a particular framework. Most already have at least one on the desk. What is usually missing is not the method but a decision about what question the method is supposed to answer.
The one question for a first session
So we do not begin with a method. We ask the executive to pick one piece of work they declined or deferred last month and to say in a single sentence why. The sentence often comes with difficulty. When it does come, most find they have never said it aloud before.
Sometimes the sentence is the rule they actually apply, and they dislike it: protect relationships, close quickly, soothe whoever is loudest. Seeing that is uncomfortable, and the discomfort is the sign that the work has started. Sometimes the sentence is sound, and the executive owns it for the first time.
A priority order is not a table; it is the executive's own word. How we work begins with writing that word down. The matrix, the scoring and the frameworks come afterwards, and are useful only in its service.