Do not lend your conviction

Entry XXXIX is usually read as a warning against overreach. Action taken beyond scope creates disorder; stay out of what is not yours. That reading is correct and it is the easy half.

The entry carries a second line that does more work: neglect can masquerade as restraint, enabling disorder through avoidance. And then the sentence that governs the whole entry. Responsibility includes what is permitted as well as what is done.

Permitted. Not performed. The things you allowed to happen are on your account too.

The case nobody writes about

The literature on handing over authority assumes one failure mode. The outgoing person cannot let go. They keep the password, they attend the meeting they are no longer in, they answer the question that was addressed to their successor. Overreach, straightforwardly, and the remedy is restraint.

This week I was in the other version of it, and I had not seen it described anywhere.

Someone is taking over work that has been mine. The pull did not run from me toward the work. It ran the other way. She offered me scope I should decline: the position of the one who decides, held open, waiting for me to step back into it. Not out of calculation. Out of the ordinary reasonableness of someone who would rather be sure than be the author of a mistake.

And the thing about being offered that is how little it resembles overreach from the inside. It feels like being asked for help by someone who deserves it, and refusing feels like withholding.

What I said, and what I had to be careful about

The distinction I set was between informing and asking.

Tell me anything. The context I hold, the history behind a decision, what was tried before and why it failed: all of that is yours for the asking and you should ask, because none of it is written down anywhere useful.

What I do not want is a call placed to borrow my conviction.

Those two calls sound identical on the surface. Both open with a question. The difference is what is wanted at the end: in the first, information that improves her judgment, and in the second, my certainty attached to her decision so that the decision stops being hers.

The second one is corrosive in both directions. She does not build the thing she needs to build, because borrowed conviction is load-bearing for exactly as long as the lender is available. And I retain authority I no longer hold, which is the overreach XXXIX names, arriving by invitation.

The part that was hardest to write

Deference is evidence.

If a decision that is hers keeps coming back to me for ratification, that is information about readiness, and it is information I would be concealing from both of us by continuing to supply the ratification. The kindness of answering is also the mechanism by which the gap stays hidden.

That is an uncomfortable thing to hold, because the generous move and the honest move point in opposite directions. Answering makes this afternoon easier. Declining makes the next six months possible.

I did not resolve it elegantly. I said the thing plainly, in writing, and accepted that it would read as colder than I meant.

The practice

Two questions, before you answer.

What is being asked for here: context or conviction? Context is history, constraint, precedent, the reason a thing is the way it is. Conviction is the answer plus your name on it. Give the first without limit. Withhold the second.

And then: if I supply this, what does not get built? If the answer is somebody's capacity to decide, the help is a cost disguised as a favour.

The operational form is narrow enough to carry. Hand over the information. Keep the decision where it now belongs.

The standard

Overreach is not only reaching. It is also accepting a reach that was offered to you.

Lending your conviction to someone who needs to build their own is a way of permitting something, and it is the version of overreach that arrives looking like generosity.

https://hoc-est-opus.com/leadership-standard/responsibility-and-stillness