How to learn from a business failure, honestly
Stories of failure are now easy to find, and easy to misread. How to listen to one, or tell your own, so that it teaches something instead of becoming a neat lesson or a fashionable badge.
Share on WhatsApp
Conceptual image · created with AI
Business failure has become a popular subject. Founders speak about it on stages, and people share it online, often with a tidy lesson at the end. Hearing it is useful. But a story told for an audience can make failure look like a stage on the way to success, and it is not always one.
Some businesses close and the founder never starts another. Some failures cost people other than the founder: staff, suppliers, family, customers. This guide is about listening to such a story, or telling one, in a way that teaches something and stays honest about the cost.
What you should come away with
- A failure account is useful for its specifics, not for its moral
- Separate what the founder decided, what they could not control and what they did not know
- Failure has a cost, often to people other than the founder, and a fair account says so
- Hindsight makes decisions look more obvious than they were; ask what was known at the time
- Be wary of lessons that are too neat or that flatter the speaker
- If you are telling your own story, do not blame named people or dress up the ending
Begin with the problem of the neat lesson. When a founder tells a story of failure, there is a pull towards a conclusion: 'I learned to trust my gut', 'I should have moved faster', 'failure is the best teacher'. These lines are comfortable, and they fit on a slide. But they rarely tell you what happened. If a lesson could have been written without hearing the story, it is not much of a lesson. The useful part of any account is the specific detail: what was decided, when, on what information, and what followed.
It also helps to remember that survivors are the ones telling the story. We hear from people who failed and went on to do something else well enough to be invited to speak. We hear less from those who closed a business, took a job and did not wish to discuss it, or who are still paying off what they owed. That does not make the stories less true. It means they are a sample, and the sample leans towards those who came out of it in good shape. Do not conclude that failure is usually followed by success. Conclude only that it can be survived, and that how it was handled mattered.
When you listen to an account, try separating it into three kinds of cause. The first is what the founder decided: a price, a hire, a loan, a launch, a decision to carry on. The second is what the founder could not control: a change in the market, a large customer leaving, a supplier failing, an illness, a policy change. The third is what the founder did not know at the time and could have found out. Most honest accounts contain all three. A story that is only about bad luck deserves a gentle question. A story that is only about the founder's own mistakes may also be incomplete, since some people take on all the blame as a way of closing the subject.
Then ask what was known at the time. Hindsight makes every decision look obvious. 'Why did you take that loan?' is a better question than 'Why did you not see it coming?', because it asks the founder to reconstruct what they believed then. Often the decision was reasonable given the information. What went wrong was that nobody was checking whether the information still held. That is a lesson you can use, and it is quite different from 'be more careful'.
Ask about the warning signs. Was there a point at which a number, a customer's comment or a colleague's worry suggested trouble? What was done with it? Why was it set aside? Founders are often honest about this, because the answer is rarely 'I did not care'. It is usually 'I was busy, and I hoped it would improve'. Seeing that pattern in another person is a cheaper way of learning it than meeting it yourself.
Ask about the end. How was the decision to close, or to carry on, made? Who was told first? What happened to staff, suppliers, customers and lenders, and what did the founder do about each? What did it cost the family? A fair account does not stop at the founder's own feelings. If the speaker skips over people who were hurt, that omission is also information.
Be careful about romance in the other direction. Failure is not a qualification, and nobody should start a business hoping to fail usefully. The sensible takeaway is not that failing is good. It is that failing is survivable more often if you notice trouble early, keep records, talk to people you trust, and do not put into the business what you cannot afford to lose. Those are cautious lessons, and they are less exciting than a story about bouncing back, but they are the ones a stage is least likely to offer.
If you are telling your own story, a few rules help. Say what happened in order, with the dates and decisions, before you say what you learned. Describe your own share first, and describe other people fairly or not at all; naming a partner, an employee or a customer as the cause is unfair when they cannot reply. Say what it cost, including to others. Do not turn the ending into a victory if it was not one. If you are still working things out, say so. People trust a speaker who admits that, and they learn more from it.
Finally, take care of your own use of the story. After hearing a failure account, write down three things: one decision you would have wanted to check, one warning sign you might also miss and one question you will now ask in your own work. Then go back to your own business or plan and test it against those. A story is not complete when the speaker finishes. It is complete when you have done something differently because of it.