Skip to the story
Startup Launched
Sign inTell your storySubmit

Telling the Story of a Failure Honestly

Writing · 9 min read ·

How to write about a project or company that did not work: what to include, how to be fair to others, what to learn and why readers trust honest endings.

Illustration: An empty shop with the lights off and a handwritten closing note on the door, soft dusk light, documentary style

Most startups do not last. Wikipedia notes that startups face significant uncertainty and high failure rates, and that only some achieve notable success. Yet most founder stories are about winning. The people who tried and stopped, who closed a shop or shut a product, rarely write about it, and what they know goes unrecorded.

If you have been through a failure, your account can be unusually valuable to others, and to you. This article is about how to write it honestly, fairly and usefully.

Why failure stories matter

A failure story does several things.

It teaches in a way success stories cannot. Successes are often explained after the fact, by selective memory. Failures are more candid about what went wrong and why.

It makes the author trustworthy. A person who can say "I was wrong, and here is how" earns a particular kind of credibility. Readers see that you are honest when it costs you something.

It helps you understand. Writing forces you to order events, to separate what you did from what happened to you and to find the lessons.

It helps others avoid the same trap. A candid account of a mistake might save a stranger months of work.

It closes a chapter. Many people find that telling the story helps them move on.

Decide whether you are ready

You do not have to write it immediately. In the first days after a failure, emotions are high and facts blur. Wait until you can describe what happened without defensiveness or self-punishment. At the same time, do not wait so long that details fade. A few weeks or months is common.

Check also that you are free to write it. Think about contracts, confidentiality agreements, legal disputes and the interests of others. If there are unresolved legal issues, take advice before publishing.

Gather the facts

Reconstruct what happened with evidence, not just memory. Gather emails, documents, numbers and calendars. Make a timeline with dates. Note decisions and who made them. Check your recollection against records, because memory tends to flatter the person remembering.

If other people were involved, consider asking them for their recollections. You do not have to include their account, but it may correct yours.

Choose what the story is about

A failure has many possible stories: the product that did not fit, the market that did not exist, the money that ran out, the team that came apart. Choose the one that carries the most useful truth, and let it organise the piece.

Ask yourself: if a reader remembered one thing, what should it be? Perhaps "we built what we wanted, not what customers needed", or "we ignored the signs that our biggest customer was unhappy". Write toward that.

A structure that works

  1. The ending, briefly. Say what happened: the company closed, the product was shut down, the project stopped. Do not make readers wait.
  2. How it began. What you hoped for, in a short paragraph.
  3. The decisions. The key choices, in order, with their reasons at the time.
  4. The turning points. The moments when things began to go wrong, and what you saw or missed.
  5. What I would do differently. Specific, practical lessons.
  6. What I took from it. What you carried into your next chapter.
  7. Thanks. To the people who helped.

Keep the tone honest and measured. Avoid melodrama and avoid minimising.

Be specific about the mistakes

Vague confessions are not useful. "We made some bad decisions" teaches nothing. Compare: "We hired three engineers before we had ten customers, which meant that when the first big client left, we had four months of runway and no way to cut costs without losing the people who knew the code."

Describe the decisions, the information you had at the time and what you now think you should have done. Be fair to your past self: judge the decision by what you knew then, as well as by the outcome.

Be fair to others

Failure often involves people: co-founders, employees, investors, customers, suppliers. Be careful.

  • Describe what you saw and did, not what you imagine others thought.
  • Avoid assigning motives. "He did not care" is a guess. "He did not reply to my messages for three weeks" is a fact.
  • Do not name people unnecessarily. Use roles ("an early investor") unless naming is important and they agree.
  • Offer a chance to check anything that affects them, especially facts about them. You are not asking for approval, only for accuracy.
  • Keep private matters private. Health, family and finances of others are not yours to share.
  • Respect confidentiality. Do not reveal information that you have agreed to keep secret.

The Information Commissioner's Office provides guidance for small organisations on handling personal information, and the same care should apply to what you publish about individuals.

Own your part

The most credible failure stories take responsibility. That does not mean taking all the blame. It means being clear about what was in your control and what you did with it. A passage such as "I should have asked customers earlier, and I did not because I was afraid of the answer" is powerful because it is specific and humble.

At the same time, avoid performative self-blame, which centres the author and offers readers little. The aim is clarity, not penance.

Do not spin

Spin is the temptation to turn the failure into a hidden success. "We did not fail, we pivoted." Sometimes that is true, but if it is not, readers can tell. Say what happened plainly. If something good came out of it, say that too, honestly.

Avoid presenting external causes as the only reason, such as "the market was not ready". Maybe so, but ask whether you could have tested that earlier.

Include the human side

Failure hurts. It is fine to say so. A line or two about how it felt, such as the relief of not having to check the bank balance, the sadness of telling employees, the strange quiet afterwards, makes the story human. You need not dwell. A few honest sentences are enough.

Include practical lessons

End with things the reader can use.

  • Questions to ask before hiring.
  • Signs of trouble to watch for.
  • A rule you now follow.
  • A conversation you would have earlier.

Frame them as what worked or would have worked for you, not as universal laws.

Say what happened to people and obligations

If the failure affected customers, employees or suppliers, say what you did for them: notice given, data returned, debts settled, references offered. Readers respect people who look after others at the end. If you did not manage it well, say so.

Consider what to publish and where

Think about where the story will live and who will read it. A personal blog, your company site, a community profile or a guest article each have different audiences. Consider the effect on future partners, employers and customers. Most people respond positively to a thoughtful, honest account.

Google's guidance on helpful content emphasises original information, honest sourcing and clarity about who created the content. A first-hand failure story, carefully written, fits that description.

A worked example

A founder who closed a small subscription box business writes a piece called "Why I closed the business, month by month". She begins with the ending: "In October, I wrote to six hundred subscribers to say that we were closing." She goes back to the start, describing the idea and the first hundred customers. She sets out three decisions: launching with eight products instead of two, signing a twelve-month lease on a warehouse and spending most of her budget on advertising before measuring retention.

She describes the turning point: in the fourth month she noticed that more than a third of subscribers cancelled after the second box, but she attributed it to seasonality. She says that she did not call a single person who had cancelled until month nine. She includes what it felt like to write the closing email, and what she did for customers: she honoured every paid-for box, posting remaining boxes at her own cost and gave suppliers early notice.

She ends with three lessons: test retention before scaling, call every cancelling customer, and avoid long leases until you have a steady pattern of orders. She thanks her two part-time helpers by first name, with their permission. Readers write to say that they have changed what they are doing. A supplier offers her a job.

A checklist

  • Is it factual, with a timeline?
  • Does the story have a single clear point?
  • Are the mistakes specific?
  • Am I fair to others and respectful of privacy?
  • Do I take responsibility without self-punishment?
  • Is there no spin?
  • Are the lessons practical?
  • Have I taken advice if there are legal issues?

On this site, the about-the-founders page shows one plain way to introduce founders, with names, roles and photographs, and the submit page is the place to start your own listing.

Frequently asked questions

Is it safe to publish while I am looking for work or funding? Many people find it helps, but consider the context and take advice if there are sensitivities.

Should I let the people involved read it first? For facts about them, yes, as a courtesy. You decide what to publish.

What if I am still angry? Wait, or write a private draft first. Publish only when you can be fair.

Questions and answers

Why write about failure at all?
Because it helps others, clarifies your own thinking and builds trust. Readers value honesty over a spotless record.
When is the right time to write it?
When you have enough distance to be fair, but while details are still fresh. For many people that is a few weeks or months.
How do I avoid blaming others?
Stick to what you did and saw, avoid guessing at motives and give people a chance to check how they are described.
Will it hurt my reputation?
Handled honestly, it often helps. The risk lies in spin, blame and inaccuracy, not in the failure itself.

Sources

Related guides

Help centre