Product demos & UI / Guide

Review whether a product demo matches the real workflow

Review the demo as a sequence of factual claims. For each scene, identify the source, the action it implies and the result it shows. A polished film can still be inaccurate if the transitions connect states the product cannot produce.

By AnimroUpdated 2 min readAI-assisted · independently agent-reviewed

Who this is for: Product owners and reviewers approving public software demonstrations.

What to prepare

  • Complete storyboard or draft
  • All source screens and workflow evidence
  • Exact voiceover and on-screen copy
  • Current role and availability facts

Link every scene to evidence

Record the asset, product version, account role, starting conditions and behavior source. Separate a captured state from a verified transition. Two screenshots can prove two appearances without proving the path between them.

Include spoken and on-screen claims in the audit. A visually accurate interaction can still carry an unsupported line such as “always instant” or “available to every user.” Review access and availability language against current product facts.

Illustrative audit of a three-scene draft

A fictional draft shows sample request R-111 moving from Unassigned to Example reviewer. The reviewer records the following findings before approving production.

  • Scene 1: queue-start.png supports R-111 and Unassigned. Missing context: the account is a configured reviewer workspace. Add a prerequisite label.
  • Scene 2: animated owner menu has no matching source. Evidence supports only the start and end screens. Request an observed interaction or replace it with a clearly labeled state comparison.
  • Scene 3: assigned.png shows the new owner, but the voiceover says “Everyone is notified instantly.” No notification evidence exists. Remove or substantiate that separate claim.
  • Final check: return to R-111 after saving if persistence is part of the promised task; do not treat an unsaved form value as the result.

Inspect the implied behavior between scenes

Watch every cut for missing commitments, role changes and unexplained scope. A jump from one user’s account to another can look like a permission change if the handoff is unlabeled. A generated click ripple can look like a native confirmation if it covers the actual state.

Check that sample identifiers, totals and filter conditions remain consistent. If the real product reorders a list, preserve or explain that behavior rather than arranging a visually convenient but misleading result.

Resolve each issue with evidence or a narrower statement

Assign each finding an owner and a disposition: verified, corrected, labeled as concept or removed. Do not close “needs verification” merely because a stakeholder likes the animation. The resolved source should support the exact final scene.

Review the resulting version again after edits. Replacing one screen can change cursor targets, captions and continuity elsewhere. Approval should identify the exact asset version inspected, not a general intention to make the film accurate.

Review checklist

  • Every implied interaction has evidence or an explicit concept label.
  • Prerequisites and role changes are visible.
  • Sample data remains consistent.
  • Final approval applies to the exact revised version.
Explore product demos & ui ↗