Skip to content
Left to Guess All fifty notes

What autonomy needs

Who can say no, and when

The late veto is the most expensive failure in a handover, and it comes from one unsaid sentence: the name of the person with a standing view.

Decisions this page is about, and where the line actually was

What the decision wasWhere you thought it ended, and where it didSteps
123456

Picking the library for the new parser

1 → 4

The architect had a standing view

Dropping a requirement nobody had asked about in six weeks

2 → 5

A commitment made before you joined

Changing a database column type

1 → 1

Small, reversible, tested once before

Where you thought it endedWhere it actually endedLess room than you thoughtYou had it exactly right
  1. 1Decide it alone and say nothing
  2. 2Decide it alone and mention it afterwards
  3. 3Check with one colleague first
  4. 4Check with the person who assigned it
  5. 5Needs a decision one level up
  6. 6Cannot be decided here at all

three decisions · not one of them gave you more room than you thought · two gave you less · one you had exactly right · the median gap was three steps on the scale

Three of the nine decisions counted on this site.

Home / What autonomy needs

Argument

A fair pilot starts with a shared purpose and baseline; managers can visit the platform online before comparing the results of a new handover practice.

A separate professional source for this subject is MIT Sloan Management Review.

Four decisions where the person who could say no turned out to matter

What the decision wasWhere you thought it ended, and where it didSteps
123456

Picking the library for the new parser

1 → 4

The architect had a standing view nobody had mentioned

Dropping a requirement nobody had asked about in six weeks

2 → 5

It was a commitment made to a customer before you joined

Telling a customer a date

3 → 6

Dates are committed by one person here, and it is not you

Hiring a contractor for two days

5 → 3

Your own budget line covered it, and nobody had said so

Where you thought it endedWhere it actually endedMore room than you thoughtLess room than you thought
  1. 1Decide it alone and say nothing
  2. 2Decide it alone and mention it afterwards
  3. 3Check with one colleague first
  4. 4Check with the person who assigned it
  5. 5Needs a decision one level up
  6. 6Cannot be decided here at all

four decisions · one of them you had more room than you thought · three gave you less · the median gap was three steps on the scale

Four of the nine decisions counted on this site, chosen because in each the real limit was set by a person rather than a rule.

The work is finished. It is shown. Somebody who has not been mentioned once in three months says "we can't do that" and turns out to be right — not because they outrank anybody, but because they hold a standing position on this area that everybody except you already knew about.

This is the late veto, and of the four missing things it is the one that costs the most, because the cost is paid at the end, when the work already exists.

Why it is the hardest to hand over

Saying "X will object to this" feels like gossip. It names a person, it predicts their behaviour, and it sounds like a complaint about them. So people say the safe version instead — "you might want to loop in the platform team at some point" — which contains none of the information and prompts no action.

There is also a more respectable reason for the silence. Managers handing over work often believe, sincerely, that the receiver should not have to navigate personalities, and that naming the obstacle in advance would be teaching them to work around a colleague rather than with one.

The intention is good and the result is a veto in week eleven.

What to say instead

The useful sentence names the person, the area and the trigger.

The architect has a standing view on which parsing libraries we use. It is not written anywhere. If you are picking one, show them the shortlist before you build on it, not after.

That is not gossip. It is a fact about how decisions actually get made here, which is exactly the thing an autonomous person needs and cannot derive.

Three things make it safe to say:

  • Name the area, not the character. "Has a standing view on parsing libraries", not "is difficult about tooling".
  • Name the moment. Before the shortlist, not before the launch.
  • Say whether it is a veto or an opinion. These are different and the receiver cannot tell.

The four kinds of no

Not every objection has the same weight, and treating them all as vetoes is how people end up asking permission for everything.

Who What their no means When to involve them
The accountable owner It does not happen Before you commit to an approach
The standing-view holder It happens with an argument Before you build on the choice
The affected party It happens, and they are annoyed Before it lands on them
The interested observer Nothing Afterwards, if at all

The commonest error from the receiving side is treating the third and fourth as the first. That is the mechanism behind every decision on the record here where somebody had more room than they thought.

Finding out when nobody told you

Ask the person handing over, in these words: "who is likely to have a view on this, and is their view a veto?"

The phrasing matters. "Who do I need approval from" produces a process answer — a name on a form — and the people who actually stop things are rarely on forms. "Who is likely to have a view" produces the real list, because it does not sound like you are asking who outranks whom.

If that fails, the archaeology works: look at what was reverted in this area and who asked for the revert. Standing views leave traces in history even when they are never written down.

Why the late veto is so expensive

The cost is not the objection. Objections are cheap and often correct. The cost is where in the work the objection lands.

An objection in week one lands on a plan. Changing a plan costs an afternoon, nobody is attached to it, and the person objecting is helping.

The same objection in week eleven lands on something that exists. Changing it costs weeks, several other decisions were built on top of it, and the person objecting is now an obstacle — not because they have changed, but because the same sentence arrives into a different situation.

There is a social cost too, and it compounds. The receiver has spent eleven weeks and is attached to the work; the objector has a legitimate position and is being treated as an inconvenience. Both are behaving reasonably and the exchange damages the relationship anyway. A pair who have been through that twice will start routing around each other, which produces exactly the organisational silence that caused the problem.

So the value of naming the decider is not that it prevents the objection. It is that it moves the objection to the week where it costs an afternoon instead of a month, and where neither person has to be the obstacle.

And the inverse

If you are the one with the standing view, write it down.

One paragraph, where the work happens, saying what your position is and why. You will be consulted less, not more, and the things you would have vetoed will stop being built. The alternative is that your view remains a piece of oral tradition that new people discover by losing three weeks to it.