Product updates / Prompt

Prompt: show where a familiar feature moved

Use a stable task label to connect two routes. This fictional example moves a member list; replace both routes with verified labels and preserve enough surrounding navigation to orient the viewer.

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

Who this is for: Product marketers and motion designers briefing a specific software update.

What to prepare

  • The old route and new route for one task.
  • Screens showing every required navigation level.
  • Role restrictions and the current destination screen.

Copyable creative brief

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

Plan a 30-second orientation sequence for a fictional workspace tool. The task is finding the workspace member list. Open with “Looking for workspace members?” and a labeled view of the previous route, Settings then Members. Hold briefly, then make an explicit editorial cut to the current workspace overview. Show the Workspace menu opening and the verified People entry. Keep an editorial label, “Workspace member list,” visible across the cut so the task stays recognizable even though interface wording differs. End on the actual member-list destination. Show only the actions available to the intended role. Do not morph the old button into the new location as though users can drag it there. Do not claim old bookmarks redirect unless that behavior is supplied. Close on the new path as a readable reference, with the approved access condition if one applies.

Make it your own

Stable task label
Name the action users recognize independently of the menu labels.
Old and new paths
Replace every level with exact approved labels.
Audience role
Capture the navigation available to that role.

Confirm every step of the route

A close crop of the destination label is insufficient when the user must first choose a workspace. Include that level or state the prerequisite. Record whether the route differs on another device before adapting the same instructions.

Handle a simultaneous rename explicitly

If the task is also renamed, show the old-to-new term once, then use the new term consistently. Do not expect motion alone to explain both a new location and a new name. For a shorter version, retain the old cue, complete new route and destination hold.

Fix a route that viewers cannot reproduce

If a reviewer cannot identify the starting menu, widen the opening current-version view. If they think the task's behavior changed, add the verified unchanged-purpose line. Check the final reference against the actual role rather than an administrator screenshot selected for convenience.

Review checklist

  • Every required navigation level appears or is a stated prerequisite.
  • The stable task label connects both versions.
  • The final destination performs the same verified task.
  • Role-specific navigation is not presented as universal.
Explore product updates ↗