apply-fidelity-before-adaptation

name	apply-fidelity-before-adaptation
description	Use when an organization adopts a new external process or evidence-based practice — implement it with strict fidelity to its original design first, resisting the urge to customize based on discomfort or habit, because premature adaptation by people who don't yet understand why the design works is a well-documented cause of practices failing to reproduce their intended effectiveness; only begin deliberate optimization once faithful execution is demonstrated.
source	Fixsen, Naoom, Blase, Friedman & Wallace, "Implementation Research: A Synthesis of the Literature", National Implementation Research Network, University of South Florida (2005); Huawei Technologies' 1998–2003 adoption of IBM's Integrated Product Development (IPD) methodology under CEO Ren Zhengfei, widely documented in business case studies of Huawei's management transformation
tags	["organizational-change","process-design","implementation","operations","change-management"]
related	["apply-pdca","design-tactical-doctrine","apply-leverage-points-analysis","apply-raci-matrix"]

Apply Fidelity Before Adaptation

When adopting a new external process, methodology, or evidence-based practice, implement it with strict fidelity to its original design first — resisting customization based on discomfort or habit — because premature adaptation by people who don't yet understand why the original design works is a well-documented cause of the practice failing to reproduce its intended effectiveness; only begin deliberate optimization once faithful execution has actually been demonstrated.

Why This Is Best Practice

Why best: A newly adopted process was designed the way it is for reasons the adopting organization typically does not yet fully understand — the parts that feel most uncomfortable or unfamiliar are often exactly the elements that differ most from the organization's prior (less effective) habits, and therefore exactly the elements it most needs. Allowing customization before the organization has actually executed the process faithfully means changes get made based on discomfort and pre-existing habit rather than on any real evidence about what does or doesn't work — and this specific failure mode, adapting before achieving fidelity, is what implementation research identifies as a primary reason imported practices fail to reproduce the results they were adopted to achieve.

Fixsen, Naoom, Blase, Friedman & Wallace (2005): This synthesis of implementation research, produced by the National Implementation Research Network, formalized a staged model of how evidence-based practices succeed or fail when adopted by a new organization — Exploration, Installation, Initial Implementation, Full Implementation, and Innovation — and specifically identified premature local adaptation, occurring before an organization has established fidelity to the practice's original design, as a recurring, well-documented cause of adopted practices failing to reproduce the effectiveness they demonstrated in their original context. The framework explicitly distinguishes adaptation informed by evidence gathered during faithful execution (legitimate, and expected in the later "Innovation" stage) from adaptation driven by discomfort or habit before fidelity has been achieved (a documented failure mode).

Huawei's IPD adoption (1998–2003): Huawei's leadership, engaging IBM as a consultant to overhaul the company's product-development process, mandated that employees adopt the newly designed Integrated Product Development methodology exactly as specified, without modification, even where it felt inefficient or unfamiliar relative to existing internal practice. This adoption-with-fidelity approach — deferring customization until the organization had genuinely internalized and could execute the new process — is widely documented in business case studies of Huawei's management transformation as a foundational episode in the company's shift toward a systematic, process-disciplined organization capable of competing globally.

Adopted by: Fixsen et al.'s implementation-stages framework has been adopted broadly across public health, education, and social-services program implementation as the standard model for rolling out evidence-based practices with fidelity before adaptation; Huawei's IPD adoption is widely cited in business case literature on organizational transformation and management-system adoption from external consultants. Impact: Fixsen et al.'s synthesis of implementation research identified premature local adaptation — occurring before an organization achieved fidelity to a practice's original design — as a recurring, documented cause of evidence-based practices failing to reproduce their original effectiveness once adopted elsewhere; Huawei's IPD adoption, requiring faithful execution of the externally-designed process before any internal customization, is widely credited in business case studies as a foundational step in the company's transformation into a globally competitive, process-disciplined organization.

Steps

1. When adopting a new external process, methodology, or evidence-based practice, resist customizing it immediately based on discomfort or habit — especially the elements that feel most unfamiliar or counter-intuitive. Those elements are frequently exactly what the organization's prior approach lacked, and exactly what it least understands yet.

2. Implement the process with strict fidelity to its original design for a defined trial period, and measure fidelity — adherence to the process as designed — as its own explicit metric, separate from outcome measurement. This makes it possible to later distinguish poor outcomes caused by the process itself from poor outcomes caused by inconsistent execution of it.

3. Only begin deliberate, evidence-based optimization after the organization has demonstrated it can execute the process faithfully — not before. Adaptation at this stage should be driven by what was actually learned from faithful execution, not by pre-adoption assumptions about what needed to be different.

4. Distinguish informed optimization (based on evidence gathered from faithful execution) from premature customization (based on discomfort or habit before fidelity has been achieved). Only the former is legitimate adaptation at this stage; the latter is the specific failure mode this technique guards against.

5. Expect and prepare for organizational resistance during the fidelity phase. The discomfort of executing an unfamiliar process exactly as designed is a predictable, temporary cost of adoption — not, on its own, evidence that the process is wrong.

6. Set an explicit, predetermined checkpoint or criterion for transitioning from the fidelity phase to the optimization phase, rather than leaving that transition's timing ambiguous or subject to whoever advocates loudest for early customization.

Rules

• Never allow customization of a newly adopted external process before the organization has demonstrated it can execute it with fidelity to the original design.
• Measure fidelity (adherence to the process as designed) as a metric distinct from outcome measurement during the initial adoption phase.
• Distinguish adaptation based on evidence gathered from faithful execution (legitimate, later-stage) from adaptation based on pre-adoption discomfort or habit (premature, the failure mode this technique targets).
• Set an explicit, predetermined checkpoint for transitioning from strict fidelity to deliberate optimization, rather than leaving the timing to whoever pushes hardest for early customization.

Examples

Huawei's IPD adoption: Following its 1998 consulting engagement with IBM, Huawei's leadership required employees to adopt the newly designed product-development process exactly as specified, without modification, even where it felt inefficient relative to existing internal habits — deferring customization until the organization had demonstrated it could execute the new process faithfully, at which point a deliberate optimization phase began.

Evidence-based practice rollout: A healthcare organization adopting a new, evidence-validated clinical protocol implements it with strict fidelity across pilot sites, tracking adherence to the protocol as its own metric before permitting any site-specific customization — consistent with implementation-science findings that premature local adaptation, before fidelity is established, is a leading cause of evidence-based practices failing to reproduce their original effectiveness.

Methodology adoption: A team adopting a new framework from an external certified source executes every specified step and role exactly as designed for an initial period, resisting the urge to skip or merge elements that feel redundant, before later customizing the framework based on what they've actually learned works and doesn't work in their specific context.

Common Mistakes

• Allowing individual team members to customize the newly adopted process from day one based on personal discomfort or habit, before the organization has any real evidence about which parts of the original design actually don't fit its context.
• Treating the discomfort of executing an unfamiliar process as evidence the process itself is flawed, rather than as an expected, temporary cost of the fidelity phase.
• Never setting an explicit checkpoint for transitioning to optimization, leaving the process to be gradually eroded by ad hoc customization with no real evidence base behind the changes.
• Confusing the measurement of fidelity with the measurement of outcomes. A process can be executed with high fidelity while outcomes are still developing, and low fidelity makes it impossible to know whether poor outcomes reflect the process itself or its inconsistent execution.

When NOT to Use

• When the newly adopted process is known in advance to require adaptation for a specific, well-documented reason (a legal or regulatory difference between contexts, for instance) — this technique concerns resisting premature customization based on unverified discomfort, not ignoring known, necessary structural differences.
• For an internally-developed process still under active, iterative design, rather than an externally-sourced methodology being adopted — an in-house process still being designed doesn't have an established "original design" whose fidelity is worth strictly protecting in the same way.
• When the organization already has strong, verified evidence — not just intuition — that a specific modification would improve the process without undermining its core mechanism; the technique guards against premature, evidence-free customization, not all customization under any circumstances.