Product demos & UI / Guide

Show a multi-user workflow without confusing identities

Follow one shared object and identify the actor whenever control changes. Collaboration becomes confusing when the viewer must infer whether a new screen represents a new person, a new item or merely another view of the same work.

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

Who this is for: Teams demonstrating requests, reviews and collaborative editing.

What to prepare

  • One shared object with stable identity
  • Verified roles and ownership rules
  • Screens for each participant
  • A status and revision continuity map

Build a role-and-object continuity map

List the object identifier, current owner, acting role and resulting status for each scene. Keep acting and owning separate: a reviewer can comment on an item without becoming its owner. Use the product’s own terminology and verified workflow rules.

Choose one visual identifier for each participant, such as an account label or avatar accompanied by text. Color can reinforce the distinction, but names and roles must carry the meaning. Avoid assigning an unrelated new color to the same person halfway through.

Illustrative map: review a sample instruction card

The fictional object is D-008, “Sample instruction card.” Example author owns the draft; Example reviewer supplies feedback. This is a planning exercise requiring matching real product evidence before production.

  • Scene 1: Author account; D-008 Draft; the author submits it for review. Show the observed status change.
  • Scene 2: Reviewer account; D-008 Awaiting review; reviewer comments “Clarify the opening step.” The object owner remains Example author.
  • Scene 3: Author account; same D-008 and quoted comment; author revises the opening sentence. Distinguish a content revision from comment resolution.
  • Scene 4: Reviewer account; D-008 with revised text; reviewer performs the documented resolution or approval action.
  • Scene 5: Shared result; hold D-008’s resulting status and preserve any unresolved comments rather than implying the entire object is approved because one thread is closed.

Make each handoff visible

Introduce a role label before the new participant acts. A brief title such as “Reviewer checks the revision” is more informative than a fast crossfade between nearly identical screens. Keep the object title in the same region when possible.

Do not pretend asynchronous work happens simultaneously. If the film compresses time between request and response, use a labeled transition. The edit can be concise without implying instant human availability or automatic approval.

Limit the cast and the number of objects

If a third participant does not make a consequential decision, exclude their activity from this film. If they must approve before publication, keep the handoff and expand the scope honestly. Cutting an essential approver produces an inaccurate workflow.

For a split-screen version, keep the active actor visually dominant and show one change at a time. For a sequential version, retain the same identifier at every cut. Review by tracing the object without narration; the path should remain understandable.

Review checklist

  • Every actor change has a readable label.
  • Object identity survives every handoff.
  • Ownership is not confused with the current actor.
  • Thread resolution is not mislabeled as whole-object approval.
Explore product demos & ui ↗