Experimentation: Moving at the Speed of Learning
Why the best-designed interventions still surprise us, and how small, safe-to-fail experiments turn those surprises into lasting change.
By Erik Bohjort, licensed psychologist and creator of the CLEAR Change Framework, Stockholm, Sweden
Experimentation in CLEAR means testing hypotheses. It means running small, contained trials that are designed to learn, not just to succeed. This page is an excerpt from Chapter 5, “Experimentation: Moving at the Speed of Learning”, of The CLEAR Change Framework, the upcoming book by Erik Bohjort.
Erik Bohjort is a licensed psychologist and behavioural design specialist based in Stockholm, Sweden, and the creator of the CLEAR Change Framework. Below are the chapter’s opening pages, its Experiment Canvas and its questions for guiding an experiment, quoted as written. The full chapter is free as a PDF.
There was a grocery store in Sweden where I once helped redesign an entire bread shelf. The brief seemed simple enough: make healthier bread options more visible, more attractive, more chosen. We were working with a major retailer and had the backing of the Swedish Food Agency’s Nyckelhålet, the keyhole symbol that marks products meeting strict nutritional standards. We placed the healthiest breads at eye level, added clear Nyckelhålet signage in the style the Food Agency itself uses, and created what I was sure would be a textbook nudge. If you had asked me the day before launch whether this would increase healthy bread sales, I would have said yes without hesitation. The behavioral science was sound, the placement was optimized, the signaling was clear.
It didn’t work. In fact, healthy bread sales slightly declined.
Let that sink in for a moment. We did everything right, by the book, by the research, by the theory, and the result was the opposite of what we intended. The prominent health messaging didn’t attract people to the bread; it subtly repelled them. The Nyckelhålet, with all its authority and good intentions, carried an unspoken message that shoppers heard louder than we anticipated: this is the healthy bread. The boring bread. The bread you should eat, not the bread you want to eat.
I stood in that store aisle, looking at the numbers on my screen, and experienced something I’ve come to recognize as one of the most important moments in any change process: the moment your assumptions collide with reality. It’s humbling. It’s uncomfortable. And it’s absolutely essential. Because that collision, that gap between what you expected and what actually happened, is where real learning lives.
This is what experimentation is about in the CLEAR framework. Not the triumphant launch of a perfectly designed intervention. Not the validation of what you already believe. Experimentation is about having the intellectual courage to test your ideas against reality, and the emotional maturity to learn from whatever comes back, especially when what comes back surprises you.
What Experimentation Means in CLEAR
After you’ve established Clarity, a shared understanding of where you’re heading and why, and after you’ve identified your Leverage, the people, points, and problems that give you the greatest potential for impact, you arrive at the moment of action. Experimentation is where CLEAR becomes tangible. It’s where ideas leave the whiteboard and enter the real world.
But here’s the critical distinction: in CLEAR, experimentation does not mean “implementation.” It doesn’t mean rolling out your grand plan across the entire organization and hoping for the best. That’s what traditional change management often does, and it’s precisely why so many initiatives fail. You’ve done all this careful thinking, built all this alignment, identified all these leverage points, and then you bet the farm on a single, large-scale deployment. If it doesn’t work, you’ve spent your budget, exhausted your people, and eroded trust.
Experimentation in CLEAR means testing hypotheses. It means running small, contained trials that are designed to learn, not just to succeed. I sometimes describe it to students as the difference between “launching a rocket” and “sending up a weather balloon.” A rocket commits you to a trajectory. A weather balloon tells you which way the wind is blowing before you commit to anything.
The concept is rooted in what some researchers call “safe-to-fail” experiments, as opposed to “fail-safe” designs. A fail-safe design tries to engineer out all possibility of failure before deployment. It aims for perfection before action. A safe-to-fail experiment, by contrast, accepts that failure is not only possible but informative. You design the experiment so that if it doesn’t work, the consequences are small, the learning is rich, and you can iterate quickly. The system absorbs the failure without breaking.
Dave Snowden, who developed the Cynefin framework for decision-making in complex environments, uses the distinction between “safe-to-fail” probes and traditional pilot programs to make exactly this point. A pilot program is designed to succeed, and when it doesn’t, it’s considered a failure. A safe-to-fail probe is designed to learn, and the only way it can fail is if you don’t pay attention to the results. In complex systems, and organizations are always complex systems, safe-to-fail probes are the only honest approach. Pretending you can predict the outcome of a complex intervention is not confidence; it’s delusion.
This distinction matters enormously in organizational change. Most leaders I’ve worked with are deeply uncomfortable with the word “experiment” in a business context. It sounds uncertain. It sounds like you don’t know what you’re doing. But that’s exactly the point. In complex systems, nobody knows what’s going to work until they try it. The leaders who pretend otherwise are the ones who commission eighteen-month strategic plans, execute them rigidly, and then wonder why the organization hasn’t changed. The leaders who embrace experimentation are the ones who say, “We have a strong hypothesis. Let’s test it. Let’s see what happens. And let’s be ready to learn.”
In the Frozen–Warm–Settled metaphor that runs through the CLEAR framework, experimentation is the phase where the warming intensifies. During Clarity, you applied the first gentle heat: establishing purpose, inviting dialogue, making the case for change. During Leverage, you turned up the temperature: engaging champions, finding pressure points, removing barriers. Now, in Experimentation, the system is warm enough to be malleable. The ice is no longer solid; it’s beginning to flow. And this is the moment where you can start to shape it, carefully, deliberately, with your hands in the material rather than just pointing at it from a distance.
But warm systems are also unpredictable. When ice melts, water flows where it wants to, not always where you planned. That’s why experimentation requires both action and attention. You must act, try something, and then observe closely what happens. The observing is as important as the doing.
The Experiment Canvas
I’ve developed a simple one-page tool that I use with teams to structure their thinking before running any experiment. I call it the Experiment Canvas, and it has six fields:
- Hypothesis: “We believe that [intervention] will cause [outcome] because [mechanism].”
- Minimum success criteria: “We will consider this experiment successful if [specific, measurable threshold].”
- Failure criteria: “We will know this isn’t working if [specific signals].”
- Learning goals: “Regardless of outcome, we want to learn [specific questions].”
- Risks and mitigations: “The biggest risk is [X], and we will manage it by [Y].”
- Timeline and decision point: “We will run this for [duration] and make a go/no-go decision on [date].”
Questions to Guide Your Experimentation
Here are the questions I return to in every project:
- What is our strongest hypothesis about what will drive change? And what’s our second-strongest? Test both.
- What would we need to see to know this is working? Define success before you start, not after.
- What would surprise us? Think about what results would challenge your assumptions. Those are the most valuable possible outcomes.
- Who is closest to the action? The people implementing the experiment often see things the designers miss. Create channels for their observations to flow back quickly.
- What are we afraid of? The experiments you’re reluctant to run are often the most important ones. Fear of a particular result usually means that result would challenge a cherished assumption.
- How big does this need to be to produce a clear signal? Small enough to be affordable. Big enough to actually learn from.
- What’s the listening channel? Every experiment needs a way for the people closest to the action to report what they’re observing. Not just the metrics, but the qualitative signals, the stories, the unexpected reactions. Design this channel before the experiment starts.
© 2026 Erik Bohjort. All rights reserved.
Stories in the full chapter
The full chapter tells these stories from Erik’s own projects in detail. As in the chapter, the clients are not named.
- A grocery store in Sweden: with clear Nyckelhålet signage on the healthiest breads, healthy bread sales slightly declined; family social proof messaging (“Here are healthy breads popular with families with children”) produced a 64% increase in sales of those healthy bread types; and aggressive retail design with a price reduction produced a 200% increase in sales.
- A large Swedish city’s digital learning platform for job seekers: simple checklists that got job seekers started on the platform in the meeting with their counsellor produced a 900% increase in platform usage, and well-timed emails produced around 200%.
- A newspaper: instead of redesigning the entire subscription funnel, the project started with a single variable, a more prominent app download prompt on the confirmation page, then tested the next variable, and the next, and eventually produced a 110% increase in conversion.
- A Swedish organization that manages package recycling: screaming coloured labels asking “Är det där en förpackning?” (“Is that packaging?”) reduced the time spent by personnel cleaning up around the containers by more than 15%.
Questions this chapter answers
Each answer is quoted from the chapter; “…” marks text left out.
What is a safe-to-fail experiment?
The concept is rooted in what some researchers call “safe-to-fail” experiments, as opposed to “fail-safe” designs. A fail-safe design tries to engineer out all possibility of failure before deployment. It aims for perfection before action. A safe-to-fail experiment, by contrast, accepts that failure is not only possible but informative. You design the experiment so that if it doesn’t work, the consequences are small, the learning is rich, and you can iterate quickly. The system absorbs the failure without breaking.
What is the Experiment Canvas?
I’ve developed a simple one-page tool that I use with teams to structure their thinking before running any experiment. … It forces precision of thinking before action. It creates a shared agreement about what “success” means (preventing the common problem of retroactively redefining success to match whatever happened). … I’ve seen teams fill out this canvas in twenty minutes and save themselves months of confusion.
What is a pre-mortem?
Before running an experiment, I often lead teams through a “pre-mortem” exercise, adapted from psychologist Gary Klein’s work. The premise is simple: imagine that the experiment has already been run and it failed completely. Now, work backward. What went wrong? … It surfaces risks and assumptions that optimism bias would otherwise hide. … The pre-mortem doesn’t prevent failure. That’s not the point. It prepares you for it.
How big should an experiment be?
If you go too small, you get stuck in endless cycles of asks, buy-in processes, and committee approvals that cost more than the experiment itself. The practical rule I use is: as small as possible without getting stuck in the machinery of organizational permission. … Small enough to be affordable. Big enough to actually learn from.
Read the Full Chapter
The full chapter continues with the stories above, the psychology of why experimentation is harder than it sounds, the pre-mortem and other tools for designing experiments, and a note on ethics. It is free as a PDF.
Download the Free Chapter
Enter your details and we'll send the chapter straight to your inbox.