Introduction
Autonomy Principle 04 2 min

Being stuck is a decision

The symptom

You are waiting on an access, an answer, or a decision. The work has stopped, and you are waiting.

The signal

Separate what you can look up yourself, the help you need, and the decision that belongs to someone else. Then act on all three.

What’s going on

Staying stuck without saying so is a decision: the decision to let the deadline slip. Nobody can clear a blockage they cannot see.

Many blockages clear in twenty minutes: documentation, an old case, an example, an AI that knows the tool. Others need help right away. In an incident, or in front of an irreversible action, go to the competent person without waiting.

A precise request gets a fast answer: the intended result, the point where you are stuck, what you checked, the effect on the deadline. A vague request gets a question back, and one more day. And when you are the one asked, answer fast, without requiring a search time first.

When you have to wait, say until when, and move something else forward in the meantime. If nobody answers, get the commitment reduced or the deadline moved, rather than letting the date fall silently.

Check this

On a current blockage, write:

I’m trying to … I’m stuck on … I checked … I’m missing … The effect on the deadline is …

Send it today to someone who can help or point you. Set the moment you will take stock again.

At that moment, check whether the blockage is cleared, whether other help is needed, or whether the commitment has to change.

To discuss

Which blockage is waiting today for a ruling nobody has asked for?

Your notes

Only you read them.