Navigating Common Scenarios in Customer Simulations

This article works through a scenario from customer simulation exercises. You play the person delivering the news, and an interviewer plays a customer who is about to hear that a validation phase has produced a worse result than expected and that the timeline or scope has to change. Your task is to deliver that news well. The misconception we will examine is the belief that gentleness and deflection are the same thing as care.

Before reading the explanation, make your own judgment. Below are two openings a candidate might use with the customer. Decide which one a careful evaluator would consider the stronger delivery, and note what makes it stronger.

Opening A: 'We really appreciate your patience throughout this process, and I want you to know how much we value the work you have put in. Our validation has been a complex undertaking, and while it is possible that some results may be a little below what we had hoped, it may be too early to draw firm conclusions, and there are a number of factors that could still be influencing the picture. We are hopeful that things could settle, and we will look at whether a few adjustments might help in time.'

Opening B: 'Validation came back worse than we expected. The result is below the level we agreed on, so the timeline has to change. Here is what we are doing about it, and here is the plan you can take to your leadership.'

Many people who have to tell a customer something unwelcome reach for the same tool first: padding. They add reassurance, qualifiers, and hedges until the message is hard to find. Opening A above follows that pattern. Read it once and ask where the bad result is stated. The answer is that it is never stated directly; it appears only as a possibility that 'may be a little below' what was hoped.

The diagram below traces what happens to the core fact as softening is added. The first sentence of a plain delivery carries the result. Each layer of reassurance and qualification pushes that result further down the message, until the customer has to dig for it.

Trace the example after the diagram. In Opening A, the customer hears about patience, value, complexity, possibility, and hope before reaching anything that could be called the result. By the end, the customer may still not know whether the timeline has changed. In Opening B, the result is the second sentence, and the change to the timeline follows directly from it.

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. If the news arrives wrapped in so many qualifiers that the customer cannot identify the core fact, they leave the conversation unsure what happened, what has changed, and what they are supposed to do.

The kindness is real in intent, but the customer pays for it 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. A message that was gentle to hear can be hard to repeat accurately, and the customer is the one who has to repeat it.

The second instinct, assigning blame to the customer's data or expectations, fails for a different reason. Many people reach for it because it feels protective: if the result is not really their fault, the team seems less responsible for the disappointment. The diagram below compares where responsibility goes in a blame response and in an owned one.

Consider this generated blame-pattern reply: 'The inputs we received were pretty messy, and honestly the expectations going in were a lot higher than the data could support. So the result is what it is.' Notice that the sentence about the result is correct in content, yet the message is now about whose fault the result is.

When a delivery team says the inputs were messy or the customer always expected too much, the message quietly becomes a dispute about whose fault the result is. That shifts attention away from the decision the customer now has to make. It also damages trust. The customer may well have supplied the data in good faith, and hearing that it was the problem leaves them defensive rather than collaborative.

Put the three styles side by side. Over-softening buries the result and leaves the next step vague. Blame moves responsibility away from the team and turns the conversation into a dispute. A direct answer states the result first, keeps responsibility with the team, and gives a next step that can be explained to others.

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.