Behaviour Change Wheel

1. What Is Behaviour Change Wheel?

The Behaviour Change Wheel is a practical framework for diagnosing why a target behaviour is not happening and for designing interventions that are more likely to change it. At its core, it helps a team move from a vague statement such as “people are not adopting the new process” to a sharper explanation of what must change in people’s capabilities, opportunities, and motivations.

It is best understood as a behavioural design and change management framework. Consultants use it when client success depends not just on strategy or structure, but on whether managers, employees, customers, or partners consistently do something differently in the real world.

What makes the Behaviour Change Wheel especially useful is that it does not treat training or communication as the automatic answer. Instead, it forces a more disciplined diagnosis of the behavioural problem and then links that diagnosis to a broader set of intervention options.

2. Origin and Background

The Behaviour Change Wheel was developed by Susan Michie, Maartje M. van Stralen, and Robert West and was introduced in a 2011 paper in Implementation Science. The framework was created after the authors reviewed multiple existing behaviour-change frameworks and concluded that many were incomplete, inconsistent, or difficult to use in a systematic way.

Their aim was to provide a more coherent method for characterising behavioural problems and designing interventions. The framework became widely known through public health, implementation science, government, and NHS practice, and it was further operationalised in Susan Michie and colleagues’ later guidance on intervention design. Although it is most famous in health settings, its logic applies just as well to business transformation, operational adoption, compliance, safety, sales execution, and customer-behaviour challenges.

3. How Behaviour Change Wheel Works

The Behaviour Change Wheel has three layers. The center defines what must be true for a behaviour to occur. The middle layer identifies the types of interventions available to influence that behaviour. The outer layer identifies broader policy or system levers that enable those interventions at scale.

In practice, teams start with a very specific target behaviour, diagnose what is blocking it using the center of the model, then choose intervention types that fit the diagnosis. The wheel is not a linear checklist so much as a structured way to move from behavioural insight to intervention design.

The center: COM-B

The core of the wheel is the COM-B model, which states that behaviour depends on three conditions:

Capability — Does the person have the ability to do it?
Capability can be physical (strength, stamina, dexterity) or psychological (knowledge, attention, memory, decision skills).
Opportunity — Does the environment make the behaviour possible or likely?
Opportunity can be physical (tools, time, process design, access, layout) or social (norms, leadership signals, peer expectations, cultural cues).
Motivation — Does the person want or tend to do it?
Motivation can be reflective (conscious goals, plans, beliefs, evaluations) or automatic (habits, emotional responses, impulses).

If a team cannot explain a behavioural failure in terms of capability, opportunity, or motivation, it probably has not yet defined the behaviour precisely enough.

The middle ring: intervention functions

Once the diagnosis is clear, the framework points to nine broad intervention functions:

Education — increase knowledge or understanding
Persuasion — use communication to stimulate action
Incentivisation — create expectation of reward
Coercion — create expectation of cost or penalty
Training — build skills
Restriction — reduce the opportunity to perform competing behaviours
Environmental restructuring — change the physical or social context
Modelling — provide examples for people to imitate
Enablement — remove barriers beyond education or training alone

The important point is that different barriers call for different intervention mixes. If the issue is habit and workflow friction, more communication will not solve it. If the issue is low skill, incentives alone will not solve it either.

The outer ring: policy and system levers

The outer ring identifies broader levers that support intervention design: communication and marketing, guidelines, fiscal measures, regulation, legislation, environmental or social planning, and service provision. In corporate settings, teams often translate these into business equivalents such as governance, managerial routines, standard operating procedures, performance systems, internal communications, workplace design, digital tools, and support services.

Many practitioners also use the APEASE criteria when selecting interventions: affordability, practicability, effectiveness and cost-effectiveness, acceptability, side-effects or safety, and equity. This helps keep the wheel practical rather than theoretical.

4. When to Use Behaviour Change Wheel

The Behaviour Change Wheel is most helpful when success depends on specific behaviours changing at scale. Typical business examples include adoption of a new CRM process, safer frontline routines, more disciplined pricing decisions, manager coaching behaviours, better cross-functional collaboration, higher-quality data entry, stronger cybersecurity habits, or more consistent customer-service behaviours.

In large transformations, it is particularly valuable when leaders are tempted to label a problem as “resistance to change” without diagnosing the real cause. In those cases, the wheel often becomes a bridge between diagnosis and broader organizational change work.

It works best when the target behaviour can be defined clearly, observed in context, and linked to outcomes the business cares about. Useful inputs typically include interviews, observation, workflow mapping, performance data, journey data, supervisor feedback, and evidence on what high performers do differently. A focused application can be done in a few workshops and a few weeks; an enterprise-wide programme can take much longer because behaviours differ by role, location, and context.

It is not a good fit when the question is purely strategic, financial, or structural and no meaningful behaviour diagnosis is needed. It can also mislead teams if they use it to explain away problems that are actually caused by flawed incentives, poor process design, inadequate staffing, or missing technology. In other words, behaviour matters, but behaviour is never isolated from the system around it.

The framework remains highly relevant today, but it is often used differently from how many change programmes were run in the past. Rather than launching broad awareness campaigns, modern practitioners use it to define critical moments, role-specific behaviours, testable interventions, and small experiments that can be refined before scaling.

5. How to Apply Behaviour Change Wheel: Step-by-Step

Clarify the decision and scope. Define the business outcome first, then identify the specific behaviour that drives it. Be precise about who must do what, when, where, and how often. “Improve adoption” is too vague; “sales managers must review pipeline quality weekly in the new tool using the standard checklist” is usable.
Gather the required inputs and data. Combine qualitative and quantitative evidence. Interview users and managers, observe work in context, review process data, examine exceptions and failure points, and compare high- and low-performing groups. If the stakes are high, formalising the diagnosis through an impact assessment helps separate perceived change from actual role-level change.
Define the units of analysis. Decide whether you are analysing behaviours by role, team, journey stage, site, customer segment, or process step. Many teams fail because they mix units of analysis. The right behaviour for a plant supervisor may be completely different from the right behaviour for a maintenance technician or regional leader.
Construct the COM-B diagnosis. For each target behaviour, assess whether the main barriers sit in capability, opportunity, motivation, or some combination. Push the team to use evidence rather than opinion. If managers say people “just don’t care,” ask what proves that motivation is the issue rather than skill, time, tools, or conflicting priorities.
Select intervention functions. Use the diagnosis to choose the most relevant interventions from the wheel. A capability gap may call for education or training. An opportunity gap may require environmental restructuring or enablement. A motivation gap may require persuasion, modelling, incentives, or redesigned feedback loops. Most serious change efforts need a portfolio of interventions rather than a single lever.
Translate insights into concrete design choices. Specify what will change in communications, routines, tools, workflows, manager actions, performance management, and reinforcement. At this stage, most clients need an explicit change architecture so that interventions are assigned to owners, sequenced properly, and embedded in governance rather than left as good intentions.
Test sensitivities and alternative assumptions. Check how your conclusions change if the behaviour is defined differently, if certain barriers are overstated, or if the time horizon shifts. It is common for headquarters to overestimate motivational barriers while frontline evidence points to opportunity barriers such as time, process friction, or tool usability.
Align stakeholders and iterate. Review the diagnosis with sponsors, frontline managers, and affected teams. Resolve disagreements openly and refine the intervention mix before scaling. The wheel works best as an iterative design tool, not as a one-time workshop output.

6. Example: Behaviour Change Wheel in Action

The problem

A global industrial manufacturer was rolling out a new reliability programme across 18 plants. The business case depended on technicians entering failure codes consistently, supervisors reviewing recurring issues in daily meetings, and planners scheduling preventive work earlier. Training had been completed, but adoption remained uneven and plant results were not improving.

Why the framework was selected

The executive team initially framed the issue as weak compliance. The project team chose the Behaviour Change Wheel because that diagnosis felt too shallow. They needed to understand whether the problem was skill, workflow, leadership behaviour, data quality, peer norms, or incentives.

How it was applied

The team defined three target behaviours by role, observed shift handovers, reviewed system logs, interviewed plant leaders, and compared two high-performing sites with two lagging sites. Using COM-B, they found that technicians had enough basic knowledge, but many lacked physical opportunity because terminals were poorly located and work orders were closed under time pressure. Supervisors had reflective motivation in principle, but daily meeting scripts did not force issue review and plant managers were not modelling the discipline consistently.

The insights generated

The diagnosis ruled out a training-first solution. The most important interventions were environmental restructuring, enablement, modelling, and selective persuasion. The team redesigned terminal placement, simplified the failure-code menu, added a short daily-meeting template, required plant managers to review one repeat failure each week, and published site comparisons to create constructive peer pressure.

The actions that followed

Before scaling, the company ran a plant-by-plant readiness assessment to identify where leadership sponsorship, process discipline, and system support were still too weak. Within four months, data-completion rates improved materially, repeat-failure visibility increased, and the programme shifted from “another initiative” to an operating routine with clear owners and reinforcement.

7. Strengths and Limitations

Strengths

It sharpens the real problem. It forces teams to define the target behaviour precisely instead of talking in abstractions.
It broadens intervention choices. It prevents overreliance on training and communication.
It connects people and system design. It recognises that behaviour depends on environment, routines, and social context, not only individual intent.
It supports structured debate. COM-B gives executives and consultants a common language for diagnosing adoption problems.
It is highly actionable. The framework naturally leads to concrete levers such as workflow redesign, manager routines, incentives, and support tools.
It works well with experimentation. Teams can test targeted interventions before scaling them.

Limitations

It can oversimplify complexity. Real organisations have power dynamics, history, politics, and resource constraints that the wheel does not fully capture.
It depends on how well the behaviour is defined. If the target behaviour is vague, the analysis will be weak regardless of framework quality.
It can become subjective. Without observation and data, teams may misclassify barriers based on opinion.
It does not replace execution discipline. Diagnosing behaviour is not the same as running a transformation, changing incentives, or redesigning processes.
Its outer ring comes from policy contexts. In corporate use, practitioners usually need to translate the policy categories into business-specific levers.

8. Common Pitfalls and How to Avoid Them

Choosing outcomes instead of behaviours. Teams often define the target as “better collaboration” or “higher compliance.” That is too broad to diagnose. Define observable actions by role, context, and frequency.
Assuming motivation is the issue. Leaders frequently conclude that people are unwilling when the real problem is time, tools, process friction, or conflicting priorities. Test capability and opportunity before judging intent.
Defaulting to training. Training is appropriate only when skill or knowledge is the main barrier. If habits, workflows, norms, or incentives are the issue, training alone will underperform.
Ignoring the social environment. Manager behaviour, peer norms, and informal signals often matter more than formal messages. Include social opportunity and modelling in the diagnosis.
Using the same intervention for every audience. Different roles face different barriers. Segment the analysis and tailor interventions accordingly.
Stopping at diagnosis. Some teams produce a neat COM-B chart and never convert it into actions, owners, timing, and measurement. Translate findings into operating changes and reinforcement mechanisms.
Failing to test assumptions. Behavioural conclusions are rarely perfect on the first pass. Pilot interventions, learn quickly, and refine before large-scale rollout.

9. How Behaviour Change Wheel Relates to Other Frameworks

The Behaviour Change Wheel fits best as a diagnostic and intervention-design tool inside a larger change effort. It is not a substitute for an end-to-end transformation model, but it is often a better instrument for understanding why a specific behaviour is not changing.

Behaviour Change Wheel and ADKAR

ADKAR focuses on an individual’s progression through awareness, desire, knowledge, ability, and reinforcement. It is useful for planning change adoption broadly. The Behaviour Change Wheel is more diagnostic about the drivers of a specific behaviour. A team might use ADKAR to structure the overall adoption journey and the Behaviour Change Wheel to design interventions for the hardest behaviour bottlenecks.

Behaviour Change Wheel and Kotter’s 8-Step Model

Kotter is a leadership and mobilisation framework for enterprise change. It addresses urgency, coalition-building, vision, and momentum. The Behaviour Change Wheel is more granular and behavioural. Use Kotter to lead the transformation and the wheel to design role-level adoption mechanisms within it.

Behaviour Change Wheel and the Theoretical Domains Framework

The Theoretical Domains Framework is often used alongside COM-B to deepen diagnosis. If COM-B tells you motivation is the issue, the Theoretical Domains Framework can help unpack whether the deeper causes involve beliefs, social role, memory, emotion, intentions, or reinforcement. In practice, COM-B gives the simple organising structure and the Theoretical Domains Framework provides more diagnostic detail.

Behaviour Change Wheel and nudge approaches

Nudge and choice-architecture methods usually focus on subtle changes in decision context. They can be powerful, but they address only part of the problem space. The Behaviour Change Wheel is broader because it includes skill-building, environmental design, incentives, restrictions, and enablement in addition to contextual nudges.

10. Key Takeaways

The Behaviour Change Wheel is a structured way to diagnose why a target behaviour is not happening and what interventions are most likely to change it.
Its core logic is COM-B: behaviour depends on capability, opportunity, and motivation.
It is especially valuable in transformations where adoption, frontline routines, or manager behaviours determine results.
Its biggest practical advantage is that it prevents teams from defaulting to communication and training.
It works best when the target behaviour is defined precisely and the diagnosis is grounded in observation and evidence.
Its biggest limitation is that it is a thinking tool, not a substitute for strong implementation, governance, and operating design.

11. FAQs About Behaviour Change Wheel

Is the Behaviour Change Wheel still relevant today?

Yes. It remains highly relevant because many change programmes still fail at the behaviour level. What has changed is how it is used: strong practitioners apply it in a more targeted, evidence-based, and experimental way than the broad awareness campaigns common in the past.

What is the difference between the Behaviour Change Wheel and ADKAR?

ADKAR is a broad change-adoption framework for individuals moving through a change journey. The Behaviour Change Wheel is a diagnostic and intervention-design framework for specific behaviours. If you need to understand why one critical behaviour is not happening, the wheel is usually the sharper tool.

Can small or early-stage companies use the Behaviour Change Wheel?

Absolutely. Smaller companies can use a lightweight version by focusing on one or two critical behaviours, interviewing a handful of users, and testing a few interventions quickly. The framework does not require a large PMO; it requires clarity and disciplined observation.

How long does it typically take to apply the Behaviour Change Wheel in a real project?

A focused application for one role or process can often be done in two to four weeks. A multi-role, multi-site transformation may take six to ten weeks for diagnosis and design, plus additional time for piloting and scaling interventions.

What data is needed to use the Behaviour Change Wheel?

The minimum useful inputs are a clearly defined target behaviour, a few interviews or observations, and some evidence on current performance. Better analysis comes from combining behaviour observation with process data, system usage data, manager feedback, and comparisons between high and low performers.

Change Management Frameworks >