The patterns we all bring to work — and how we work them out

Long before anyone has a job, they've learned what work means, what authority is for, whether rest is earned or stolen, whether their worth is a given or something to keep proving. Those lessons don't stay home. They walk into the office every morning — and most of what gets called a performance issue or a personality clash is really inherited script meeting inherited script.

Start with yourself, because that's where this is honest. There is probably one move you make at work that you didn't choose and can't quite stop. Apologising for things that aren't yours to apologise for. Going quiet, or going sharp, the moment someone senior pushes back. Not being able to hand a task over without redoing it. Taking on more than is yours, then resenting it. Never quite letting yourself be seen taking credit.

None of those is a skill you lack. You can know exactly what you "should" do and still do the other thing, because the response isn't coming from the present. It's coming from a much older place.

Where the script was written

A study from Pepperdine examined how people's family of origin shapes their behaviour at work. The pattern it found was direct: those who grew up under an authoritarian style of power carried it forward into power struggles, pushing back at the wrong moments, avoidance, bulldozing others, or feeling triggered by particular people — behaviours that were adaptive at home and unhelpful at work. Family systems research makes the same point more broadly: how effectively a person operates in any relationship depends partly on how well they've differentiated from the patterns they were raised inside.

The allegiance a child learns toward parents and teachers is, later, quietly transferred to bosses. Most people never notice the handover.

Then there's culture, layered on top of family. Hofstede's research across more than 117,000 employees in over 50 countries mapped how deeply work values vary — how much hierarchy a person expects and accepts, whether they're oriented to the individual or the group, how they handle uncertainty and direct disagreement. In some cultures, openly questioning a manager is healthy engagement; in others it's a breach of respect that early life trained hard against. Neither person is right or wrong. They're running different inherited code, and at work that code collides.

An organization is these patterns, multiplied

Here's the widening. If it's true for you, it's true for everyone you work with — each carrying their own family script and cultural grammar, mostly unexamined. A team is not a clean system executing tasks. It's dozens of inherited patterns meeting each other in real time.

So the manager who can't delegate, the talented person who self-sabotages before visibility, the two colleagues who keep misreading each other across a cultural gap, the high performer quietly burning out to prove a worth they were taught was conditional — these usually aren't competence problems. They're old scripts, running underneath the work, shaping it more than any process does.

Why surface coaching can't reach it

This is the layer skills training and performance metrics cannot touch, because they operate on behaviour, and this lives beneath behaviour. You can teach someone delegation frameworks all year; if handing over control trips a childhood alarm about safety and trust, the framework loses every time. The behaviour only changes when the pattern underneath it is seen, named, and understood as something inherited rather than something true.

That seeing is the actual work. Not advice. Recognition — the moment a person traces a stuck reaction back to where it was learned and realises, often for the first time, that it was never theirs to begin with. From there, choice becomes possible where before there was only reflex.

And it's always a personal choice

Which is why this can't be installed from above like a policy. The person reading this is a person too — inside an organization, yes, but a human first, with their own inherited patterns running quietly through their days. If any of it landed, it landed personally, before it landed professionally.

That's the right order. Someone brings this kind of support to their organization because they first recognised something true in themselves — and wanted, for the people around them, the same chance to see clearly and choose freely. It serves the organization, plainly: fewer collisions, less burnout, more of each person's actual range available. But underneath the business case it stays what it always was — one person deciding that being seen at depth is worth offering to others. A personal choice, made by a human, for other humans.