Site Logo
All articles
Research MethodsImplementation and Process Evaluation

Normalization Process Theory: why interventions fail to stick

Evidano8 min read

Plenty of interventions work in trials and then fail to survive contact with ordinary practice. Normalization Process Theory addresses that gap directly, and it does so by shifting the object of explanation. Most implementation frameworks list factors that predict adoption. NPT instead asks what people actually have to do — the work of making sense of something, of committing to it, of enacting it, and of appraising it — for a new practice to become the unremarkable way things are done. Because it is a theory of work rather than of attitudes, it produces findings that point at something changeable.

Normalization as work, not attitude

Normalization in NPT means a practice becoming routinely embedded in everyday work — done without deliberation, sustained without a champion, surviving the departure of the person who introduced it.

The theory's central move is to treat that embedding as the outcome of collective work that people do, individually and together. It is not primarily about whether staff have positive attitudes toward the intervention; it is about whether the sense-making, relational, operational and appraisal work required to normalise it actually gets done, and whether the setting makes that work possible.

The practical consequence is that NPT findings tend to be actionable in a way that attitudinal findings are not. "Staff were resistant" supports nothing. "Nobody could distinguish the new pathway from the existing referral route, so both were maintained in parallel and the new one was dropped under pressure" identifies a coherence failure with an obvious remedy.

The four constructs

ConstructThe work it namesA diagnostic question
Coherence (sense-making)Understanding what the practice is, how it differs from what came before, and what it is forCan people describe how this differs from what they already do?
Cognitive participation (engagement)Building and sustaining the community of practice around it — who drives it, who legitimately does itIs there anyone whose job it is to keep this going?
Collective action (enacting)The operational work of doing it: skills, workflow fit, resources, division of labour, confidence in itDoes the workflow actually accommodate this, or does it require a workaround?
Reflexive monitoring (appraisal)Formally and informally judging whether it is worth it, and reconfiguring accordinglyDo people see any evidence of whether it is working?

Where the theory comes from

NPT was developed by Carl May, Tracy Finch and colleagues from work on why telehealth and other complex healthcare interventions repeatedly failed to embed. The foundational statement is Development of a theory of implementation and integration: Normalization Process Theory in Implementation Science.

Its practical use in evaluation is set out in Using Normalization Process Theory in feasibility studies and process evaluations of complex healthcare interventions, which is the single most useful reference for an evaluator applying it. A current overview appears in the Handbook on Implementation Science.

A quantitative instrument, NoMAD, was developed from the constructs — see Improving the normalization of complex interventions: measure development based on normalization process theory — and has been translated and validated in several languages, for example the Swedish version. Most applied work uses the qualitative constructs; NoMAD is the option where a survey across a large staff group is feasible.

Using NPT in a process evaluation

Decide whether it is a lens or a framework

NPT can be used prospectively to design an implementation and its evaluation, concurrently to explain what is happening as it happens, or retrospectively to explain why something did or did not embed. Each is legitimate; they demand different data.

Retrospective use is the most common and the weakest, because it relies on people reconstructing work they may never have consciously performed.

Build the topic guide from the constructs

Interview questions should ask about work, concretely: what do you actually do differently, who else is involved, what did you have to stop doing, how do you know whether it is helping.

Asking people directly about "coherence" produces nothing. The constructs are the analyst's framework, not the participant's vocabulary.

Sample across roles, not just adopters

Collective action is collective. A study interviewing only the clinicians using the intervention will miss the administrative, managerial and support work that determines whether it is sustainable.

Non-adopters and people who tried and stopped are the highest-yield interviews and the ones most often omitted.

Code deductively, then look at what will not fit

Code to the four constructs and their sub-components, then attend carefully to the material that resists them. NPT does not account for everything — power, professional hierarchy and resource scarcity often sit outside the constructs and drive the outcome.

Forcing that material into a construct is the commonest analytic failure in NPT studies and produces bland findings.

Report by construct, with the interaction

Findings are most useful organised by construct, because that is what points at a remedy. But the interactions matter: strong coherence with no cognitive participation produces a practice everyone understands and nobody owns, which fails in a specific and predictable way.

Worked example: a medicines review service

A regional health service introduced structured medicines reviews in community pharmacies. Uptake was strong for four months and then fell to near zero in eleven of fourteen sites. A process evaluation used NPT across pharmacists, technicians, practice managers and two GPs per area.

Coherence was strong among pharmacists — they could articulate what the review was for and how it differed from a dispensing check. It was weak everywhere else. Technicians described it as "the pharmacist's paperwork", and GPs largely did not know it existed, which mattered because the review generated recommendations that needed a prescriber to act.

Cognitive participation had been carried by a regional lead who moved post in month five. No site had a designated owner. This coincided exactly with the drop-off.

Collective action revealed the operational obstruction. The review took 25 minutes and required the pharmacist to leave the dispensary; in single-pharmacist sites this stopped dispensing entirely. The three sites where uptake was sustained were the three with a second pharmacist — a workflow fact, not a motivational one.

Reflexive monitoring was almost entirely absent. Pharmacists sent recommendations to GP practices and heard nothing back. Several said they had stopped because they had no evidence any of it was ever acted on.

The recommendations followed directly from the constructs: brief GP practices and establish a response loop (coherence and reflexive monitoring), name a site-level owner (cognitive participation), and either fund locum cover or restrict the service to multi-pharmacist sites (collective action). A satisfaction survey would have reported that pharmacists valued the service, which was true and would have explained nothing.

Common mistakes

  • Using it as a coding frame and stopping there. Sorting data into four boxes is not analysis. The finding is in how the constructs interact and where they fail.
  • Only interviewing adopters. Guarantees a study that cannot explain non-adoption.
  • Asking about attitudes. NPT is a theory of work. Questions about beliefs and satisfaction produce data the constructs cannot use.
  • Ignoring what does not fit. Hierarchy, funding and professional boundaries frequently determine the outcome and sit outside the framework. Say so.
  • Retrospective-only designs. People reconstruct implementation work poorly; where possible, collect during rather than after.
  • Treating NoMAD as a substitute. The instrument measures the constructs; it does not explain them.
  • Assuming normalization is desirable. Embedding a practice that turns out to be ineffective is a bad outcome, and NPT is silent on whether the intervention was worth normalising.

Quality criteria

A strong NPT study shows sampling across the roles implicated in the work, not just the intended users; a topic guide asking about concrete practice rather than the constructs by name; analysis that reports negative cases and material the framework could not accommodate; attention to interactions between constructs; and recommendations that name specific work to be changed rather than "improve engagement".

A weak one is recognisable at a glance: four sections, one per construct, each reporting that the construct was "partially achieved", with no account of what anyone should do differently.

Limitations

NPT explains embedding. It does not assess whether the intervention works, and it is indifferent to whether the thing being normalised is any good — a well-normalised ineffective practice is a success by the theory's own terms and a failure by any other.

It also under-theorises power and structure. Where a practice fails because of a professional demarcation dispute or because the funding model pays for something else, NPT can describe the resulting collective-action problem but not the cause of it. Framework-guided evaluation using CFIR handles the outer setting more explicitly and is sometimes the better choice.

It carries a healthcare accent. The theory was built from health-services work and its examples, language and validated instruments all sit there; it transfers to education, social care and organisational settings but the fit needs argument rather than assumption.

Where software helps

NPT studies are deductive coding at scale: thirty to eighty interviews across several roles and sites, coded to four constructs and their sub-components, then compared across sites to find where a construct failed and why.

That cross-site comparison by construct is the analytic step that produces the recommendation, and it is exactly the operation a qualitative platform is built for — retrieving everything coded to collective action across fourteen sites and reading it together. Evidano supports Normalization Process Theory studies as a named methodology, so coding follows the construct structure rather than an emergent frame. Deciding which material genuinely belongs to a construct, and which is telling you the framework does not fit, stays the analyst's call.

Topics

  • normalization process theory
  • implementation science
  • process evaluation
  • complex interventions
  • evaluation
  • health services research

Other methods in implementation and process evaluation

Written guides are linked directly; the rest have a reference entry in the methodology directory.

Published research using these methods

Studies and evaluations where this family of method was applied with Evidano — the work, not the claim.

Keep reading

Browse all articles
Company
About
Newsletter

Product updates, research, and tips — straight to your inbox.

© Evidano, All Rights Reserved.