From complex to compelling: How to turn dense business content into executive-ready slides and video scripts

Most ‘complex’ content isn't actually complex. It's just unedited.‍

by Julian Rogers

You know the old joke about a thoroughbred horse who walked into a committee meeting and came out a camel? Somewhere between the research doc, the fifteen-person working group, and the eventual slide deck, every idea picks up baggage: caveats nobody removed, jargon nobody translated, and a structure that follows how the work happened instead of how a decision gets made. By the time it lands in front of an executive, the idea itself might be simple. But the path to it can be convoluted and lengthy.

That’s a recipe for exhaustion, not scintillation.

This is the actual job of a content writer who works at the executive level: not making things sound smarter, but removing everything standing between an audience and the point. Here's the framework I use to do it, and where it breaks down when people get it wrong.

The problem isn't the subject matter. It's the ownership.

Give me a dense clinical trial summary, a technical platform update, or a quarterly performance review, and often none of it is actually hard to explain. What's hard is that everyone who touched it before me had a stake in keeping their part in. The scientist wants the methodology in. The product manager wants every feature mentioned. Legal wants six qualifiers per sentence. Nobody in that chain is incentivized to cut. Why? Cutting feels like loss.

That's the writer's job: be the only person in the room whose incentive is the audience's understanding, not the source material's completeness. Every dense document you've ever sat through in a meeting was written by committee. The good ones get edited by one person with a spine.

A framework for the cut: Problem → Insight → Implication

When I take a pile of research notes, an SME interview transcript, or a stack of technical documentation and need to turn it into three slides or a ninety-second script, I run it through three questions, in this order, and I don't move to the next until the current one is answered in one sentence:

1. What's the problem, in terms the audience already cares about?
Not "what does the data show" — what's actually broken, slow, expensive or risky, described the way the audience would describe it if they noticed it themselves.

2. What's the one insight that changes how they'd act?
Out of everything in the source material, there's usually exactly one finding that matters for a decision. Everything else is supporting evidence, not the headline. If you can't name the one insight, you don't understand the material well enough to simplify it yet. Go back to the source; don't paper over the gap with more words.

3. What's the implication — what happens next, or what should?
This is the part dense content almost always skips, because the source material was written to inform, not to move someone toward a decision. An executive audience doesn't want to be informed. They want to know what to do with what you just told them.

You have to get to what they care about. Because they really don’t care about what they don’t care about.

If you can fill in those three blanks in three sentences, you have your slide headlines. You have your video script's spine. Everything else — the data, the methodology, the caveats — becomes supporting detail that earns its place only if it strengthens one of those three sentences. If it doesn't, it goes in the appendix. Or nowhere.

What this looks like in practice

Take a disguised but realistic example: a healthcare platform's product team hands you forty pages of user research on why physicians aren't adopting a new charting feature.

The raw material is genuinely complex. It likely consists of usability data, interview quotes, a comparison against three competitor workflows, and a section on integration friction with existing EHR systems, etc.

Run it through this framework:

• Problem:‍ ‍
  Physicians are reverting to their old charting workflow within two weeks of training, which means the feature isn't sticking and the investment isn't paying off.

• Insight:‍ ‍
  It's not a training problem or a UX problem — it's a trust problem. Physicians don't believe the new workflow captures liability-relevant detail as reliably as the old one, so they hedge by doing both.

• Implication:‍ ‍
  Fix the trust gap, not the tutorial. That means a targeted feature (an audit-trail indicator, or a side-by-side comparison in-app) beats another round of training videos.

That's a three-slide executive narrative built from forty pages, and it's a stronger story than the raw research because it has a point of view. The forty pages of research are still valuable — they're the backup deck, the source of truth if someone challenges the conclusion. But nobody in a leadership meeting should have to read them to understand the decision in front of them.

Where AI tools actually help — and where they don't

I use AI writing tools daily, and they're genuinely useful for exactly one part of this process: getting from raw material to a rough first pass faster. Feed a transcript or a research doc into a tool and ask it to identify candidate "problem/insight/implication" statements, and you'll usually get something serviceable to react to instead of a blank page.

What AI tools are bad at, in my experience, is knowing which insight actually matters to this audience, in this moment, given this organization's politics and priorities (the judgment part). That's still a human job, and it's the part that's actually hard to hire for. The writers who are worth paying for aren't the ones who can generate a script. They're the ones who know which of the twelve technically-correct scripts an AI tool could generate is the one an SVP will actually sit through.

Don't forget the frame around the words

Content this dense doesn't just need better sentences. It needs a visual structure that reinforces the cut you just made. A three-part narrative (problem, insight, implication) should look like three parts on the slide, not get buried in six sub-bullets per slide because someone couldn't bear to cut a data point. The same discipline that shapes the script should shape the deck: one idea per slide, one takeaway per scene in a video, and enough white space that the audience trusts you've already done the hard work of deciding what matters.

Making content clear and plainly understandable does not equal “dumbing it down.” That's the whole craft, really. The goal is not to make complicated things sound simple. The goal is to make the genuinely important part visible by removing everything that was hiding it.

‍

Have a dense idea that needs a story? Get in touch. Interested in boosting your executive presence? Learn more.

‍ ‍