Where your say ends
The decision you could have made
Four of nine decisions on the record had more room than the person assumed. Nothing visible happened in any of them, which is exactly why they are worth counting.
Decisions this page is about, and where the line actually was
Changing the wording on a customer-facing error message
4 → 1It had been yours all along
Refunding a customer under fifty pounds
3 → 1A written policy you had never been shown
Rescheduling the weekly review
2 → 2Hiring a contractor for two days
5 → 3Your own budget line covered it
Reordering your own week
4 → 1You asked twice before believing the answer
- 1Decide it alone and say nothing
- 2Decide it alone and mention it afterwards
- 3Check with one colleague first
- 4Check with the person who assigned it
- 5Needs a decision one level up
- 6Cannot be decided here at all
five decisions · four of them you had more room than you thought · one you had exactly right · the median gap was two steps on the scale
Five of the nine decisions counted on this site.
A fair pilot starts with a shared purpose and baseline; managers can open the features page before comparing the results of a new handover practice.
The wider organisational question can also be compared with resources from Personnel Today.
The error message said something slightly wrong. Changing it was a five-minute job. The person who noticed it put it on a list, raised it in the weekly call, was told to go ahead, and changed it the following week.
It had been theirs the whole time. Nobody had ever said so, and nobody said so afterwards either — they just said yes, which is what you say when somebody asks for something they are entitled to.
That exchange cost about nine days of elapsed time, two people's attention twice, and taught nobody anything. It is the most common event on this site and the hardest to see, because from every angle it looks like a small thing handled properly.
Why these never surface
They produce no artefact. There is no incident, no rework, no missed date. The only trace is a slightly longer cycle time on a task nobody was measuring.
They look like good behaviour. Checking before acting is what a conscientious person does, and from the manager's side a question is evidence of care. Nobody involved has any reason to examine it.
And they are individually tiny. Nine days on an error message is not worth a conversation. It is only visible in aggregate, which requires somebody to count, which nobody does.
What they add up to
On the record counted on this site, four of nine decisions had more room than the person assumed. The gaps were three steps, two steps, two steps and three steps on a six-step scale — which is to say, in every case, the person believed they needed somebody else and did not.
Four unnecessary escalations in a quarter, on decisions anybody remembers. The real figure is higher, because the ones nobody remembers are the ones that were resolved in a minute and forgotten.
The honest way to express the cost is not in days. It is this: a quarter of this person's decisions were made by somebody else, for no reason, and both of them experienced it as collaboration.
The four, briefly
- The error message. Thought it needed the assigner's agreement. It had always been theirs.
- A refund under fifty pounds. Thought it needed a colleague's sanity check. There was a written policy, which they had never been shown, setting the limit at two hundred.
- Hiring a contractor for two days. Thought it needed a decision one level up. Their own budget line covered it.
- Reordering their own week. Thought it needed the assigner. It did not, and they asked about this twice before believing the answer.
The last one is worth dwelling on. Being told once that something is yours is often not enough, because a single yes is ambiguous: it might mean "you did not need to ask" or it might mean "yes, on this occasion". Only the second telling resolves it.
What it looks like from the other side
It is worth putting this from the manager's view, because the manager in all four cases did nothing wrong and would be surprised to learn they were part of a pattern.
From where they sit, somebody asked a reasonable question and got a fast yes. Four such exchanges in a quarter is not a volume anybody notices. Each one took under a minute and felt like the system working: a person checked, which is better than a person not checking.
They cannot see the eleven days of hesitation before the question, or the two days of waiting after it, because neither of those appears in their inbox. The only visible artefact is a short, pleasant exchange.
So there is no signal. Nothing about four unnecessary asks looks different from four necessary ones, and managers are not in a position to tell them apart without being told.
Which means the correction has to be requested rather than offered. The question that produces it takes four seconds to answer and almost nobody asks it:
What have I checked with you that I should not have had to?
Expect a real answer. Most people can name two or three immediately, because they noticed at the time and said nothing.
What to do about your own
Look for the pattern rather than the instance. The decisions people escalate unnecessarily cluster into a few recurring kinds — small spends, customer-facing wording, scheduling, anything with a number attached.
Take the kind rather than the case to whoever can settle it, and ask for a rule rather than a ruling:
I have asked you about three refunds this quarter and you have said yes to all three. Is there an amount below which I should just do it?
That question is easy to answer, it is not a complaint, and one answer retires the whole category. It is also, from the other side, a gift: most managers would rather set a limit once than approve fifteen things.