Who this is for: Teams explaining the first use of a product area.
What to prepare
- Empty-state screen
- Required creation fields
- Saved object and list evidence
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Plan a 30-second illustrative demo of creating the first sample project. Start in a configured account with an empty Projects area and show its actual empty-state instruction. Activate the verified create control. Enter the fictional name “Sample launch review” and show any required consequential choices; identify other fields as prefilled only if that matches the starting state. Perform the real save action. Hold the resulting project name and identifier, then return to the project list so the viewer can find the same object again. Use “Create your first project” as task copy only when the demonstrated setup supports it. Label the data illustrative. Do not populate multiple unrelated projects in the ending or imply a full account setup was completed when the film starts in a configured account.
Make it your own
- Object type
- Use one real product object.
- Sample name
- Repeat the same fictional name after saving.
- Starting setup
- Identify which account and workspace conditions already exist.
Define what first use means
State whether the account and workspace already exist. A first object in one section is not necessarily a first-ever product session. Supply all required fields and their observed validation.
Adapt the object
Replace project with a board, list or request only after checking the real creation path. For a 15-second cut, begin with nonessential fields already filled and state that condition, while retaining the required choice and save confirmation.
Fix unearned population
If the final screen suddenly contains a complete workspace, return to the single created item. If the empty-state button opens a setup wizard, show the required steps or choose a longer sequence. Do not jump over decisions that determine the object’s type or access.
Review checklist
- The starting setup is explicit.
- Required decisions remain visible.
- The final object can be found again.