Forty-Five Seconds Is Long Enough to Find the Real Point

Draft for team review. This article is not approved for external posting.

A short explanation can expose a problem that a long document politely hides: you have not yet decided what matters.

That is why a 45-second exercise is useful. It is not a contest in talking faster. It is a small design constraint. A listener has room for one clear claim, one concrete image or consequence, and one reason to care. Everything else must earn its place.

The first version is rarely wrong. It is raw material.

Look for the distinction

The most useful revision usually begins when two ideas that arrived tangled together are pulled apart.

In one explanation of generative AI, the important distinction was between fluent output and understanding. A model can produce a polished answer while a person is still working out the purpose of the work. That changes the workflow, but it does not make the response correct or purposeful on its own.

In a conversation about Blender, the distinction was between a view and structure. A photograph gives an AI pixels from one angle. A 3D scene can expose geometry, scale, and relationships. It still does not contain the physical world unless those additional properties have been modeled.

In an engineering story, the distinction was between useful constraints and scarcity for its own sake. A 64K memory budget and a 150-baud network forced priorities into view. Modern AI can make output feel cheap, but the cost often returns later as review, maintenance, complexity, energy use, and human attention.

The same move works in a personal introduction. A career chronology may be accurate, but it does not tell someone what connects the jobs. The stronger explanation finds the recurring work: making complicated systems understandable and useful.

Ask questions that create friction

A chat tool can help with this stage if it is used as a questioning partner rather than a word machine. Open with the actual work: “We are going to create a 45-second elevator speech, let’s start by gathering our thoughts on this topic: [topic].” Then give it the audience, the purpose, and the boundary. Ask it to surface one material question at a time.

“What am I assuming the listener already knows?” is a useful question. So is “Which claim could sound stronger than the evidence supports?” Or “What concrete image would make this easier to remember?”

Before requesting a draft, say what the explanation is really about, what must remain true, and what the tool must not invent. “Make this punchier” can wait.

The person doing the explaining remains responsible for the meaning. They decide what must stay, what changes, what sounds false, and when the explanation is ready. A fluent draft is a proposal, not a verdict.

Draft for an actual listener

Once you have confirmed that direction, request a first plain-language draft for the named listener. Then read it aloud. Spoken timing catches crowded sentences, unfamiliar vocabulary, and the places where a list has replaced a thought. Give one targeted refinement direction and keep the first draft beside the revision. Ask someone to say back the main point and next step. If they cannot, a better adjective probably will not solve the problem.

Make another version for a different listener. The underlying idea may remain steady while the example, vocabulary, and invitation change. A busy owner may need a low-risk practical benefit. A potential learner may need permission to begin imperfectly. A skeptical collaborator may need the boundary before the promise.

Forty-five seconds is enough time to practice a durable habit: choose what matters, make the tradeoffs visible, and leave the listener carrying the right idea rather than a pile of accurate details.

Review needs: learning-design, accessibility, timing with varied speakers, factual and audience review for any real-world use, and editorial review before publication.

---

Source: labs/forty-five-seconds-to-make-it-clear/companions/article-medium-draft.md