The Origin Code: How a Handful of Childhood Rules Still Run Your Executive Operating System

Last week, I told you we were going back to the source. Not because your outputs weren't the real problem, but because auditing the outputs alone was never going to be enough. You can rebalance the Resentment Ledger, retire the Existential Perfectionism Trap for a quarter, and still watch the same deficit rebuild itself the moment the pressure returns - because the tools were addressing the interface, not the operating system underneath it.

This article provides the first diagnostic in that operating system: the Origin Code, the set of implicit rules your nervous system wrote about safety, worth, and belonging long before you held a job title, and the mechanism by which those rules keep executing, unexamined, in every room you enter today.

From Childhood Environment to Executive Instruction Set

In clinical terms, the Origin Code is best understood as implicit relational memory - the procedural, largely non-verbal learning a child absorbs about what keeps them safe, loved, and acceptable within their specific family and social environment. Unlike a belief you could argue yourself out of over a coffee, implicit memory isn't stored as a sentence. It's stored as a reflex. You don't remember deciding that your worth was conditional on achievement; you simply flinch, decades later, whenever a quarter closes without a win.

Every child in every environment writes some version of this code, because every child is, structurally, dependent on the adults around them and highly motivated to work out the rules that keep the relationship intact. The specific content of the code, however, is entirely local. It's compiled from whatever your particular environment rewarded, tolerated, or punished. A child raised by an anxious, high-achieving parent might write: performance equals safety. A child raised in a chaotic household might write: hypervigilance equals safety. A child who was told, directly or through a thousand smaller signals, that a core part of who they were needed to be managed, minimised, or hidden, writes something considerably heavier.

The problem executives run into decades later isn't that the code was badly written. For the environment it was written in, it was frequently the single most intelligent adaptation available. The problem is that the code has no expiry date. It doesn't check whether the current environment - a board seat, a leadership team, a life you built yourself - still requires the same rule. It just runs, silently, in the background, the same way it always has.

Why Queer Leaders Compile Under Higher Stakes

If you're a queer executive, I want to be precise about why this carries extra weight, because I don't say it to generate sympathy. I say it because it changes the diagnostic.

For many LGBTQ+ leaders, the origin environment required a much higher-stakes version of this same process. The question a child is unconsciously solving isn't just "what makes my caregivers proud" - it's frequently closer to "what makes it safe for me to exist here at all." When part of your identity is met, even subtly, with confusion, discomfort, or outright rejection, the code you write in response tends to be stricter, more comprehensive, and installed earlier than the code your straight, cisgender peers were writing at the same age. Achievement becomes a shield. Competence becomes camouflage. Vigilance becomes a full-time background process, because in that original environment, it frequently needed to be.

None of this makes you broken, and none of it was a flaw in your design. It was, as I said last week, a reasonable response to real risk. But a script written for survival in a hostile childhood environment is rarely the same script an organisation needs from you as its most senior leader. The tragedy isn't that you wrote defensive code. It's that almost nobody ever told you the code was allowed to be rewritten once the threat that required it had gone.

Locating Your Own Code: What to Look For

You don't need a six-month excavation to start this work, and I'd actively discourage you from treating it as one. What you need is precision about three things:

1. The Rule
The specific, usually one-sentence instruction the code is running - "I am only safe when I am useful," "Needing help is evidence I don't belong here," "If I am visible, I will be punished for it."

2. The Trigger
The exact modern-day condition that activates the old code - a delayed reply from your board chair, an unstructured hour in your calendar, a room where you are the only person like you.

3. The Original Evidence
The early experience, or more often the repeated pattern of small experiences, that made the rule feel like the only reasonable conclusion available at the time.

Most executives I work with can name the trigger almost immediately. Very few, on their first attempt, can name the rule with any precision, and almost none arrive already able to connect it back to the original evidence. That gap is exactly why this work is diagnostic rather than instinctive - you cannot audit a rule you've never actually stated out loud.

Two Ways to Start the Rewrite

Precision requires structure. These two exercises are designed to move you from a vague sense of "I always do this under pressure" to a stated, examinable rule. This is a time where radical self-honesty is going to be helpful.

The Rule Extraction Exercise

Execution
Choose one recurring pattern - a decision you always make the same way under pressure, regardless of the specifics of the situation. Write down the exact internal sentence that fires right before you act. Not the polished, board-ready version. The raw, private one.

Action
Test that sentence against a single question: is this rule true of my current environment, or was it true of the environment I learned it in? Write both answers down separately.

Target
A single, stated rule you can recognise firing in real time, rather than a vague pattern you only notice in hindsight.

The Environment Delta Check

Execution
For the rule you've extracted, list the specific features of the original environment that made the rule necessary - who held the power, what the actual consequence of breaking the rule was, how much choice you genuinely had.

Action
List the equivalent features of your current environment against each one. Be specific about where you now hold authority, resources, or exit options you did not have as a child.

Target
A clear, evidenced case for why the rule's original justification no longer holds - considerably more durable under pressure than simply deciding to "think positive."

Reclaiming the Source Code

None of this is about rejecting the child who wrote that code. They were solving the problem as it appeared to them, with the only tools they had, and they solved it well enough that you're reading this as a senior leader rather than someone who didn't make it out. The work now is not demolition. It's a deliberate, adult rewrite - keeping the parts of the code that still serve you, and retiring the instructions that were only ever built for a room you no longer stand in.

Over the next three editions, we'll trace exactly how this code shows up in your specific leadership behaviour: the Over-Functioning Mandate that tells you rest must be earned, the Blame Node that routes every organisational failure back through you first, and the Silent Operator strategy of staying so competent and so quiet that nobody looks too closely. Each one is a symptom. This week was the source.

Schedule a confidential consultation to find out how I can help you locate and rewrite the origin code still running your leadership from the inside.