Explain a renamed feature without implying new functionality

A rename announcement needs more than two words and an arrow. Record what the feature does, whether its location changes, whether stored objects keep their names and which help material still uses the old term. These fields reveal where confusion is likely.

Do not say “Nothing else changes” unless the release owner has verified that broad statement. Name the relevant unchanged behavior instead: saved lists remain available, the approval action is unchanged, or existing links still resolve.

• Previous label: the exact term users may search for.
• Replacement label: the approved new term.
• Purpose: one sentence explaining the task.
• Location: unchanged or a verified new route.
• Continuity: the specific behavior or object that remains available.

In this fictional example, a planning tool renames Boards to Workspaces. The illustrative release facts say that existing boards remain available with the same task columns and saved items. They do not establish changes to permissions, billing or project limits.

Useful copy: “Boards are now called Workspaces. Open Workspaces to find your existing task columns and saved items.” If the menu location is unchanged, show that stable location. If it moves, add a separate route cue rather than making the viewer infer it.

• Mapping: Boards → Workspaces.
• Purpose: organize tasks in columns.
• Verified continuity for the example: existing columns and items remain.
• Not established by the example: new collaboration, increased capacity or pricing changes.
• Search bridge: use both terms once in the supporting description so users recognize the relationship.

Hold the old label first, then reveal the new one beside it. Keep a recognizable task object or interface region in view. The point is recognition, so an elaborate letter transformation is less useful if it obscures either complete word.

Use the new name consistently after the mapping. Repeating both labels throughout the video can make the rename feel provisional. A final reference frame can retain the mapping for viewers who pause or revisit the announcement.

Make a small follow-up list: navigation, empty-state text, help links, screenshots and recurring messages. This is a communication check, not a promise that all surfaces can be updated at once. Where the old term remains, state the transition accurately in the supporting notes.

If the name differs between audiences or rollout groups, describe the verified condition. Do not manufacture a universal cutover date. A clear rename notice should help users find familiar work today, even while a terminology transition is incomplete.