Don’t fail fast. Learn fast!

Don’t fail fast. Learn fast!

“Fail fast.”

Are you tired of this cliché? I know my teams often are. I’ve seen eyes roll when I use this popular phrase, and it’s easy see why. After all, “fail fast” is one of those semi-meaningless phrases some managers love and repeat as a mantra.

Turn the phrase around, though, and watch those eye rolls become smiling eyes.

Don’t encourage your team to fail fast. Encourage them to learn fast.

Any team should be encouraged to take on experiments, try new ideas, innovate in their space. We want to encourage them to get outside of their comfort zones and work with innovation always on their minds.

We want to encourage our teams to learn.

When they try something new, when they learn, a new set of options opens up. They may not be able to embrace all the ideas they’ve explored, but they probably can embrace some – and sometimes those ideas open the door to new ideas. Better to have a vast panoply of options than just one or two options which follow traditional, antiquated thinking.

It’s not a failure when an experiment doesn’t bear fruit in the way you hoped it would. After all, the team took the initiative – and the risk – to try something new. They gave the experiment a sincere try. In the process the team learned more about their technologies, about themselves and about their teammates. As the Agile manifesto declares, we favor responding to change over following a plan.

A few years back, one of my teams used their failure to drive innovation inside our company. My team was excited to create a continuous deployment system which could deliver small website updates on a frequent cadence. But the team struggled creating their CD pipeline. They learned fast that our legacy system was underpowered and under-tooled for their needs.

The team’s report about their learning triggered me to have conversations with my peer Scrum Masters around root causes. In turn, those conversations triggered chats with management to add an Initiative to drive implementation of a CD pipeline company-wide, and have my team be pilot adopters. Our “failure” led to learning, which lead to a well-considered upgrade.

Continuous learning is also a key to a positive mindset. A team member who is learning is frequently brings new ideas to their team. The learner is then perceived as a leader. The learner doesn’t have to overcome the negative attitude of embracing failure. Instead, the learner embraces the positive mentality of learning. They understand the power of one person learning. They understand one person can help an entire organization grow.

Consider the contrasting effect on individuals and their ambitions when you shift the emphasis from failure to learning. People no longer are forced in their reviews to explain why something failed. Instead, they are freed to embrace innovation. Those with the greatest imagination tend to be the ones leading teams. They are always learning and never letting an obstacle get them down. Continuous learning leads to a positive mindset and thus leads to virtuous cycles.

For us Agilists, those virtuous cycles map nicely to the Agile principles and to self-organized teams. When you give your team members the space to grow and learn, you can achieve goals beyond what you could have imagined.

“Failing fast” is a noble idea and makes a lot of sense. But don’t be negative! Encourage your teams to learn fast. If you do, you’ll be delighted with the results.

Paul Bronowski

Software Engineering Manager FlightSafety, International.

3 年

Good point, but I'm going to keep using 'fail fast, fail hard, fail early', when speaking of engineering systems (like build systems), to mean: find problems early in the process, don't ignore warnings, fail early in validation, etc. :)

回复
Tammy Bare

Sr Technology Leader - International Digital at lululemon

3 年

??this!

要查看或添加评论,请登录

Jason Sacks的更多文章

  • Minimum Viable Process: A Case Study

    Minimum Viable Process: A Case Study

    Ever hear your team say “I hate process!”, only to turn around an hour later and say “Why can’t anybody plan around…

    3 条评论
  • Inclusiveness Begins with the Scrum Master

    Inclusiveness Begins with the Scrum Master

    I love working as a Scrum Master because I get to work with an incredibly diverse set of people. In my career, I’ve…

  • Top 5 Reasons Why I Hate the Term Scrum Master

    Top 5 Reasons Why I Hate the Term Scrum Master

    My name is Jason. I’m a Scrum Master.

    3 条评论
  • Get Educated, Get Paid, Get Engagements

    Get Educated, Get Paid, Get Engagements

    Thinking about getting a new Agile certification after my post last week? Well, there’s a new survey out regarding…

  • Why I Got Yet Another Certification - the PMI-ACP

    Why I Got Yet Another Certification - the PMI-ACP

    I’m a collector. It’s my nature.

    7 条评论
  • Experiments – How to Not Blow Everything Up

    Experiments – How to Not Blow Everything Up

    One of the most interesting bits of feedback I ever received in a retrospective came from a team that believed Scrum…

  • When numbers lie

    When numbers lie

    Look at that velocity chart up above. What does it tell you? Without knowing a lot about the team, you’d believe the…

    2 条评论
  • Know your numbers

    Know your numbers

    One of my favorite TV shows is Shark Tank. If you’ve never seen the show, the premise is simple: an entrepreneur brings…

  • Dashboards: Give the People What They Want

    Dashboards: Give the People What They Want

    One day my team was happily working away when the VP of my division stopped by my desk. “How is your team doing?” she…

    1 条评论
  • Silence Does Not Equal Failure

    Silence Does Not Equal Failure

    I have a confession: there are some types of people I have trouble understanding. Those people are called introverts.

社区洞察

其他会员也浏览了