Legacy is a gift. It’s history, a promise made real again and again over time. But legacy is also pressure, and can feel constricting when it comes time to innovate and re-invent. We’ll explore both here.
I work in growth, which is a fancy word for business strategy and development, positioning, portfolio work. The way I describe it is that I find what’s worth building toward and how. I work with companies to improve how they compete, what and how they sell, what their profile looks like in the market, and how the organization can pull in one direction to make all of this possible. And for the most part, I work with companies that have already existed for a long time and have something to lose. Which is a completely different situation from a startup that is still building legacy.
One question often comes up these days: What does growth look like for something with real history, when everything around it is pushing for loud, fast, and visible, and that’s not part of the original DNA? Not because loud and fast are wrong. They work for some. But they’re a bad fit for something built slowly, around a specific point of view. Chasing that logic can do the opposite of moving things forward. It can hollow out what made the thing worth growing in the first place, usually quietly, and usually under the banner of progress.
There’s a distinction worth making here. Heritage is not legacy. Heritage is history, but also reputation built over time, the proof points, the story of how we got here. Legacy is what that heritage does in the market. What it triggers. How it gets woven into practice, expectation, or culture. It’s heritage put to work, made relevant, and given a role.
You can have deep heritage and no real legacy. The difference is intention, but also adoption. Whether people inside and outside the organization still know what to do with it.
But nobody decides to abandon what made something great. It erodes over time. And it’s a big fat red flag to management, because erosion rarely looks dramatic while it’s happening.
It happens when precision slips. What started as a sharp point of view becomes a vague gesture. Then generic. It also happens when legacy is treated as a given, instead of something that has to be proven continuously. Especially in established companies, where reputation can easily be mistaken for relevance. But legacy isn’t a stored asset. It’s a living signal of commitment: to the product, the standard, the way of doing things that made the thing matter in the first place.
Take values. Most organizations with real history have them. But values written in one era, by one generation, for one set of problems, don’t automatically speak to the next. When a younger team member joins and can’t see how the founding principles connect to the decisions being made today, the legacy suddenly has a shelf life and stops being theirs. They work within it without feeling part of it. That’s a slow leak. Not because the values are wrong, but because they’ve stopped helping people interpret what good judgment looks like now.
Or take culture. The original culture of something is often implicit, carried by the people who lived it, expressed through instinct rather than instruction. When the organization grows, or the original builders move on, that culture doesn’t transfer automatically. What fills the gap is usually a diluted version: the surface behaviors without the underlying drive. It becomes words without weight, plastered on empty office walls. We all know those workplaces. The language is still there, but the standard underneath it has gone soft.
Legacy needs to be reinterpreted with every generation. That’s how continuity works. That’s how legacy remains relevant.
That’s the part people sometimes resist, because reinterpretation sounds suspiciously close to compromise or erosion. But it isn’t. It’s how continuity works. New generations inside an organization don’t just need to understand the legacy. They need room to bring something to it: different expectations, different ways of working, different things they’re willing to stand behind. If legacy can’t metabolize that contribution, it calcifies. It becomes a story about the past rather than a force in the present.
So you have to tend the fire deliberately. Revisit the original attitude and ask what it actually means now for the people doing the work today. Not in theory, but in practice. In decisions, in standards, in trade-offs, in what gets protected and what gets challenged. Every era brings its own interpretation. That’s how living things stay alive.
Evolution isn’t a threat to legacy. It’s often the proof that the core was strong enough to travel.
And that also means accepting that some of what made something great in one chapter becomes dead weight in the next. The instinct is to protect all of it, because it all feels meaningful. But that’s sentiment dressed up as strategy.
Not everything inherited is essential. Some things are principle, while others are just precedent.
Real stewardship means being willing to let go. The question isn’t only what did this stand for? It’s what does that same commitment actually demand today? Sometimes the answer looks nothing like the original expression. That can feel disloyal if people have confused the essence with the artefacts around it. But keeping everything is not respect. Often it’s avoidance. Legacy asks for — and deserves — sharper judgment than that.
Growth for something with real legacy isn’t about protecting the past or chasing the present. It’s about staying faithful to something real while being honest about what that faithfulness requires now. Which usually means keeping the standard, but modernizing the script around it.