The Signal
The highest-risk person in a growing company is often the person everyone praises most. The rainmaker who closes weird deals. The operator who fixes every delivery fire. The product lead who always knows which customer complaint deserves action.
Their output is real. The problem starts when the company treats that output as a personality trait instead of an operating pattern. Once that happens, the business stops building a system and starts protecting an exception.
Why this matters now
Managers are being asked to carry more weight with less energy. Gallup's 2026 workplace data puts global manager engagement at 22%, down from 31% in 2022. Employee engagement sits at 20%. That means the layer responsible for turning founder intent into daily work is already stretched.
In that environment, hero-dependent performance breaks faster. A founder can usually see the difference between a brilliant exception and a broken process. A depleted manager cannot always afford that nuance. They keep routing hard work to the trusted person, which makes the trusted person more central, which makes everyone else less capable.
The better move is to extract the actions behind the performance. Do not copy the person. Copy the sequence. What do they notice before others do? What customer signals do they respond to? Which decisions do they make without escalation? Which internal rules do they bend because the current process is too slow?
That last question matters. Sometimes the standout performer is not special because they ignore process. They are special because the process is incomplete. If the only way to produce the right customer outcome is to work around the system, the founder does not have a people problem. The founder has an operating design problem.
Stop mistaking exceptions for excellence
Founders often protect the person who creates chaos because the numbers look good. Sales tolerates bad handoffs because the rep closes. Delivery tolerates undocumented fixes because the client is saved. Product tolerates political activity because the person seems influential internally.
That bargain gets expensive. The team learns that process is optional if results are loud enough. Managers lose the authority to coach. Customers get whatever version of the business happens to show up that day.
There is another trap: expecting employees to care like founders. Most people are not driven by ownership hunger, existential pressure, or the thrill of building something from zero. That is normal. A role system should not require every employee to borrow the founder's nervous system. It should make the work clear enough that different motivations can still produce the right customer outcome.
Build the role, not the myth
A useful role system has four parts. It names the outcome the customer would feel. It lists the repeatable actions that drive that outcome. It removes the exceptions that make the process optional. It gives the manager a way to understand what the person actually values.
For a service business, that might mean turning a rainmaker's invisible sales judgment into accountabilities around qualified demand, clean handoffs, and client retention. For a SaaS company, it might mean separating product work that improves customer outcomes from internal relationship work that only creates visibility. For a D2C brand, it might mean turning a strong creative or CX operator's instincts into a playbook tied to profitable demand and repeat purchase.
The point is not to flatten exceptional people. Strong performers should still get room to do strong work. The point is to stop letting their undocumented behavior become the only way the company performs.
The first move
Choose one role where everyone knows the company is leaning too hard on one person. Sit with the last five wins from that role. Write down the action before the visible result, the customer signal that triggered the action, and the decision the person made without waiting for permission.
Then write the role scorecard in customer language. Not internal activity. Not politics. Not who seems busy. What outcome does the customer experience because this role exists?
The move this week
Run a 30-day experiment. Pick five actions from the standout performer and teach them to the team. Remove one exception that only the standout person gets to use. Add one weekly manager review focused on motivation, capability, and the customer outcome.
If the team can repeat even part of the person's best work, you reduced key-person risk. If they cannot, you found the real constraint before it became a resignation, a bad quarter, or a customer problem.