Dependency-Reduction Scorecard¶
Tracking scorecard — instantiates Dependency-Capture Exit Design
Tracks, period over period, how much of the organization's need still runs through the captured role, turning "we're less dependent now" into a measured trend.
Dependency is hard to reduce because you cannot feel it shrinking; it is invisible right up until the day the indispensable person is out and everything stalls. Dependency-Reduction Scorecard makes the shrinkage visible. It is a small, repeated set of quantities — measured every month or quarter — that answer one question: what share of this need still has to pass through the captured role? Its defining property is that it is a continuous, forward-looking trend line, watched while the reduction program is still underway, not a verdict at the end. The scorecard does not decide whether to exit and it does not check, after the fact, whether the exit held; it is the instrument that tells you, week over week, whether the concentration is actually coming down or whether the last "fix" quietly bounced back.
Example¶
A mid-size newsroom has a star investigative reporter through whom nearly every high-value source relationship runs. Editors love the scoops and fear the exposure: if he leaves, or leverages his indispensability, whole beats go dark. Instead of arguing about how dependent they are, the masthead stands up a quarterly Dependency-Reduction Scorecard. Three lines: the share of the outlet's confidential sources reachable by at least one other journalist; the fraction of major stories in the quarter that required his direct involvement to land; and the number of documented source-handoffs completed to named colleagues.
Q1 is bleak — 8% of sources have a backup contact, 90% of big stories route through him. But the trend is the product. By Q3 the backup-coverage line has climbed to 45% and story-dependence has fallen to 55%; more importantly, when it stops climbing in Q4, the scorecard flags it, and editors discover he has quietly stopped introducing colleagues to new sources. The number caught the backslide the anecdotes missed.
How it works¶
- Map the pathways, then meter them. Each route by which the need depends on the role — source access, tacit method, sole system credentials — becomes a line item, expressed as a share concentrated on the role holder rather than a yes/no.
- Measure durable resolution, not activity. The metric rewards the need being met independently of the incumbent (a source another reporter can call), not the incumbent being busy; effort by the captured person counts against the trend, not for it.
- Watch the second derivative. A flat or reversing line is itself a signal — a monitor for stalled progress or active back-sliding, whether from inertia or from quiet re-entrenchment by someone with an interest in staying necessary.
- Refresh on a fixed cadence. The same lines, same definitions, every period, so the trend is comparable and cannot be reset by a favorable one-off snapshot.
Tuning parameters¶
- Concentration metric — headcount-can-cover vs. volume-weighted share vs. criticality-weighted. Weighting by how critical each pathway is focuses attention but is more subjective; simple counts are auditable but can flatter you on trivia.
- Cadence — monthly catches back-slides fast but costs collection effort and adds noise; quarterly is cheaper and smoother but lets a reversal run longer before it shows.
- Backslide sensitivity — how large a stall or reversal trips the monitor. Tight thresholds surface re-entrenchment early but cry wolf on normal variance; loose ones miss slow recapture.
- Attribution rule — whether work done by the incumbent counts toward "resolved." Excluding it is what keeps the score honest; including it lets busywork masquerade as progress.
When it helps, and when it misleads¶
Its strength is converting an anxiety into a governable trend: leaders can set a target slope, hold reviews against it, and notice a reversal before it becomes a crisis. It reframes the problem from the person ("is he a flight risk?") to the structure (key-person risk[n1] as a measured concentration), which is both fairer and more actionable.
Its failure mode is the metric that measures motion instead of independence — counting training sessions held, documents written, or hours the expert spent "mentoring," all of which can rise while genuine coverage does not. A captured incumbent can even drive those vanity lines up to look cooperative while ensuring no colleague ever gets an unsupervised relationship. The number then certifies progress that is not real. The guard is to define every line as independently-verifiable coverage — can someone else actually do it, demonstrated — and to treat incumbent effort as neutral-to-negative, never as credit.
How it implements the components¶
durable_resolution_metric— the scorecard is the metric: it quantifies how much of the need is durably met without routing through the captured role, tracked over time.dependency_pathway_map— each metered line corresponds to a mapped pathway of dependence, so the score is a live reading of the map rather than an abstraction.recurrence_and_sabotage_monitor— a stalled or reversing trend is the early-warning signal for re-entrenchment or quiet obstruction while the program is still running.
It does not run the one-time forensic check after exit or protect those who report a recaptured dependency (challenge_and_whistleblower_protection) — that's Post-Exit Dependency Audit; the scorecard is a continuous in-flight trend, not a post-mortem.
Related¶
- Instantiates: Dependency-Capture Exit Design — supplies the running measure of whether dependence is actually falling.
- Consumes: Independent Needs Assessment — its definition of the true underlying need sets what the scorecard should be measuring coverage of.
- Sibling mechanisms: Capability Handoff Checklist · Exit-Readiness Review · Fixed-Term or Sunset Mandate · Independent Needs Assessment · Open Documentation Package · Outcome-Based Contract · Post-Exit Dependency Audit · Rotation or Term Limit · Second-Source Review
Editorial Notes¶
Form Classification¶
Form family: Monitoring, Sensing & Alerting
Rationale: Dependency-Reduction Scorecard operates as an ongoing sensing arrangement that repeatedly observes actual state and surfaces changes or alerts because it tracks, period over period, how much of the organization's need still runs through the captured role, turning 'we're less dependent now' into a measured trend.
Independent corroboration: The frozen evidence defines Dependency-Reduction Scorecard as 'Tracks, period over period, how much of the organization's need still runs through the captured role, turning 'we're less dependent now' into a measured trend', so its operative form is Monitoring, Sensing & Alerting.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Enterprise risk management cohered recurring scorecards that track key-person and role concentration as a declining exposure over time.
Related originating lineages:
- Economics & Finance — Concentration-risk measurement supplied portfolio-style exposure metrics.
Review resolution: Enterprise risk management cohered recurring scorecards that track key-person and role concentration as a declining exposure over time. The retained alternate lineages materially shaped the mechanism's form.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Key-person risk (also "key-man risk") — the exposure a business carries when a single individual's knowledge, relationships, or skills are so concentrated that their loss would materially damage operations. It is the risk the scorecard renders as a measurable, trendable concentration rather than a vague worry. ↩