Every founder can name them: the two or three people who know where everything is. The operator who reconciles the numbers nobody else can find. The account lead whose head contains the client history. The business is proud of these people, and it should be. But it is also quietly taxed by them, because everything routed through a hero queues behind a human.
Here is the uncomfortable arithmetic. Heroics feel free because they do not appear on an invoice. But they compound like debt: every new client, channel and product adds load to the same few heads, and the business’s real capacity ceiling becomes the sleep schedule of its most competent person. Worse, heroics hide the system’s true shape. When you ask "how does onboarding work?", the honest answer in a heroic business is "ask Dana". Which means the process does not exist; a person does.
How it actually works #
Measure the tax before fixing it. For one ordinary week, have your two most load-bearing people keep a simple log: every task that exists only because systems do not talk to each other, or because knowledge lives in their head instead of somewhere findable. Re-keying, chasing, reconciling, re-explaining. Do not optimise anything yet. Just count.
The log converts a vague cultural worry into an engineering brief. Every recurring entry is one of two things: a missing connection (route it to systems, which is where practical automation earns its keep, quietly, on unglamorous work) or a missing artefact (write it down once, properly, where the next person can find it). Sequence by frequency, fix the top three, re-run the log in a month. This is what "rebuilding the engine" actually means at the operations layer. Not a reorg, not new tools, but the deliberate retirement of heroics.
Running it on Monday #
The point is not to make heroes unnecessary. It is to spend them properly: on judgement, on clients, on the new thing, instead of on being the glue.
Heroes are how a business survives. Systems are how it grows.