How to brief a walkthrough in one sentence

We ask for one product and one task in a sentence. It may look like a formality, but nothing predicts more reliably how fast a sample comes back, or whether the finished video is the one you wanted.

The pattern

A brief that works has three parts: the thing being operated, the task as a verb phrase, and the result that would settle the question.

[product]  +  [one task, as a verb]  +  [the result that proves it]

Briefs that worked

• "Alert me when any product drops below 20 in stock", proved when the alert arrives.
• "Restore a single file from last night's backup", proved when the restored file matches the original.
• "Invite a teammate with read-only access", proved when the teammate can see the dashboard but not the settings.
• "Connect the billing integration and issue one refund", proved when the refund appears on both sides.

Briefs that need a second round

Three kinds of brief cost a day or two while we come back with questions.

• A feature instead of a task. "Show the reporting module" has no finish line, so there is nothing to verify.
• Several tasks at once. "Set up the account, import data and build a dashboard" is three videos, and you should be the one to pick which comes first.
• A claim instead of an action. Before anyone can film "show how fast it is", it needs a number, a method and something to compare against.

What we confirm back

In one reply we confirm the scope, the access we need and the environment. Access is always a trial or a demo tenant, never production. If data has to exist before the task can run, we tell you, because seeding it is part of the run and goes in the log.

Languages

Tell us which languages you want at the same time. We write narration separately for each language instead of machine-translating it line by line, and knowing up front lets one recording serve all of them without a second run later.