Mastery: your playbook

Your mastery artifact is a presentation packet containing the brief, title spine, source ledger, accessible visuals, timed notes, and Q&A prep. It should let a competent colleague repeat create a seven-minute decision deck for a six-week customer-support pilot without inheriting unstated assumptions. Include the job card, source requirements, prompt contract, examples, rubric, privacy boundary, escalation rule, and recovery steps.

Use brief → spine → evidence → design → rehearse → decide as the spine. For every stage, name the input, action, output, owner, check, and stop condition. Include the concrete prompt:

Create a six-slide outline for leaders deciding whether to assign two staff to a six-week support pilot. Use only my evidence. Each title must be a complete takeaway sentence; add 2–3 support bullets, a suggested visual, and speaker notes under 40 words. Mark missing evidence; never invent metrics or quotes.

Then include a specimen response: A title-only story that moves from current support delay to bounded pilot, measurement plan, risk controls, and a final staffing decision. Label it as an example, not a guaranteed result. Attach proof from the independent check: you must read titles alone for logical flow, trace every number to a source, inspect chart axes, rehearse to seven minutes, and test contrast, font size, and alt text.

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: remove confidential strategy, customer names, internal forecasts, and unreleased product information before using an external tool.
6. Operations: I can recover from decorating before structuring; invented metrics; slide titles that name topics rather than conclusions; overcrowded notes; unlabeled generated imagery.
7. Communication: I disclose limitations and ownership clearly.

A weak score is a practice target, not a reason to pad the playbook. A deck is a guided argument, not prose divided into rectangles. If the titles alone do not tell the story, visual polish will not rescue it.

Package the project as build and rehearse a six-slide pilot approval deck with an evidence appendix and anticipated-question sheet. 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.