Every question, answered plainly

Key person dependency is when important work waits on one person: decisions that only reach a result through their calendar, knowledge or relationships only they hold, approvals only they give, or rescues only they perform. It feels like strength while the company is small. It becomes the ceiling when the company grows, because every new customer, hire, and initiative queues behind the same person.

Take the Hero Test

Make what they know transferable instead of making them replaceable. Grant the authority that was never granted, help the expert transfer what only they know, and set a cadence that closes decisions without them in the room. The expert does not get a smaller role. They move to higher value work: helping others make sound decisions instead of approving every step.

Module 5: Build the Operating Loop and Transfer Judgment

Because the dependency costs you every week they stay, not only the week they leave. Work waits for their calendar, decisions queue behind them, and the people around them stop building judgment of their own. The goal is a business that can scale without them even if they stay, so their time goes to the work only they can do.

Ask three questions about a normal working week: Who is the company waiting for? Why does it wait? What would it take to move without them? Then test it with evidence. For two working days, record every decision that reaches that person. The 48-Hour Decision Queue Audit turns a feeling into a list you can act on.

Run the 48-Hour Decision Queue Audit in Module 0

Heroic effort gets a company through a crisis, but it cannot carry a company through growth. When one capable person substitutes for a working system, the company's capacity is capped at that person's hours. Heroes don't scale. Systems do. The course replaces the dependency with a system: clear direction, defined outcomes, real ownership, a review cadence, and repeatable work.

Very. Research by Cross, Rebele and Grant in Harvard Business Review (2016) found that 3% to 5% of employees deliver 20% to 35% of the collaboration that adds value. A 2019 McKinsey survey of 1,259 executives and managers found 37% of their time goes to decisions, and more than half of that time is spent ineffectively. An APQC survey of 1,000 organizations (2025) found only 8% consistently capture knowledge from employees who are retiring.

Because the hold period does not wait. The AlixPartners PE Leadership Survey (2026) reports that 65% of private equity firms see CEO turnover at a portfolio company during the hold. A company that depends on one person, including the CEO, carries that risk into every value creation plan, integration, and exit. A company that runs on a system can absorb a leadership change.

The Hero Test is a free, one-minute diagnostic from Russ Reeder's book Heroes Don't Scale. A few taps name why the work in your company waits on one person, which of three cases you are living in, and the first move to make this week.

Take the Hero Test

About a minute. The quick test is three to six taps. Seven deeper reflection questions come after your result if you want them, and they are optional and private.

Never granted: the resources, authority, or support to hand the work off were never granted. Never transferred: a valuable expert holds knowledge nobody has yet helped them transfer. Kept close: after the company has kept its side, someone keeps withholding knowledge, overriding agreed decisions, or blocking successors. No time to teach is not withholding. The first two are support and transfer problems, and most heroes live in one of them. Start there before you treat the third as resistance.

Your case, a first move for this week with a calendar file and a blank audit sheet, your path through the thirteen free modules, and how your answers compare with everyone who has taken it, shown as percentages. You can save the result, share it, or send the test to your leadership team.

Run the 48-Hour Decision Queue Audit. For the next two working days, record every decision that reaches the person the company waits for, using role titles only. Bring that record to the module your result names.

No. The Hero Test prints no score and no number. It is a discussion tool, not a validated assessment, and its subject is the dependency on a role, not a verdict on a person.

About yourself first, about a normal working week. What would stop if you were away, why would it stop, and what would a capable replacement need? Then widen the question to the company. Keep the discussion on the work, not the person, and take any performance question to that person's manager in private.

All three. The test asks which seat you answer from: the CEO or executive, the manager at any level, or the person others wait on. The same test taken from different seats shows where the company depends on one person and why. A CEO may see a habit where a manager sees authority that was never granted.

Yes. A printable worksheet runs the same questions on paper, which works well in a room where not everyone has a laptop open.

Print the Hero Test worksheet

A free online course that adds the full toolkit and working sessions to Russ Reeder's book: the Hero Test, thirteen modules (0 to 12) with tools and sixty-minute working sessions, a facilitator track, and the 90-Day Install. There is one module for each chapter, numbered to match, with the chapter's tools, its working session, and the three questions printed at the chapter's end.

See the modules

Yes. Everything the book names is free: the test, the thirteen modules, the tools, the session plans, and the 90-Day Install. There is no paywall and no account required.

Every module from 1 to 12 has the same six parts: Objectives, Lesson, Tool, Working Session, the Hero Test for that chapter, and Evidence of Completion. Lessons take seven to twelve minutes to read and run scene first, mechanism second, tool last. Module 0 is the front door: the Hero Test.

The one your Hero Test result names. Your answer about what waits sets where you start, and your case sets what you emphasize. If decisions wait for the top, for example, start with Module 1, Transfer a Recurring Decision, then Module 8, Make the Authority Agreement Hold.

Take the Hero Test

Each lesson is seven to twelve minutes. Each working session is sixty minutes. Run one module a week and the twelve chapter modules take twelve weeks. The team reading program runs the 90-Day Install alongside them: the first session in week one, a review in the weeks that hold days 7, 15, 30, and 60, and the day 90 review in week thirteen.

An Authority Grant puts in writing the five elements a person needs to carry an outcome: the decisions they can make, budget and staffing, tradeoffs, standards, and escalation with a deadline. It is the repair for the never granted case. A signed grant is useful only if the organization honors it, which Module 8 tests.

Module 8: Make the Authority Agreement Hold

It grows. The Hero-to-Multiplier Map tracks where the leader's time goes as decisions leave their inbox: the rescue, its cause, the new owner, and the higher value work they take on instead. Expertise creates value. Gatekeeping traps it.

Module 5

Not on its own. AI can preserve a process that no longer needs to operate that way, and swapping a human hero for a software one leaves the dependency in place. Module 4 follows one real transaction from request to accepted result, repairs the complete result first, and only then decides at the Operations First AI Gate: a bounded experiment, further repair, or no investment.

Module 4: Test a Better Workflow Before Adding AI

One outcome, one owner, one record, and reviews on the calendar through day 90. A facilitator runs it: a two hour first session, four windows, five review questions, and a gate decision. Ninety days is the first test of the operating method, not a guarantee that every business result arrives in one quarter.

See the 90-Day Install

The lesson videos are in production. Every lesson is live as text today, so you can run each module and its working session now.

Everyone takes the Hero Test from their own seat, using role titles, never names. Create a team in your account and share the invite link. Then run one chapter a week: its three questions and one action are the agenda, and the module's sixty-minute session is the work. Run the 90-Day Install on one dependency while you read: the first session in week one, the first 30 days following the Conclusion's first-month plan, and the day 90 review in week thirteen.

Read it with your team

How many members have taken the test and how the team's latest results spread across the three cases. It appears once five members have a result and refreshes only after five more arrive, so no one person's answer shows up as a change. It never names who answered what.

Not the outcome owner. The person running the room cannot also be the person carrying the result. An operating leader from another function or an outside advisor holds the agenda, keeps time, keeps the discussion on the work rather than the person, and names a recorder who keeps the record.

Facilitator Track

Follow the protect-people rules. Answer the Hero Test for yourself first. Use role titles, never names. Where a tool names a person, the subject is the dependency on that role. Performance questions go to the responsible manager in private, and concerns about suspected misconduct, retaliation, or serious risk go through a protected route, separate from execution disputes.

A book by Russ Reeder, Heroes Don't Scale: Build a Business That Grows Without You, coming in early 2027. It shows why capable companies stop scaling when heroic effort substitutes for a working system, and how to replace the dependency with VOOCS: Vision, Outcomes, Ownership, Cadence, Systems.

No. Each module carries its chapter's tools, sessions, and evidence, so you can run the course on its own. Each chapter of the book ends on three questions and one action that point to its module, so the two work together when the book is out.

VOOCS is the operating system for execution in Heroes Don't Scale: Vision, Outcomes, Ownership, Cadence, Systems. The VOOCS Operating Record puts all five on one page for one initiative, with an owner, a sponsor, and a next review date. Every module writes into it. The mantra: Define it. Measure it. Own it. Close it. Scale it.

Module 5

Decisions Before Data and Commitments Before Scale. Before collecting more numbers, name the decision, the options, and the evidence that could change it. Before a pilot begins, agree on the production owner, the adoption plan, the funding conditions, and the result that justifies expansion. Modules 11 and 12 teach them.

HEAR is the leadership values framework in the book: Honesty, Empathy, Accountability, Respect. In the course it becomes four questions for a hard conversation: the fact being avoided, why a peer believes in a different path, who acts by when, and how the team moves forward together once it decides.

Module 3

Russ Reeder is the founder and CEO of KeyDelta. Its promise: fix what's broken, build what pays, keep it relevant. He has spent more than thirty years scaling technology companies, including Oracle, GoDaddy, Media Temple, OVHcloud, Netrix Global, and XTIUM, founded Rightsline, and is a member of the Forbes Technology Council.

No. An account is optional. Sign in with a one-time email link, no password, only if you want to keep your result, track your module progress, or build a team view. A result you take before signing in is kept when you sign in on the same device.

Your case and your seat. Never your answers, your name, or your email. Your typed answers to the seven deeper questions are private to you and never appear on a shared link or a team view.

Your single-choice answers and reading path, tied to a random code in your browser. If you sign in, your email and your progress. Page counts use no names, no answers, no IP addresses, and no third-party analytics, and nothing is counted if your browser sends Global Privacy Control or Do Not Track. To delete your data, write to russ@keydelta.com from the address you signed in with.

Read the privacy page

Yes. KeyDelta, the firm Russ Reeder founded to fix what's broken, build what pays, and keep it relevant, offers a thirty-minute call on the dependency you named and a facilitated session where your leadership team takes the Hero Test from every seat, compares cases in the room, and leaves with one owner, one record, and the first ninety days on the calendar. Russ also gives a keynote for leadership offsites, PE portfolio summits, and boards.

Work with KeyDelta

The course is free and most teams can start alone. When the dependency is tangled in a sale, an integration, or a founder handoff, a conversation saves months. An outside facilitator also solves a structural problem: the outcome owner should never run their own room.

Use the feedback page or the note box at the end of your result and each module. It goes straight to Russ. An email address is optional and used only to reply.

Send feedback or an idea