On Legacy, Identity, and How We Got Lost

We do not build legacy. We either live in a way that creates it, or we do not.

Nobody in the history of childhood has ever paused mid-game to consider what they might be leaving behind. Children do not play with one eye on posterity. They play because the game is right in front of them, because their friend is right there, because the problem of how to build something in minecraft, win the race, or include the kid standing on the side is genuinely urgent and worth all of their attention.

And yet, without intending any of it, they are doing something that looks remarkably close to what the most thoughtful adults mean when they talk about legacy at its best. They are in genuine relationship. They are catalysing change in each other. They are failing constantly and continuing anyway. They are absorbed in the problem in front of them without performing for an audience that is not there.

At some point we wean ourselves off this.

And then, for much of adult life, we spend enormous energy trying to find our way back to it, usually through language, frameworks, values statements, strategic plans, and all the other structures that would have made no sense to us at seven years old.

This is where the concept of legacy starts to become slippery. Because what we often mean by it is not what children are doing at all. What we often mean is something more self-conscious. Something shaped by time, identity, mortality, and the wish that something of us might remain.

But the playground raises an uncomfortable possibility.

What if the deepest form of legacy was never something to construct later, but something we already knew how to do before we learned to observe ourselves doing it?

The Wrong Problem

A lot of what gets called legacy is ego working quite hard in sophisticated clothing.

The desire to be remembered, to matter, to have your ideas persist, to leave something that outlives your involvement, none of that is inherently dishonest. It is deeply human. But it is worth being honest about what is driving it. At its core, it is often a response to mortality and insignificance dressed in the language of contribution.

Underneath that, there is often something older and more vulnerable. Not ego exactly, but the inner child asking much simpler and more painful questions.

Was I enough? Did I matter to the people close to me? Was I seen? Did I belong?

These questions do not disappear when we grow up. They just become more elaborately managed. They get routed through careers, achievements, credentials, artefacts, intellectual property, influence, and the careful construction of a life that appears to prove something.

So you end up with people genuinely trying to do meaningful work, trying to orient toward impact, toward change in others, toward something that lasts, while at the same time the ego is quietly trying to secure continuity, and underneath that again some earlier self is still just trying to finally feel sufficient.

All three can be operating at once.

All three can occasionally pull in different directions.

And that is part of what makes the whole idea of legacy so difficult to think about cleanly. Because the question is not just what am I trying to leave behind. It is also, for whom? Which part of me is solving for this? The conscious self? The ego? The part that never quite stopped waiting to be chosen?

Most of what people deliberately try to leave behind is not what ends up mattering.

And a great deal of what genuinely persists was never planned at all. It was simply the residue of how someone consistently showed up.

That is worth sitting with for longer than is comfortable. Because it suggests that what many of us call legacy may actually be an attempt to solve the wrong problem, or at least an attempt to solve a human problem with the wrong materials.

The Hamster Wheel of Proof

There is another tension here, and this one is less philosophical than structural.

Much of the work that pays the bills produces artefacts. Deliverables. Reports. Frameworks. Slide decks. Systems. Intellectual property. Things that can be shown, explained, transferred, counted, priced.

In one sense, those things matter. They are often part of how change gets facilitated. They make work legible. They create continuity. They help other people pick something up and carry it forward.

But the artefact itself is rarely the legacy.

More often, it is scaffolding.

Something temporary that had to exist for the real thing to happen.

The real thing is the shift in how someone sees a problem. The moment a team starts operating differently because of a conversation that happened at the right time. The person who goes on to do something significant because someone else held a line, opened a door, or named something they could not yet name for themselves.

That is the part that persists.

And it is almost entirely untrackable.

It does not sit neatly in a portfolio. It is difficult to invoice for. It rarely lends itself to tidy proof.

This is where survival complicates everything.

Because when survival depends on output, it becomes very easy to conflate who you are with what you produce. The asset justifies the invoice. The invoice supports continuity. Continuity starts to feel like evidence that the work mattered. And before long, you are no longer simply producing scaffolding, you are organising your sense of self around it.

This is the loop.

You build the artefact to survive. You survive by building the artefact. And somewhere in that cycle, it becomes harder to tell whether you are still serving the actual thing or merely accumulating proof that you existed.

We build the thing to survive, and then slowly mistake it for the work itself.

That is why so many smart, thoughtful people end up caught on a kind of hamster wheel of assets and IP. Not because they are shallow. Not because the work is false. But because the conditions under which most meaningful work happens are structurally biased toward the countable and the demonstrable, even when the deepest value of the work lives somewhere else entirely.

This is not a failure of character.

It is what pressure produces.

And perhaps part of what makes legacy so difficult to work toward deliberately is that it requires a degree of detachment from the very outputs your survival depends on. Not indifference. Not refusal. You still have to produce them. But a kind of dual awareness. Doing the work seriously while holding it lightly. Making the thing, while refusing to confuse it with yourself.

Orientation, Not Destination

If legacy is not something you can reliably build through accumulation, what is it?

The most useful framing may be to think of it not as a destination, but as an orientation.

A North Star.

Not a fixed outcome, but a question sitting underneath everything else, quietly shaping what you notice, what you prioritise, what you are willing to let go of, and what you refuse to confuse for the real thing.

Lending from a design perspective, the question might be this:

What is the problem I am actually trying to solve?

It sounds simple, but it is not.

Because most people are not solving for the thing they say they care about. They are solving for recognition. Security. Continuity. Control. Proof of existence. They are optimising for output, accumulation, and legibility without ever stepping back to ask whether any of those things touch the actual problem they believe they are here to address.

And when you ask that question honestly, legacy becomes much less flattering.

What would be different in the world, or in the people around me, if I did this work well?

What would remain if my name came off it?

What if the actual thing I am here to solve cannot be measured in the same units that make my survival feel secure?

That is the tension.

The North Star does not resolve it. It does not magically remove the need to produce, to earn, to demonstrate value, or to keep moving. But it gives you somewhere to return when the noise starts to take over.

Not a productivity tool. Not a neat answer.

A calibration.

A way of noticing when you have started solving for continuity and proof instead of the thing itself.

The Way Back Is Not Forward

What is striking about the child at play is that they do not need this calibration.

They have not yet learned to split attention between experience and evaluation. They are not managing how they are perceived. They are not building a case for their own significance. They are not producing for an imagined future audience. They are simply in relation, in motion, in problem-solving, in experiment, in play.

That does not make childhood ideal or uncomplicated. But it does reveal something.

The child at play is not trying to build legacy. They are doing something that maps remarkably closely onto the deepest version of what we later claim to want. They are present with real people. They are solving real problems, even if those problems are small or imaginary. They are trying things, failing, adapting, continuing. They are influencing each other all the time without naming it as influence.

The kid who invents the game, keeps the group together, includes the child on the edge, changes the shape of the afternoon. That is relational impact. That is influence. That is the substance of legacy before it becomes self-conscious.

So maybe the move into adulthood is not simply that we begin to care about legacy.

Maybe it is that we become capable of imagining ourselves from the outside. We begin projecting forward. We become aware of endings. We encounter mortality, responsibility, scarcity, competition. Identity becomes something we construct rather than simply inhabit. And from there, much of adulthood becomes an attempt to recover something we once knew how to do instinctively, now under very different conditions.

That is why the way back is not forward.

It is not a matter of constructing a better legacy strategy. It is not solved by becoming more intentional in the managerial sense, or more articulate about values, or more prolific in what you produce. In fact, those things can sometimes create yet another layer between you and the work itself.

The way back is stranger than that.

It is a return, not to childhood, but to a way of being in which presence is not constantly interrupted by self-observation. A way of working in which you are not forever translating experience into evidence. A way of relating in which the real people in front of you matter more than the story you will later tell yourself about what you built.

So perhaps the question is not whether you are building a legacy.

Perhaps the question is whether you are still capable of being fully in the work and with the people beside you without constantly converting it into proof.

Not performing. Not producing. Not accumulating evidence that you were here.

But actually being in it, with your full attention.

Because if that is true, the legacy tends to take care of itself.

If this is a conversation that interests you, and a space you’d like to explore more deliberately, feel free to reach out via info@dialecticalconsulting.com.au or contact me via LinkedIn.