Product updates / Prompt

Prompt: explain a feature rename

A rename sequence should make recognition easier, not suggest an unannounced capability. The fictional mapping below is a complete planning example that needs approved terminology before use.

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

  • Exact old and new labels.
  • Confirmed purpose and continuity statements.
  • Current navigation and representative task imagery.

Copyable creative brief

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

Create a restrained 30-second planning sequence for a fictional task tool renaming Boards to Workspaces. Open on the previous word Boards beside a clearly labeled illustrative task board. Introduce “Boards are now called Workspaces” and show both complete words together before fading the old label. Retain the same task columns and sample items as the visual anchor. Show the verified current navigation entry using the new name. Explain only the supplied continuity: “Find your existing columns and saved items in Workspaces.” Do not imply expanded collaboration, changed pricing or greater capacity. If location also changes, include the separately verified new route; otherwise keep the location stable. Avoid elaborate letter morphing that prevents either name being read. End with the new label and a small old-to-new reference. Use the new term consistently after the mapping.

Make it your own

Term mapping
Supply exact capitalization and spelling for both labels.
Continuity statement
Name only the behavior or objects confirmed to remain.
Location status
Declare whether the route is unchanged or provide its verified replacement.

Separate the rename from functional claims

Before using the brief, list any actual behavior changes separately. If none are established, do not use copy such as “a whole new workspace.” The same illustrative task objects should remain visible so the comparison teaches terminology rather than a different product.

Adapt for longer or translated names

Give each full term enough space and avoid shrinking the new label just to fit the old layout. A stacked mapping may be clearer than a horizontal arrow for long labels. Approved translations should be supplied as whole phrases, not improvised during animation.

Correct false expectations during review

If viewers infer new permissions, remove decorative controls that were not part of the rename. If the old term remains in some product surfaces, explain that approved transition context in the supporting copy. Do not assert that every old link or label has already changed.

Review checklist

  • Both terms match approved spelling.
  • The unchanged purpose is specific and verified.
  • New functionality is not implied through decorative UI.
  • The mapping remains readable before the old term disappears.
Explore product updates ↗