Mastering Customer Simulation Exercises

Bad news delivered with heavy softening can leave the customer unsure of the core fact and what they must do next.

Programming

Delivering Unwelcome News in a Simulation

In a customer simulation exercise, you play the person delivering the news while an interviewer plays a customer. The scenario is specific: a validation phase has produced a worse result than expected, and the timeline or scope of the work has to change. The customer is about to hear this, and your task is to deliver it well. This article focuses on one misconception that makes these conversations go badly: the belief that gentleness and deflection are the same thing as care.

Many people reach for the same tool first when they have to say something unwelcome: padding. They add reassurance, qualifiers, and hedges until the message is hard to find. Others reach for a different tool, explaining why the result is not really their fault and pointing toward the quality of the inputs or the reasonableness of the original expectations. Both instincts feel protective in the moment, and both tend to make the conversation go worse.

What do you think happens?

Before reading on, decide which of these two openings a careful evaluator would consider the stronger delivery.

Opening A: We really appreciate your patience with this work. Given how many moving parts the data has and how tricky expectations were always going to be, the validation may have come back in a range somewhat lower than we had hoped, though things could still shift.
Opening B: The validation came back worse than expected. Our team should have flagged the scope risk earlier, and we are sorry for that. The timeline needs to change, and I want to walk you through the plan we propose.

Reveal answer

Answer:

Opening B is the stronger delivery.

Opening B states the result plainly, owns the team's part, and moves to a next step. Opening A is padded with reassurance and qualifiers, so the core fact is hard to pin down, and it also points toward the difficulty of the data and the expectations rather than the team's own part.

Tracing What the Customer Knows

The easiest way to judge a delivery is to follow what the customer actually knows after each sentence. Softening feels like kindness because it lowers the emotional temperature of the moment. The problem is that the customer needs to act on the message. Work through the cushioned opening (Opening A from the prediction above) one step at a time.

1
Sentence one: the customer learns that the team values their patience. They know the tone is friendly but nothing about the work has changed yet.
2
Sentence two: the customer learns that the data is complicated and expectations were hard to meet. Their attention now drifts toward whether the inputs were the problem.
3
Sentence three: the customer hears that the result may be lower than hoped. The word may and the phrase a little lower leave them unsure whether this is a settled fact.
4
Sentence four: the customer hears that things could still shift. Now they cannot tell whether the validation failed, whether it is still in progress, or whether a change is needed at all.
5
End of message: the customer knows the tone but cannot identify the core fact, what has changed, or what they are supposed to do next.

The customer pays for this later. They have to reconstruct the facts themselves, or they take the message to their own managers and find that it does not hold together. The kindness was real in intent, but the message did not carry the information the customer needed.

Two Failure Patterns

The two common failure patterns look different on the surface, but both move the customer away from the decision they now have to make. Each is described below, followed by how a direct answer avoids both.

The Three Parts of a Direct Answer

A direct answer does three jobs in sequence. First, it states the result plainly, so the customer knows the validation came back worse than expected before anything else is said. Second, it acknowledges the team's part in the outcome instead of locating the cause outside the team. Third, it sets out a next step that the customer can explain to people above them.

What are the three required parts of a direct response, and in what order do they appear in the message?

The order matters. The result comes first so the customer anchors on the core fact. Ownership comes next, while the team's part is still fresh. The next step comes last, because it is the part the customer will carry upward and repeat. The source notes that a customer who has to defend a changed timeline needs a reason and a plan they can repeat, not just an apology.

Tracing a Direct Reply

Now trace the direct opening (Opening B) the same way. Each sentence adds a piece the customer can use.

1
Sentence one: the customer learns the core fact immediately. The validation came back worse than expected.
2
Sentence two: the customer learns that the team owns part of the outcome. The scope risk should have been flagged earlier, and the team apologizes for that.
3
Sentence three: the customer learns the required action. The timeline needs to change.
4
Sentence four: the customer learns a plan is coming. The speaker will walk through a proposed plan.
5
End of message: the customer knows what happened, what has changed, and what happens next, and can repeat all three to their own managers.

How do over-softening and blame each differ from a direct answer in what the customer walks away knowing about the bad result and their next step?

The comparison shows the difference clearly. Over-softening leaves the core fact hidden and the next step vague. Assigning blame keeps the core fact visible but turns the conversation toward fault, so the next step is pushed aside. A direct answer keeps both the core fact and the next step in front of the customer.

Mistakes Beginners Make When Delivering Bad News

Common mistake
Treating gentleness as the same thing as softening
What it looks like
Opening with several sentences of reassurance before stating the result
Why it fails
The customer needs the core fact to act on, and padding hides it
Do this instead
Be kind in tone, but state the result in the first sentences
Common mistake
Explaining that the result is not really the team's fault
What it looks like
The inputs were messy, so the result was always going to be weak
Why it fails
The message becomes a dispute about fault and the customer may feel defensive
Do this instead
Name the team's part in the outcome and move to the decision ahead
Common mistake
Ending with an apology and no plan
Why it fails
The customer who must defend a changed timeline needs a reason and a plan they can repeat
Do this instead
Close with a next step the customer can explain to people above them
Common mistake
Using hedges like may or could for a result that is already settled

Practice: Rewriting a Cushioned Message

MEDIUM

You are the delivery lead. The validation phase produced a worse result than expected, and the timeline must change. Write a three-part reply: first state the result plainly, then name the team's part in the outcome, then propose a next step the customer can explain to their own managers. Avoid any reassurance or qualifiers that hide the core fact, and avoid locating fault in the customer's data or expectations.

Hints

Start with the result itself, in a plain sentence
Name something the team did or did not do, without blaming the inputs
End with a concrete next step and a reason the customer can repeat

Your attempt (not saved)

Key Takeaways

Bad news delivered with heavy softening can leave the customer unsure of the core fact and what they must do next.
The two common failure patterns are over-softening, which buries the core fact, and assigning blame, which turns the conversation into a dispute about fault.
A direct answer states the result plainly, owns the team's part, and sets out a next step the customer can defend internally, in that order.
Gentle tone and clear content work together: be kind in how you speak, but precise in what you say.