Why Approved Solutions Never Become Normal Operations

The Hidden Structure Between Buying and Operating

Consider the following illustrative scenario, based on structural patterns repeatedly observed in international operations.

A manufacturing company in Southeast Asia spends eighteen months evaluating a production-scheduling system. The evaluation is rigorous. Internal teams test compatibility with existing infrastructure. Finance approves the budget after three rounds of revision. Legal clears the contract. The board signs off. The vendor delivers on time. Installation proceeds without significant technical obstacles. Training sessions are completed. The system goes live on the scheduled date.

Six months after go-live, the system runs. It is technically active. Data flows in. Reports generate on demand. Dashboards display real-time metrics. Yet the actual scheduling of production — the daily decisions about what runs, when, in what sequence, and who adjusts when conditions change — still happens in spreadsheets, phone calls, and the memory of three senior supervisors who have been doing it their way for twenty years.

The system was approved. It was purchased. It was installed. It was activated. But it never became the way production scheduling actually works in that organization.

This is not a failure of technology. It is not a failure of decision-making. It is not a failure of the vendor. It is not even a failure of intention. It is a failure of a different kind entirely — one that most organizations cannot name, because they lack a framework for distinguishing between what was introduced and what became established.

The Problem That Has No Name

Organizations worldwide invest extraordinary resources in selecting, approving, and deploying operational solutions. Enterprise systems. Process redesigns. Automation platforms. Quality management methodologies. Digital workflows. Supply chain technologies. Consulting frameworks. Compliance tools.

The investment is real. The decision process is often rigorous. The technical deployment frequently succeeds by every conventional measure: on time, within budget, technically functional.

Yet documented research across implementation science and organizational practice shows that deployment, adoption, and routine incorporation are not equivalent outcomes. A solution can be deployed without being adopted. It can be adopted without being routinely incorporated. Each transition represents a different organizational achievement — and each can fail independently of the others.

Gartner reports that more than 70% of recently implemented ERP initiatives fail to fully meet their original business goals. This statistic measures a broader construct — failure to deliver expected outcomes — that includes but is not limited to the specific phenomenon examined here. It serves as context for the distance between deploying a solution and achieving the result that justified the investment.

The critical question is not whether a gap exists between deployment and operational reality. The critical question is why it persists — and more specifically, why it persists even when the solution itself is correct, the market conditions are favorable, and the decision to adopt was sound.

Why Conventional Explanations Fail

When an approved solution does not produce its expected results, organizations typically look for explanations in three places: the solution was wrong, the vendor was incompetent, or the people resisted change.

Each of these explanations captures a fragment of reality in some cases. But none of them explains the most structurally interesting cases — the ones where the solution is demonstrably functional, the vendor delivered as contracted, and the people involved are neither incompetent nor hostile. Cases where everything appears correct on paper, and yet the solution never becomes part of the way the organization actually operates.

In those cases, a different mechanism is at work. Not a failure of the solution. Not a failure of the decision. Not a failure of effort. But a failure of incorporation — the organization’s inability to absorb an approved, available, functional solution into its actual operational architecture.

This failure has no standard name in business practice. It is not “change resistance” — a term that implies intentional opposition where often none exists. It is not “implementation failure” — a term that suggests the solution was never technically deployed when in fact it was. It is not “adoption failure” — a term that conflates the initial decision to try something with the sustained organizational transformation required to make it permanent.

It is something more precise: the structural inability of a receiving organization to convert an available solution into an embedded operational capability.

What Implementation Science Established

The distinction between introducing something into an organization and making it part of normal work is not new in academic research. It has been studied extensively — though primarily in healthcare and public-service settings rather than in international operations or commercial contexts.

Normalization Process Theory, developed by Carl R. May, Tracy Finch, and colleagues between 2003 and 2009, provides the most rigorous framework for understanding what happens after a new practice or technology enters an organization. NPT specifically explains how new technologies, ways of acting, and ways of working become — or fail to become — routinely embedded in everyday practice.

The theory makes a structural distinction that most business practitioners never encounter. It separates:

Implementation — the deliberate initiation of a new practice or system into an organizational environment.

Embedding — the process through which that practice becomes woven into existing work patterns and social relationships.

Integration — the incorporation of the practice into the broader organizational context.

Routine normalization — the state in which the practice operates as an unremarkable, taken-for-granted part of daily work.

NPT identifies four mechanisms through which people contribute to normalization: making sense of the new practice (coherence), building commitment to it (cognitive participation), enacting it collectively (collective action), and appraising its consequences (reflexive monitoring). These mechanisms can promote or inhibit normalization. Their presence does not guarantee normalization, and weakness in them can make routine embedding harder to sustain.

The central implication for international operations is direct: technical implementation does not by itself establish routine embedding. A system that has been implemented — technically deployed and made available — is not necessarily a system whose use has become an unremarkable part of daily work. And a system that is not normalized remains, structurally, an addition rather than a replacement — regardless of how long it has been technically active or how much was spent to deploy it.

The Taxonomy That Separates Adoption From Outcome

A complementary contribution comes from implementation-outcomes research. In 2011, Proctor and colleagues proposed a taxonomy of eight conceptually distinct implementation outcomes: acceptability, adoption, appropriateness, feasibility, fidelity, implementation cost, penetration, and sustainability.

The taxonomy establishes a precise and consequential separation. It demonstrates that these outcomes — though related — are not equivalent and must not be treated as interchangeable evidence of the same thing. Specifically:

Adoption measures whether an organization or individual has taken up a new practice.

Penetration measures the degree to which that practice has spread across the eligible population within a setting.

Sustainability measures whether the practice continues to be delivered over time after initial support structures are withdrawn.

Crucially, the framework distinguishes implementation outcomes from service outcomes and from client outcomes. The act of implementing something successfully — by implementation metrics — does not automatically produce the service-level or client-level results that justified the implementation. These are separate constructs requiring separate evidence.

KYOTEN carries forward the analytical discipline rather than the healthcare-specific taxonomy: evidence of one organizational outcome should not automatically be treated as proof of another. If an organization adopted a solution, that does not prove the solution penetrated into routine practice. If it penetrated, that does not prove it is sustainable. And none of these — critically — prove that the solution produces the operational results it was expected to deliver. This extension to international business operations is a KYOTEN inference; the structural logic — that measuring one construct does not prove another — holds in any organizational setting where a solution must move from “available” to “operational.”

A Solution Never Operates Alone

Understanding why approved solutions fail to normalize requires examining what actually happens when a new operational capability arrives inside an organization.

A new solution enters an organization that already has routines, responsibilities, information flows, tools, and established ways of making decisions. Those elements did not emerge to accommodate the new solution; they evolved around the operation that already existed. The organization’s current architecture represents accumulated solutions to previous challenges — it was optimized for what came before, not for what is arriving now.

This means technical availability alone cannot determine whether the solution becomes normal work. The surrounding work system must also be capable of incorporating it. When those internal conditions allow incorporation, the solution settles into daily practice and becomes unremarkable. When they do not, the solution remains a layer alongside the existing operation — technically present, but functionally separate from the way work actually gets done.

KYOTEN reserves the diagnostic structure of that incorporation for a separate operational analysis; the public point is simpler: a solution and the system receiving it must eventually function as one operational reality. When they do not, the organization is paying for a capability it approved but cannot use as intended.

The Second Scenario

The following illustrative scenario reflects a recurring structural pattern observed across international markets.

An automotive-parts distributor in Central Europe purchases a demand-forecasting tool. The selection process takes eight months. The tool is technically excellent — validated algorithms, clean integration with existing ERP data, demonstrated accuracy in pilot conditions. Installation is successful. Training is completed for all relevant purchasing teams.

Three months later, the purchasing managers who are supposed to use the tool’s outputs to generate orders continue placing orders based on historical patterns and personal relationships with suppliers. They check the tool occasionally. They acknowledge its existence in weekly reports. When asked directly, they confirm they “use” it. But the actual purchasing decision — the one that determines what arrives at the warehouse next week — remains governed by the old logic: personal judgment, supplier familiarity, and last year’s numbers adjusted by intuition.

The tool is present. It is not established. It was introduced, but it never took root. It exists in the organization without operating through the organization.

The gap is no longer technical availability; it is incorporation into ordinary work.

The Japanese Operational Lens: Teichaku

Japanese business practice offers a useful operational concept for examining this distinction.

Teichaku (定着) means “becoming established” — the state in which a practice, system, or capability ceases to be new and becomes part of the normal functioning of the environment it entered. The word combines 定 (tei — fixed, constant, definite) and 着 (chaku — arrive, attach, settle). It describes not merely arrival but settlement — something that has attached itself to the existing structure and become part of its ongoing reality.

This is not a decorative cultural reference. Teichaku has direct, documented, contemporary operational use in Japanese business practice.

PwC Japan, in its published work on Sales DX Change Management, identifies 定着化 (teichaku-ka — the process of becoming established) as the critical and highly difficult objective of digital transformation in sales operations. Their analysis states directly:

“営業現場におけるDXの定着化は難易度が高い”

The establishment of DX in the sales field has high difficulty.

PwC Japan further documents the specific manifestation of this problem: organizations invest in SFA (Sales Force Automation) and CRM systems, deploy them technically, and yet the field does not use them and effects do not materialize. Their published observation:

“せっかく投資してSFA/CRMを導入したのに、現場で使ってもらえず効果が上がらない”

Despite investing and introducing SFA/CRM, the field does not use them and results do not emerge.

The distinction PwC Japan draws operationally is between 導入 (dōnyū — introduction, deployment) and 定着化 (teichaku-ka — becoming established in actual practice). A system can be introduced without becoming established. A process can be deployed without settling into normal work. The transition from one state to the other requires specific intervention — it does not happen automatically merely because the technology is available.

KYOTEN uses teichaku as an operational lens because it names the exact condition that separates a solution that was merely introduced from a solution that became part of normal work. The question changes from “Was this solution introduced?” to “Did this solution achieve teichaku — did it settle, attach, and become established as part of how work actually happens?”

This is a KYOTEN extension: we apply the concept of teichaku specifically to the analysis of operational solutions post-approval within receiving organizations. PwC Japan’s evidence demonstrates that the concept has contemporary operational use in Japanese business consulting to describe and pursue exactly this transition. It is not an abstract philosophical term — it is a working operational concept used by practitioners facing this problem daily in Japanese organizations.

Why This Asymmetry Persists

The reason approved solutions fail to become normal operations is not random, not accidental, and not primarily about people resisting change. It is structural.

Organizations are designed for stability. Their routines, roles, systems, and decision structures exist because they solved previous problems. Every existing workflow represents an accumulated solution to a previous challenge. Every reporting line exists because at some point someone needed that information to flow in that direction. Every operational habit persists because it works — or at minimum, because it works well enough that no one has been forced to abandon it.

When a new solution arrives, it does not simply add itself to this structure. It requires the structure to make room. It requires existing patterns to yield. It requires people to stop doing something that previously worked and start doing something that has not yet proven itself in their specific context.

KYOTEN inference: as the gap increases between the operating logic assumed by a solution and the operating logic already embedded in the receiving organization, incorporation can become more difficult. Solution quality alone does not determine that difficulty. A technically excellent solution that assumes a different operational logic than the one the organization currently runs may face greater structural resistance than a simpler solution that fits within the existing architecture.

When sufficient organizational energy is applied — when the work system actively reorganizes itself around the new capability — the solution displaces the old logic and becomes the operation. When that energy is not applied — when the organization assumes that installation equals integration, that go-live equals normalization, that providing access equals achieving establishment — the new solution simply coexists with the old logic. Both run simultaneously. The organization pays for both. Neither is fully effective.

The asymmetry is this: deploying a solution requires a coordinated effort with a defined scope. Making that solution become the normal operation requires sustained reorganization of the work system that receives it — a transformation with no guaranteed completion.

The Boundary Between External Viability and Internal Incorporation

There is a critical distinction that must be drawn here — one that separates Operational Absorption from adjacent problems that are often confused with it.

A solution that cannot function because of external conditions in the target market faces a different kind of problem entirely. When national regulations prohibit a material, when the electrical infrastructure of a country is incompatible with equipment requirements, when no distribution channel exists for a product category, when local labor markets cannot supply the skills a system requires — these are market-level constraints. They originate primarily in conditions external to the specific receiving organization.

Operational absorption begins after those external questions have been resolved. It studies what happens when a solution is viable in the market and yet fails to become part of normal operations inside a specific organization.

The distinction is precise:

National voltage standard incompatible with the equipment → external market condition.

Equipment compatible with the country but incompatible with the internal electrical infrastructure of a specific plant → internal organizational condition.

National regulation prevents the use of a chemical compound → external market condition.

Internal ERP configuration does not recognize the product categories the new system requires → internal organizational condition.

No distribution channel exists in the target country → external market condition.

Internal master data architecture cannot process the new workflow without manual intervention → internal organizational condition.

The first category in each pair belongs to a different territory — one that studies whether a solution can work within the conditions of a given market. Operational Absorption Asymmetry studies exclusively the second: the internal organizational conditions that determine whether an approved, viable, available solution can actually be incorporated into the work system of a receiving organization and become part of its normal operation.

This boundary matters because the interventions are completely different. Solving an external market constraint requires adapting the solution to the market. Solving an absorption constraint requires adapting the organization’s internal work system to the solution — or selecting solutions whose absorption requirements do not exceed what the organization’s internal architecture can provide.

What This Means for International Operations

The implications for international commerce are immediate, consequential, and largely unrecognized in standard commercial practice.

Every cross-border sale of an operational solution — whether it is a manufacturing system, a logistics platform, a quality-management methodology, an automation tool, or a consulting framework — implicitly assumes that the buying organization can absorb what it purchases. The negotiation focuses on price, scope, specification, delivery timeline, technical compatibility, and post-sale support. The contract assumes that what is delivered will become operational.

But absorption is not guaranteed by delivery. It is not guaranteed by installation. It is not guaranteed by training. It is not even guaranteed by initial use. Absorption requires that the receiving organization possesses specific internal conditions — conditions that allow the solution to displace the previous operational logic and become the new normal.

That capacity is often less visible in conventional commercial evaluation than price, specification, compatibility, and delivery. It is rarely part of any contractual obligation or success criterion. It is rarely measured after go-live.

This creates a structural asymmetry that operates in every international transaction involving operational solutions. The seller knows the solution works — they have evidence from other installations, other organizations, other contexts. The buyer believes the solution will work — they have approved it through their evaluation process, verified its technical specifications, and confirmed its market viability. But the gap between “this solution is now available to you” and “this solution is now part of how you operate” remains largely unexamined in the transaction itself.

When the solution does not become operational — when it remains a parallel system, a project layer, an unused tool, a technically active but functionally disconnected capability — both parties lose. The buyer pays for something that does not produce its expected value. The seller faces dissatisfaction, contract disputes, or lost renewal opportunities for a failure that was not primarily their fault. The relationship deteriorates over a problem that neither party can precisely diagnose because neither has a framework for distinguishing between delivery success and absorption success.

Within the KYOTEN framework, this is Operational Absorption Asymmetry: the structural difference between having access to an approved, viable operational solution and having incorporated that solution into the normal operational architecture of the receiving organization until it achieves teichaku — until it settles, attaches, and becomes established as part of how work actually happens.

KYOTEN Finding: The eLWIS Transformation

The structural reality of absorption failure is not theoretical. It manifests at significant documented scale.

Lidl, the German discount retail chain, invested in a major transformation of its merchandise-management systems. The project, internally known as eLWIS, aimed to replace Lidl’s legacy system — Wawi — with SAP-based enterprise architecture. Handelsblatt reported the cost at roughly €500 million. The project ran for approximately seven years.

In 2018, after years of investment in the eLWIS transformation, Lidl terminated the SAP project rather than making it the intended replacement for its merchandise-management environment. The company returned to its legacy system Wawi, significantly updated.

This is presented here as documented evidence of a structural pattern — not as a complete diagnosis of internal causation. The specific organizational dynamics that led to termination are not fully documented in public sources, and no external analysis can claim certainty about the binding constraint. What is documentable is the structural fact: the intended SAP transformation did not become the replacement merchandise-management environment before the project was terminated. After approximately seven years and significant investment, the organization returned to what it already knew.

KYOTEN inference: the case illustrates why long investment and formal commitment cannot be treated as evidence that operational incorporation has occurred. A project that runs for years and absorbs significant resources may still never become part of the normal operation. The existence of effort does not prove the achievement of establishment. Time and money do not automatically produce normalization.

What cannot be affirmed from publicly available evidence: the specific internal binding constraint that prevented incorporation, whether the solution was appropriately designed for Lidl’s operational context, whether different organizational conditions would have produced a different outcome, or whether the failure was primarily one of absorption versus design, scope, or compatibility. These questions require evidence that is not available in public reporting.

What the case does demonstrate, within the limits of public evidence: the gap between approving a solution, funding a solution, and sustaining investment in a solution — and that solution actually becoming the way the organization operates — can persist for years, absorb hundreds of millions in resources, and ultimately remain unbridged.

The Unasked Question

Most organizations ask: “Is this the right solution?”

Some organizations ask: “Can this solution work in our market?”

A third question receives far less explicit attention: “Can our internal work system actually incorporate this solution into normal operations?”

This third question — the absorption question — is where value is created or destroyed after the purchase decision has been made. It is the question that separates organizations that convert approved solutions into embedded operational capabilities from organizations that accumulate technically active but functionally disconnected systems — systems that exist in the organization without operating through it.

The distinction is not between good solutions and bad solutions. It is not between good organizations and bad organizations. It is between organizations whose internal work-system architecture allows approved solutions to settle — to achieve teichaku — and organizations whose architecture structurally prevents settlement, regardless of the quality of what was introduced.

Approval is not absorption. A solution that arrives but never settles remains a project — not an embedded operational capability.

The question that changes how organizations evaluate operational investments is not “Did we buy the right solution?” It is: “Can our work system incorporate this solution until it becomes part of how we normally operate — and what specific conditions would that require?”

Radar Transition

The structural explanation of why this asymmetry exists is only the beginning. The next question is operational: where does this phenomenon appear in observable market behavior? Where can an analyst identify the visible signal — the evidence that an approved solution has not achieved establishment within the receiving organization? What does that signal look like from the outside?

That question requires a different lens. Not explanation but observation. Not why, but where.

Technical References

May, C. and Finch, T. (2009). “Development of a theory of implementation and integration: Normalization Process Theory.” Implementation Science, 4:29. https://implementationscience.biomedcentral.com/articles/10.1186/1748-5908-4-29

May, C. and Finch, T. (2009). “Implementing, Embedding, and Integrating Practices: An Outline of Normalization Process Theory.” Sociology, 43(3): 535-554. https://journals.sagepub.com/doi/10.1177/0038038509103208

PwC Japan (2021). “How to Transform the Field Through Change Management — Part 2: Methods for Achieving Standardization and Adoption in Sales Operations.” SalesZine/PwC Japan Knowledge. https://www.pwc.com/jp/ja/knowledge/journal/saleszine2101.html

PwC Japan. “Sales DX Change Management.” Service page. https://www.pwc.com/jp/ja/services/consulting/front-office-and-experience/sales-solution/sales-dx.html

Health Data Management (2026). “Why it’s difficult to move past deployment to adoption.” https://healthdatamanagement.com/articles/why-its-difficult-to-move-past-deployment-to-adoption/

Gartner (2026). “Latest Enterprise Resource Planning (ERP) Insights.” Key finding: “More than 70% of recently implemented ERP initiatives will fail to fully meet their original business use case goals. As many as 25% of these will fail catastrophically.” https://www.gartner.com/en/information-technology/topics/enterprise-resource-planning

Consultancy.uk (2018). “Lidl cancels SAP introduction having sunk €500 million into it.” https://www.consultancy.uk/news/18243/lidl-cancels-sap-introduction-having-sunk-500-million-into-it

KYOTEN Knowledge Base

Operational Absorption Asymmetry — the structural difference between having access to an approved, viable operational solution and having incorporated that solution into the normal operational architecture of the receiving organization. The asymmetry emerges because making a solution available and making it routine operation are different organizational achievements.

Teichaku (定着) — the Japanese organizational concept describing the state in which a practice, system, or capability ceases to be new and becomes established as part of normal work. Distinguished from 導入 (dōnyū — introduction/deployment). Used operationally by Japanese consulting firms including PwC Japan in the context of DX change management and SFA/CRM standardization. Within the KYOTEN framework, teichaku names the terminal condition of successful absorption: the solution has settled.

Core doctrinal principle: Approval is not absorption. A solution that arrives but never settles remains a project — not an embedded operational capability. The conditions that allow settlement are internal to the receiving organization, distinct from the quality of the solution, and distinct from the external market conditions in which the solution operates. The question that changes operational evaluation is not “Did we buy the right solution?” but “Can our work system incorporate this solution into normal operations — and what specific conditions would that require?”