Product demos & UI / Prompt

Prompt: separate processing from confirmed completion

Use different labels and visuals for work in progress and a verified result. Keep the affected object visible so the audience knows what the system is processing.

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

Who this is for: Teams explaining asynchronous product actions.

What to prepare

  • Request action
  • Observed intermediate feedback
  • Verified final state

Copyable creative brief

An authored planning example. Replace illustrative details with your approved product facts and assets.

Create a 30-second illustrative export sequence from supplied product evidence. The sample object is “Example review report.” Show the real export request action, then the actual queued or processing feedback with the report name visible. Do not invent progress percentages. If the source wait is shortened, use “Processing interval shortened” or another clear editing disclosure. Cut to the verified completed state and inspect the available report item. Use “Processing” during the wait and “Report ready” only when the product confirms readiness. If the evidence ends at queued, end with “Request queued” and do not fabricate a completed file. Keep any error or retry outside this main path unless the brief is specifically about recovery. The report data is illustrative and the runtime is an editing plan, not a benchmark.

Make it your own

Async task
Use one verified action and object.
Pending wording
Match the product’s actual status.
Completion evidence
Supply a ready-state screen or limit the claim.

Define completion from the product

Document what each observed status means. A submitted job, completed generation and available download can be separate states. Use the finish line that matches the viewer’s question.

Adapt the wait

For a short film, compress waiting with an explicit cut while preserving the status distinction. For training, show where the user can return to check progress. Do not fill the wait with unrelated success imagery.

Correct false success

If a checkmark appears during processing, remove it or identify its limited meaning. If an animation turns a spinner into a file without supplied evidence, replace it with the actual completion screen or narrow the ending to pending.

Review checklist

  • Pending and complete labels are distinct.
  • Any shortened wait is disclosed.
  • The final claim matches available evidence.
Explore product demos & ui ↗