Who this is for: Product marketers and motion designers briefing a specific software update.
What to prepare
- The approved source and destination field names.
- Mapping rules, direction and trigger.
- Matching source and destination evidence for one example object.
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Plan a 30-second update sequence for a fictional connection from a request tracker to a planning board. The new supported field is Due date; the existing title transfer is context only. Begin with one labeled illustrative request and hold its title and due date together. Show a simple field map, Request due date to Board due date, using the approved transformation rule. Then show the actual transfer trigger and any verified pending state. End on the matching board item with the destination date readable. Keep the same example identifier or title throughout. Do not imply reverse synchronization, continuous updates or automatic connection setup. If an empty source date has a documented behavior, state it briefly; otherwise leave that case outside the demonstration. Use a restrained connector graphic to explain direction, but make destination inspection the proof. Close with the supported scope and current release availability.
Make it your own
- New field
- Name the exact addition without expanding to the whole object.
- Transformation rule
- Supply format, timezone or empty-value handling where relevant.
- Trigger and direction
- State manual or automatic behavior only as verified.
Separate the addition from the existing path
Mark the previously supported fields as context and visually emphasize only the new one. This prevents the announcement from implying that the entire integration is new or that every field now transfers.
Adapt the value without changing the rule
Choose an example that makes the mapping inspectable. A date with ambiguous formatting may need a clear label; a text field may need a truncation limit if the owner confirms one. Do not invent a transformation simply to make the source and destination look cleaner.
Repair a handoff without proof
A line arriving at the destination logo is not a confirmed transfer. Request the matching destination state or label the graphic as conceptual. If the destination value differs, explain the approved transformation or correct the asset rather than hiding the discrepancy.
Review checklist
- The new field is distinct from existing support.
- One object remains traceable across both systems.
- Direction and trigger match the approved behavior.
- The destination value provides the proof moment.