Who this is for: Product, marketing and customer teams choosing a suitable release communication workflow.
What to prepare
- The approved retirement record and milestones.
- Affected users, tasks and configurations.
- Available alternatives, limitations and action ownership.
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Illustrative planning brief: explain the retirement of a fictional legacy scheduled-summary format. Identify the affected schedule label and administrator role. Show each approved milestone with the event it represents rather than inventing one universal cutoff. Explain the verified replacement setup and state that schedules do not convert automatically if that is the confirmed behavior. Reserve time to inspect a replacement summary using the owner's criteria. Disclose important unsupported options in the alternative. End with the required action, approved deadline and guidance destination. If no suitable replacement exists, use the owner's actual next step rather than creating a fictional workaround.
Decide what the notice must answer
The audience needs to know whether it is affected, when the change matters, who can act and how to verify completion. The internal reason for retirement can support the message when approved, but it should not displace the practical task.
A single video may not serve both administrators and ordinary members. Administrators may need a transition path; members may need to identify the issue and contact the responsible person. Keep the facts consistent while adapting the next action.
Prepare the retirement record
Separate dates for new setup, existing operation and other relevant milestones. A date without an event is ambiguous. Keep consequences tied to the approved record rather than inferring data deletion, access loss or automatic conversion.
- Suitable inputs: confirmed scope, dates and a verified alternative path.
- Insufficient inputs: an internal target date or a replacement idea that is not available.
- Important boundary: an alternative may not cover every old option.
- Required owner: the role authorized to perform the transition.
- Reference: the current approved notice or procedure.
Build a clear action sequence
Start with a recognizable affected object, then explain timing and action. Show the alternative only to the extent it is verified. Use a stable reference ending that can be paused to inspect owner, task and deadline.
Do not hide a replacement gap in fast-moving text. If it affects the choice, explain it next to the alternative. A transparent limitation is more useful than an animation implying an effortless one-to-one successor.
Maintain the notice
Track every date-bearing video, thumbnail and embedded copy. A changed deadline requires coordinated correction, not only an edited description. After retirement, decide whether the asset remains useful as historical context or gives obsolete instructions.
Keep the communication plan connected to the responsible product and policy owners. They should confirm the notice timing, affected audience and approved transition path before production; the creative team then checks that the final video preserves those decisions accurately.
Review checklist
- Affected tasks and roles are recognizable.
- Every date names an approved event.
- Alternatives and their gaps are stated accurately.
- The ending gives a verified action and completion check.
- Date-bearing publication copies have a maintenance owner.