The Inherited Assumption: Why Organizations Keep Doing Things No One Would Choose to Start Today
When operational practices outlive the conditions that justified them, organizations spend real capacity sustaining work that serves a problem which no longer exists.

Every organization carries a set of activities that no one explicitly decided to continue. They persist not because anyone evaluated them recently and concluded they remain valuable, but because stopping them requires a decision and continuing them requires nothing at all. This asymmetry, where inertia favors continuation and discontinuation demands justification, is one of the quietest capacity drains in otherwise well-managed organizations.
The origin of these practices is rarely negligence. Most were rational responses to real conditions. A reporting cadence was created because a prior system lacked visibility. A review layer was added because a specific failure had occurred. A cross-functional sign-off requirement appeared after a coordination breakdown. Each made sense when introduced. The problem is not that they were created. The problem is that organizations do not have a natural mechanism to retire them when the original conditions change.
Why Discontinuation Rarely Happens Organically
In most organizations, starting something and stopping something are not symmetric acts. Starting a process, meeting, or role typically involves visible sponsorship, a stated rationale, and some form of approval. Stopping something requires someone to raise the question, which is socially awkward when the activity has identifiable stakeholders, and organizationally risky when the person raising the question might appear to be undermining a predecessor's decision or dismissing a current colleague's work.
This means the people closest to an outdated practice have the most information about its low value and, often, the fewest structural incentives to say so. A team that has quietly adapted around a cumbersome approval process will frequently absorb the friction rather than challenge the process, particularly when challenging it requires escalating to someone who originally designed it.
Senior leaders rarely have visibility into which practices have outlived their purpose because the reporting that reaches them emphasizes activity outputs, not whether those activities are still load-bearing. A weekly summary arrives. The meeting still appears on the calendar. The process still runs. None of these signals reveal that the original justification dissolved two years ago.
What Inherited Assumptions Actually Cost
The cost is not primarily financial, though the financial component is real. The deeper cost is attentional and organizational. When capable people spend meaningful portions of their week on work that no longer produces value, the capacity lost is not recoverable by adding headcount. It is consumed invisibly, and it crowds out the discretionary work, the thinking, the cross-functional collaboration, that organizations consistently say they want more of but rarely protect time for.
Consider a hypothetical scenario that is common in practice: a compliance review step that was added after a regulatory change several years ago. The regulation was later modified in a way that eliminated the original requirement, but the internal review step was never retired. The team running it has developed expertise around it. It appears in the process documentation. New staff are trained on it. The absence of any visible failure creates no pressure to examine whether it is still necessary. This is not a contrived example; it is a structural pattern that repeats across functions and industries.
The cumulative weight of several such practices across a large organization is not trivial. Even if each individual instance consumes modest time, they collectively represent organizational capacity operating against no live objective.
A Practical Approach to Surfacing Inherited Practices
The most effective leaders approach this not as a cost-cutting exercise but as a hygiene practice, analogous to how healthy organizations handle technical debt. The question is not whether any given practice has value, but whether it has value that is proportionate to what it actually consumes today, given conditions today.
One practical suggestion is to introduce a periodic review specifically framed around origin conditions rather than current outputs. The guiding question is not whether a practice is being executed well, but what problem it was designed to solve, and whether that problem still exists in the same form. This distinction matters. A practice can be executed efficiently and still be solving for a condition that has changed.
A second suggestion is to create low-friction channels for people close to the work to surface these observations without the social exposure that often prevents them from doing so. When the path to raising a concern runs directly through someone who has ownership over the practice in question, the concern frequently goes unspoken. Organizations that want this information need to design pathways that are genuinely safe and genuinely heard.
A third suggestion, particularly relevant to leaders inheriting established teams or operating units, is to treat the first six months in a role as an explicit window for asking why practices exist, before the answer becomes obvious and the question disappears. New leaders have a brief period of legitimacy to ask foundational questions that tenured leaders can no longer ask without implied criticism. That window is an asset worth using deliberately.
The Governance Dimension
Organizations that manage this well tend to share a specific structural feature: they assign ownership not just to practices but to the conditions that justify those practices. When the condition changes, there is a named person responsible for evaluating whether the practice should be modified or retired. This sounds simple, and in principle it is. In practice, it requires organizations to resist the instinct to define ownership by what someone manages rather than by what outcome that management is meant to serve.
Without this structure, the default is that no one is accountable for asking whether a practice still belongs. The people executing it are accountable for executing it well. The people who rely on its outputs are accountable for using those outputs. But the meta-question, whether this activity should exist at all given current conditions, belongs to no one and therefore gets asked by no one.
The Leadership Judgment Required
Retiring inherited practices requires a form of organizational courage that is distinct from the courage to launch something new. Launching new initiatives is typically celebrated. Discontinuing existing ones involves naming that something previously valued is no longer worth sustaining, which can feel like criticism even when it is simply accurate assessment.
Leaders who develop the habit of distinguishing between practices that are valuable and practices that are familiar serve their organizations in a way that compound over time. Capacity freed from outdated obligations does not simply disappear into the next urgent request. When the decision to free it is deliberate and the freed capacity is intentionally redirected, organizations find room for the work that has been perpetually deferred, not because it was less important, but because something older never got out of the way.