Journal

November 17, 2026· Brad J. Henderson

Most Owners Try to Document Their Way Out of Being Indispensable

Ask an adviser how to make your business less dependent on you and you will almost always get the same prescription. Write it down. For most owner-led businesses it is the wrong diagnosis.

Most Owners Try to Document Their Way Out of Being Indispensable

Ask an adviser how to make your business less dependent on you and you will almost always get the same prescription. Write it down. Map the processes, build the operating manual, capture what lives in your head, and the business will stop needing you to run it.

I understand the appeal, because I have prescribed versions of it myself. For most owner-led businesses it is the wrong diagnosis. A business rarely depends on its owner because nobody wrote the process down. It depends on the owner because the owner has spent years, usually without noticing, teaching everyone around them to bring the hard calls back.

The Discount Every Buyer Already Knows About

John Warrillow, who built the Value Builder System, counts dependence on the owner among the eight drivers of what a business is worth, and he gives it a name that sticks: hub and spoke. When every important customer relationship, every pricing exception and every difficult decision runs through one person at the center, a buyer is not really acquiring a business. They are acquiring a job with an expensive transition attached, and they price it that way.

Most owners have heard some version of this. What happens next is where it goes wrong. The dependency gets treated as an information problem, so the remedy becomes an information project: process maps, a shared drive, a binder. Six months later the binder exists and the phone still rings, because the binder was never what anyone was waiting for.

None of this only matters at the point of sale. Most owners I work with have no plans to sell. The same dependency decides whether you can take three weeks off without the business stalling, whether it can grow past the number of decisions one person can make in a day, and what happens to the people who rely on it if you are suddenly unavailable. A buyer simply puts a price on what the owner is already living with.

What the Documentation Actually Captured

Some years ago, an old friend from my earliest days in commercial real estate asked for my help. He had spent decades building a specialist practice inside a large firm, and he wanted to develop his team and, in time, hand the leadership to his son. We worked on it together for five years.

When I wrote about that engagement in The Consistency Effect, I described what we built: standardized processes for complex transactions, documentation protocols, quality controls, clear responsibilities and performance measures. All of it was real, and by the end it was all in place.

Reading that account again, I think I put the emphasis in the wrong place. The documents were the visible output. The real work was his son. Five years of him making the calls, being asked rather than told, getting some of it wrong while the stakes were still survivable, and building the judgment that no manual could carry. The systems recorded what he had learned. They did not teach it to him. Had we handed him the same documents on the first day, the practice would still have run through his father.

Where I Have Changed My Mind

In September I wrote that the most consistent teams do not depend on consistent people, and that consistency is a design problem: make the standard visible, stop rewarding heroics, and build it so it survives the leader's absence. I still believe the design matters. I underweighted the part design cannot do.

You can design a standard so that everyone can see it. You cannot design someone into being willing to hold it when you are not there, or able to make the call it leaves open. That comes from how you lead them, over time, and it is slower than any system you could build. Owners prefer the system for exactly that reason. It feels like progress and asks very little of them personally.

Dependency Is a Set of Habits

If the dependency is not mainly an information gap, what is it? In the owner-led businesses I work with, it is usually a handful of leadership habits, each of which made sense on the day it started.

1. You answer faster than anyone can think. A question arrives and you solve it on the spot, because you can. Everyone learns that the quickest route through a problem is to bring it to you. 2. You overrule quietly. You let someone make a decision and then adjust it afterwards without much comment. They learn the decision was never really theirs. 3. You keep the relationships. The key customers, the banker and the one supplier who matters all call you, and you take the calls because you enjoy them. 4. You protect people from mistakes. You step in before a call goes wrong, which means nobody learns what a wrong call feels like while it is still cheap. 5. You keep the reasons to yourself. You make the call but rarely say why, so the next similar decision has to come back to you, because nobody else knows what you were weighing.

None of these shows up in a process map. All of them show up in a buyer's diligence, usually in the first conversation with your management team.

This is also why the documentation project feels productive and changes so little. It asks nothing of the owner except time. Changing the habits asks for something much harder: tolerating a slower answer, a different answer and occasionally a worse one, for long enough that someone else's judgment has room to grow. In my experience, that tolerance is the single best predictor of whether an owner ever becomes optional in their own business.

Where to Start Next Week

You do not need a five-year succession plan to begin. You need an honest record of what still comes to you.

1. Keep a decision log for two weeks. Write down every decision that reached you, who brought it, and why it came to you rather than being made where it started. 2. Sort each one by its real cause. For each, ask whether it came to you because nobody else had the information, or because nobody else has been allowed to make that kind of call. Expect the second list to be longer. 3. Give one decision away completely. Choose one recurring call from that second list, hand it to a named person along with the criteria you use, and agree in advance that you will not quietly overrule it. 4. Ask before you answer. When it comes back to you anyway, and it will, ask what they would do before you say what you would do. It is the same answering reflex I wrote about in October, applied to the calls that matter most. 5. Write it down after they have learned it. Let the documentation follow the development. It will be shorter, more useful, and theirs.

Expect the first month to feel worse. Answers will come more slowly, a few will be different from the ones you would have given, and one or two will be wrong. That is the cost of the transfer, and it is far smaller than the cost of discovering, at the worst possible moment, that the business has only ever had one decision maker.

My friend did not hand his practice a manual. He handed it a person who had already been making the calls for years, and the manual came along with him. That is the order that works.

Sources referenced: John Warrillow, Built to Sell and the Value Builder System; Brad J. Henderson, The Consistency Effect.

A decision log shows you two weeks. The harder question is which decisions would stall on an ordinary week if you were not there to make them.

I built a short diagnostic for that question. The Absence Test asks twenty five questions about how much of your business still runs through you, and what keeps working when you are not there. About six minutes. Your answers stay in your browser, and it ends by naming the one thing worth working on first.

https://absence.consistency-edge.com

The Newsletter

Enjoyed this?

Get the next essay in your inbox.