Delivering Bad News to Customers: Delays, Prices, and Mistakes

Why does bad news arrive too late in a business?

A supplier reports that a component will arrive three weeks late. The customer expects the system in ten days. In many businesses nothing happens at first. People hope a solution will turn up and call the customer when the date has almost passed. It is similar with rising costs that require a price change, or with your own mistake in a project.

Acting like this is not dishonest. You protect yourself from an unpleasant conversation and hope to avoid it altogether. The price, however, is paid by the customer, who has less time to adjust, and in the end by the business, whose credibility suffers.

The guiding question of this guide is: how do you deliver bad news to a customer so that trust is not damaged, or even grows? To answer it, I first explain why we hold back bad news, then present a model from communication research, examine whether an apology always helps, and finally give you a structure for the three most common cases.

The MUM effect: why we hold back bad news

In 1970 the psychologists Sidney Rosen and Abraham Tesser described that people pass on bad news less often and later than good news. They called this the MUM effect, after the English expression "to keep mum," meaning to stay silent. The effect has been confirmed many times since. O'Neal, Levine, and Frank (1979) left postcards on public transportation in Paris, London, Geneva, Frankfurt am Main, and Madrid. Cards with important good news were forwarded more often than those with important bad news, in four of the five cities.

Self-presentation offers one explanation. Uysal and Öner-Özkan (2007) showed in a scenario study with 275 students in Turkey that people deliver good news more readily because they expect liking and gratitude in return. Whoever brings the bad news fears being associated with it. For businesses the effect is particularly well studied in projects. Keil and colleagues (2004) describe that in large IT projects it often takes weeks to years before senior management learns how badly things stand. Park, Im, and Keil (2008) found in an experiment that time pressure and the question of who caused the fault influence the willingness to report.

How to build a culture in which mistakes are reported early is described in the article Learning from bad decisions. This guide starts one step later, at the conversation with the customer.

The model: expectancy violations theory

From the 1970s onward the communication scholar Judee Burgoon developed expectancy violations theory. Its basic idea: people have expectations about how others will behave. When an expectation is violated, attention rises and the recipient evaluates two things. First, the deviation itself, that is, whether it is better or worse than expected. Second, the sender, that is, how much the relationship is worth to him and how he has experienced the sender so far.

Applied to bad news, three rules follow. First: it is not the news itself that disappoints but the gap to the expectation. A three-week delay announced two weeks in advance is a new expectation. The same delay discovered on the delivery date is a breach. Second: a sender with a good relationship to the customer has more leeway, but uses it up if he exploits it. Third: a violation raises attention. After bad news the customer reads everything more closely, including the next proposal.

Bad news that comes early is information. The same news that comes late is a breach of trust.

Does an apology always help? Two views

The usual answer is: when you make a mistake, you apologize, and as early as possible. Crisis communication research supports this. The article Reputation in a crisis describes an experiment in which an apology led to a better reputation after the crisis. There is, however, a second view, and it is well supported.

Jenkins, Fombelle, and Steffel (2026) examined in five experiments what an apology does when the customer would not have noticed the failure at all. The most important study was a preregistered field experiment with a U.S. food delivery service. For orders that were likely to be late, some customers received an apology and others did not. The analysis covered 3,083 customers. Of those who received an apology, 74.8 percent ordered again within 90 days; of those who did not, 78.8 percent. Those who did reorder also ordered less often after an apology.

The authors' explanation fits the model: the apology first made customers aware that something had gone wrong and lowered perceived competence. At the same time it increased the provider's perceived honesty and warmth. When customers were already aware of the failure, these positive effects were more likely to prevail. A factual notification without an apology did less harm than an apology. A side finding stands out: 74 percent of the surveyed employees in customer-facing roles thought one should apologize even for a ten-minute delay.

The limits are clear. The studies concern consumers and small, short-lived failures such as a late food delivery. A business customer whose system arrives three weeks late notices the failure in any case. My assessment: this is no excuse for silence but a distinction. Whatever the customer feels or whatever touches his planning belongs on the table early and openly, with an apology if the fault is yours. A small deviation that has no consequences and has been fixed needs no dramatic apology, but a factual note if the customer asks about it.

The Five-Sentence Frame for bad news

A simple structure can be derived from the model and the findings. It works for a phone call, a meeting, and an email. The order matters: first the fact, then what it means for the customer, and only then the reasons.

1. What happened

   State the news in the first sentence, without preamble. "The system will not be delivered on the 12th but probably on the 2nd of next month."

2. What it means for the customer

   Translate the news into his situation: which date, which amount, which consequence. This shows you have thought about his planning.

3. Why

   Explain the cause briefly and honestly. If the fault is yours, say so and apologize once, without excuses.

4. What you are doing

   Name concrete steps: a replacement part from another warehouse, a partial delivery, advance installation, compensation. Offer a choice if possible.

5. When you will talk next

   Set the next contact with a date, even if there is nothing new by then. This replaces uncertainty with a commitment.

The frame deliberately leaves out three things: long preambles that hide the news, blaming third parties the customer cannot check anyway, and reassurances such as "It's not that bad." Whether it is that bad is for the customer to decide.

Three cases: delivery delay, price change, your own mistake

Delivery delay

Say it as soon as you know it with reasonable certainty, not only once you have a solution. The customer needs the time to replan himself. How commitments and handovers in order processing can be designed so that a delay becomes visible early is described in Optimizing order processing.

Price change

Here the advice from the article Raising prices without losing customers applies: give business customers at least two to three months' notice, before their planning round if they work with annual budgets, and state the amount for a typical order. If higher energy or material costs are the reason, a comprehensible justification helps, as described in Energy prices and pricing.

Your own mistake

Your own mistake requires clearly taking responsibility. Say what went wrong, apologize, and explain what you are changing so that it does not happen again. How companies make crises worse by denying, justifying, and deflecting is described in the article Deny, justify, deflect.

The next step

Bad news cannot be avoided. Its timing and form you can decide before the next case occurs.

• Set a rule: whoever learns of a delay or mistake reports it to you or the responsible person the same day.
• Decide from which deviation onward the customer is informed, for example from a two-day delay or above a fixed amount.
• Save the Five-Sentence Frame as a template in your email program.
• Go through current orders and check whether there is a message you are currently putting off.
• Visibly thank the next employee who brings you bad news early.

The last point is the most important. An owner who punishes the bearer of bad news will receive it later in future, and so will his customers.

Conclusion: how do you deliver bad news without losing trust?

We set out to ask
to deliver bad news to a customer so that trust is not damaged. The answer has three parts. First, early, because the customer measures news against his expectation and early information shifts that expectation. Second, openly and in a fixed order: fact, meaning, cause, action, next date. Third, with judgment about the apology: it belongs with every failure that reaches the customer, but not with every trivial matter without consequences.

The real work lies inside your own business. A business in which bad news travels upward quickly can also pass it on quickly. Trust does not come from nothing going wrong, but from the customer hearing it from you first.