Building Legacy

Ask almost any founder about legacy, and you’ll usually get an answer about reputation. What people will say. What the company stood for. Whether the thing mattered.

We treat it as an operating question instead, because it behaves like one. Building Legacy is the fourth phase of our People, Process, Culture model, and it asks something the first three phases can’t. People build the capability in individuals. Process gives the capability to live somewhere. Culture is what emerges when enough people run the process under the same pressures for long enough. Building Legacy asks whether any of it regenerates once the person who built it stops showing up.

That question has a specific commercial name. Buyers call it key-person dependency, and they price it. A multiple is a forecast about repetition, and repetition is the thing this phase either produces or fails to produce.

Why this phase gets skipped

Nothing in it shows up this quarter.

The first three phases, crucibles, establishment, and development, produce visible output. Someone gets better at a job. A handoff stops failing. A team starts operating the way the leadership team hoped. Building Legacy produces no observable result while the leader is still in the building, because its only real test is an absence, and the person most motivated to run the test is the one who cannot be there to see it.

So it gets deferred, usually until the exit conversation, at which point it’s a diligence finding rather than a program.

What actually reproduces

A pattern persists in an organization for one reason. Something in the environment keeps regenerating it. Not memory, not commitment, not the founder’s continued attention. Regeneration.

That’s an uncomfortable frame for leaders who like the idea of lasting impact, because it removes the author from the story. The behaviors that outlive you will do so because you built something that makes them happen again next Tuesday without your involvement, and the behaviors that die will die quietly, over about two quarters, while everyone assumes they’re still in force.

Three questions tell us whether a given behavior will survive.

• Does the behavior have a home outside a person?Most standards in growing companies live inside somebody’s head and are expressed through their judgment. That works, and it works well, right up until that person is on leave, promoted, or gone. A behavior has a home when it’s attached to something structural. A recurring meeting nobody can cancel. A gate in the workflow that won’t advance without the step. A number that appears on a report, whether or not anyone asks for it. The test is whether the behavior would still happen if the person most associated with it went dark for 90 days.
• Does the organization notice when it stops?This is the one almost everybody fails, and it’s the difference between a standard and a habit.I ran after-action reviews in the infantry for years. The thing that made them work wasn’t the quality of the discussion or anyone’s commitment to learning. It was whether the AAR happened, whether the mission went well or badly, whether the leadership wanted one, and whether anybody had time. It was scheduled. That’s the entire mechanism. Because it was scheduled, a lesson learned by one squad was passed on to the people who replaced it, and the knowledge outlived every individual who learned it.Detection is what turns a good practice into a durable one. A behavior with no detection layer degrades invisibly, and by the time the degradation is obvious, nobody connects it to a cause 18 months back.
• Do the next leaders get selected on it?This is the reproduction step, and it’s the one that decides the outcome. The factors a company promotes people on become what the next generation of managers optimizes for, and they’ll optimize for it whether or not it appears in the values deck. If the behavior you care about most has never once been the reason someone got promoted, the organization has already priced it accurately.We find this is the fastest read available on where a company is actually heading. Look at the last five promotions and name, honestly, what each person was rewarded for. That list is the culture in three years.

Naming the failure before reaching for the fix

When a behavior stops holding, the reflex is to go talk to the people. Sometimes that’s right. Usually, it isn’t, and the wasted quarter is expensive.

Problem-type diagnosis is worth running first. An operational failure means the work is genuinely undoable as designed, and no amount of conversation fixes a broken workflow. A behavioral failure means individuals can do it and aren’t, which is where coaching earns its keep. A structural failure means the org chart, the incentives, or the reporting lines actively work against the behavior, and good people will lose that fight every time. A cultural failure means the behavior contradicts something the organization has been reinforcing for years, and it will require a longer horizon than the others.

Most leadership teams can’t tell them apart from the inside, default to the behavioral fix, and conclude after two quarters that their people are the problem.

The uncomfortable part

Building Legacy asks a leader to put real effort into making themselves unnecessary, at a moment when being necessary is what generates the most obvious value.

That trade is hard to take at the individual level and easy at the ownership level. The founder who cannot leave for two weeks is the same founder whose business gets a lower valuation at exit, and the two facts have a single cause. Every hour spent moving a behavior out of your own judgment and into the structure is an hour that shows up twice, once in the quarter you stop firefighting and once in the multiple.

Pick one behavior you’d be proud to have outlasted you. Run the three questions on it this week. If the honest answer to any of them is no, you’ve found the work.