Module 3 · Lesson 2 of 4

Write instructions that survive the handoff

Turn your task and constraints into a concise brief an assistant or colleague can use.

Go to the exercise

What you will leave with

A working brief with inputs, boundaries, output format and checks.

Understand

The idea behind the work

A working brief is a contract for a piece of work. Name the recipient and useful output, supply the authoritative context, describe allowed actions and define the checks. Include open questions and what to do when a required input is missing. Specific instructions are more useful than asking the model to be an expert or to do its best.

Keep the brief readable enough to review before running it. Separate stable project guidance from this task's changing details. If the assistant repeats a mistake, correct the instruction or input that caused it and inspect the next result. More wording is not automatically more clarity; contradictory constraints can make the task impossible.

Inspect a worked example

Synthetic example: brief a community page

This is a fictional teaching example, not a client result or a claim about Joseph Carroll's past work.

The event and website are fictional learning material.

The starting input

Approved title, date, venue and contact action. Goal: a mobile-friendly event information page.

Work through it

  1. Specify the audience, required content and one primary action.
  2. Request a small local page without a database or login, and name the files the builder may change.
  3. Require phone-layout and link checks; inspect deployment target and access before any publishing step.

The result

A bounded build instruction with evidence requirements and a clear finish.

A mistake to recognize

Saying ‘make it amazing’ and allowing the assistant to invent testimonials or add unnecessary services.

How to recover

Provide the actual content and explicit acceptance checks; mark missing facts as questions.

Adapt the method

What changes in your business?

The same method can serve different settings. Data, allowed actions and operational support matter more than headcount alone.

Owner-led business or small team

Keep your source and brief together so a later session can resume without guessing.

Department or growing team

Agree on one current brief and a place to record changes.

Large or complex organization

Use approved instruction storage and include the actual review and release authority.

Try it, then inspect the result

Draft the brief

Write outcome, audience, sources, allowed actions, output format, checks and stop conditions for one task. Keep it short enough for another person to review.

Create and edit the brief

Use a sample or a description you are allowed to share. Your answer stays in this browser when storage is available; export it to keep a separate copy. 0 / 6,000 characters.

Check your reasoning

Two source documents disagree about the launch date. What should a good brief require?

Inspect your own output

Check each statement after you look at your answer. These evidence checks apply to this visit; your answer and completion status can be saved.

To mark completion, write an answer, check the reasoning scenario and inspect every evidence statement. You can continue to another lesson at any time.

Self-reported completion does not certify competence. Open My AI Plan to review your saved work.

Sources and further practice

The lesson is Carroll Consulting's teaching synthesis. These sources support the underlying capabilities and concepts; check the current product, plan and configuration before applying them.

You can move between lessons freely. Revisit the checks whenever your answer, evidence or business context changes.