The disciplined practice of testing ideas, approaches, and assumptions through small, safe-to-fail experiments that generate evidence and insight. Experimenting is not about proving what you already believe, but about exploring possibilities, reducing uncertainty, and allowing successful patterns to emerge. Leaders who experiment build adaptability, innovation, and resilience in complex environments by learning their way forward.

“In complex systems, you can’t predict the future. You run a series of small experiments, see what works, and let direction emerge.” Dave Snowden

Barriers to Experimenting

Pressure for certainty: Leaders are often expected to provide definitive answers. This discourages experimentation, which begins with admitting uncertainty and exploring options instead of promising solutions.

Fear of failure: In cultures where mistakes are punished, experiments become too risky. Leaders and teams avoid experimentation if failure is seen as weakness rather than learning.

Over-investment: When experiments are too large, costly, or visible, they lose their “safe-to-fail” nature. Leaders sometimes label pilots or projects as experiments, but if they cannot be stopped without consequences, they are too risky.

Bias toward big initiatives: Many leaders favour large-scale, well-structured projects over small steps. This bias creates rigidity and reduces the organisation’s ability to adapt when conditions change.

Short-term urgency: The pressure for immediate results often overrides curiosity. Leaders may default to action plans instead of exploring uncertainties first, missing opportunities for deeper learning.

Attachment to favourites: Leaders sometimes fall in love with their own ideas, amplifying them regardless of feedback. This undermines the objectivity needed to test and learn.

Confusing pilots with experiments: Pilots are designed to validate a chosen solution. Experiments are designed to test assumptions. Treating one as the other risks narrowing learning and missing unexpected insights.

Low psychological safety: Without trust, people hesitate to suggest unconventional or risky ideas. Teams avoid proposing experiments if they fear embarrassment, ridicule, or blame for failure.

Neglecting feedback: Experiments that lack clear measures or observation mechanisms yield little value. Leaders sometimes run tests without monitoring signals, resulting in wasted effort and anecdotal conclusions.

Activity without review (innovation theatre): In some organisations, experiments are launched for the sake of looking innovative, but results are never systematically reviewed. Without analysis and reflection, experimentation becomes busywork instead of a learning tool.

“I have not failed. I’ve just found 10,000 ways that won’t work.” Thomas Edison

Enablers of Experimenting

Authorise safe-to-fail: Encourage experiments that are small, bounded, and reversible. Leaders who make it clear that failure is acceptable signal that learning is valued more than the appearance of success.

Frame clear hypotheses: Each experiment should test a specific question or assumption. This keeps experimentation disciplined and ensures that outcomes generate actionable insights, not just activity.

Design a portfolio of probes: Running several small experiments in parallel provides resilience. Diversity across approaches, focus areas, or teams increases the chance of discovering valuable patterns and reduces reliance on a single initiative.

Set boundaries: Keep experiments time-boxed, limited in cost, and ring-fenced in scope. This protects safety and reassures stakeholders that risks are being managed responsibly.

Define amplify and dampen triggers: Establish clear signals for when to scale up an experiment or when to stop it. This prevents bias, ensures timely action, and reinforces discipline.

Balance data and stories: Collect both quantitative evidence (metrics, uptake, performance indicators) and qualitative evidence (anecdotes, team narratives, customer stories). This gives a richer picture of impact and helps detect early weak signals.

Value learning as much as outcomes: Celebrate insights gained even from failed experiments. Leaders who shift the focus from success/failure to learning foster a culture of exploration and resilience.

Model curiosity: Leaders who say, “Let’s try and see what happens,” normalise uncertainty. By showing openness and curiosity, they encourage others to take thoughtful risks and explore new ideas.

Create review loops: Build structured reflection into team routines so that every experiment is analysed, insights are captured, and learning is shared. This prevents experiments from being forgotten and strengthens organisational memory.

Protect cultural and psychological safety: Leaders must shield experimenters from blame or reputational damage. In risk-averse or hierarchical cultures, this protection is even more critical. When people know they are safe, they are more willing to try bold experiments.

“In organisations, real change begins with small disturbances.” Margaret Wheatley

Self-Reflection questions for experimenting

Comfort with uncertainty: How willing am I to admit I don’t know and explore options rather than provide answers? When was the last time I told my team, “I don’t know, let’s test it”? Do I see not knowing as a weakness or as a chance to learn?

Risk mindset: How do I personally respond when an experiment does not deliver the expected result? Do I treat it as failure, or as a source of insight? What signals do I send to others about my tolerance for setbacks?

Experiment size: Are the experiments I run truly small and safe-to-fail, or do I over-commit resources? Would I feel comfortable shutting one down quickly if it was not working? How often do my pilots become too big to abandon?

Curiosity in action: Do I actively seek out alternative ideas and test them, or default to proven paths? How often do I try something new when the outcome is uncertain? Do I encourage my team to suggest experiments, even unconventional ones?

Feedback discipline: Do I design experiments with clear ways of knowing if they are working? What data or stories do I rely on to assess outcomes? How do I avoid only seeing what I want to see?

Amplify and dampen: Do I pre-define conditions for scaling up or stopping an experiment? When have I let bias override signals to stop? What signals would tell me that something deserves more investment?

Time for reflection: Do I create space to review experiments and embed learning? How do I ensure that insights are shared across the team? What practises help me avoid letting experiments fade without follow-up?

“If you want to test a new idea, the cost of not testing it is often higher than the cost of failure.” Chris Argyris

Explore related leadership resources

To further develop this capability, examine how it intersects with other core leadership dimensions across the libraries:

Leadership library:

  • Questions (Asking good): Use powerful, open-ended inquiries to challenge assumptions and uncover the underlying variables worth testing.
  • Creativity: Generate a diverse range of novel ideas and unconventional solutions that serve as the raw material for your experiments.
  • Adaptability: Pivot your strategy based on real-world feedback, ensuring you don’t stay committed to a path that the evidence no longer supports.
  • Perseverance: Maintain the stamina to continue testing and iterating even when initial experiments fail to yield the desired results.

Supporting libraries

Continue exploring: Return to the Leadership Library to view the full directory of competencies and resources.