Mastery: your playbook

Your mastery artifact is a formula test card containing schema, formula, expected rows, edge cases, and a safe-fill checklist. It should let a competent colleague repeat build and validate a June regional-revenue formula in Excel 365 without inheriting unstated assumptions. Include the job card, source requirements, prompt contract, examples, rubric, privacy boundary, escalation rule, and recovery steps.

Use describe → draft → test → explain → fill as the spine. For every stage, name the input, action, output, owner, check, and stop condition. Include the concrete prompt:

Excel 365, comma separators. A=Date, B=Customer, C=Region, D=Revenue; F2 contains a region. In G2, total D where C=F2 and A is in June 2026. Give one formula, explain every condition, and provide normal, boundary, and blank/error tests. Do not invent columns.

Then include a specimen response: A SUMIFS formula using >=DATE(2026,6,1) and <DATE(2026,7,1), with an explanation that the exclusive upper bound includes every June timestamp. Label it as an example, not a guaranteed result. Attach proof from the independent check: you must calculate a tiny hand-checked table, test June 1 and June 30, inspect dates stored as text, confirm absolute references, and compare the total with a filtered sum.

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: do not upload payroll, customer records, account numbers, hidden sheets, or an entire confidential workbook; substitute synthetic rows.
6. Operations: I can recover from wrong locale separators; text dates; shifted ranges; hidden filters; formulas filled down with relative criteria cells.
7. Communication: I disclose limitations and ownership clearly.

A weak score is a practice target, not a reason to pad the playbook. Keep raw columns untouched. Use helper columns for cleanup so every transformation is reversible, and never accept a formula whose result you cannot reproduce on five known rows.

Package the project as produce a tested regional monthly-summary sheet with helper checks and a short data dictionary. 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.

Transfer the method to an XLOOKUP that assigns account tiers from a reference table. Create synthetic rows for an exact match, a missing account, a duplicated key, and an ID stored as text. Require a formula that returns an explicit review label rather than hiding failure with an empty string. Compare results with a manual lookup, inspect locked ranges, and fill only five rows before scaling. Record whether duplicate keys are a formula problem or a source-data problem. This exercise demonstrates that mastery includes diagnosing workbook structure and data types, not merely obtaining syntactically valid formulas.