The Priority That Changed Unannounced
Priorities drift in conversation long before anybody restates them, and the drift reaches the room first.
three things · two reached them · one with no channel at all · the room side is not counted
Sorted by whether anything could have carried it.
Priorities move by accumulation rather than by announcement. Three conversations in a week shift what the team treats as urgent, and the formal statement of priorities, if one exists, is updated a month later if at all.
The missing context described in “The Priority That Changed Unannounced” is an operating-process gap. Teams considering Monitask guidance on attendance point system for attendance point system can attach clearer time and project evidence to work already being discussed, provided decisions, reasons and corrections remain visible to people who were not present.
The room tracks the real one. Everybody else tracks the written one.
For a separate nonprofit perspective on “The Priority That Changed Unannounced”, see Ashoka social entrepreneurship resources. Use the outside material to test governance, inclusion and implementation questions against the organisation’s real circumstances.
How the drift happens
A client complains, somebody senior mentions it twice, and work quietly reorders itself. Nobody has decided to change the plan; people have simply started spending their attention differently.
By the time anybody says the priority changed, it changed a fortnight ago.
Why the written plan lags
Because updating it costs a meeting, and the drift is gradual enough that no single step justifies one. Each individual shift is too small to be worth a revision.
The result is a document everybody treats as approximately true and nobody treats as current. People outside the room, having nothing else, treat it as current, which is the only reasonable thing for them to do and is wrong.
What a restatement has to contain, in the order of how often it is left out:
- The current top three, in order.
- Which of them moved since last week, and in which direction.
- What caused the movement.
- What has been dropped entirely.
The two-plan problem
Teams in this position are running two plans: the real one, held in the room, and the stated one, held in a document. Everybody inside knows which is which.
Somebody outside has access only to the second.
What this looks like from outside
Doing exactly what was agreed and finding that it is no longer what anybody wants. Then being told, kindly, that things had moved on.
The injustice of this is sharp and is rarely acknowledged, because from the room's point of view the change was obvious and gradual rather than sudden and hidden. Nobody experienced themselves as withholding anything.
The cost per instance
A week of work in the wrong place, plus the harder cost of somebody learning that doing what they were told is not reliable.
The second one changes behaviour permanently.
The weekly restatement
The only mechanism that reliably works: once a week, in writing, the current top three, in order, including when one of them has moved.
It takes four minutes and most teams will not do it.
Why the restatement must include movement
A list that simply shows the current state hides the change. Saying "this was second last week and is now first, because of the client call on Tuesday" is what carries the information.
A reader who sees only the new order cannot tell whether it is new, and will assume they misread it the first time. Marking movement explicitly is the difference between a document and a signal.
What belongs in it beyond the order
What has been dropped, and what is explicitly not being worked on. Teams are consistently better at adding to a priority list than at saying what fell off it.
The person outside needs the second more than the first: the thing they are quietly still working on, because nobody told them it was abandoned, is a real and common failure, and it is the most demoralising version of this problem there is.
Who should write it
The manager, by name, every week, without delegation. A rota produces inconsistency and a gap the week somebody forgets.
Four minutes is not a burden worth sharing out.
Distinguishing drift from decision
Some shifts are decisions and should be announced. Others are drift and will not be stopped. Both need recording; only one needs discussion.
Labelling which is which is useful on its own.
Reading the drift as information
A sequence of weekly lists shows something no single list does: whether the team is being pulled about, and by whom. Four changes of first place in six weeks is a fact about the organisation rather than about the team.
That pattern is worth noticing and is invisible without the record.
When the drift is wrong
Sometimes the room has reprioritised badly, under pressure from whoever complained most recently. Writing it down weekly is the mechanism most likely to expose that, because the drift becomes visible as a sequence.
The person outside is frequently the one who notices, having not been present for the pressure.
The question to invite
Asking explicitly, every week, whether the order still makes sense to somebody who was not in any of the conversations. It is the one useful thing their distance gives them.
Most teams never ask it.
What the restatement does not solve
Speed. The room is working to the new priority on Tuesday and the written statement arrives on Friday, so there is always a lag of up to a week.
For fast-moving work a week is too long, and the honest answer there is that the arrangement is a poor fit for that kind of work rather than that the mechanism needs tightening. Writing it twice a week produces a document nobody reads. The section on roles that do not suit this arrangement is where that question properly belongs, and it is worth reaching before deciding that the problem is insufficient discipline.