A neighborhood node goes down and knocks out internet for six blocks. Four customers call in about it inside twenty minutes. The rep gives all four the same facts: a piece of equipment failed, a truck is en route, service should be back in two to three hours. One customer says "fine, thanks" and hangs up satisfied. One keeps asking follow-up questions and won't let it go. One says "okay but is this going to keep happening" in a tone that suggests she already believes the answer is yes. One wants to know exactly what part failed and why it's not been replaced already.
Same outage. Same facts. Four different calls. The difference isn't what the rep knows, it's how the rep tells it. Structure and calibration, the two ideas at the center of the site's storytelling framework, come together here. The story doesn't change. The shape it takes for each caller does.
Why the same facts land differently
Every caller is running the story through a filter built from their DiSC style: what they need to hear first, how much detail satisfies them, and what would make them trust the explanation instead of just tolerating it. Give a fact-first explanation to someone who needs reassurance first and the facts don't stick, because the caller is still stuck on whether this is going to be okay. Give a reassurance-heavy explanation to someone who wants the mechanism and they'll hear it as padding, or worse, as a rep who doesn't actually know what's wrong.
This is where DiSC and story structure meet directly. DiSC tells you what the caller needs. Story structure is how you deliver it. Neither one works as well without the other.
The four shapes
D · Outcome-first
What lands: The ending, moved to the front. "You'll have service back by 2pm. Here's the short version of why." A D doesn't need the story told in order, they need the resolution stated before anything else, then just enough of the middle to make it credible.
What backfires: Building up to the answer. Any version of "well, first I want to explain what happened" reads as delay. Say the outcome, then answer the "why" only if they ask for it.
i · Scenario-led
What lands: A story they can picture themselves in. "You're not the only one, this hit the whole block, and our tech is already on the way to fix it for everyone at once." An i wants to feel like part of a shared situation, not an isolated complaint ticket.
What backfires: A dry, clinical rundown with no human framing. It's technically complete and emotionally flat, and an i will read the flatness as the rep not caring.
S · Process and reassurance
What lands: A clear sequence with the uncertainty named and handled. "Here's what happened, here's what's being done right now, here's when to expect it fixed, and here's what to do if it's not." An S needs the process spelled out because unpredictability, not the outage itself, is what unsettles them.
What backfires: Rushing past the plan to get to a close. An S who isn't sure what happens next will stay quietly unconvinced even after saying "okay."
C · Logic chain, verifiable
What lands: Cause, then effect, then fix, in order, with real terms. "A power supply on the neighborhood node failed around 9:40. That took down the node serving your area. A tech is replacing the unit, ETA 2pm." A C wants to be able to follow the reasoning, not just accept the conclusion.
What backfires: Vague causes like "there's an issue in your area." A C hears that as either a rep who doesn't know or a rep who isn't telling them. Either read costs trust.
Same structure, different pacing
Notice that all four versions still carry the same three-part shape: what's happening, why, what changes. Structure doesn't disappear when you calibrate, it just gets compressed or stretched. The D version compresses all three into a sentence and a half. The C version stretches the "why" into its own paragraph. The story's skeleton holds. Only the amount of time spent on each beat moves.
That's the practical value of thinking about calibration this way. A rep doesn't need four separate scripts memorized. They need one structure and the judgment to know which beat to lean on for the person on the line.
Reading the style fast enough to use it
None of this works if the read comes too late. By the time a rep has delivered the wrong version of the explanation, the caller has usually already formed an opinion about whether this call is going well. The read has to happen in the opening seconds, off pace, word choice, and how the caller framed their own question, and the explanation has to shift on the fly.
In practice this means holding the explanation loosely at first. Open with something short and watch how the caller responds. A caller who cuts in with "just tell me when" is telling you to skip to the outcome. A caller who asks "what exactly failed" is telling you they want the mechanism. The caller tells you which version they need if the rep is listening for it instead of just running through the explanation they'd planned to give.
The facts of an outage don't change caller to caller. What changes is which fact goes first, how long you stay on the reasoning, and how much reassurance gets built in along the way. That's the whole skill.
Where this connects
This piece pairs directly with the DiSC track's style breakdowns and with the structure work in "What Narrative Structure Actually Is." The DiSC pages tell you what each style needs. This page is about applying that knowledge to the specific moment of explaining something technical that just went wrong. Together they cover the full move: read the style, then shape the explanation to fit it.
Want to go deeper?
The DiSC Deep Dive Guide covers all four styles across three stages, with exercises, a friction matrix, and scripts for real conversations.
Download free PDF guide Book a free intro call