Explain a product people do not recognize yet

An unfamiliar term asks the viewer to learn vocabulary before they know why it matters. Try opening with a recognizable moment instead: someone makes a decision, the reasoning is scattered across messages, and a colleague later needs to understand it.

This guide uses a fictional decision-log product as an illustrative example. The imagined product stores a decision, its owner and linked supporting notes. No product result or customer experience is being claimed. The exercise is to explain that defined behavior without inventing a larger category promise.

Write five rungs in order. Each rung should earn the next rather than introduce a new abstract noun.

• Familiar task: “You need to explain why a team chose this option.”
• Friction: “The decision and its supporting notes are in different places.”
• Concrete action: “Open a decision record and attach the notes that support it.”
• Observable result: “The record shows the choice, owner and linked context together.”
• Category name and boundary: “This is a decision log: a place to record a choice and its context. It does not make the decision for the team.”

Opening one begins with jargon: “The intelligent decision infrastructure for modern teams.” Rewrite it as “Find the reasoning behind a decision without reconstructing the conversation.” The revised line identifies a task; the next scene must show the actual record and its context. Avoid implying a search performance claim that the film cannot establish.

Opening two stretches an analogy: “A second brain that remembers everything.” Rewrite it as “A record for the decision you want the next colleague to understand.” This removes an unsupported universal memory claim and narrows the example to material the team intentionally records.

Opening three jumps straight to a category label: “Meet our decision intelligence workspace.” Rewrite it as “A choice was made. Here is where the owner and supporting notes stay together.” Introduce the approved category term after the viewer sees those fields. The motion should reinforce the relationship rather than decorate the unfamiliar phrase.

A metaphor can make the first sentence easier to grasp, but it should return quickly to actual behavior. A “folder for decisions” may communicate grouping, yet viewers could infer document storage or automatic filing. Show the real record and explain the important difference before the metaphor hardens into an expectation.

If two viewers might interpret the category differently, add a concise boundary. For the example: a decision log records a team's choice; it does not evaluate every alternative or approve work automatically. Boundaries can live in supporting copy if they would overload the opening, but the film should not visibly imply the opposite.

Ask a reviewer to describe the product after reading only the opening and looking at the planned first demonstration. If their description introduces a capability absent from the brief, revise the wording or image. This is a useful review exercise, not evidence that a rendered video has been tested.