A neighborhood-wide internet outage hits, and the rep gets the customer on the line. The rep opens with the cause: there's signal degradation on a node upstream, engineering flagged it overnight, and it's affecting a cluster of addresses in the area. Two sentences in, the customer cuts them off. "So when's it back on?" The rep hadn't gotten there yet. They were still explaining, accurately, why it happened.
Nothing the rep said was wrong. The cause was real, the explanation was accurate, the words were plain enough. It still failed, because it made the customer sit through the cause before telling them the effect. That's not a clarity problem. It's a structure problem, and the two get confused constantly on calls where the rep knows exactly what's wrong and still can't get the customer to calm down and listen.
Clear isn't the same as ordered
"Just explain it clearly" is the advice every new rep gets and almost nobody can act on, because it treats clarity as a property of sentences. Pick simpler words, cut the jargon, drop the node numbers. All useful. None of it fixes an explanation that's ordered wrong, because ordering isn't a sentence-level problem. It's what happens between sentences, the sequence the customer is forced to sit through to get to what they actually called about.
A customer who doesn't know where an explanation is going has to hold every piece of it in suspended judgment until the end. On a call, that's expensive fast, because they're not a captive reader, they're a person who can interrupt, get louder, or ask for a supervisor. It's why a technically accurate explanation delivered in the wrong order reads as stalling or evasive, even when every line is true and every word is plain. The problem was never the vocabulary.
The three-part arc
Narrative structure, stripped down to what's actually useful here, is close to the oldest story shape there is: Problem, Complication, Resolution. Translated into plain terms for an explanation rather than a plot:
The effect, stated first and stated to the person listening, not to the situation in general. What changes for them, what they need to know right now, before any explanation of why.
The reasoning, now that the listener has somewhere to put it. Cause makes sense once the listener already knows the effect it's attached to. Offered first, the same reasoning just sounds like a wall of context with no destination.
The forward-looking piece. What's different starting now, what the listener does or doesn't need to do about it. This is what most explanations skip, because the writer assumes it's implied. It rarely is.
Same facts, resequenced
Take the outage call and run it through the arc instead. Here's what's happening: service is down for your address and a group of your neighbors right now. Here's why: there's an issue on the node feeding your area, and engineering is already working it. Here's what changes: we're seeing a restore estimate of about two hours, and I'll text you the second it's confirmed back up.
Same information. Same length, roughly. The only thing that moved is the order, and the order is the difference between a customer who says "okay, thanks for the update" and one who escalates to a supervisor mid-explanation. Nothing was added to make it land better. Something was just put where the customer could use it.
Structure isn't decoration
It's tempting to treat sequencing as a soft skill, something you layer on top of the real technical content once the facts are settled. It's closer to the opposite. Structure is the part of the explanation that tells a frustrated customer whether it's safe to keep listening instead of talking over you. Get it right and they'll sit through the diagnosis. Get it wrong and they stop listening before you reach the part that actually helps them.
This is craft observation more than settled science, so treat it as a lens to test on your own calls rather than a law. But the pattern holds up under scrutiny: customers tolerate far more technical complexity than they tolerate uncertainty about where an explanation is headed. Order removes the uncertainty. Word choice barely touches it.
Lead with where it's going
The practical version of this is small enough to use on the next call. Before explaining anything, whether it's an outage, a bill, or why a bundle upgrade makes sense, ask what the customer needs to know first, not what's easiest to say first. Usually that's the effect, not the cause. State it, then back into the reasoning once they have somewhere to put it, then close with what actually changes for them. The content barely has to move. The order does the work.
Want the full communication playbook?
The DiSC Deep Dive Guide covers communication scripts, adaptation strategies, and structure for real customer conversations, not just theory.
Download free PDF guide