← All resources

PRACTICAL SKILLS

A useful brief is a skill you can practise.

Five things to make clear before asking an AI tool for a draft, summary or checklist.

A practical guide

Vivi
17 November 2026

Talk about your team

A clear brief makes an AI-assisted task easier to understand and review. It also gives you a more useful way to discuss what needs improving.

Give the task a purpose.

Say what the output is for and who will use it. A note for an internal project team and a message to a customer need different context.

Provide suitable source material.

Use the information the task actually needs, through tools and processes your organisation approves. Make it clear when the answer should be limited to those sources.

Name the constraints.

Specify length, tone, format and things the draft must not claim. For example: do not invent a delivery date; flag it for confirmation instead.

Ask for uncertainty to stay visible.

If an owner, date or fact is missing, ask for it to be marked as unknown. This does not guarantee accuracy; it makes review expectations clearer.

Review against the brief.

Check facts, omissions, tone and any commitments before using the output. Keep a person accountable for the final version.

Keep it within your working arrangements.

These are practical learning notes. Your organisation’s tool approvals, information-handling rules and review responsibilities still apply.

Your next step

Start with one useful conversation.

Tell us what your team does and where AI feels useful, confusing or both. We’ll help define a sensible next step.

Talk about your team