Who this is for: Launch teams planning a specific communication asset and its production handoff.
What to prepare
- Approved product names and roles
- Verified relationships and availability
- A shared user task
- Evidence for each product's contribution
Scene-by-scene storyboard
60-second planning sequence · illustrative copy and visual direction
- 01
0–7s
Introduce the shared purpose
Show an illustrative work item that moves from collection through decision to handoff.
On screen:One task, several distinct needs.
- 02
7–17s
Introduce the first role
Show the first approved product and its supplied task evidence.
On screen:Collect the item and its context.
- 03
17–27s
Introduce the second role
Show the second product with its distinct decision task.
On screen:Review the item and record a decision.
- 04
27–37s
Introduce the third role
Show the third product's supplied handoff task.
On screen:Prepare the next supported step.
- 05
37–47s
Explain the relationships
Display a labeled family map. Use arrows only for verified connections and distinguish manual handoffs.
On screen:Understand how the products relate.
- 06
47–54s
Help the viewer choose
Highlight the product relevant to the viewer's starting task.
On screen:Begin with the task you need to complete.
- 07
54–60s
Close with current scope
Show individual availability states if they differ.
On screen:Check each product's current availability.
Make it your own
- Product roles
- Give each product one distinct supported job.
- Relationships
- Separate verified connections from manual handoffs.
- Availability
- State per-product differences accurately.
Avoid a family feature wall
The collect-review-handoff example is fictional. It illustrates distinct product roles, not an existing Animro suite or an automatic end-to-end integration.
A family map is useful when it clarifies purpose and relationships. Three nearly identical benefit cards would not help the viewer choose.
Adapt the number of products
For two products, use the released space to explain their boundary and the handoff. For more than three, focus this film on the core relationship and place detailed coverage in separate assets.
A 30-second version can introduce roles and the map without full demonstrations. Keep each role accurate rather than compressing several products into a single vague claim.
Verify family claims
Check naming, bundling, eligibility and access separately for each product. Shared branding does not establish shared pricing or availability.
If the map contains a manual step, show it. A line joining products can imply a supported integration even when no caption makes that claim.
Review checklist
- Each product has a distinct role.
- Connections are verified or labeled manual.
- Availability is not generalized across the family.
- The viewer has a clear starting point.