Preparing for Customer Simulations

Customer simulations are a setting where concrete stories about past engagements show problem-solving and communication.

Programming

Why a Simulation Asks for Stories

Imagine being asked in a customer simulation how you handle a difficult client. It is tempting to answer with a list of qualities such as being proactive, communicative, and flexible. The source material warns that describing skills in general terms rarely shows either problem-solving or communication. What does show them is a concrete story about something that actually happened on an engagement.

Definition

A customer simulation is a setting where you are asked to show how you handle a client relationship, not only what you know about the work. The evaluator wants to see how you solve problems and how you communicate when things do not go as planned.

The preparation this article covers is simple to state. Before the simulation, you should have three specific stories ready. Each one comes from a different kind of moment, and read together they cover problem diagnosis, honest reporting, and boundary-setting. The rest of this article follows the stories through their purposes, their required components, and the rules that govern how each one is told.

The Three Stories and Their Purposes

The three recommended stories are 'They asked for X, I built Y', 'The bad-news conversation', and 'The scope-creep refusal'. Each one is meant to demonstrate a different capability. The first shows that you can diagnose a problem beneath a request. The second shows that you can report an unfavorable result honestly and handle the conversation that follows. The third shows that you can decline an addition to the work while keeping the relationship intact.

How do the three stories differ in what they are meant to demonstrate, and which purpose does each one serve?

Story	Moment it comes from	Purpose	Required components, in order
They asked for X, I built Y	The customer asked for the wrong thing	Problem diagnosis	Stated solution, diagnosed problem, alternative, endorsement
The bad-news conversation	Delivering an unfavorable result	Honest reporting	Unfavorable result, people informed, responsibility, next steps
The scope-creep refusal	Declining an addition mid-engagement	Boundary-setting	Original scope, proposed addition, trade-off, alternative path

The three stories, the moment each one draws on, and the components each must contain

Tracing the 'They Asked for X' Chain

The first story has a strict sequence of ideas. The source describes it as a chain: the customer asks for something, you find that the request does not solve the real problem, you propose a different path, you carry it out, and the customer comes to accept it. Each link depends on the one before. Without a stated solution there is nothing to diagnose, and without a diagnosis there is no reason to propose a different approach.

In what order do the required components appear, and what comes immediately after the stated solution?

What do you think happens?

In the first story, which component comes immediately after the stated solution is introduced?

The endorsement, because the customer must accept the work
The diagnosed problem, because there is nothing to diagnose without a stated solution
The alternative, because you propose a new path before examining the request

Reveal answer

Answer:

The diagnosed problem.

The source states that without a stated solution there is nothing to diagnose. The diagnosis comes next, and only once the request is shown not to solve the real problem does the alternative make sense.

Worked example

Outlining a 'They Asked for X' Story from a Past Engagement

Suppose a client asked for a nightly export of a full data table as a spreadsheet, but their real goal was to have the figures reviewed by their finance team each week. Show how this moment maps onto the four components.

1
Stated solution
Name what the customer literally asked for: a nightly full-table spreadsheet export.
2
Diagnosed problem
Explain why the request misses the real need. A nightly full dump gives the finance team far more data than a weekly review requires, and the real need is a reviewable weekly summary.
3
Alternative
Describe the different path you proposed, such as a weekly summary report that covers only the figures finance reviews.
4
Endorsement
Report how the customer came to accept the approach, for example after seeing a sample summary. Keep it tied to what actually happened on the engagement.

Result

The story now runs in the required order, from the request to the customer's acceptance, and each step carries a specific detail from one engagement.

Why Each Story Must Be Specific and Timed

The source sets three rules for every story. It must describe one specific past engagement or moment, it must be drawn from a real past engagement, and it must be told within three minutes. The first two rules determine what the listener learns. The third sets the boundary on how much of it you can tell.

What changes in the listener's understanding when a story names a concrete engagement and outcome instead of a general description of past work?

The source is direct that a concrete story about something that actually happened is what reveals how you work. A named engagement and a real outcome give the listener something to test your reasoning against. A general description offers nothing to examine. The source does not give a reason for the three-minute limit, so treat it as a fixed constraint: prepare each story so that it fits inside that window without being cut off mid-sequence.

Following the Bad-News and Refusal Stories

The other two stories also follow fixed component lists. The order is given in the source for each one and is best kept as written. The two sections below trace them in turn.

Mistakes When Preparing Stories

Common mistake
Describing a skill instead of telling a story
What it looks like
Saying 'I am good at handling difficult clients' and stopping there.
Why it fails
The source says general terms rarely show problem-solving or communication. Only a concrete moment does.
Do this instead
Name one real engagement and describe what happened in it.
Common mistake
Refusing without a trade-off
What it looks like
Telling a customer 'no, that is not in scope' with no further explanation.
Why it fails
A plain no does not meet the scope-creep story. The trade-off is what makes the refusal clear to the customer.
Do this instead
Show what the addition would cost in time, risk, or displaced work, then offer an alternative path.
Common mistake
Reordering the components
What it looks like
Presenting the endorsement before the diagnosed problem in the first story.
Why it fails
The chain depends on order. Without a diagnosis there is no reason to propose a different approach.
Do this instead
Keep the four components in the order given in the source.
Common mistake
Making the bad-news story only about the bad result
Why it fails
The listener is evaluating how you handled the conversation afterward.
Do this instead
Spend real time on who you informed, what you took responsibility for, and what you proposed next.
Common mistake
Letting one story run past three minutes

Drafting Your Own Outline

MEDIUM

Choose one real past engagement that fits either the 'They asked for X, I built Y' story or the scope-creep refusal. Draft an outline with one line for each required component, in the order the source gives. Keep each line specific enough that a listener could picture the moment. Then check the total against the three-minute limit by reading the outline aloud.

Hints

For the first story, start from the request the customer actually made, then write the stated solution before anything else.
For the refusal, make sure the trade-off names a concrete cost such as time, risk, or displaced work.
If your outline reads like a list of qualities, replace each quality with the specific moment that shows it.

Your attempt (not saved)

Key Takeaways

Three stories should be ready before a customer simulation: 'They asked for X, I built Y' shows problem diagnosis, 'The bad-news conversation' shows honest reporting, and 'The scope-creep refusal' shows boundary-setting.
Each story has required components that appear in a set order: stated solution, diagnosed problem, alternative, and endorsement for the first; unfavorable result, people informed, responsibility, and next steps for the second; original scope, proposed addition, trade-off, and alternative path for the third.
Each story must describe one specific, real past engagement or moment and be told within three minutes, because a concrete story reveals problem-solving and communication where general skill descriptions do not.
The scope-creep refusal depends on preserving the relationship, which the trade-off and the alternative path make possible.