Mastery: your playbook

Your mastery artifact is a campaign evidence pack: source brief, claim ledger, variants, hypothesis, review sign-off, and measurement plan. It should let a competent colleague repeat turn a verified meal-prep class brief into a truthful two-variant email test without inheriting unstated assumptions. Include the job card, source requirements, prompt contract, examples, rubric, privacy boundary, escalation rule, and recovery steps.

Use brief → claims → draft → review → test → learn as the spine. For every stage, name the input, action, output, owner, check, and stop condition. Include the concrete prompt:

Use only these facts: two-hour in-person class; ingredients included; participants leave with five recipes. Audience: busy cooking beginners. Draft a subject line and email under 140 words with one sign-up CTA. Do not claim savings, health outcomes, superiority, scarcity, or testimonials. Then make variant B by changing only the angle from convenience to confidence.

Then include a specimen response: Two compact emails with the same offer and CTA; each claim maps to the brief, while the changed angle is explicitly labeled as the sole test variable. Label it as an example, not a guaranteed result. Attach proof from the independent check: you must trace every factual phrase to the approved brief, check link and disclosure requirements, review accessibility and brand voice, then measure the predeclared conversion event.

Run the same playbook on a second case that differs in one meaningful way. Keep the quality bar fixed. Explain which context fields and constraints changed. If the workflow only succeeds on the memorized example, it is not mastered.

Teach the method in five minutes to someone who has not read this chapter. Ask them to identify the source of truth, the riskiest failure, and the human decision. Their answers reveal whether your playbook is explicit.

Score yourself:

1. Framing: I can reject work outside the stated job.
2. Context: I distinguish evidence, assumptions, and untrusted input.
3. Prompting: I constrain output and request inspectable artifacts.
4. Verification: I use an external check, not model confidence.
5. Safety: I enforce this boundary: never paste customer lists, personal profiles, unpublished campaign data, or sensitive targeting attributes into an unapproved model.
6. Operations: I can recover from fabricated urgency; fake statistics; multiple variables changed; vague CTA; stereotyped audience language; optimization without a hypothesis.
7. Communication: I disclose limitations and ownership clearly.

A weak score is a practice target, not a reason to pad the playbook. Generation volume is not strategy. A useful campaign has a defensible promise, a specific audience action, and a test that can teach one thing.

Package the project as design a small email campaign with a claim ledger, two controlled variants, approval record, and results template. Show the before state, constraint decisions, failed case, correction, measured result, and reflection. Remove sensitive inputs and avoid claiming impact you did not measure. Professional credibility comes from showing judgment under constraints.