Who this is for: Product teams writing a precise visual brief for a software update.
What to prepare
- Approved participant criteria.
- Current working scope and meaningful limits.
- A verified application or request destination.
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Create a 30-second invitation sequence for an illustrative early-access feature in a fictional research tool. The task is testing a draft note-grouping workflow with supplied text examples. Open with the task, then show a labeled concept or verified product screen according to the available evidence. State the approved participant criteria clearly and reserve a readable beat for the text-only scope and required human review. Show the actual request action, describing it as an application or access request rather than immediate entry. Do not invent limited seat counts, acceptance deadlines or selection guarantees. Avoid presenting hypothetical generated groups as tested results. End with what applicants should expect only to the extent the team has approved it, plus the correct destination. Keep the tone specific and useful rather than urgent.
Make it your own
- Participant fit
- Supply explicit criteria and exclusions.
- Test scope
- State the working task and known boundaries.
- Request wording
- Match the destination's actual action and acceptance process.
Separate fit from access
A viewer may fit the test but still need approval. Write two separate lines: who the test is intended for and how access is requested. If selection criteria are not public, do not invent them to make the invitation feel complete.
Adapt when only concept imagery exists
Use clearly labeled conceptual scenes and explain the proposed task. Do not simulate a finished output and call it a current result. A verified working screen can carry a stronger demonstration, but it still needs the same eligibility boundary.
Repair an impression of guaranteed entry
Replace “Start using it now” with the approved request action. Remove success checkmarks that imply admission after form submission unless that is the actual process. Keep any follow-up timing within the team's confirmed communication policy.
Review checklist
- Eligibility and acceptance are separate statements.
- Limits are readable before the invitation.
- The request destination matches the promised action.
- No invented scarcity or admission guarantee appears.