Why a screen tour is not a product story

The working approach

Identify whether the viewer needs orientation or conviction.
Choose a structure that matches that need.
Judge the edit against the chosen question.

A concrete example

A sequence of Dashboard, Settings and Library labels is a tour. Finding a reference, saving it and using it for a brief is a story.

Before recording this scenario, write down what the starting screen contains and what should be different at the end. This gives the reviewer an observable result to check, rather than asking them to approve a general impression.

The mistake to avoid

Adding music does not turn navigation into a story.

If the source cannot support the intended message, narrow the claim or capture the missing evidence. A transition, caption or voiceover can explain a real change; it should not manufacture one.

Put it into a production brief

Replace the bracketed fields before using this brief. The scenario is illustrative; keep only the actions your product actually supports.

EDITABLE PRODUCTION BRIEF

Purpose: Why a screen tour is not a product story.
Audience: [specify the viewer and their familiarity with the product].
Decision: [what should the viewer understand or do next?].
Approach: A tour explains where controls live. A story explains why a person would use them. Both can be useful, but they answer different questions.

Required evidence:
1. Identify whether the viewer needs orientation or conviction. Show the relevant entry state, action and completed result.
2. Choose a structure that matches that need. Show the relevant entry state, action and completed result.
3. Judge the edit against the chosen question. Show the relevant entry state, action and completed result.

Reference scenario: A sequence of Dashboard, Settings and Library labels is a tour. Finding a reference, saving it and using it for a brief is a story.
Avoid: Adding music does not turn navigation into a story.

Deliverable: [duration], [format], [placement].
Use only recorded product behaviour. Preserve the full original.
Acceptance: check each claim against its visible scene, review at actual viewing size, and test the final file.

Review before delivery

Evidence: can a new viewer identify the result described in the example without being told where to look?
Reading distance: are the relevant controls and labels understandable at the intended placement size?
Continuity: does each cut preserve the relationship between the action and its result?
Accuracy: does the final caption describe the visible product state, including any limits?

Using this with Demovela

The automatic URL workflow currently supports Postraid and Adfolio. Other product scenarios on this page are production-planning examples, not compatibility claims. Adapt the brief to your own recorder or editor. Demovela preserves originals and creates separate outputs; review the resulting file before publishing.

Check the current preview scope →

Keep the workflow moving

Choose the next resource based on the decision you still need to make.

Browse the complete resource library →