Chapter 11: Entrenchment and Continuity

The person no one could work without

For nine years, Daniel has run the monthly settlement process at a logistics company. He knows which data feed fails after public holidays, which customer contracts allow manual adjustment, and which finance manager must approve an exception. When a reconciliation breaks, people call Daniel. He is patient, fast, and usually right.

His importance has grown gradually. Daniel now approves changes to the process he operates, trains the people who assist him, keeps the exception guide, and advises the committee that chooses his possible successor. Several departments have asked him to document the process. He always agrees, then delays because the next close is urgent. Proposed deputies rotate out after spending months on routine tasks without learning the difficult cases.

When Daniel takes unexpected leave, settlement nearly stops. The company treats this as proof that it needs him even more. It gives him another retention payment and postpones a planned system change until his return. Daniel has not threatened anyone. He may be protecting a fragile process with too little staffing. Yet the organization has built a circle: his control creates dependence, and dependence becomes the reason to preserve his control.

Entrenchment is influence that has become difficult to examine, transfer, or replace because authority, knowledge, relationships, and process are concentrated in the same place. It can form around a founder, executive, administrator, specialist, vendor, committee, team, or software system. It is not automatically improper. Deep expertise and stable ownership often keep organizations functioning. Classic organizational research links power to the ability to manage important uncertainties and to positions within dependence structures, which helps explain why operational centrality can become influence without any formal promotion.¹²

The test is continuity: can the organization preserve legitimate service, evidence, and decision quality when a person changes role, is unavailable, disagrees, or leaves? If the answer is no, admiration for an indispensable contributor should coexist with concern about the design.

This chapter examines five patterns: accumulating decision rights, allowing one owner to control an entire process, narrowing succession through unclear criteria, concentrating history and operating knowledge, and delaying documentation, delegation, or cross-training.

Concentration is not the same as wrongdoing

A specialist may hold many responsibilities because the team is small. A crisis may require temporary command. A regulated role may need independence or exclusive authority. A confidential investigation may have a tightly limited group. A founder may reasonably make broad decisions during an organization’s early life.

Concentration becomes risky when it is hard to see, has no boundary or review, and reproduces the conditions that justify it. Ask:

• What is concentrated: formal authority, practical access, knowledge, relationships, or all four?
• Why is concentration necessary?
• What decisions require separation or independent review?
• Who can act during absence or conflict?
• How will the arrangement end or be reassessed?
• What evidence would show that distribution is now possible?

The purpose is not to remove every dependency. Organizations are networks of dependency. The purpose is to keep a valuable dependency from becoming a single point through which all correction, succession, and change must pass.

1. Accumulating decision rights

Decision rights can accumulate without a formal reorganization. A trusted specialist begins by recommending options. Because the advice is rarely challenged, colleagues start treating recommendation as approval. The specialist then controls the data needed for the recommendation, chooses who attends the review, and confirms whether the resulting action is complete.

Each step may be convenient. Together, they collapse roles that provide useful challenge. The same person defines the problem, selects the evidence, proposes the solution, authorizes it, and reports success.

Map verbs rather than titles. For a consequential process, who can:

• request work;
• set priority;
• define eligibility or scope;
• supply or restrict information;
• recommend;
• approve, reject, or stop;
• implement;
• verify;
• change the rule;
• grant an exception;
• hear a challenge;
• report the outcome?

A job description may say “process owner” while these verbs sit across several teams—or quietly sit with one person.

Separation is most important where error, self-interest, or abuse would be hard to detect and costly to correct. Payment creation and payment approval are a familiar example. So are hiring and final salary approval, system administration and access review, or sales credit and compensation calculation. Small organizations may not be able to separate every task. They can use compensating checks: a periodic independent sample, dual approval above a threshold, immutable logs, rotating review, or external assurance.

Avoid decorative separation. If a verifier sees only the evidence selected by the process owner, or an approver never has time to question a recommendation, the boxes are separate but the judgment is not. Give reviewers sufficient access, time, expertise, and authority.

Accumulated rights should also have an origin. Was the authority delegated by policy, inherited after a departure, created during an emergency, or merely assumed? Confirm it. An arrangement can be sensible and still need formal recognition, boundaries, and a review date.

2. Letting one owner control the whole process

Single ownership can create clarity. Product managers, case owners, and service leads exist because fragmented responsibility is frustrating. The distinction is between end-to-end accountability and unchecked end-to-end control.

An accountable owner should ensure the process works. They need not personally control every gate, record, exception, and review. Daniel can be accountable for settlement quality while another role approves high-value adjustments and a second person maintains access.

Look for a closed loop:

1. one owner defines the intake;
2. that owner decides which requests qualify;
3. the owner controls the queue and status information;
4. the owner approves exceptions;
5. complaints return to the owner;
6. performance reports use measures chosen by the owner.

In such a loop, poor service may remain invisible because all evidence passes through the same interpretation. This does not prove bad faith. Overloaded owners frequently simplify in order to survive. Their local adaptations become rules because no other vantage point exists.

Open the loop at points that improve evidence. Publish eligibility and service standards. Let requesters see status. Require reasons for material refusals. Route appeals elsewhere. Have measures jointly defined with users and an accountable sponsor. Sample closed cases. Create an emergency alternative when the owner is unavailable.

Do not multiply checkpoints mechanically. Every handoff adds delay and can diffuse accountability. Use risk to decide where an independent view matters. A low-value routine request may need automated rules and audit sampling; a rare, irreversible exception may warrant two-person review.

The owner should participate in redesign. Treating them as the problem can destroy the tacit knowledge the organization needs to preserve. Ask where they experience overload, ambiguity, repeated exception, or weak upstream data. Often the person at the center wants relief but fears that a rushed handoff will produce failure for which they will still be blamed.

3. Narrowing succession through unclear criteria

Succession is not only the replacement of chief executives. Every role with scarce knowledge, decision authority, or critical relationships has a continuity question. Who could perform it tomorrow, and how could someone become ready?

An unclear process allows incumbents and sponsors to define readiness after seeing the candidates. A potential successor is told she needs international experience; after gaining it, she is told she lacks exposure to senior leadership. Another is deemed ready because leaders “can see him in the role,” though no one explains the evidence.

Judgment is unavoidable in succession. Future roles change, and leadership capability cannot be reduced to a checklist. The answer is not to pretend the decision is mathematical. It is to make the main requirements visible enough for development and comparison.

Separate:

• eligibility: minimum requirements to enter consideration;
• readiness: evidence a person could perform now or within a stated period;
• potential: a forecast of capacity for larger or different work;
• preference: a decision among qualified options based on current needs;
• risk: gaps and conditions that require support.

These terms are often blurred. Someone can have high long-term potential and not be ready today. A ready person may not be selected because another candidate better fits a particular transition. A preference should not be rewritten as proof that the unselected person was unqualified.

Use multiple sources: demonstrated work, structured examples, stakeholder experience, simulations where appropriate, performance over time, and explicit development goals. Train reviewers to distinguish confidence and familiarity from evidence. Record material changes to criteria and apply them to all plausible candidates.

Incumbents provide indispensable insight into the role, but they should not hold a private veto over succession. Their preferences may favor a similar style, a loyal deputy, or someone who will preserve existing choices. Include the role’s manager, relevant partners, and an independent talent or governance perspective for consequential appointments. Address conflicts openly.

Succession also concerns opportunity. A list of names is not a pipeline if only favored candidates receive the acting assignments, executive exposure, and difficult decisions needed to become credible. Chapter 1 described access; here the consequence is continuity. An organization that withholds developmental work may later cite the resulting lack of experience as a natural shortage. Research on workplace mentoring offers one evidence base for treating developmental relationships as a real part of this pipeline rather than an incidental benefit.³

4. Concentrating history and operating knowledge

Documents hold only part of what people know. Teams also rely on tacit knowledge: cues, relationships, exceptions, judgments, and physical or social routines acquired through experience. A procedure may say “investigate differences above the threshold.” Daniel knows which difference indicates a duplicated shipment, which comes from currency timing, and whom to call before a customer’s warehouse closes.

Research on transactive memory describes how groups develop shared knowledge about who knows what; performance can depend not only on individual memory but on a system for locating expertise.⁴ Organizational knowledge can also move through people, tools, routines, and networks rather than through documents alone.⁵ The practical implication is that continuity requires more than asking an expert to write everything down.

Concentration appears in several forms:

• technical: one person knows the code, calculation, equipment, or configuration;
• procedural: one person knows the true sequence behind the formal process;
• relational: one person holds customer, vendor, regulator, or internal trust;
• historical: one person remembers why an exception or control exists;
• interpretive: one person can distinguish a normal anomaly from an important one;
• access-based: one person has the account, key, permission, or physical entry needed to act.

Inventory these forms separately. A shared folder solves none of the problem if only one person can interpret its contents. A second password holder does not transfer judgment. Shadowing may reveal routines but not rare exceptions. Build several paths: clear procedures, paired work, scenario rehearsal, decision records, contact handovers, supervised practice, access review, and rotation through real cases.

Prioritize knowledge by service impact, replaceability, learning time, and likelihood of loss. Do not demand exhaustive documentation from every employee. It creates a cemetery of outdated pages and signals distrust. Protect the activities that would cause serious harm, long delay, legal breach, or irreversible loss if the expert were unavailable.

Make maintenance part of the work. Every critical guide needs an owner, review trigger, and evidence of use. A procedure last updated three years ago but used successfully by a deputy last month may be more reliable than a polished document no one has tested.

Relational continuity deserves care. Introducing a deputy to a customer or regulator is not the same as transferring trust, but it creates a second route. Explain roles honestly. Do not use contact sharing to bypass confidentiality, professional duties, or commitments. Record institutional history without collecting unnecessary personal information.

5. Delaying documentation, delegation, or cross-training

Delay often sounds reasonable because it is reasonable. “After the quarter closes.” “Once the new system stabilizes.” “When we hire the vacancy.” Critical experts are usually busy precisely because others cannot perform their work. Asking them to create redundancy adds work before it removes any.

This produces a continuity trap:

1. dependence creates urgent demand on the expert;
2. urgent demand leaves no time to transfer knowledge;
3. failed transfer preserves dependence;
4. preserved dependence creates more urgent demand.

Break the trap by funding transfer as delivery, not as an optional extra. Remove some operating work, narrow the first documentation target, pair the expert with a named learner, and schedule a real test. The manager—not the expert alone—owns the trade-off.

Use small transfer units. Instead of “document settlement,” choose “enable a deputy to identify and route the five highest-impact reconciliation exceptions during Daniel’s two-week absence.” Capture inputs, decision cues, actions, approval boundaries, contacts, evidence, and recovery steps. Then let the deputy perform the task while Daniel observes.

Delegation transfers a decision or task within stated boundaries. It is not dumping work while retaining every choice. Define what the delegate can decide, what requires consultation, what must be escalated, what resources are available, and how mistakes will be handled. If every non-routine case returns to the expert, the deputy is an assistant, not a successor.

Cross-training also needs depth. Watching a demonstration creates familiarity. Capability requires retrieval, judgment, and action under realistic conditions. Use scenario drills, planned absence, peer review, and evidence from live work. Avoid letting practice become unpaid invisible labor or an indefinite acting role without recognition.

Some incumbents resist transfer because scarcity protects status or employment. Others resist because earlier delegation led to mistakes they had to repair, because their value has never been recognized except through indispensability, or because leaders demand a handover while leaving them accountable for the result. Diagnose before moralizing. Align incentives: recognize teaching, adjust workload, protect role dignity, and make shared capability part of performance.

Persistent refusal after support, clarity, and reasonable time is different. If knowledge belongs to the organization and continuity is a role requirement, a manager may need a formal performance or conduct response under policy. Preserve employee rights, confidentiality, intellectual-property terms, and professional obligations; not all knowledge can be copied or broadly shared.

The indispensable-person bargain

Organizations often make an implicit bargain with key people: absorb impossible complexity and we will excuse the controls that would make you less central. The person receives autonomy, status, or security. The organization receives heroic recovery. Both postpone structural repair.

The bargain is unstable. It burdens the expert with constant interruption and limits their growth because no one can release them from the old work. It leaves colleagues underdeveloped. It makes leaders reluctant to challenge the expert, even on unrelated questions. It turns vacation, illness, promotion, retirement, and ordinary disagreement into operational threats.

Appreciation and deconcentration can happen together. Say: “Your knowledge has protected this service. We need to make that achievement durable and give you room for larger work.” Reward the creation of capable successors, tested processes, and shared relationships. Do not wait for departure to value the transfer.

Retention remains legitimate. Some skills are scarce, and replacing them is expensive. Compensation, flexibility, career opportunities, and recognition can reduce avoidable loss. A retention plan is strongest when paired with continuity, not when used instead of it.

Vendors, founders, and systems can be entrenched too

A vendor may control a proprietary format, administrative account, or implementation knowledge. A founder may hold customer trust and informal authority beyond the organization chart. A committee may have renewed its own mandate for years. A legacy system may encode rules no one understands, making technical limitation function like policy.

Use the same questions: what is controlled, how was the authority created, what evidence and alternatives exist, who can review it, and how can the organization continue if the center is unavailable?

For vendors, examine data portability, documentation, access, subcontractors, termination support, intellectual property, escrow or recovery arrangements where appropriate, and the practical cost of switching. Contract language is not enough if no one has tested export or transition.

For founders and long-tenured leaders, formal governance may coexist with personal relationships that still determine outcomes. Clarify which decisions belong to the current role, move commitments into organizational records, broaden external relationships, and create a succession process that does not require the incumbent’s private approval.

For systems, distinguish real technical constraints from choices hidden behind “the system won’t allow it.” Who configured the rule? Can an authorized person change it? What audit and exception path exists? A machine cannot be accountable for a policy decision made through its settings.

Transitions reveal the true operating system

Mergers, reorganizations, outsourcing, rapid growth, long leave, and planned exits expose dependencies that stable routines conceal. Leaders often begin these transitions with boxes and names. Continuity begins with services, decisions, knowledge, and relationships.

Before changing roles, identify what must remain true on day one. Which payments, care, access, customer responses, safety checks, approvals, and reporting duties cannot pause? Who performs them now—not according to the chart, but in practice? Which workarounds and relationships make the formal process succeed?

Use structured handover conversations alongside documents. Ask the current owner to walk through a normal case, a difficult case, the last failure, the most likely upcoming decision, and the people whose context is essential. The incoming owner should restate the process and run a scenario. Differences reveal hidden assumptions better than a passive presentation.

Capture “why” with “how.” A rule that seems irrational may protect against an old failure, fulfill a contract, or compensate for a system limit. It may also be obsolete. Record the origin, current owner, and review condition. This lets successors challenge the rule without erasing history.

Relationship handover requires consent and dignity. Customers and partners should not be treated as transferable assets. Introduce the new contact, explain the continuing mandate, and create overlap where possible. For sensitive professional, health, legal, or representative relationships, follow the governing confidentiality and consent requirements.

Departing employees can be especially vulnerable to unfair narratives. A rushed handover may be treated as proof that they withheld knowledge even when leaders left no time. Define the expected artifacts, access, meetings, and support early. Give the successor responsibility for confirming what they can use. Record unresolved gaps without guessing at motive.

The organization must also avoid coercive extraction. Employees should transfer organizational records and role knowledge as required, but continuity work must respect contracts, law, personal data, health, reasonable workload, and intellectual-property boundaries. Personal contacts, private devices, memories of confidential matters, and professional knowledge are not an unlimited corporate repository. Seek qualified advice in a contested exit.

After the transition, hold a thirty-day continuity review. Which decisions stalled? What only the predecessor could answer? Which documents were wrong? Which access arrived late? What relationships need broader ownership? Correct the system before the gaps harden around the new incumbent.

Do not let the replacement become indispensable in the same way. The pressure of transition encourages leaders to centralize everything again. Establish the backup, shared record, independent check, and learning time while the role is being rebuilt. Continuity is easiest to design before the new emergency routines become tradition.

Handled well, transition is not merely a risk event. It is an opportunity to distinguish valuable expertise from accumulated workaround, preserve the former, remove the latter, and give the next owner a role that can be learned rather than inherited as a mystery.

A response ladder for concentrated power

Map. Identify decision verbs, critical knowledge, access, relationships, and review paths. Focus on a process, not a personality.

Test absence. Ask what fails after one day, one week, one month, and permanent departure. Use a tabletop exercise before risking live service.

Open one loop. Add visibility, independent review, backup access, or a second route at the highest-risk point.

Fund transfer. Give the incumbent and learner time, tools, recognition, and a concrete capability target.

Exercise. Let the deputy perform real or simulated work. Record gaps in both the guide and the learner’s authority.

Reassign rights. Separate incompatible duties and confirm delegated authority. Add proportionate compensating controls where staffing is limited.

Govern succession. Publish relevant criteria, broaden development opportunities, manage conflicts, and record the basis for consequential choices.

Review. Set a date and evidence for reducing the remaining concentration. Continuity work without review easily returns to emergency mode.

Escalate sooner when concentration enables financial abuse, safety risk, privacy breach, unauthorized access, evidence suppression, or a legal or regulatory failure. Use qualified specialists and preserve records appropriately. Do not test a live control or access someone else’s account without authorization.

For managers: a ninety-day continuity experiment

Choose one critical activity. During the first thirty days, name the accountable owner, backup, essential inputs, decision boundaries, and failure impact. Observe a complete cycle. Record the top exceptions and missing access. Protect time for the expert and learner.

During the next thirty days, the backup performs bounded parts while the expert reviews. Update the guide from actual use. Introduce the backup to necessary partners. Move shared credentials into an authorized access system; never duplicate personal credentials informally. Confirm who can approve an emergency exception.

During the final thirty days, run a planned absence or tabletop exercise. The incumbent should be unavailable for routine questions for a defined window but reachable through an emergency threshold. Measure completion, errors, delay, escalations, and the kinds of judgment the guide did not capture.

At the review, do not ask only, “Can the backup do it?” Ask whether the role design, tools, upstream data, workload, and decision rights make success possible. Decide the next unit of transfer. Reward both operational performance and the reduction of fragile dependency.

For a senior role, use a longer horizon but the same logic. Succession candidates need development assignments, relationships, and decision practice before a vacancy. Emergency succession and long-term selection are different processes; document both.

Returning to Daniel

Daniel’s director stops treating the missing manual as a personal overdue task. She removes two reporting responsibilities for one quarter and assigns Mei, an experienced analyst, as a named deputy. Together, Daniel and Mei map the seven settlement exceptions with the greatest customer and financial impact.

Finance takes approval of high-value adjustments. Technology moves shared configuration into a managed repository with backup administration. Daniel remains accountable for process quality, but a risk manager samples closed exceptions and the operations director hears appeals. Mei performs the next close while Daniel observes and intervenes only at agreed thresholds.

The exercise finds that three steps in the old procedure are obsolete and that Daniel had been compensating for a broken data feed every month. Fixing the feed removes more dependency than another hundred pages of documentation would have done.

Daniel receives recognition for stabilizing the system and for building continuity. He is invited to lead the replacement design—a role he could not have accepted while every settlement depended on him. The organization has not made his expertise less valuable. It has stopped requiring his constant presence as proof of its value.

Practice: draw the continuity map

Choose a legitimate process you know well and are authorized to examine. For each important activity, record:

1. the person or role that decides;
2. the person or role that performs;
3. the knowledge or relationship the activity depends on;
4. the access needed;
5. the backup and the last time they performed it;
6. the independent check, if one is warranted;
7. what would fail after a week of absence;
8. the smallest useful transfer exercise;
9. the time and support required;
10. the date on which the concentration will be reviewed.

Do not score the people involved or circulate sensitive access details. The output is a service-continuity plan, not a suspicion map.

Notes

Footnotes

1. David J. Hickson et al., “A Strategic Contingencies’ Theory of Intraorganizational Power,” Administrative Science Quarterly 16, no. 2 (1971): 216–229, https://doi.org/10.2307/2391831. ↩

2. Daniel J. Brass and Marlene E. Burkhardt, “Potential Power and Power Use: An Investigation of Structure and Behavior,” Academy of Management Journal 36, no. 3 (1993): 441–470, https://doi.org/10.5465/256588. ↩

3. Lillian Turner de Tormes Eby and Melissa M. Robertson, “The Psychology of Workplace Mentoring Relationships,” Annual Review of Organizational Psychology and Organizational Behavior 7 (2020): 75–100, https://doi.org/10.1146/annurev-orgpsych-012119-044924. ↩

4. Kyle Lewis, “Measuring Transactive Memory Systems in the Field: Scale Development and Validation,” Journal of Applied Psychology 88, no. 4 (2003): 587–604, https://doi.org/10.1037/0021-9010.88.4.587. ↩

5. Linda Argote and Paul Ingram, “Knowledge Transfer: A Basis for Competitive Advantage in Firms,” Organizational Behavior and Human Decision Processes 82, no. 1 (2000): 150–169, https://doi.org/10.1006/obhd.2000.2893; Linda Argote and Ella Miron-Spektor, “Organizational Learning: From Experience to Knowledge,” Annual Review of Psychology 75 (2024): 257–286, https://doi.org/10.1146/annurev-psych-022123-105424. ↩