Mastery: your playbook

Your mastery artifact is a four-week practice log containing baseline, prompt versions, checked outputs, time/quality measures, failures, and adoption decision. It should let a competent colleague repeat run a thirty-minute weekly practice loop that improves one real workflow without inheriting unstated assumptions. Include the job card, source requirements, prompt contract, examples, rubric, privacy boundary, escalation rule, and recovery steps.

Use choose → baseline → practice → check → reflect → repeat as the spine. For every stage, name the input, action, output, owner, check, and stop condition. Include the concrete prompt:

This week I want to improve meeting-note follow-up. Baseline: 25 minutes and occasional missed owners. Design one 30-minute practice: a sanitized sample, one constrained prompt, a checklist for owner/date/source accuracy, and a five-minute retrospective. Keep the tool fixed and change only one prompting variable.

Then include a specimen response: A bounded weekly experiment with a baseline, one controlled change, an output check, and a decision to keep, revise, or discard the technique. Label it as an example, not a guaranteed result. Attach proof from the independent check: you must compare against the baseline, verify every owner and due date against source notes, record failure cases, and repeat on a second sanitized example before adopting.

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: practice with synthetic or redacted material; keep a standing list of data that must never enter consumer tools and review vendor settings.
6. Operations: I can recover from collecting prompts without testing; changing tool and task simultaneously; counting speed while quality falls; skipping reflection; automating before understanding.
7. Communication: I disclose limitations and ownership clearly.

A weak score is a practice target, not a reason to pad the playbook. Consistency beats novelty. One checked experiment each week produces transferable judgment; browsing new tools without measuring work does not.

Package the project as complete four weekly cycles on one follow-up workflow and publish a before/after playbook with evidence. 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.