12-minute read · Evidence architecture, paper edit, claim review, and visual plan
Start with a change worth explaining
The familiar challenge–solution–results structure is not wrong; it is merely empty until the specifics arrive. “Company struggled with efficiency, adopted Platform X, and transformed operations” could describe almost any vendor. The audience needs to understand the old process, why change was difficult, what was actually implemented, and which result can be attributed responsibly.
Before booking an interview, write the evidence hypothesis: “This customer can show that [specific intervention] changed [specific process or outcome] under [relevant conditions].” If the customer cannot substantiate that story, choose a different angle rather than manufacturing one in the edit.
Build an evidence packet before the script
- 1
Document the baseline
Capture the previous workflow, frequency, people involved, failure mode, and cost. “Before” must be more specific than “it was difficult.”
- 2
Document the decision
Record trigger, alternatives, objections, buyer criteria, and why the customer believed change was possible.
- 3
Document implementation
Show setup, behavior change, integrations, training, timeline, and the customer’s own contribution. This is often where credibility lives.
- 4
Document outcomes
Collect metrics with baseline, measurement window, source, owner, and caveat. Add qualitative changes that can be observed or corroborated.
- 5
Document permission
Confirm names, logos, screens, data, claims, channels, paid usage, review owner, and expiration before the edit depends on them.
Use a paper edit, not invented customer dialogue
Transcribe the interview, tag useful statements by story beat, and assemble a paper edit from the customer’s exact meaning. A narrator may bridge time or explain context, but should not put conclusions in the customer’s mouth. Keep the unedited source and timecodes so reviewers can trace every consequential claim.
When the cleanest quote is incomplete, ask a follow-up interview instead of building a sentence from fragments that changes intent. Ethical editing can remove repetition and hesitation; it cannot create certainty the speaker did not express.
A practical three-minute architecture
- 0:00–0:15 · Consequence
- Open with the meaningful result or sharpest tension. Make the viewer understand why the story matters.
- 0:15–0:40 · Context
- Identify the customer, role, operating environment, and relevant scale without an extended corporate biography.
- 0:40–1:15 · Before
- Make the old process concrete. Show the workaround, constraint, or risk in the customer’s language.
- 1:15–1:55 · Decision and work
- Explain why this approach, what implementation required, and which obstacle had to be overcome.
- 1:55–2:35 · Change and evidence
- Pair verified outcomes with process footage, product states, documents, or qualified on-screen data.
- 2:35–3:00 · Meaning and next step
- Let the customer explain what the change unlocked, then offer a relevant path for a similar viewer.
Write pictures into the script
Use an audio-visual script. Beside every spoken claim, specify what the viewer can see that adds evidence or understanding: the previous spreadsheet, a task moving through the product, a team ritual, a physical result, a dated dashboard, or a customer environment. Generic office footage spends time without increasing belief.
Plan text overlays sparingly. A number on screen needs the same context as a number spoken aloud. “42% faster” is incomplete without the measured task, baseline, period, sample, and responsible source.
Run two different approvals
First, ask the customer and internal subject experts to verify facts, quotations, attribution, confidentiality, and permissions. Then ask brand and creative reviewers to assess clarity, pace, visual quality, and CTA. Factual approval should not become an invitation for every department to rewrite the customer’s voice.
Lock the narrative before detailed animation. Late changes to an approved metric, product name, or implementation description can alter several scenes and voiceover timing at once.
What working practitioners report
This guide addresses the same revision and expectation risks filmmakers raise when clients add material beyond the agreed scope or dislike an edit after approving earlier decisions. The practical answer is traceability: agreed evidence, interview source, paper edit, and staged approvals. The interview method also incorporates field advice to capture self-contained answers and conduct a conversation rather than reciting questions. Together, those practices protect both the customer’s meaning and the production from late factual rewrites.