What Is a Behaviour Sprint?

A Behaviour Sprint is a focused, five-day process that helps teams diagnose why people are not doing what they need to do, and design interventions that actually change what happens next.

Most change initiatives fail not because of bad ideas, but because they optimise the wrong thing. Teams launch tools, training, and communications, then wonder why nothing shifts. KPIs flatline. Adoption stalls. Old habits persist.

The Behaviour Sprint addresses this by making behaviour the core design problem, not an afterthought.

By the end of the sprint, you will have a precise target behaviour (not a vague outcome), a diagnosis of what is actually blocking action, tested interventions grounded in how people actually work, and evidence from real behaviour, not just feedback.

Every business problem is a behaviour problem.

Results like adoption, engagement, retention, and performance are reflections of upstream behaviours. Metrics only move when people do something different.

Traditional approaches fail because they chase outcomes instead of behaviours ("improve engagement" rather than "get managers to give weekly feedback"). They assume motivation is the problem when context is the real barrier. They launch solutions before diagnosing what blocks action. They measure vanity metrics like opens, clicks, and attendance instead of observable behaviour.

The Behaviour Sprint flips this. It starts with the behaviour you need to change, diagnoses the real blockers, and designs interventions that address what is actually in the way.

When to Run a Behaviour Sprint

Good fit

A Behaviour Sprint is the right format when there is a gap between what people know they should do and what they actually do. When previous initiatives have failed despite good intentions. When the outcome depends on sustained behaviour change, not one-off actions. When you need rapid alignment and decision-making across a team.

Poor fit

A sprint is not the right format when the problem is purely technical and the system does not work. When the solution is already known and just needs building. When key decision-makers are not available. When there is no willingness to test and iterate.

Sprint Formats

Intensive (5 consecutive days). Best for focused challenges and urgent timelines. High energy, fast decisions.

Extended (2 weeks, sessions spread). Best for most teams. Allows reflection between sessions and async work.

Deep Dive (4 weeks). For complex or cross-organisational challenges. More research, more stakeholders, more iteration.

The Methodology Behind the Sprint

The Behaviour Sprint is built on a set of foundational ideas that shape how behaviour is understood and changed.

Lewin's Equation: B = f(P, E)

Kurt Lewin showed that behaviour is a function of the person and their environment. Behaviour is not fixed. It is shaped by context. Change the context, change the behaviour.

This is why "try harder" rarely works. If the environment makes the right action awkward, risky, or unclear, even motivated people will stall.

The ME, WE, SYSTEM Lens

A triage framework for diagnosing where behaviour breaks down.

ME (Self). Individual psychology, capability, mindset. Barriers include confidence, skill gaps, information overload, mental model mismatch, habit strength, competing priorities, memory, willpower, and risk perception.

WE (Social). Norms, peer influence, social dynamics. Barriers include unclear norm signals, fear of judgement, lack of support, identity mismatch, and no visible modelling.

SYSTEM (Environment). Tools, processes, environment, rules. Barriers include task difficulty, cue invisibility, poor feedback, missing resources, unhelpful structures, and high perceived cost.

Most "motivation problems" are actually context problems. This lens helps you see where the real drag lives.

The Drive Grid

At the heart of the Behaviour Sprint is the Drive Grid, a codified system that connects diagnosis to design. It includes 24 Barrier Cards (behavioural frictions that explain why people stall), 8 Strategies (evidence-based approaches to shift behaviour), and 24 Tactics (concrete design moves that operationalise the strategies).

This system eliminates guesswork. Instead of brainstorming from intuition, teams diagnose barriers systematically and select interventions with known mechanisms.

The Eight Strategies

Once you have diagnosed the barrier, you select a strategy. These are the eight behavioural levers available in the Drive Grid:

1. Remove Friction. Cut steps, simplify, pre-fill, automate.

2. Add Friction. Insert pauses, confirmations, or delays where needed.

3. Give Scaffolding. Break tasks down, offer templates, provide cues.

4. Add Spark. Make the cue pop at the right moment.

5. Frame Value. Reframe benefits, make costs visible, connect to goals.

6. Add Social Proof. Show what others do, surface norms, use messengers.

7. Close Feedback Loop. Surface progress, flag errors, show what is working.

8. Lock-In Commitment. Get early pledges, create stakes, build momentum.

The Change Pathways

Not all behaviour change is the same. The pathway depends on what you are trying to achieve.

Start. Break inertia. Make the first action obvious, tiny, and in-flow.

Stop. Halt unwanted behaviour by removing cues, interrupting actions, or substituting rewards.

Evolve. Achieve big changes through small, sequenced goals and progressive challenge.

Realign. Detect drift and gently guide behaviour back on track before relapse.

Modify. Fine-tune established behaviours to prevent burnout and maintain effectiveness.

Choose your pathway before you design your intervention.

How the Five Days Work

Pre-Sprint: Set the Stage (1 to 2 weeks before Day 1)

The quality of a Behaviour Sprint is largely determined before Day 1 begins. The team drafts a challenge statement using the formula: "How might we encourage or discourage [target audience] to [target behaviour] so that [outcome for user] and [outcome for organisation]?"

The team also writes a Behaviour Statement defining WHO does WHAT, WHEN, and INSTEAD OF what current behaviour. This statement must pass four tests: Is it specific? Is it observable? Does it replace something? Is it time-anchored?

Day 1: Frame the Problem

Build shared understanding. Get everyone seeing the same thing. The team walks through the core principles, presents the draft challenge, conducts expert interviews, clusters "How Might We" notes, rewrites the challenge statement together, selects the keystone behaviour using frequency, importance, leverage, and changeability criteria, and defines success in observable terms.

Outputs: Finalised Behaviour Challenge Statement, selected Keystone Behaviour, documented Success Criteria.

Day 2: Map and Diagnose

Understand what actually happens when people try to perform the target behaviour. The team maps the behaviour journey step by step (what people are doing, thinking, feeling, and where things go wrong), diagnoses barriers using the ME-WE-SYSTEM lens and Barrier Cards, and prioritises using the Force Filter (scoring barriers on impact and ease to shift).

Outputs: Behaviour Journey Map, diagnosed Barriers with ME-WE-SYSTEM labels, 1 to 2 Priority Opportunity Points.

Day 3: Design Interventions

Generate intervention ideas grounded in behavioural science, not intuition. The team selects strategies from the Drive Grid based on diagnosed barriers, explores tactics, sketches ideas individually, shares and clusters, and converts the best ideas into Behaviour Design Hypotheses: "If we [intervention], then [target users] will [target behaviour], because [behavioural mechanism]. We will know it is working when [early signal]."

Outputs: 1 to 2 Behaviour Design Hypotheses with clear rationale linking barrier to strategy to tactic to intervention.

Day 4: Build the Prototype

Build a testable version of the intervention. The team storyboards the intervention step by step, chooses the minimum viable prototype format (paper mockup, slide walkthrough, role-play script, working digital prototype), builds it, runs through it, and writes the test protocol including who to test with, what to observe, and what to ask.

Outputs: Working Prototype, Test Protocol, Observer Scorecard.

Day 5: Test and Decide

Validate the hypothesis by observing real behaviour, not just collecting opinions. The team runs 5 tests of 30 minutes each (context questions, prototype exposure, follow-up questions), synthesises findings, evaluates against the hypothesis (validated, partially validated, or invalidated), and decides next steps: iterate, pivot, pilot, or scale.

Outputs: Test Findings, Hypothesis Evaluation, Clear Next Steps with Owners and Timelines, Sprint Summary Document.

What You Get from a Behaviour Sprint

1. Behaviour Challenge Statement. A clear, evidence-based articulation of the behaviour problem.

2. Behaviour Journey Map. A visual map showing how behaviour unfolds in context.

3. Barrier Diagnosis. A systematic analysis of why behaviour breaks down, using the ME-WE-SYSTEM lens.

4. Behaviour Design Hypothesis. A testable statement linking intervention to expected change.

5. Tested Prototype. A functional prototype validated against real user behaviour.

6. Test Findings. Documentation of what was observed during testing.

7. Next Steps Roadmap. Clear actions with owners and timelines.

Specialised Sprint Formats

Team Behaviour Sprint

Focused on internal team behaviour: ways of working, tool adoption, manager behaviour, culture shifts. Emphasis on social barriers (norms, modelling, group dynamics). Testing is done with team members. Interventions often include rituals, meeting formats, and shared artefacts.

Product Behaviour Sprint

Focused on external user behaviour within a product or service. Emphasis on system barriers (UX, flows, cues, feedback). Testing is done with actual or representative users. Interventions include interface changes, notifications, and onboarding flows.

Iteration Sprint

A shorter follow-up sprint (2 to 3 days) to refine based on learnings from a previous sprint. Day 1: review findings, diagnose what failed, generate refined hypotheses. Day 2: build improved prototype. Day 3: test and evaluate.

What the Behaviour Sprint Does Not Cover

The sprint is focused and intentionally limited.

Full implementation. The sprint produces a tested prototype and roadmap, not a production-ready solution.

Rigorous impact measurement. Day 5 testing validates directional learning, not statistical significance.

Deep primary research. The sprint uses existing insights and rapid testing, not months of ethnography.

Multiple behaviour challenges. Each sprint focuses on one keystone behaviour.

Change management. The sprint designs interventions but does not manage organisation-wide buy-in.

How Is a Behaviour Sprint Different from a Design Sprint?

A design sprint (as developed by Google Ventures) focuses on prototyping and testing a product solution in five days. It starts with a challenge and ends with a tested prototype.

A Behaviour Sprint focuses on understanding the behaviour itself before jumping to solutions. It starts with a situation where behaviour is not as expected and ends with a diagnosed barrier, a tested intervention, and a clear next step. The output might be an interface change, a team ritual, a communication redesign, a consultation script, or a recommendation to change the environment rather than the product.

The key difference: a design sprint assumes the team knows what problem to solve. A Behaviour Sprint assumes the team does not yet have the right reading of the problem.

Where Have Behaviour Sprints Been Used?

Health technology. Three Behaviour Sprints for MyHabeats identified why patient engagement with a post-bariatric surgery app dropped after three weeks. The diagnosis shifted the product strategy from adding features to supporting the real moments where eating habits are shaped: in kitchens, with family, during emotional triggers. 90-day retention improved.

Government policy. One-day Behaviour Sprints with six ministries of the Estonian Government tackled live policy challenges including vaccination uptake, disability access to work, and police-community trust. In the vaccination sprint, the team discovered trust was being built or lost in a thirty-second GP consultation moment.

Enterprise AI adoption. A seven-week sprint-based engagement with Infosys Consulting diagnosed why AI usage was inconsistent after rollout. The work produced a diagnostic and intervention system focused on five behavioural levers: trust, enablement, fit, capability, and adaptation.

Organisational values and culture. Working with the World Economic Forum and Accenture, Behaviour Sprints helped ten high-growth startups identify where values slip in day-to-day decisions and design routines that made them easier to live.

Learning and training. A sprint-based approach with D&AD turned a well-regarded masterclass programme into a more reliable system by designing for trainer behaviour, group dynamics, and knowledge transfer beyond the session.

The Behaviour Sprint Toolkit

The Behaviour Sprint is powered by BehaviourKit, a codified system for understanding and changing behaviour.

BehaviourKit includes 90+ tools, card decks, facilitation guides, and training courses. The Drive Grid, Barrier Cards, ME-WE-SYSTEM lens, and related frameworks are available through BehaviourKit for teams who want to run behaviour-informed work independently.

Explore BehaviourKit: behaviourkit.com

Run a Behaviour Sprint with Lauren A. Kelly

Lauren A. Kelly is the creator of the Behaviour Sprint methodology. She is a behavioural strategist based in Manchester, UK with 15 years of experience across product, programmes, teams, learning, policy, and AI adoption.

She has run Behaviour Sprints with teams at MyHabeats, Infosys Consulting, the Estonian Government, the World Economic Forum with Accenture, D&AD, PwC, and others.

Book a sprint fit check: laurenakelly.com/behaviour-sprint

Learn more about working with Lauren: laurenakelly.com

Subscribe to The Behavioural Read: Lauren's newsletter on what most teams miss about behaviour.

Frequently Asked Questions

How long does a Behaviour Sprint take?

The intensive format runs over 5 consecutive days. The extended format runs over 2 weeks with sessions spread. The deep dive format runs over 4 weeks for complex or cross-organisational challenges. Most teams use the extended format.

How much does a Behaviour Sprint cost?

Sprint costs depend on scope, complexity, and format. Contact Lauren directly for a specific quote based on your situation.

Can we run a Behaviour Sprint remotely?

Yes. Sprints have been run remotely, in person, and as hybrids. The critical requirement is access to the real behaviour: the people experiencing it, the context it happens in, and the system around it.

What do we need to prepare before a sprint?

Four things. A draft challenge statement. Existing data on the behaviour (analytics, research, feedback). Access to 5 target users for testing on Day 5. And the right people available for the sprint sessions (ideally 5 to 7 people including a decision-maker, a subject matter expert, a designer, and someone close to the audience).

What is the difference between a Behaviour Sprint and a behaviour change workshop?

A workshop introduces behavioural concepts to a team. A Behaviour Sprint works on a specific, live problem and ends with a tested intervention and a clear next step. The difference is between learning about behaviour and designing a solution for a specific behaviour.

What is the difference between a Behaviour Sprint and a Design Sprint?

A Design Sprint (Google Ventures method) assumes the team knows what problem to solve and focuses on prototyping a solution. A Behaviour Sprint assumes the team does not yet have the right reading of the behaviour problem. It focuses on diagnosis first, then designs an intervention grounded in the diagnosed barrier. The output is often not a product prototype but a changed process, environment, communication, or routine.

What happens after the sprint?

If the hypothesis was validated: design a pilot with a larger sample over 2 to 4 weeks. If the hypothesis needs iteration: schedule a 2 to 3 day iteration sprint. If the hypothesis was invalidated: return to the barrier diagnosis and generate alternative hypotheses. For all paths: track behaviour signals, not just satisfaction metrics.

Can our team learn to run Behaviour Sprints themselves?

Yes. The Behaviour Sprint methodology is supported by BehaviourKit, which provides the tools, frameworks, and facilitation guides teams need to run sprints independently.

What is the Drive Grid?

The Drive Grid is a codified system within BehaviourKit that connects diagnosis to design. It includes 24 Barrier Cards (behavioural frictions), 8 Strategies (evidence-based approaches), and 24 Tactics (concrete design moves). It eliminates guesswork by giving teams a systematic way to move from "we know what is blocking the behaviour" to "here is what we will do about it."

What is the ME-WE-SYSTEM lens?

A diagnostic framework for identifying where behaviour breaks down. ME covers individual psychology (confidence, skill, memory, habits). WE covers social dynamics (norms, peer influence, identity, support). SYSTEM covers the environment (tools, processes, cues, resources, structures). Most problems that look like motivation problems turn out to be context problems when examined through this lens.