Who this is for: Teams demonstrating boards and status workflows.
What to prepare
- Board state sequence
- Transition evidence
- Role requirements
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Plan a 30-second illustrative workflow for sample card K-014, “Review sample packaging.” Use supplied board states with columns Draft, In review and Approved only if those are the verified labels. Start with K-014 in Draft and hold its identifier and title. Show the actual action that moves it to In review; use drag motion only when dragging is supported and evidenced. Preserve the card’s identity, owner and unrelated values. Identify the reviewer before the approval action if permissions matter. End with K-014 visibly in Approved and any required confirmation complete. Callouts should explain “Send for review” and “Approval recorded,” not merely repeat column names. Mark sample data clearly. Do not imply moving a card automatically performs an external publication or approval that the product does not support.
Make it your own
- Card identity
- Keep identifier and title constant.
- Statuses
- Use exact product labels and verified allowed transitions.
- Actor
- Identify any role required for a consequential change.
Confirm transition rules
Supply each starting and resulting board state, plus the actual trigger. Some workflows use a status menu, some require review and others permit dragging. The brief must follow the observed rule instead of choosing the most cinematic action.
Adapt the board
For a crowded board, crop to the relevant columns while retaining their headings. Keep nearby sample cards stationary unless the real product reorders them. For two statuses, use the saved time to hold on the result rather than adding another card.
Fix identity loss
If the card changes color, size and title together, restore stable text and explain any legitimate changes separately. If the final column is off-screen, establish the board location before the move. A card flying into empty space is not a readable workflow.
Review checklist
- The same card is traceable throughout.
- Movement matches actual controls.
- Final status is not overstated as an external outcome.