Soma Kiran Gonella
Back to Writing
Organizations·August 10, 2026·5 min read

Organizational inheritance: the practices nobody can explain

Soma Kiran Gonella
Soma Kiran GonellaHR Business Partner · Author · Builder of SigmaGo
"There is a story, sometimes told in negotiation workshops, about a mother who always made small pancakes even though her pan was large. When her daughter asked why, the mother said that is how my mother taught me."
There is a story, sometimes told in negotiation workshops, about a mother who always made small pancakes even though her pan was large. When her daughter asked why, the mother said that is how my mother taught me. The daughter asked the grandmother. Same answer. Finally the daughter found the great-grandmother. The old woman laughed. We had a small pan, she said. That was all.

Three generations following a practice whose reason had expired before the second generation was born. The small pancakes continued. The small pan was gone. Nobody asked, because the practice was inherited, and inherited things do not invite questions. They just continue.

Every company past a certain size is running on some version of this. I call it organizational inheritance, and it is the lowest form of institutional continuity.

How inheritance forms

A company's head of operations had been there for seven years. She was not the founder, not someone whose departure would make a headline. She was the person other people asked when they needed to understand why things were the way they were.

She resigned. For the first two weeks, nothing seemed wrong. Then the questions started.

Why does every purchase above two lakhs require three levels of sign-off when the company's average transaction is now fifteen lakhs? Nobody knew. She would have known. The threshold was set in the company's first year, when two lakhs was a significant commitment. The business had grown tenfold. The threshold had not moved. Every mid-size purchase now took three days longer than it needed to, routed through two approvers who added no judgment because the amount was routine at the company's current scale.

Why does the Monday leadership meeting include a thirty-minute review of open customer complaints when the company now has a dedicated support team with its own escalation process? Nobody knew. She would have known. Three years ago, before the support team existed, the founder wanted visibility on every unhappy customer. He asked for the review. The support team was hired six months later. The review continued. Thirty minutes of seven senior people's time, every Monday, covering ground that a team was already covering, and nobody had questioned it because it had always been on the agenda.

Why does the quarterly board deck include a twelve-slide section on regional revenue breakdowns when the board has repeatedly said they only care about the consolidated number? Nobody knew. She would have known. The regional breakdown was added after a board member asked a specific question about the southern region in 2021. The question was answered. The breakout stayed. Two days of finance time every quarter, building slides nobody reads, because three years ago somebody asked a question once.

Each of these was a decision, made once, by a person with authority, for a reason that was real at the time. The decision happened in a call, a meeting, a quick conversation. The practice it created survived. The reasoning did not. What remained was inheritance: the company doing something because it has always done it, enforced by inertia, unchallengeable because the basis was never recorded.

Why inheritance is invisible

The dangerous thing about organizational inheritance is not that it exists. Every company has it. The dangerous thing is that it is indistinguishable from deliberate practice.

From the outside, and from the inside, a company following an inherited practice looks exactly like a company following a well-reasoned one. The three-level sign-off looks like governance. The Monday complaints review looks like founder engagement. The regional breakout looks like board diligence. Nobody can tell the difference between a practice that is followed because it was decided and one that is followed because it was inherited, unless somebody stops and asks: why do we do this?

That question is surprisingly rare. Not because people lack curiosity. Because asking it implies you do not know, and not knowing something the company has been doing for years feels like a confession of ignorance rather than an act of diligence. So the practices continue unchallenged.

What inheritance costs

The cost is not any single practice. It is the accumulation of dozens running on autopilot, each carrying a cost that may or may not still be justified, with no way to evaluate which.

The three-level sign-off on purchases above two lakhs generates hundreds of unnecessary approval cycles a year at a company where two lakhs is now routine. The Monday complaints review costs three and a half hours of senior leadership time every week, fifty-two weeks a year. The regional board slides cost eight days of finance time annually, producing content the board has said it does not use.

A new COO joins the company. She walks through the processes and finds thirty things she cannot explain. She asks. Nobody knows. She is told, in various forms, that is how we have always done it. She can either accept the inheritance, which means carrying costs she cannot evaluate, or challenge it, which means fighting battles without evidence, because there is no record to examine and no original decision to revisit.

Most new leaders accept the inheritance. They make their changes at the margin and leave the inherited core untouched, because unwinding a practice whose purpose is unknown feels riskier than maintaining one whose cost is invisible.

And so it compounds. Each year, more practices. Each departure, more reasoning lost. Each new arrival, more inheritance accepted without examination. The company is not getting worse. It is getting heavier. Carrying the accumulated weight of every decision that was made and not kept, every reason that expired and was not retired, every practice that outlived its purpose and was not questioned.

The small pancakes, made on a large pan, in a kitchen that forgot why they were ever small.

The first step

Organizational inheritance is the starting point, not the destination. The next post looks at what happens when companies move one level up, from practices nobody can explain to knowledge that exists somewhere but takes an hour of archaeology to find. That is a different problem, with its own costs, and its own kind of fragility.

But the first step is simpler than either. It is asking the question that inheritance discourages: why do we do this? Not as a challenge. As a genuine inquiry. And discovering, in many cases, that the answer is a small pan that was replaced years ago.

Part of The Other Books, an ongoing series on the decisions companies forget.
Tags:#Organizational Inheritance#Policy Drift#Culture#Institutional Habits
Found this perspective valuable?
Soma Kiran Gonella

About Soma Kiran Gonella

HR Business Partner with 11+ years of experience across fintech and automotive R&D environments. Author of The Other Book and builder of SigmaGo, exploring how organizations can turn decisions into institutional intelligence.