When the Process Outlives the Problem It Was Built to Solve

An institution can be orderly, disciplined, and increasingly ineffective at the same time.

That kind of failure is hard to see because it still looks like competence.

The weekly report arrives on time. Every project clears the required stage gate. The dashboard is green. The audit finds no missing fields. Yet customers are leaving, quality is slipping, decisions take longer, and the people closest to the work have learned that raising an anomaly creates more trouble than ignoring it.

Nothing is obviously broken because the organization has become excellent at demonstrating fidelity to its process. The difficulty is that fidelity to process and fidelity to purpose are not the same thing.

That distinction is what I kept returning to after my conversation with Eliot Frick on The Unfolding Thought Podcast. Frick makes a much larger philosophical argument about whether modernity has entered the final stage of its life. His description of late-stage systems is immediately recognizable in organizations.

A system begins with generative power. It solves problems that could not previously be solved. Its methods become credible because they work. Over time, however, the methods become inseparable from the system’s identity. When results deteriorate, the system rarely concludes that its operating assumptions may be exhausted. It concludes that people are no longer following them faithfully enough.

So it adds oversight, tightens compliance, and treats deviation as the cause of decline. The process that once produced the outcome becomes the ritual through which the organization proves it still deserves to exist.

A process is a memory of a problem

Most recurring processes began for a reason. Someone shipped defective work, exposed the company to risk, made an expensive decision without enough evidence, or forced other people to reconstruct information that should have been recorded. A checklist, review, approval, or report was created to keep that failure from recurring.

When the process works, the original problem becomes less visible. New employees encounter the solution without experiencing the conditions that made it necessary. They know the form must be completed but not what judgment the form was meant to improve. They know who must approve a decision but not what uncertainty that approval was supposed to reduce.

The process is therefore a kind of organizational memory. It preserves an answer after the question has faded.

That can be useful. We do not want every generation of employees to rediscover fire safety or financial controls from first principles. But a memory becomes dangerous when the organization cannot distinguish the enduring purpose from the historical method. Conditions change while the ritual remains. Eventually, people measure whether the process occurred because they have lost the ability to measure whether it still helped.

Success teaches a system what to stop noticing

Every successful institution develops an operating grammar. It creates categories, incentives, reporting systems, professional language, and approved ways of reasoning. This grammar lets large groups coordinate. It also makes the organization increasingly good at recognizing what it already knows how to see.

James March described a related tension as the difference between exploiting old certainties and exploring new possibilities. Exploitation improves what the organization already knows how to do. Exploration searches for something better but produces uncertain returns. March’s warning was that adaptive systems often refine exploitation more quickly than exploration. That can make them effective in the short run and self-destructive over time.

The problem is not that managers foolishly choose the old over the new. The old process comes with evidence, owners, budgets, benchmarks, and political support. The alternative begins as a question. One side can produce a forecast. The other can only promise learning.

The imbalance compounds. The more an organization invests in a process, the more careers, systems, and explanations depend on that process remaining legitimate. Evidence that fits the current model is easy to absorb. Evidence that challenges the model arrives looking incomplete, undisciplined, or irrelevant.

Threat makes the rulebook harder

Declining results ought to create curiosity. In practice, they often create rigidity.

Barry Staw, Lance Sandelands, and Jane Dutton’s work on threat rigidity describes two common responses to adversity: information processing narrows and control constricts. Organizations rely more heavily on familiar knowledge, reduce the number of voices involved, centralize authority, and formalize procedure.

Those responses are understandable. A threat creates urgency, and coordination can matter more during an immediate crisis. The problem comes when a short-term crisis response becomes the operating model for a system whose assumptions are failing. The organization reduces variation at precisely the moment it most needs alternatives.

This creates a cruel feedback loop. The system produces weaker results. Leadership tightens the system to protect performance. Tighter control suppresses dissent and experimentation. The organization receives less information about why the system is failing. Its leaders become even more convinced that inconsistent execution is the problem.

People who question the process are then easy to cast as undisciplined. Yet they may be carrying the information the process was designed to exclude.

Collapse stories can be another form of loyalty

Frick makes a surprising argument about stories of collapse. We assume that someone predicting the end of a system has escaped its influence. Often the opposite is true.

The defender says the institution must be saved. The critic says it must be destroyed. Both keep the institution at the center of the imagination. The defender uses its categories to explain what must continue. The critic uses the same categories to explain what must end. Neither has necessarily described what could make the old conflict less important.

This pattern appears in organizations whenever two factions fight over control of a process whose usefulness neither side is examining. One department wants stricter enforcement. Another wants the process abolished. Both assume the available choices are compliance or rebellion.

A more useful question is what problem the process was built to solve and whether that problem still exists in the same form. If it does, perhaps the method needs repair. If it does not, the fight over the method may be consuming attention that belongs somewhere else.

A new system may not win the old argument

Thomas Kuhn’s account of scientific revolutions is helpful here. Transformative ideas do not always emerge by accumulating better answers inside the accepted model. Anomalies build until a different framework can organize them.

A new framework may not defeat the old one by its own measures. It can change which observations matter, which problems deserve attention, and what counts as an explanation. Questions that once felt decisive can become smaller or disappear.

Organizations routinely make this transition harder than it needs to be by requiring every experiment to justify itself with the current system’s metrics. But those metrics contain assumptions about value, time, quality, and risk. An idea that tests the assumptions cannot always prove itself using measures designed to preserve them.

This does not mean experiments should escape accountability. It means their first obligation may be to produce information rather than scale, efficiency, or immediate financial return. Leaders need to know what the experiment is trying to learn and what evidence would cause it to stop. That is different from demanding that it look like a small version of the established business.

Leadership is the preservation of options

Frick uses the word “aperture” for a protected opening through which unfamiliar possibilities can develop. The metaphor matters because most new ideas do not begin with enough power to survive the full force of an established institution.

A leader does not need to believe every unconventional proposal. Most will be incomplete, and many will fail. Leadership requires preventing the current operating system from eliminating all unfamiliar ideas before any can produce evidence.

Amy Edmondson’s research on psychological safety helps explain one condition for such an opening. Teams learn when people believe they can take interpersonal risks. That does not mean conflict disappears. It means uncertainty, error, and disagreement can enter the conversation without immediately becoming evidence that someone does not belong.

Authenticity matters too. Research by Charlan Nemeth, Keith Brown, and John Rogers found that a genuinely held minority position produced better quantity and quality of solutions than several forms of assigned devil’s advocacy. An organization does not receive the full benefit of dissent by appointing someone to perform disagreement inside a meeting whose real boundaries remain untouched.

What protecting an aperture looks like

Protected exploration does not have to mean an innovation lab separated from the real work. It can begin with a few operating choices:

• Separate delivery work from exploratory work so the two are not judged by identical expectations.
• Give small experiments explicit sponsors, modest budgets, and expiration dates.
• Ask which measures reflect the purpose and which merely prove compliance.
• Record anomalies before explaining them away.
• Invite authentic dissent from people who actually hold a different view.
• Require experiments to produce learning before requiring them to produce scale.
• Periodically ask what problem each recurring process still solves.
• Retire rituals whose connection to outcomes can no longer be demonstrated.

These practices will not reveal the next paradigm on command. That is not the promise. Their value is that they preserve variation long enough for the organization to learn from it.

Jim Dator’s four generic futures include continuation, collapse, discipline, and transformation. Frick’s argument rearranges that sequence, but the categories remain useful. Organizations are usually comfortable planning for continuation. They can imagine collapse because fear supplies the story. They understand discipline because tightening control feels actionable.

Transformation is harder because it cannot be fully described in the language of the system it may replace.

The practical question is therefore not whether modernity, an industry, or a company is truly at the end of its life. The better question is diagnostic: are our institutions still producing results, or are they spending more of their energy demonstrating loyalty to the way those results used to be produced?

A process deserves protection when it remains connected to purpose. When that connection is gone, enforcing the process more intensely will not restore it. Leadership begins by noticing the difference and preserving enough room for another possibility to become visible.

Listen and read further

• Are We Living at the End of Modernity?, The Unfolding Thought Podcast with Eliot Frick
• It Was Always Already There, Eliot Frick
• The Structure of Scientific Revolutions, Thomas S. Kuhn
• Exploration and Exploitation in Organizational Learning, James G. March
• Threat Rigidity Effects in Organizational Behavior, Barry M. Staw, Lance E. Sandelands, and Jane E. Dutton
• Psychological Safety and Learning Behavior in Work Teams, Amy Edmondson
• Devil’s Advocate Versus Authentic Dissent, Charlan Nemeth, Keith Brown, and John Rogers
• Alternative Futures at the Manoa School, Jim Dator