
Shannon Mason
Published on 19 November 2026
How behavioural nudges can encourage teams to experiment
Most organisations want their teams to experiment, but everyday habits, competing priorities, and fear of failure get in the way. By making experimentation easier, more visible, and safer, behavioural science can help turn good intentions into everyday practice.
Innovation is a stated priority for most businesses. When executives are asked if they want their teams to challenge assumptions and explore new ideas, the answer is yes. Yet, if you ask how many organisations have made experimentation a natural part of daily work, the reality often looks quite different.
Leaders encourage curiosity, yet employees are measured against strict delivery deadlines and established processes. When workloads spike, experimentation is often dismissed as a luxury to revisit "when there's more time."
It is tempting to view this as resistance to change, but behavioural science offers a different explanation. If we want teams to experiment, we need to stop asking how to make people more innovative and start fixing what makes experimentation so difficult in the first place.
The hidden psychology behind resistance
Humans gravitate toward the familiar, especially under pressure. Status quo bias helps explain why we tend to favour familiar routines over potential alternatives, especially when we're under pressure.
Consider a project manager with an idea to streamline a workflow. Testing it requires stakeholder approvals, disrupts routines, and carries the risk of failure. With a deadline looming, sticking to the status quo often feels like the most rational choice. Multiply that choice across a team, and an organisation can end up discouraging the very behaviour it says it wants.
Small nudges, meaningful changes
A behavioural nudge is a subtle change to how choices are presented, designed to influence action without removing autonomy. The Behavioural Insights Team’s EAST framework (Easy, Attractive, Social, and Timely) offers a useful way to build experimentation into everyday work.
1. Make it the easiest next step: If testing an idea requires a ten-page proposal, a budget hunt, and multiple stakeholder approvals, friction will likely halt the experiment before it starts.
To address this, create a lightweight process. Replace heavy business cases with a simple template covering three questions:
- What do we want to learn?
- What is the smallest safe way to test it?
- What evidence tells us whether to continue?
Removing unnecessary bureaucracy gives teams more opportunities to test ideas and learn from the evidence.
2. Make the value visible: Present bias helps explain another barrier: people tend to give more weight to immediate effort than future rewards. Telling a team that experimentation ensures market competitiveness in three years may be strategically true, but it rarely motivates someone deciding how to spend a busy Tuesday afternoon.
To counter this, make the benefits immediate and tangible. Show how a small test removed a frustrating manual process or stopped resources from being spent on an ineffective approach. Crucially, reward the learning itself. If performance reviews only praise predictable delivery, employees may rationally avoid the uncertainty of an experiment. You cannot expect thoughtful risk-taking if you only reward predictable outcomes.
3. Use social proof to make it contagious: People look to colleagues for cues on acceptable behaviour. If experiments happen in silos and only successes are shared, the barrier to entry feels impossibly high.
Leaders can use social proof by building experimentation into regular team rituals. Dedicate five minutes in a weekly meeting to ask, "What did we test this week, and what surprised us?" When leaders openly share their own flawed assumptions and unsuccessful tests, they signal that experimentation is safe. That visibility provides a cultural permission slip that corporate messaging often cannot achieve on its own.
4. Prompt action at the moment it matters: A yearly innovation offsite might generate dozens of ideas, but enthusiasm tends to fade the moment employees return to their overflowing inboxes. Introduce prompts exactly when teams are already making decisions:
- Project kick-offs: What core assumption must we test before committing budget?
- Sprint planning: What is one micro-improvement we can trial this week?
- Retrospectives: What hypothesis could we have tested to avoid that bottleneck?
These prompts create implementation intentions, specific plans for when and how to act. Embedding prompts into existing routines removes the burden of remembering to initiate an experiment.
Nudges won't fix a punitive culture
You can introduce all the templates and prompts in the world, but if employees believe an unsuccessful test could damage their career, participation will remain low.
Behavioural nudges must sit atop a foundation of psychological safety. Employees also need genuine capacity. Adding experimentation to an overloaded plate simply creates another competing priority. They need to know that responsible failure is supported, too. Leaders should ask themselves: "What are we currently rewarding, tolerating, or making difficult that discourages people from experimenting?"
Organisations should also avoid the trap of measuring success by the sheer volume of experiments. Rewarding quantity can breed activity without meaningful learning. Instead, look at the impact: Are teams validating assumptions earlier? Are findings shaping future decisions? Experimentation should create a feedback loop between evidence and action.
Make experimentation part of how work happens
No organisation lacks ideas. What is often missing is an environment that makes acting on those ideas feel practical, worthwhile, and safe. Behavioural science suggests that minor tweaks to processes, social expectations, and timing can bridge the gap between wanting to experiment and actually doing it.
The true test of an experimental culture happens on an ordinary Tuesday under the weight of looming deadlines. When an employee spots a better way to work, do they feel empowered to explore it, or do they quietly return to business as usual? For leaders serious about building adaptable teams, the goal is to make that choice easier.
