Does your idea have a value? Do you want to reduce your debugging effort? Adopt Fail Fast Philosophy!
What Is a Fail Fast Philosophy
Debugging can be very annoying. How to avoid as many bugs as possible? Try Fail Fast technique - create code that tries to fail as soon as possible. Software that fails immediately and visibly helps you to find and fix bugs easier.
Another part of the Fail Fast Philosophy is this: if you think that your project is likely to fail, stop all the work immediately rather than continue with possible flaws. This is known as pivoting - quickly changing directions, just like in basketball.
Why You Might Want to Fail Fast
Iteration is the most effective way how to go forward. It may help you to validate fast your vision with real clients and prepare a really useful application or concept.
The main philosophy of the Fail Fast principle is to avoid or reduce the sunk cost effect which is often caused by the effort to develop a product that simply does not work.
The whole problem stems from the natural human nature of continuing to do meaningless work because of the internal guilt of failure.
Fail Fast is one of the main practices that the team should adopt mostly in the Research phase. Conversely, the correct application of this principle can connect the team and allow it to focus on substantial solutions to real problems. Often, when applying this principle, teams also report an increase in motivation and relief from the opportunity of finding a truly meaningful product development path.
Problems the Fail Fast Philosophy Helps to Solve
- Demotivated team
- Increased cost
- Unsuccessful product
- Unnecessary functions
- Unhappy clients
- Meaningless work
- "Not my problem" mentality
- Disconnect Between Business and IT
- Poor code quality
- Toxic team culture
How to Implement the Fail Fast Philosophy
Hunt the negatives
Seek out a negative opinion. Find people who are critical of the problems you are solving. Remember that your friends and family may not be completely honest or they are not sufficiently critical. They may tell you how great everything is and how well things are going. Do not listen to them!
Listen to your data including negative feedback.
Do not go away to perfect your product. If you have a Minimum Viable Product, go with it. In many respects, fewer means more.
Prepare milestones and consult them often, by this you may quickly identify if you are still on the right path.
Find people (best from your organization) who can assess your milestones and progress objectively. Consult your progress with them continuously.
Fail at the right time
Regularly validating the meaning of the problem you are addressing and adhering to the above principles will allow you to decide to stop the nonsensical development at the right time and focus on the real problem.
Practices that they can help you to fail-fast:
Always look at the fail-fast philosophy as on the positive way how to improve your product. Realize that is the first step to success!
Common Pitfalls of the Fail Fast Philosophy
Syndrome of failure
The most common mistake is to continue to make meaningless developments because of the feeling that anything else is a failure.
The mistake is inadequate informing the business owner of the reasons for stopping the project/development.
Not learning from mistakes
It is not enough to stop continuing to implement the meaningless product or functionality, it is also necessary to evaluate the reasons why we end and take the result into future designs.