What is Behaviour Thinking?

The short answer

Behaviour Thinking is a practical discipline for seeing, judging and working with the behaviour that work depends on.

It is a way of thinking with behaviour: noticing it in the room, asking better questions of it, judging it honestly, and using it to explore ideas and make decisions. Behaviour change is sometimes the outcome. The discipline itself is the seeing, the questioning and the judging.

At its smallest, it is a single question asked early in a project: what behaviour does this depend on? That one question, asked before the money commits, can change the direction of a plan. At its fullest, it is a methodology for defining, judging, designing and supporting the behaviours that products, services, strategies, policies and business models need in order to work.

One plain definition underneath it all. A behaviour is something a person does, at a moment, in a situation. If you cannot picture it happening, you have not named the behaviour yet. We call this the camera test, and it does more work than anything else in this guide.

It can be used as a lens, a canvas, a workshop, a review, a design method, a team capability or an organisational practice. The scale changes. The core move stays the same: stop treating behaviour as an assumption, and start treating it as the thing the work depends on.

Whatever the scale, the discipline does three things to behaviour that most work never does. It makes behaviour visible: what, exactly, must people do? It makes behaviour judgeable: is that realistic, supported, and worth the risk? And it makes behaviour changeable: what needs to shift in the product, service, message, system or strategy so that action becomes more likely?

The rest of this guide explains why the discipline needs to exist, where it came from, and how to use it at every size.

Where good work fails

Walk across any park and you will find two paths. There is the paved one, laid by people who planned the park. And there is the worn line across the grass, made by thousands of feet that had somewhere to be. Planners call these desire paths. They are what happens when a design meets real behaviour, and real behaviour wins.

Every organisation has desire paths. The finance process people route around. The new tool that sits open in a tab while the old spreadsheet does the actual work. The service redesign that customers experience once and quietly avoid. The training everyone enjoyed and nobody applied.

Here is the pattern underneath all of them. Most work gets judged on the visible plan. Is it desirable? Is it feasible? Is it viable? Is it on budget, on brand, on time? Those are good questions, and teams have become genuinely skilled at answering them. But underneath every plan sits a quieter assumption: that people will do the thing the plan needs. Customers will switch. Staff will adopt. Users will return. Managers will follow the process when the quarter gets busy.

That assumption almost never gets tested. It hides inside familiar words: adoption, engagement, uptake, compliance, retention, culture change. Useful words, right up until they turn to fog. A plan can say "we expect strong adoption" and pass every review in the building, because nobody in the review asked who has to do what, at which moment, instead of what they do now.

The plan looks good where people are not yet involved. It breaks where someone has to act. And when it breaks, the cost arrives under other names: wasted budget, a stalled rollout, a support team doing the model's job by hand, work people quietly route around. Nobody writes "the managers kept using their spreadsheets" in a post-mortem, but that is usually what happened.

The core idea: behaviour is the test

Design Thinking gave the world three questions that changed how organisations build things. Is it desirable? Is it feasible? Is it viable? Behaviour Thinking adds a fourth, and argues it should often be asked first.

Is it behaviourally fit? Can this work survive contact with what people actually do?

The question sounds simple. Answering it honestly is the method. Because behaviour is never just a choice floating in space. It happens at a moment, under pressure, next to an old habit that already works well enough. A strategy can be coherent and still depend on behaviours that are unlikely, unsupported, or too costly for people to sustain. A product can be useful and still lose to the fridge at ten o'clock at night. A message can be understood perfectly and acted on by nobody.

Pension auto-enrolment is the cleanest public example of what taking the question seriously can achieve. For decades, governments tried to persuade people to save for retirement: campaigns, incentives, education. The numbers barely moved, because the plan depended on millions of people filling in a form during weeks when they had more urgent things to do. Auto-enrolment redesigned the situation so that saving required no behaviour at all. You were in unless you opted out. Participation moved from persuasion to design.

Behaviour Thinking treats behaviour as the test of the work, and gives teams a repeatable way to run that test: name the behaviour, judge its conditions honestly, and change the work before the behaviour becomes the reason it fails.

A scale of practice

Behaviour Thinking is sized to the work in front of you, and it grows the way useful disciplines usually grow: from one good habit into a way of operating.

One question. What behaviour does this work depend on? Ten seconds, free, and it has redirected more projects than most steering committees. Ask it of the next brief that crosses your desk and watch what happens to the room.

A lens. You start seeing plans through the behaviours they assume. The strategy deck reads differently once you notice the sentence that begins "people will just". So does the business case, the campaign, the org chart.

A question set. Who has to do what, at which moment, instead of what, under what pressure? Five questions that turn fog into something a team can actually examine.

A method. Name the behavioural bet. Understand the current route. Find the collision. Judge the conditions. Decide what to change. One bet, six moves, a verdict.

A methodology. A repeatable way to define, diagnose, design, test and support behaviour across whole projects.

A capability. A team learns to make behavioural judgement part of how it works: in reviews, in planning, in the meetings that already exist. The judgement stops depending on one person.

An infrastructure. The organisation builds the rituals, standards, tools and decision points so behaviour is never left to instinct. New work gets judged by default. This is the size at which the discipline pays for itself annually rather than per project.

Most people enter at the question and stay for the method. Organisations that keep meeting the same behavioural problems climb further. Nobody needs the whole ladder to get value from the first rung, and the first rung costs nothing.

The basic move

Whatever the scale, the basic move in Behaviour Thinking is translation. It turns vague success words into specific human actions.

"Adoption" becomes a manager opening the tool at the moment the old workaround would normally win. "Engagement" becomes a customer coming back on day three, or a user asking for help instead of quietly giving up. "Culture change" becomes a team lead challenging an unrealistic deadline in the planning meeting, under pressure, while the old norm is still easier. "Trust" becomes a person handing over personal information before they have proof the service will help them.

Fog in, behaviour out. Once you have seen the translation done a few times, you start doing it automatically, and plans read differently forever.

The translation produces the discipline's basic unit: the behavioural bet, the point where a piece of work assumes someone will do something. Design thinking has the problem. Service design has the journey. Strategy has the choice. Behaviour Thinking has the bet, and every plan is carrying several.

Once a bet is visible, it can be worked with. Who has to act? What do they do now instead? Why does the current route make sense to them? Where will the new behaviour collide with the old system? What evidence do we have? What breaks if we are wrong? The scale of the engagement changes; this move never does. Turn the assumption into behaviour, then decide what the work must do about it.

And that word, decide, is deliberate. Behaviour Thinking is complete when it changes a decision. Everything short of that, however enjoyable the workshop, is preparation.

Where it came from

Behaviour Thinking was coined in 2014 by Lauren A. Kelly, a behavioural scientist who kept meeting the same pattern in live projects: good work, properly funded, praised in every review, coming apart at the exact point where someone had to act. Behavioural science had the evidence to explain why. Too much of it stayed in journals and reports, written for other researchers rather than for a product team with a launch in six weeks.

So the method was built the other way round: from live work, backwards into principles. It grew through practice rather than publication. In 2018 it became equipment, with the launch of BehaviourKit, first as a collection of canvases, prompts and methods, later as a connected way of working through whole projects. In 2022 it entered the classroom, with programmes and courses at Hyper Island, Manchester Metropolitan University and Politecnico di Milano.

Along the way the method has run inside organisations including PwC, Accenture, Infosys, the World Economic Forum and the Estonian Government, on problems ranging from AI adoption to vaccination uptake to what a school should teach instead of two GCSEs.

Behaviour Thinking® is a registered UK trademark, created and led by Alterkind. It is deliberately built to spread: the thinking is open, the instruments are shareable, and the name exists so the method stays coherent as more people use it.

Behaviour Thinking and Design Thinking

The two are relatives, and they work best side by side.

Design Thinking asks what people need. Behaviour Thinking asks what people must do. Design Thinking is at its strongest early, when the problem is fuzzy and the team needs empathy, ideas and prototypes to find what is worth building. Behaviour Thinking is at its strongest at the moments of commitment: when an idea is about to receive serious money, when a service goes live, when the plan starts depending on thousands of people acting differently on a Tuesday.

A team can run a flawless design process and still leave the behaviour untested. The idea is validated, the prototype is loved, the pilot works. Then the pilot scales, the founding enthusiasm thins out, and the product meets people who never attended a workshop. Behaviour Thinking is the discipline for exactly that seam: it pressure-tests whether the validated idea can survive real habits, real pressure and real systems.

Design Thinking is a bridge into this method, never a villain. If your team already thinks in terms of people, you are most of the way here. The remaining step is a shift in the unit of analysis: from needs, which are states, to behaviours, which are events. Needs explain why someone might act. Behaviour Thinking works on whether they actually will, at the moment the work requires it.

Behaviour Thinking and behavioural science

Behavioural science is the evidence base: decades of research into how people actually decide and act, as opposed to how spreadsheets assume they do. Behaviour Thinking is a working method built on that base. The relationship matters, because the two get confused, and the confusion causes two common failures.

The first failure is treating behavioural science as a library of tricks. Frameworks and nudges get bolted onto finished work: a scarcity message here, a default there, a poster campaign to fix an adoption problem that was never about awareness. This is behavioural science as decoration, and it fails because it intervenes at the surface of a problem whose causes sit in the system underneath.

The second failure is treating behavioural science as a lecture course. Teams learn the theories, enjoy the workshop, and return to projects that have no place to use any of it. The launch gate still asks about budget, risk and delivery. Nothing in the week asks anyone to use the judgement they just learned, so it fades.

Behaviour Thinking is the answer to both. It carries the science into the structure of the work itself: into how problems get framed, how plans get reviewed, how decisions get made, and what evidence is required before money commits. You do not need a psychology degree to use it. You need a live project, an honest question, and a method that fits inside a working week.

Behaviour Thinking, systems and leverage

Two older disciplines run through this method, and naming them helps explain why it works.

The first is systems thinking. Behaviour is never freestanding. It is the output of a system: incentives, workloads, tools, norms, what gets praised, what gets punished, what the busiest week of the quarter makes impossible. When a manager ignores the new dashboard and phones her warehouse contact instead, the system is working exactly as built. Her old route is faster, it has never let her down, and being the person who knows her store without needing a system is part of how she earned respect. Behaviour Thinking treats that old route with respect, because the old route always makes sense from inside. The method's central diagnostic object, the collision, is a systems idea: the point where the new behaviour meets everything the current system rewards, protects and normalises. Find the collision and you have found where the plan will actually be decided.

The second is strategic leverage. In any plan there are places where a small change moves a large outcome, and places where enormous effort moves almost nothing. Behaviour is very often the leverage point, for a simple reason: it sits at the narrowest part of the funnel. Millions can be spent on strategy, technology and communication, and all of it converges on a person, at a moment, doing a thing. Judge that moment early and the whole investment gets cheaper to protect. This is why the method insists on working before money commits where possible. A behavioural judgement that costs a day, made before a rollout that costs two million, is the highest-leverage line in the budget. It is also why the method ends in verdicts rather than reports: proceed, test, simplify, support, redesign, sequence, localise, pause, stop. Each verdict is a strategic option, and choosing between them is where leverage gets exercised.

Put plainly: behavioural science supplies the evidence, systems thinking supplies the diagnosis, and strategic leverage supplies the point. Behaviour Thinking is where the three meet a Tuesday deadline.

How the discipline is organised: three questions

The discipline expresses itself through three named questions, each owning a stage in the life of a piece of work, from the boardroom to the go-live to the years afterwards. None of them is the whole of Behaviour Thinking; each is Behaviour Thinking applied at a particular moment.

Behavioural Fit is the judgement layer. Its question: can this work survive real behaviour? Use it before a launch, a scale decision, an investment, an AI rollout, an operating model change. This is where behavioural bets get named and priced while the plan can still change cheaply.

Behavioural Design is the action layer. Its question: how do we shape the moment so people can act? Use it on live work: onboarding, drop-off, trust, adoption, follow-through, any place where the behaviour is struggling to happen. This is where conditions get changed rather than people blamed.

Behavioural Infrastructure is the system layer. Its question: what needs to exist so the behaviour holds over time? Use it when a behaviour must outlive its launch: owners, rituals, manager behaviours, decision standards, maintenance, repair routes. Without infrastructure, behaviour depends on heroics, and heroics do not scale, take holidays, or survive a reorganisation.

Alongside the three questions sits a strategic application. The Invisible Business Model asks what hidden behaviours a business model depends on: the visible model shows how value is meant to move, the invisible one shows what people have to do for any of it to happen. It is Behavioural Fit pointed at the model itself, and its canvas, a strategic one-pager for finding the hidden behavioural bets inside a plan, is the discipline's most widely shared instrument.

Most failed change efforts skipped a question. The strategy was judged but the moment was never designed. The moment was designed but nothing held it up. All three, asked in order, are the discipline's insurance policy.

How it works in practice: the six moves

The working process walks one behavioural bet through six moves. Teams learn it in an afternoon and get better at it for years. It is written here as a sequence because sequences are easy to learn; in practice teams loop back constantly, and the moves become a shared language rather than a checklist.

1. Name the bet.
What it looks like: you write the behaviour the plan depends on as one structured sentence. For this to work, this actor must do this behaviour, at this moment, despite this pressure. Keep it filmable: if you could not point a camera at it, it is not a behaviour yet, it is an outcome wearing a costume. "Improve stock accuracy" is an outcome. "Store managers review and act on the tool's recommendations every Monday morning, despite staffing gaps" is a behaviour.
Why it matters: fog cannot be judged. A filmable sentence can.

2. Respect the current route.
What it looks like: you describe what people do now instead, and why it makes sense to them. The managers trust their own judgement. It is faster, it has never failed them publicly, and knowing your store without needing a system is a point of pride.
Why it matters: the old route is your real competitor, and it is undefeated at home. Plans that treat it as laziness or resistance design interventions for a problem that does not exist.

3. Find the collision.
What it looks like: you locate the point where the new behaviour meets what the current system rewards and protects. Here: the organisation praises decisive local judgement and firefighting, and the tool asks managers to defer to a recommendation. Monday morning is also the week's worst moment for reflective work.
Why it matters: the collision is where the plan will be decided. Everything else is upstream of it.

4. Weigh the conditions.
What it looks like: you ask what pulls people back, what the behaviour asks of them, and what would have to hold it up: training, yes, but also who owns it, which ritual carries it, what a manager's manager asks about on Wednesdays.
Why it matters: behaviour that has to be sustained by willpower alone is already failing, just slowly.

5. Judge exposure against evidence.
What it looks like: two honest ratings. Exposure: what breaks, and how expensively, if the behaviour does not happen? Evidence: what proof exists that it will? In the example, exposure is high (the whole model rides on Mondays) and evidence is weak. The pilot may have worked because someone at head office phoned every store each Monday, which is enthusiasm doing the job the design was supposed to do.
Why it matters: high exposure with weak evidence is the danger zone, and it is exactly where organisations most often scale. This one question, asked in every review, would save more money than most change programmes.

6. Decide.
What it looks like: you end in a verdict. Proceed, test, simplify, support, redesign, sequence, localise, pause or stop. The retailer's verdict: test the Monday behaviour properly in six stores before scaling, and roll the tool out as a weekly operating behaviour rather than a technology installation.
Why it matters: a canvas full of honest answers changes nothing on its own. The decision is the product. Rolled out as a technology, the investment becomes a dashboard. Rolled out as an operating behaviour, it becomes the model.

Two things change around the moves, and both are easy to miss.

The discipline changes research. Instead of asking whether people like the idea, it asks what would have to be true for the behaviour to happen, and what evidence would change our mind. Those are different studies, and the second kind is the one that protects money.

It also changes what teams measure. Once work is live, Behaviour Thinking looks for early behavioural signals rather than waiting for late outcomes: the manager who opened the tool this Monday, the patient who came back on day three. Outcomes usually arrive too late to help; behaviour tells you the truth in the first fortnight.

Beyond the six moves sit the other two questions. When the verdict is support or redesign, Behavioural Design takes over: shaping the moment itself, the way Estonia's vaccination work moved from revising policy documents to scripting a thirty-second GP consultation, because that half-minute was where the decision actually lived. Design starts by naming the route being asked of people: are they starting something new, stopping something, evolving what they already do, returning after a lapse, or modifying how they act? Different routes need different support, and treating them all as "change" is how programmes end up supporting nobody in particular. And when the behaviour has to hold for years, Behavioural Infrastructure takes over: rituals, standards, owners and trained trainers, so the judgement survives staff churn and the end of the project.

Continue the field guide: the six moves in detail

What Behaviour Thinking is not

It is a discipline of honesty before it is anything else. If work depends on people doing something, the ethical move is to say so: to make the behavioural assumption visible before it becomes someone else's burden, carried by a support team, a frontline worker, or the person the plan was supposed to serve. The work improves conditions so that a genuinely worthwhile behaviour becomes easier, clearer and better supported, with the assumptions named in the open, on a canvas, in front of the people who own the plan. Work that only succeeds by tricking people fails the discipline's own test, because tricked behaviour does not hold.

It is a thinking discipline before it is a change discipline. Behaviour Thinking is thinking about behaviour and working with it: asking questions of it, seeing it happen in the room, using it to explore new ideas and pressure-test old ones. Plenty of engagements end with no behaviour change programme at all, because the verdict was proceed, or stop, or this was never a behaviour problem. When change is needed, the discipline shapes it. Change is one of its outputs, never its definition.

It works alongside design methods, never as their replacement. Teams fluent in design thinking, service design or product discovery adopt it fastest, because the habits of research and iteration transfer directly.

It is a working method, so it asks to be judged like one. The test of Behaviour Thinking is whether decisions change and signals move, on live work, within weeks. A method that only produces workshops has failed by its own standard.

And it is honest about its limits. Some problems are genuinely about awareness, or price, or a product that does not work. The method's first question, asked of any brief, is whether this is a behaviour problem at all. Sometimes the most valuable verdict is that it is not.

Who it is for

Behaviour Thinking is for people whose work depends on what other people do. That is a dependency, not a job title, and it covers two broad groups.

People who decide. Founders, executives, service owners, change and venture leads, policy makers. Their plans carry behavioural bets, usually unpriced. The method gives them a way to judge those bets before committing money, and a vocabulary for challenging work that arrives with "adoption" written where a behaviour should be.

People who deliver. Designers, researchers, product managers, change and comms teams, consultants, teachers. Their job is to make behaviour happen inside live work. The method gives them the tools to name it, diagnose it and design for it, plus the standing to push back when the brief assumes people will "just" do something.

Many roles need this capability. Almost nobody needs a new job title to use it.

Getting started

Three routes in, depending on where the work is.

Run it yourself, today. The Invisible Business Model Canvas, a strategic one-pager for finding the hidden behavioural bets inside a plan, is free to download. One A3 page, six moves, ending in a decision. An hour alone, or ninety minutes with the team. The field that usually stops the room is the exposure question: what breaks if this behaviour does not happen, and what proof do we have that it will?

Bring it into live work. BehaviourKit is the toolkit for applying the discipline inside delivery: the canvases, prompts and workflows teams run week to week. The Playbooks, a series of short free guides, cover the common failures one at a time.

Bring in judgement. Alterkind is the practice that created the discipline and applies it: the Behavioural Fit Session and Review for decisions carrying real money, and capability programmes for teams that want the judgement to stay in-house.

Frequently asked questions

Is Behaviour Thinking the same as behavioural science?
Behavioural science is the research field. Behaviour Thinking is a working discipline built on it, designed for live projects rather than journals. You need the second to use the first on a Tuesday.

Do we need a behavioural scientist to use it?
No. The instruments are designed for teams. A behavioural scientist adds depth and judgement, which matters most when the exposure is high, but the method's whole purpose is to make behavioural judgement usable by the people already doing the work.

Is it manipulation?
The opposite, and deliberately so. If work depends on people doing something, we should be honest about that dependency. The discipline makes the assumption visible before it becomes someone else's burden, and requires evidence rather than optimism. If a plan only works while people are fooled, the verdict is redesign or stop.

How is it different from service design?
Service design shapes the journey. Behaviour Thinking judges the specific behaviours the journey depends on, and whether they will happen under real pressure. They pair naturally: many of the method's heaviest users are service designers.

When is the right moment to use it?
The cheapest moment is before money commits: before a launch, a scale decision, an investment. The most common moment is when live work is struggling: adoption stalling, drop-off, the old way creeping back. The most valuable moment, for teams who keep meeting the same problems, is building it in permanently.

Does it only work on customers?
It works on any behaviour a plan depends on: customers switching, staff adopting, managers following process, partners sharing data, students asking for help earlier. Internal behaviour is where the biggest unpriced bets usually hide.

What is a behavioural bet?
Any point where a plan assumes someone will do something differently. Every plan carries them. The method's job is to find the ones carrying the most money and the least evidence.

Where does the name come from?
It was coined in 2014 and is a registered UK trademark, created and led by Alterkind. The trademark exists so the method stays coherent as it spreads; the thinking itself is open, and the canvas is free.

A short glossary

Behaviour Thinking® is the discipline of seeing, judging and shaping the behaviour work depends on. It is practised through the Behavioural Fit Review, BehaviourKit and team capability programmes, and its core instrument, the Invisible Business Model Canvas, is free to download. Behaviour Thinking is a registered UK trademark, created and led by Alterkind, the behavioural practice run by Lauren A. Kelly.

Get the canvas Book a Behavioural Fit Session Explore BehaviourKit