Who this is for: Product, marketing and customer teams choosing a suitable release communication workflow.
What to prepare
- An approved release fact and intended audience.
- Screens or recordings proving the changed action and result.
- Current availability, role and scope statements.
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Illustrative planning brief: explain personal saved views in a fictional review tool to members who repeatedly inspect the same queue. Start from a familiar queue with status and owner filters. Show the approved save action, name the view and reopen it through the verified route. Hold on the retained filters and matching records. State that views are personal and include the current eligibility line. End with the appropriate next information or access step. Do not imply shared views, universal availability or measured time savings. Treat the example as a storyboard plan until real product assets and facts are supplied.
When this job fits
Use a feature announcement when a viewer needs to know what changed and why it matters to a recognizable task. It works best when one action can be demonstrated with clear before and after states. A small change may still deserve explanation if it introduces a meaningful decision.
A broad release list is a poor input unless it is first narrowed. A feature whose behavior is still uncertain needs fact gathering before production. If the audience needs a full setup lesson, a detailed guide or walkthrough may be the better primary resource.
Prepare the evidence
Collect exact labels, prerequisites and a verified result. An attractive screenshot of a new button is not enough to show what the button does. Keep the sample data consistent and label fictional records so they are not mistaken for customer evidence.
- Suitable: one approved action, a clear audience and a matched result.
- Unsuitable: an unverified concept presented as shipped behavior.
- Needs more work: a release note with unresolved scope or access conditions.
- Optional support: a detailed release-note destination for exceptions that would overcrowd the announcement.
Build and review the story
Extract the change into input condition, action and result. Write a short script and pair each line with evidence. Then storyboard the proof moment before choosing transitions or decorative effects. This keeps the film's promise tied to what can actually be shown.
Review the final encoded candidate against the release record, including title, captions, thumbnail and destination links. A factual change during production can invalidate a previously approved line or screenshot.
Understand the limits
The brief supports planning a clear explanation; it does not make a feature publicly available or establish business impact. Keep conceptual assets labeled and avoid fabricated user results. The planning example above describes a fictional product, not an Animro capability announcement.
If availability is limited, give eligible and ineligible viewers accurate next steps. Check the eligibility line again on publication day, because rollout conditions can change after the storyboard is approved.
Review checklist
- One changed action defines the announcement.
- The proof scene visibly confirms that action.
- The audience and availability conditions are accurate.
- Illustrative material is distinguishable from product evidence.
- The final publication candidate is reviewed against current facts.