Key takeaways
- Owner dependency is not the same as a busy owner. It exists where work or decisions cannot proceed correctly without that specific person.
- Measure five dimensions separately: decision authority, recurring work, relationship concentration, evidence visibility and exception ownership.
- Documents solve recall; they do not prove transfer. A successor must use the evidence on real normal and exceptional cases.
- Do not turn an operational diagnostic into a valuation conclusion. Relationship and leadership risk may remain even after processes improve.
A busy owner is not automatically an indispensable owner
An owner may choose to sell, supervise jobs or speak with customers without being an operating bottleneck. Dependence appears when the team cannot reproduce the right result, does not know who may decide, or cannot recover an exception unless that one person intervenes.
That distinction matters. “Delegate more” is too vague to act on, and an hours-worked score can punish a hands-on owner whose team still has clear authority and evidence. Diagnose the point of interruption instead.
| Dimension | Observable sign | Evidence of transfer |
|---|---|---|
| Decision authority | Routine work waits for an owner approval or unwritten threshold | Named successor limits tested on a live case |
| Recurring work | The owner starts, sequences or finishes a process from memory | A successor completes normal and imperfect cases from a current contract |
| Relationships | A customer, supplier or employee accepts context or commitments only from the owner | Successor handles a live interaction with explicit authority and shared history |
| Evidence and visibility | Inputs, promises or decisions sit in private messages and memory | Source records and the decision trail are findable and verifiable |
| Exception ownership | Anything unusual gets forwarded to the owner | Named owner, response clock, fallback and verified closure for each exception type |
Run a bounded absence test instead of guessing
- 01Choose one normal operating cycleHuman approvalTwo weeks is a useful diagnostic window for many weekly processes, but not a universal duration. Choose a period that actually contains the work you want to test and does not create unsafe customer or business risk.
- 02Define stop conditionsHuman approvalName the situations that require immediate owner or accountable-executive involvement. The test is controlled observation, not abandonment.
- 03Route ordinary work to successorsTriggerUse named accounts and current procedures. Preserve a queue of every question, delay, correction and missing permission instead of solving it invisibly in private chat.
- 04Classify each interruptionCodeMark whether the gap was authority, procedure, relationship context, source evidence, an exception route or an actual leadership decision that should remain human.
- 05Retest one repaired processHuman approvalUpdate the procedure or authority, then repeat a real or safely simulated case. A document edit alone is not proof of transfer.
FEMA continuity guidance uses a much broader public-sector context, yet the underlying disciplines are useful here: identify essential functions, delegations of authority, vital records and the people equipped to carry the work. An acquisition handover should make those elements concrete at process level.
Documentation fixes memory; real cases expose judgment
A procedure can state the normal route perfectly and still fail on Tuesday's awkward case. Owners often explain an exception only after seeing the customer history, the technician note or the supplier response. Capture the correction beside that case: what evidence changed the path, who was allowed to decide and what result confirmed the issue was closed.
This is where SOP automation becomes useful. Stable clauses can become fixed checks. Ambiguous interpretation can stay bounded. A pricing departure, contract commitment or other consequential decision remains with the accountable person even if evidence collection is automated.
A simulated diagnosis keeps the dimensions separate
Northline is a fictional service company. During a planned owner absence, dispatch continues and routine jobs close. That means workload transfer is better than the team expected.
Three problems remain. A long-standing commercial customer refuses a schedule change until the owner confirms it. Two invoices wait because nobody knows whether a missing photograph is an absolute stop. An urgent callback bounces between managers because the escalation threshold and response clock were never assigned.
One overall “readiness score” would blur the result. Northline has moderate recurring-work dependence, high relationship and authority dependence, and high exception-ownership dependence. Its first backlog is a successor customer introduction, a billing-evidence decision table and an urgent-callback escalation contract.
Fix the interruption in the order the evidence suggests
- Name the process and the exact interrupted case, rather than launching a company-wide documentation project.
- Assign authority and an exception fallback before optimizing the steps. A better SOP cannot grant someone permission to decide.
- Observe enough real cases to capture normal work and meaningful variation.
- Write the process contract and link it to source evidence, examples and the record of final effect.
- Reverse-shadow with the successor in control, then run an agreed owner-unavailable test.
- Only after transfer works, decide which stable steps should become code and which human gates remain permanent.
The free owner-dependency assessment applies this model and exports the first three observation actions. The seller handover checklist tracks the resulting transfer.
Limitations and when not to use this
- This framework measures observable operating dependence. It is not a valuation, saleability, due-diligence, continuity certification or key-person risk opinion.
- Software and documentation cannot remove every relationship, leadership or accountable-judgment dependency.
- The Northline case is simulated and contains no customer, product-outcome or connector claim.
- Design an absence test with the accountable owner. Do not withhold required leadership, approvals or emergency response merely to complete a diagnostic.
Sources
- Continuity Guidance Circular 1 — FEMA Accessed 5 August 2026
- Contingency Planning Guide for Federal Information Systems — NIST Accessed 5 August 2026
- The Great Ownership Transfer: A new era of business stewardship — McKinsey Institute for Economic Mobility Accessed 5 August 2026
Run the owner-dependency assessment
Translate the diagnosis into three concrete processes to observe and transfer first.
Run the owner-dependency assessmentUli Prantz
Builds and operates all-agents
Uli Prantz builds all-agents, the process-automation platform this site documents. He writes about the operational side of automating recurring business work: where deterministic code beats model judgment, where it does not, and where a human still has to approve.