Safe to fail experiments

{{<quote text=I have not failed. I've just found 10,000 ways that won't work. author=“Thomas A. Edison” >}}

Problem Statement

• When learning new skills, a significant part of the process may not yield immediate or desired results.
• We are hardwired to avoid failure, which, while crucial for survival, hinders trying new things.

Intent

Create an environment where experimenting with new ideas or practising skills becomes less intimidating. This fosters faster and less stressful learning, potentially adding an element of enjoyment.

Contextual forces

Enablers

The following factors support effective application of the practice:

• Your learning goals are clear and motivating.
• Your environment values gaining and sharing knowledge.
• You are in a safe environment where failure is not punished.
• You can apply results from learning experiments to your work.
• You can break down learning goals into small, achievable steps.

Deterrents

The following factors prevent effective application of the practice:

• Lack of interest in learning new things.
• Environment devalues learning or is unwilling to invest in it.
• Presence of an expert in the subject you’re trying to learn.¹
• Environment prioritizes optics over results, punishing failure.

Solution

• Reframe your goal to focus on gathering knowledge rather than “making something work.”
  • Form hypotheses and try to prove theories.
  • Have multiple approaches to a problem to embrace the experimentation mindset.
  • Inform stakeholders about your intent to experiment.
• Set up small-scale experiments to test ideas.
• Hold yourself accountable by investing effort based on learning goals.
• Isolate experimentation from regular work to lower the stakes of your learning efforts.
• Pass on what you have learned: Share your findings, even if the experiment doesn’t meet expectations, to facilitate learning and prevent others from making the same mistakes.²

Examples

Trying a Novel Framework

Situation: You have learned of a novel framework or technology that you would like to try out. You are not sure if it will be useful for your current project, but you are interested in learning more about it.

• You set up a small project, and try to implement a small – non-critical – feature using the new technology.
• You document your findings (both advantages and disadvantages), and share them with your team.
• You park your small feature, discuss your recommendations with your team, and move on with your work.

Possible outcome: You decide to not use the new technology for your current project, but you (and your colleagues) have learned something new.

Further Exploration

• Hunt, A. (2008). Pragmatic Thinking and Learning: Refactor Your wetware. The Pragmatic Bookshelf. isbn: 9781934356050.
  https://pragprog.com/titles/ahptl/pragmatic-thinking-and-learning/.
• Hoover, D.; Oshineye, A. (2009). Apprenticeship Patterns. O'Reilly Media, Inc.. isbn: 9780596518387.
  https://www.oreilly.com/library/view/apprenticeship-patterns/9780596806842.
• Holiday, R. (2016). Ego Is the Enemy. Portfolio. isbn: 9781591847816.
  https://www.goodreads.com/book/show/27036528-ego-is-the-enemy.
• Pink, D. H. (2009). Drive: The Surprising Truth About What Motivates Us. Riverhead Books. isbn: 9781594488849.
  https://www.goodreads.com/book/show/6452796-drive.
• Mario 'Moonprayer' Trappein (2016). Ladder anxiety, and how to overcome the fear of ranked play. TempoStorm.com.
  https://tempostorm.com/articles/ladder-anxiety-and-how-to-overcome-the-fear-of-ranked-play.