When we hear or say the words “fail” or “failure” in relation to all things tech, we generally conjure up images of locked doors, garage sales of office supplies, empty chairs and desks, and a battle for the best developers who are now on the job market. But there’s more to it than that, and in every startup failure, there are more details than most of us will ever know about because we weren’t there. We can only watch from the sidelines and make armchair quarterback calls about what we would have done differently.
But how do we actually learn from failure? It’s too often a platitude like “we only learn when we fail,” but that doesn’t help the person or startup that just failed. What we need is a tangible process or exercise to walk through – painstakingly – to make sure that we do indeed learn from each and every failure, regardless of how small or how epic. That process is outlined below:
Understand what caused the failure
Take responsibility for your own actions
Say it out loud – Own it
Document your failure like a textbook