Skip to content

Guide · Work

The brief is part of the work.

Delegation fails when the requested output looks clear but the intended outcome does not. Before asking an AI assistant for a draft, write down the decision or action the draft should support.

Five fields that remove ambiguity

A useful brief can be short. Include enough context to make the task concrete, but not every document you have. Mark uncertain inputs so the assistant does not mistake assumptions for facts.

  1. Outcome: what should the reader decide or do?
  2. Context: which facts are necessary, and where did they come from?
  3. Constraints: time, audience, scope and what must not change.
  4. Deliverable: format and approximate length.
  5. Review: what you will verify before accepting the result.

A reusable example

For a founder choosing an onboarding improvement, the goal is not 'write something about onboarding'. It is to compare possible fixes and choose a test. Keep customer details anonymized unless sharing them is appropriate.

Example prompt · adapt before use

Outcome: choose one onboarding improvement to test. Context: three anonymized feedback notes below. Constraints: no new services and one week of implementation. Deliverable: compare two options in a short memo. Review: label assumptions, identify missing evidence and list what I must verify. Do not invent customer quotes or results.

Review before accepting

Check whether the response answers the original question. Then verify the underlying facts, not just the prose. Reject invented evidence and ask for a revision where the scope drifted.

Musivo's Work Advisor, CEO agent and specialist conversations give you different places to use a brief. Access depends on current product settings and your plan. A brief does not authorize spending, publishing or other external actions.

Keep exploring