Mastering Customer Simulation Scenarios

Imagine a customer who has just learned that a mistake made by your team has affected their work. They are reading your reply closely, probably with their own leaders watching over their shoulder. Your first sentence will shape how everything after it is heard. Two replies can describe the same event and still leave the customer in very different positions. One gives the customer a story they can carry back to their own leaders. The other leaves them with questions they cannot answer.

The difference between those two replies is not mainly one of tone. The source material treats it as a matter of structure. A reply that works tends to move through a specific set of steps in a specific order, and a reply that fails usually skips one or more of them. This article makes those steps visible so that you can check your own draft against them before you send it.

Effective bad news communication is built from five moves. The source names them in a fixed sequence, and the sequence is part of the lesson. Each move prepares the ground for the next, so the customer can follow the reasoning rather than having to rebuild it on their own. The five moves are: lead with the news, take specific responsibility, name the cause concretely, show evidence of a fix, and propose a path that protects the customer's downside.

A helpful way to hold the sequence in mind is to read it as a chain of questions the customer is silently asking. First, what went wrong? Second, who owns it? Third, why did it happen? Fourth, is it being fixed? Fifth, what happens to me now? Answering in the order those questions arise keeps the conversation coherent. Answering the last question first, before the customer knows what went wrong, tends to sound like an attempt to move past the problem.

The arrows matter as much as the boxes. Each move answers the question the previous move raised. Ownership makes the diagnosis credible, because the customer can see that the speaker is not hiding behind the system. The diagnosis makes the evidence of a fix meaningful, because the customer can see that the fix targets the actual cause. The evidence makes the final proposal safe to consider, because the customer can see that the work is under control before being asked to plan around it.

The source describes a candidate who handled a bad news conversation well. Its annotation does not praise style. It checks each move against what the candidate actually said, and it treats the sequence itself as the signal the interviewers were looking for. The method below follows the same approach: take a reply and test it move by move. The reply in this example is illustrative and was written for teaching purposes, not quoted from the source.

The source identifies two kinds of weakness. A reply that omits direct ownership or a concrete diagnosis weakens the communication. A proposal without downside protection gives the customer nothing to defend internally. These weaknesses can be read as losses of three things: ownership, diagnosis, and downside protection. A draft can lose one of them while still reading smoothly, which is why it helps to check each move rather than judging the reply as a whole.

Read the comparison row by row. In the weak column, each gap is a move that has been left out or softened. The first row is about ownership: the wording hides who made the mistake. The second row is about diagnosis: the reply gestures at a problem without naming its cause, so the customer cannot judge whether it will recur. The third row is about downside protection: the reply ends by handing the next step back to the customer, which gives them nothing concrete to defend internally. The strong column closes each gap with a specific statement the customer can repeat to their own leaders.

Bad news does not always mean a mistake. Sometimes the difficult conversation is about a request. The source describes a scope-creep scenario, which it defines as a situation where a customer requests a major addition to a project in the middle of the engagement. The request may be reasonable on its face, yet it changes what the work is. Customers may request changes or additions mid-engagement, and those changes can affect both scope and timeline.