The Hero Test

Take the Hero Test Start the 8-minute lesson Jump to the tools8 minute lesson

In short

Module 0 of the free Heroes Don't Scale course, by Russ Reeder, is the front door: the Hero Test. Name one dependency and one case, for yourself first. What the Hero Test is, in one minute.

Objectives

Name one dependency and one case, for yourself first.
You leave knowing which case you are living in, which chapter to read next, and one action to take before you bring anyone else into a room.

Lesson

About 8 minutes to read

Open on the reader's desk

Your team is good, but they're still waiting on you. They have learned that the safest way to get a decision accepted is to run it through your calendar, even when the work belongs to them. The company moves at the speed of your availability. That is a ceiling, and you built it without meaning to.

Name the disease

Hero culture feels like leadership and rewards itself with importance. The dependency is the disease, not the hero. It can form anywhere: the engineer who alone understands the system, the salesperson who controls the relationships, the executive who centralizes approvals, the former founder who keeps a private channel alive. The repair is a system, which the book defines as an agreed way to carry work from a need to a verified result: who decides, how the work gets done, what information people share, and how they correct a failure. It can begin with a shared record and a regular conversation.

Sort it into three cases

Sometimes a person deliberately protects the moat. More often the person is carrying too much because nobody gave them the resources, authority, or support to hand work off, or holds expertise nobody has helped them transfer. Call the three cases never granted, never transferred, and kept close. The first two are support and transfer problems, and most heroes live in one of them. The response follows the sort: expectations, coaching, support, authority, and systems first, and a role change only after a fair opportunity. An urgent response to serious misconduct or risk may have to come first. Expertise creates value. Gatekeeping traps it.

Three seats

If you run the company, the ceiling comes down the way it went up, one decision at a time. If you are in the middle, you may hold the responsibility without the authority, as I did as president of Media Temple when work hit a wall and people went around me, straight back to the founder. If you are the one everyone waits for, you were told to make yourself irreplaceable. If critical work depends on you alone, nobody around you can carry it forward, and that dependency makes it harder to promote you.

The test

Ask the three questions printed below about yourself first, about a normal working week, not the last emergency. Then take the test on this site. It runs in four steps: choose your seat, answer why the work waits, which sorts the case, pick the Bottleneck Check choice that describes most of what waits, which sets where you start, and, after your result, answer the seven deeper questions if you want to widen it to the company. Those seven are private and optional.

Close

The goal is not to make people replaceable. It is to make their value transferable. When no one is indispensable, everyone becomes more valuable.

Tools

Module 0: The Hero Test. From the free course toolkit for Heroes Don't Scale.

The Hero Test as the book prints it

Who is the company waiting for?

Why does it wait?

What would it take to move without them?

Two rules. Take the test yourself before you bring it to anyone else. Aim it at a dependency, not at a colleague's character. The answer you want to the first question is no one. Ask the questions 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 and name the capability or route an important result waits on. Keep the discussion on the work, not the person, and take any performance question to their manager in private.

The assessment

Worksheet

Step 1. Choose your seat: the CEO or executive, the manager at any level, or the person everyone waits for. The result page speaks to the seat you choose.

Step 2. Answer one question for yourself, about a normal working week: why does the work wait? Never granted: nobody gave the authority, budget, or help to hand it off. Never transferred: one expert knows it, and nobody has made time for them to teach it. Kept close: the company has given time, a backup, coaching, and credit, and the work is still held back. Before kept close counts, the test asks whether the company has already put teaching time on the calendar, named a backup, and recognized the teaching in reviews. If the answer is not yet, the case is never transferred, because the company's side comes first. The sort decides the response, and it decides the result page you see.

Step 3. Narrow it with the Bottleneck Check. Pick the one choice that describes most of what waits. Your choice sets where you start.

Which decisions wait for the top?
Which initiatives wait for a person instead of an agreed rule?
Which budget or staffing choices sit above the person accountable for the result?
Which rescues and know-how does only one person hold?

Two follow-ups adjust the path. If initiatives wait for a person, the test asks whether the initiative is a tool. If rescues and know-how sit with one person, it asks whether this is inside an acquisition or integration.

Choose one recurring dependency to change.

Step 4. After your result, the seven deeper questions widen it to the company. They are private and optional. Role titles, never names.

Who is the company waiting for?
Which decisions can only that person make?
What knowledge or relationship exists only with them?
Who can cover their absence?
What can the team decide without seeking permission?
What evidence shows that real work and a relevant exception are handled without that person's routine intervention?
Why does the dependency exist: resources, authority, or support that were never granted; knowledge a valuable expert has not yet had help transferring; or work kept close after the company has kept its side?

Initiative: ________________________ Owner: ________________________ Date: ____________

The 48-Hour Decision Queue Audit

Run the 48-Hour Decision Queue Audit during two working days. Start with the unresolved decisions already waiting, then record each new decision that reaches the person you named. Don't count ordinary consultation as a blocked decision. Continue the same record after the audit as the Waiting Decision Log, whose fields are in Module 1. Record personnel and other confidential decisions by category, owner, and age only.

Your result page

The result page is built from two answers. Your Bottleneck Check answer sets where you start. Your case sets what you emphasize when you get there. The page prints no score and no number. It tells you which case you are living in, which chapter to read next, and one action.

Where you start. If decisions wait for the top, start with Chapter 1 and Module 1, then Chapter 8 and Module 8. If initiatives wait for a person instead of an agreed rule, start with Chapter 5 and Module 5, then Chapter 7 and Module 7; when the initiative is a tool, Chapter 4 and Module 4 come before Chapter 7. If budget or staffing choices sit above the person accountable, start with Chapter 8 and Module 8, then Chapter 6 and Module 6. If rescues and know-how sit with one person, start with Chapter 5 and Module 5, then Chapter 7 and Module 7, then the 90-Day Install; inside an acquisition or integration, Chapter 10 and Module 10 join the path.

The three result pages below are what the reader sees, with the seat filled in from Step 1.

Result: never granted. You answered from the [seat] seat. The company waits on someone carrying too much because the resources, authority, or support to hand the work off were never granted. This is a support problem. The repair is an Authority Grant written down for one owner, with all five elements: the decisions delegated, budget and staffing authority, tradeoff authority over competing priorities, standards and constraints, and an escalation path with a response deadline. Read next: the chapter your Bottleneck Check named, then Chapter 8, where the grant is written and tested. This is a discussion tool, not a validated score; its subject is the dependency on a role, not a verdict on a person. One action: for the next two working days, run the 48-Hour Decision Queue Audit on your own queue, starting with what is already waiting, and bring the record to the module your check named. Module 5 opens the VOOCS Operating Record, and the 90-Day Install follows it.

Result: never transferred. You answered from the [seat] seat. The company waits on a valuable expert who holds knowledge nobody has yet helped them transfer. This is also a support problem. The repair is a path to greater contribution, not a smaller role: the Hero-to-Multiplier Map in Module 5 names the recurring rescue, its root cause, the judgment to teach, and the higher value work the expert takes on instead. Inside an acquisition or integration, the Key-Person Dependency Map in Module 10 does the same for the capabilities the integration depends on. Read next: the chapter your Bottleneck Check named, then Chapter 5. This is a discussion tool, not a validated score. Where the expert is you, ask what you would do with your time if the work no longer came back to you. One action: for the next two working days, run the 48-Hour Decision Queue Audit on the queue that reaches the expert, counting decisions, not ordinary consultation. Then Module 5 and the 90-Day Install.

Result: kept close. You answered from the [seat] seat. The company waits on work kept close: knowledge withheld, agreed decisions overridden, or successors blocked after the company has kept its side. The book is specific about the order of response: clear expectations, coaching, support, real authority, and time to teach first, then a system that holds them in place. No time to teach is not withholding, and disagreeing in the room or raising a misconduct or risk concern is the system working. A role change comes only when someone keeps undermining that system after the company has done its part and given a fair opportunity to change, decided privately with continuity planned before the handoff whenever practicable. An urgent response to serious misconduct or risk may have to come first. The shared record holds the work; expectations for the individual and any next step for their role belong in the manager's private record. Read next: the chapter your Bottleneck Check named, then Chapter 5, which carries that private record rule. If agreed decisions are being reopened through private conversations, read Chapter 3 and bring the Backchannel and Bypass Record from Module 3. This is a discussion tool, not a validated score, and it never produces a number about a person. One action: for the next two working days, run the 48-Hour Decision Queue Audit on the queue the work keeps returning to, using role titles only. Then Module 5 and the 90-Day Install.

Every result ends the same way because every repair starts the same way: two working days of evidence about what actually waits, then one record, then ninety days of following the work.

Check yourself: sort three cases

Pick the case for each line. The answer and the reason appear when you choose.

1Every discount waits on the VP because nobody ever wrote down what the account leads may approve.
2The engineer who alone knows the restart sequence says there has been no time to teach it this quarter.
3For two quarters the company has given teaching time, a named backup, and coaching, and the manager still overrides the backup's agreed decisions.

Working Session rules

Module 0 has no session of its own. The rules below govern every working session in the course.

Start with the problem. Choose an outcome that matters, find the dependency holding it back, and leave with a decision the team can carry out. A completed worksheet is preparation. The proof comes when the work improves and more people can carry it.
Bring the people who know and own the work: the outcome owner, the sponsor who can authorize the decision, someone doing the work, and someone receiving it. Don't treat silence as consent. Bring evidence: a recent transaction, an unresolved decision, a measured result. A meeting cannot create authority that its participants don't hold.
Use one record. Every session writes into the VOOCS Operating Record. Close with something people can act on: a decision and reason, a next commitment, an owner, a due date, and evidence the receiving person will check. If you cannot decide, name the authorized decider, the missing evidence, and the date the choice returns.
Protect people and controls. Where a tool names a person, the subject is the dependency on that role. Keep misconduct, retaliation, and sensitive performance matters in the appropriate protected process. A faster workflow must still meet its legal, safety, security, financial, and customer obligations.

Evidence of Completion

Module 0 is complete when you can name your dependency, its case, the chapter you read next, and one action. Here is what the course gives you.

Your result shows on screen first, with your first move for this week, a calendar file for it, and the blank audit sheet. Sign in with an email only if you want to keep the result, track the sessions you have held, and build a team view. Two weeks after the handoff, ask the one question from Session 1: did the handoff hold on real work, including an exception? Then use the review questions on days 30, 60, and 90 of the 90-Day Install.