Safe to Fail Agile Culture
Building a new software product and testing it is a highly innovative and creative process. Things simply don't go to plan all the time, setbacks and failures are inevitable along the way. What makes a difference is how a team deals with them. Each failure is an opportunity to reassess, make a change and try a different approach. In order to succeed, testing teams must become resilient to failure and focus on the learning outcomes that they present. As a QA lead, you need to encourage initiatives and via the right questions assist the team in taking the best possible decision based on what they know. Let them be the first to experience the initiative journey so that they learn from any possible failures that might be on that path. If you know the way do not push it to the team. Let them decide what's best for the team, support it and wait to see the results. Retrospect the actions, identify what went wrong and take one or two action items for the next time so we do not fail again.When we feel that it is safe to fail we are more likely to try riskier experiments, and sometimes these riskier experiments have huge payoffs.