You’ve seen this. A founder builds something that works. Tight controls, every spend approved, every hire filtered through them personally. The company survives two cash crises. He knows where every euro is at every moment.
Then he starts a second company. Same founder. Same instincts. Same controls.
Within eight months, his senior team is gone.
Not fired. Left. They came for the autonomy the role promised. They found themselves waiting days for approval on decisions that should never have needed a signature.
He didn’t become a worse leader. He took a mechanism that kept one organism alive and transplanted it into a completely different one.
That is not strategy transfer. That is context blindness.
Every operational decision that works is a survival mechanism.
It did not emerge from a theory. It emerged as a response to a specific system at a specific moment: the capital pressure, the stage, the team, the market, the founder’s psychology, the scars from the last crisis.
Strip those conditions away, and what you have is not a practice. You have behavior without the logic that made it rational.
This is what gets copied. The behavior. Always the behavior. Never the conditions that produced it.
Why does the illusion persist?
Four things sustain it.
Media compresses complexity into a story. “Company X does Y” travels across LinkedIn and conference stages stripped of every condition that made Y rational. The behavior gets published. The system that produced it does not.
Outcome bias does the rest. Success gets attributed to what is visible: the management style, the org structure, the decision ritual. Not to what is invisible: the specific trust between that team, the timing, the investor patience, the market window that happened to be open. None of that makes it into the writeup.
Founder mythology amplifies it further. When one person runs multiple ventures, observers assume the same playbook applies. It does not. A founder does not operate from a fixed philosophy. They react to constraints. The constraints are never the same twice. What looks like a contradiction from the outside is an adaptation from the inside.
And the consulting industry has no structural incentive to correct any of this. Selling repeatable frameworks scales. Diagnosing context does not. A framework you can package and present in a deck is worth far more commercially than the honest answer, which is: it depends on what organism you are working with.
Each company runs on a different operating system.
That OS is shaped by the founder’s psychology, the capital model, the risk tolerance, the governance structure, the market pressure it operates under.
Practices are applications running on top of that OS.
Copy the application without matching the OS and you do not get the result. You get the side effects.
A flat structure copied from a well-capitalized technology company into a manufacturing business with thin margins and a workforce that needs clear task definition does not produce innovation. It produces chaos. The application is incompatible with the underlying system.
What actually transfers is not the practice. It is the decision logic behind it.
Before importing anything into your system, the real questions are not “should we do what company X does?”
They are: what problem was that practice solving? Under which constraints did it emerge? What trade-offs did it introduce to make it work? Does our system share those conditions?
Run those questions, and you will rarely arrive at the same answer as the company you are looking at. That is not a problem. That is the point. If your system is different, your answer should be different.
This is closer to engineering than management theory. You are not looking for a model to copy. You are reverse-engineering a solution to understand whether your problem is actually the same one.
One distinction worth making clearly.
Some principles do not require context to justify. Financial transparency. Clear accountability. Fast decision loops. These hold across systems.
Context does not eliminate fundamentals. Anyone using “our company is unique” to avoid operational discipline is not applying this thinking. They are hiding behind it.
The distinction: context shapes implementation. It does not eliminate what must be true in any functioning system.
The real failure in most business advice is not that it is wrong.
It is that it describes visible behavior and skips the structural conditions that made that behavior rational.
The behavior was the output.
The conditions were the cause.
The conditions are never on the slide deck.
