Things will go wrong. Products will break, customers will be upset, and mistakes will be made. What separates great companies from mediocre ones is not whether they make mistakes, but how they handle them. This chapter is about owning your problems with speed and honesty.
Own Your Bad News
When something goes wrong, you should be the one to tell your customers â not the press, not social media, not a disgruntled employee. Get out in front of the problem. Deliver the bad news yourself and do it quickly.
âWhen something bad happens, tell your customers (even if they didnât ask). Donât think you can just sweep it under the rug.â
â Jason Fried & David Heinemeier Hansson
Getting Ahead of the Story
- Be the first to break your own bad news
- Transparency builds trust, even when the news is bad
- Hiding problems makes them worse â people always find out
- A company that owns its mistakes earns more respect than one that hides them
- Think of it like pulling off a bandage: fast and honest is less painful than slow and deceptive
Speed Changes Everything
The speed of your response matters as much as the content. A mediocre response delivered quickly is often better than a perfect response delivered days later. When customers are upset, they want to know youâre listening â now.
The Power of Fast Response
- Respond within minutes, not days
- Even a quick âWeâre looking into thisâ is better than silence
- Speed signals that you care and that youâre competent
- Old-fashioned customer service is slow, impersonal, and scripted â be the opposite
- A fast, empathetic response can turn an angry customer into a loyal advocate
How to Say Youâre Sorry
Most corporate apologies are terrible. Theyâre vague, legalistic, and clearly written by someone in the PR department. A real apology is specific, takes responsibility, and explains what youâre doing to fix it.
The Anatomy of a Real Apology
- Take full responsibility: No weasel words, no blaming circumstances
- Be specific: Say exactly what went wrong
- Show empathy: Acknowledge how it affected the customer
- Explain the fix: Tell them what youâre doing so it doesnât happen again
- Keep it human: Write like a person, not a corporation
What a Bad Apology Looks Like
- âWe apologize for any inconvenienceâ â vague and dismissive
- âMistakes were madeâ â passive voice hides accountability
- âDue to circumstances beyond our controlâ â blame-shifting
- âWe take this very seriouslyâ â corporate speak that means nothing
- If the apology doesnât feel uncomfortable to write, itâs probably not honest enough
Put Everyone on the Front Lines
Donât insulate your team from customer complaints. Everyone â including the founders, the developers, and the designers â should spend time dealing with customers directly. Itâs the fastest way to understand whatâs broken.
Direct Customer Contact
- When the people who build the product hear customer pain directly, they fix things faster
- A support ticket filtered through three people loses its urgency
- Having developers answer support emails creates empathy and accountability
- The cooks at a restaurant should occasionally talk to the diners
- You canât improve what you donât see
Key Takeaways
- Own your bad news â tell customers before someone else does
- Speed changes everything; a fast response shows you care
- Write real apologies: specific, responsible, human, and honest
- Bad apologies are worse than no apology at all
- Put everyone on the front lines â direct customer contact creates empathy
- Transparency in a crisis builds more trust than silence ever could