Collaboration feature demo brief

The working approach

Establish the shared object.
Make a comment or assignment.
Verify the receiving state.

A concrete example

Audience: team managers. Target: 40 seconds. Use prepared demo identities and show an assignment or comment appearing in the shared task.

Before recording this scenario, write down what the starting screen contains and what should be different at the end. This gives the reviewer an observable result to check, rather than asking them to approve a general impression.

The mistake to avoid

Avoid sending real invitations solely for a promotional shot.

If the source cannot support the intended message, narrow the claim or capture the missing evidence. A transition, caption or voiceover can explain a real change; it should not manufacture one.

Copy and adapt the brief

Replace the bracketed fields before using this brief. The scenario is illustrative; keep only the actions your product actually supports.

EDITABLE PRODUCTION BRIEF

Purpose: Collaboration feature demo brief.
Audience: [specify the viewer and their familiarity with the product].
Decision: [what should the viewer understand or do next?].
Approach: Collaboration is a change in shared work, not merely a list of members. Show what one person contributes and what another sees.

Required evidence:
1. Establish the shared object. Show the relevant entry state, action and completed result.
2. Make a comment or assignment. Show the relevant entry state, action and completed result.
3. Verify the receiving state. Show the relevant entry state, action and completed result.

Reference scenario: Audience: team managers. Target: 40 seconds. Use prepared demo identities and show an assignment or comment appearing in the shared task.
Avoid: Avoid sending real invitations solely for a promotional shot.

Deliverable: [duration], [format], [placement].
Use only recorded product behaviour. Preserve the full original.
Acceptance: check each claim against its visible scene, review at actual viewing size, and test the final file.

Review before delivery

Evidence: can a new viewer identify the result described in the example without being told where to look?
Reading distance: are the relevant controls and labels understandable at the intended placement size?
Continuity: does each cut preserve the relationship between the action and its result?
Accuracy: does the final caption describe the visible product state, including any limits?

Using this with Demovela

The automatic URL workflow currently supports Postraid and Adfolio. Other product scenarios on this page are production-planning examples, not compatibility claims. Adapt the brief to your own recorder or editor. Demovela preserves originals and creates separate outputs; review the resulting file before publishing.

Check the current preview scope →

Keep the workflow moving

Choose the next resource based on the decision you still need to make.

Browse the complete resource library →