Chapter 7 — From Hand-Built to AI-Directed: What Changes, What Doesn’t

Further reading

Books, articles, and papers beyond the book’s own bibliography (Appendix C, updated in errata) on the analyst-side experience of shifting from hand-builder to AI-director.

• Mollick, E. (2024). Co-Intelligence: Living and Working with AI. Portfolio. The most useful single volume on how a knowledge worker should organize their working relationship with generative AI without abdicating judgment. Mollick’s «jagged frontier» framing — that the model is superhuman at some tasks and dangerously wrong at adjacent ones — is the exact reason the readiness gate is not optional. Newsletter with weekly essays at oneusefulthing.org.
• Dell’Acqua, F., et al. (2023). «Navigating the Jagged Technological Frontier: Field Experimental Evidence of the Effects of AI on Knowledge Worker Productivity and Quality.» Harvard Business School Working Paper 24-013. The empirical study behind Mollick’s framing. Consultants using GPT-4 outperformed non-users on tasks inside the frontier by ~40% and underperformed on tasks outside it — the direct evidence for why the readiness gate’s «can I review the output?» question matters more than the «can I generate output?» question. Free PDF at hbs.edu/faculty/Pages/item.aspx?num=64700.
• Kahneman, D. (2011). Thinking, Fast and Slow. Farrar, Straus and Giroux. The System 1 / System 2 framing that underlies the «verification cost, tacit vs explicit» distinction. Hand-building embeds verification in System 1 (fast, unconscious, embedded in the act of building); AI-directed work moves it to System 2 (slow, deliberate, a scheduled review pass). Chapters 1–3 for the framing, Chapter 9 («Answering an Easier Question») for the failure mode Ch 7’s hinge is designed to prevent.
• Kozyrkov, C. — Decision Intelligence writing. Kozyrkov (former Google Chief Decision Scientist) has written extensively on the role transition from producer to reviewer — the exact shift Ch 7 names as the author-to-director contract. Her writing is short, opinionated, and operational. Medium at kozyrkov.medium.com.
• Anthropic — Prompt Engineering Guide. The vendor-neutral operational guide to structuring prompts for Claude and similar models. The «chain-of-thought» and «role-and-context» patterns are the technical scaffolding under the CSAR loop Ch 8 introduces. Free at docs.anthropic.com/en/docs/build-with-claude/prompt-engineering/overview. Microsoft’s equivalent for Copilot in Power BI lives in the vendor documentation catalogued in Resources.

Last curated: 2026-07-18. Reviewed quarterly. Suggestions welcome via the Feedback page.

Self-check quiz

Five questions on Ch 7’s hinge concepts. Answer them out loud before opening the reveal.

1. Q1. Chapter 7 introduces the «author-to-director contract» as the shift Part II depends on. State it explicitly: what changes about decision rights when AI produces the first draft?

   Show answer

   The analyst stops making every chart choice and starts briefing, critiquing, and deciding whether the draft ships. In hand-built work, the analyst is the author — every choice on screen is theirs. In AI-directed work, the analyst is the director — the AI makes the first-draft choices, the analyst names the specification (Crystallize), reviews the output against a rubric (Refine), and holds the ship-or-discard decision. The role changes; the ownership of the artifact does not. A director who accepts an undirected first cut is not directing.

2. Q2. Ch 7 organises analyst attention along the «cognitive concern ladder.» Name the rungs bottom-to-top and describe what AI direction lets the analyst offload.

   Show answer

   Physical → Signal → Data → Information → Knowledge/domain → Strategic. Physical is the mechanics of the artifact (typing, clicking, wiring). Signal is whether the encoding preserves the numbers. Data is the field set, grain, filtering. Information is whether a cold reader extracts the takeaway. Knowledge/domain is whether the takeaway matches what you know about the business. Strategic is whether this is the right chart to be building at all. AI absorbs the lower rungs (physical, signal, and much of data) — but only for analysts who built them by hand first, because reviewing what you offload is a rung-4-and-up activity that presupposes rung-1-through-3 fluency.

3. Q3. Ch 7 names «verification cost, tacit vs explicit» as a load-bearing concept. What is the distinction, and where does the verification cost go when the analyst moves from hand-built to AI-directed?

   Show answer

   Tacit verification cost is the cost that hand-building embedded silently in the act of building — the analyst notices the wrong axis mid-drag, the color choice fails a mental grayscale check while placing the swatch. Explicit verification cost is a scheduled review pass on the finished AI-generated output. The cost does not disappear when the analyst moves to AI-directed work — it moves above the line. Same total cost, different location. The analyst who treats AI as «free» because generation is fast has missed that verification moved, not vanished. Skipping it produces plausible-looking output (Ch 1).

4. Q4. Ch 7 gates Part II entry with a six-check readiness pass. What are the six checks, and what does failing one specifically imply?

   Show answer

   The six checks are Context, Story, Chart selection, Focus, Color and accessibility, and Defensibility. Context through Color and accessibility reload Chapters 2–6. Defensibility is the capstone: can you anticipate executive questions and name the data move that answers each? The pass rule is six out of six. A failed check sends the reader back to the named Part I practice before Part II.

5. Q5. Ch 7 introduces the «Copilot-ready capacity» as a practical prerequisite for Part II. What does the term mean, and what specifically has to be true for Part II’s exercises to run?

   Show answer

   An administrative prerequisite: paid Fabric F2+ SKU or Power BI Premium P1+ SKU with Copilot enabled in the tenant. A Power BI Free workspace or a trial-capacity workspace cannot run Copilot. A trial workspace can consume Copilot if it is assigned to a paid Fabric Copilot capacity, but a trial capacity by itself cannot host the feature. Named as a check because it is better to find out on page 145 than mid-Chapter-9 when the reader is trying to reproduce a Copilot Report Generation walk-through and the button is grayed out.

Nadia’s Q3 revenue-by-region, up close

The chart on the left is what Copilot produced Wednesday morning from Nadia’s off-hand prompt: a sorted bar of Q3 revenue by region with a descriptive title, no plan reference, and no per-region variance callout. The chart on the right is the one Nadia has hand-built quarterly for two years and the one her CFO trusts. The quarter aggregate ($28.4M) lands exactly on plan on both charts — and only the right chart makes visible the NA -5.3% miss that is the actual story of the quarter.

1. Sort order carries the argument. Alphabetical (APAC, EMEA, LATAM, NA) is the default output shape. Sorting by plan-variance ascending puts the region that missed plan in the eye’s first landing zone — the position the CFO’s attention lands on first when the chart appears on screen.
2. Plan reference is the load-bearing comparison. Without the per-region plan tick, the CFO reads the chart as «NA is our largest region» and moves on. With the plan tick, the CFO reads the chart as «NA is behind plan by 5.3% while every other region beat theirs» — a fundamentally different conclusion from the same numbers.
3. Accent color is a decision, not a default. A single accent color on the NA bar tells the CFO where to look; uniform brand color tells the CFO to look everywhere and read carefully. The accent is the visual expression of the Big Idea in the title.
4. The title asserts the claim. «NA -5.3% behind plan; every other region on or ahead» is the sentence the CFO would need to say in the meeting. The chart’s job is to make that sentence visually inspectable in five seconds. «Q3 revenue by region» is the sentence the raw table already told you; a chart that repeats it does no additional work.

Why the AI first draft is not defensible. The chart on the left scored red on Context (BRD asked plan-tracking; chart shows region comparison) and Story (viewer cannot summarize the argument in one sentence) on the five-principle rubric — the diagnosis Fig 7.3 walks through step by step. The rubric is what let Nadia name the defects out loud and hand-build the corrected chart in the same twenty minutes. The chart on the right passes the same rubric on all five checks.

Inspect the numbers. The four-region dataset with plan and actual for each region is available as a flat CSV so you can rebuild either chart in your own tool. Download nadia-q3-region.csv · Dataset README and schema.

Try this activity — run the six-check readiness gate on yourself

This activity is the one Ch 7 explicitly asks the reader to run before Part II. Total time: 30–45 minutes; can be done on paper.

1. Print or open the readiness rubric. Score the six checks below. Each check requires evidence from your own recent work.

   • Context: Write a six-field BRD for a recent chart in fifteen minutes or less.
   • Story: State a recent chart’s Big Idea and have a colleague read the same takeaway cold.
   • Chart selection: Classify your last three charts among the five families and defend each against one alternative.
   • Focus: Remove elements from a recent chart until the next removal would damage the takeaway.
   • Color and accessibility: Run a recent color-coded chart through a CVD simulator and explain whether the encoding survives.
   • Defensibility: Name three questions an executive might ask about a shipped chart and the data move that answers each.

2. Check the unscored administrative prerequisite. Confirm you have access to a Copilot-enabled workspace where you can run the Part II exercises. If not, use Power BI to choose an access path; do not count access as one of the six scored checks.

3. Score honestly. The pass rule is six out of six:

   • 6 Pass: proceed to Chapter 8.
   • Any Partial or Fail: return to the named Part I practice and rerun it on recent work before proceeding.

4. Reflect (three prompts). Write one sentence in response to each:

   1. Which check was hardest, and does the difficulty match what you would have predicted before the exercise?
   2. Where is the biggest gap between what you thought you knew and what you can recall?
   3. What one Part I concept would most change how you review Copilot output tomorrow?

The readiness gate is not a test to pass under pressure; it is a diagnostic. Failing a check now saves a much larger cost later — a shipped Copilot artifact whose defects the analyst could not name.

Related site resources

• Practice-on-your-own hints: short diagnostic hints for the chapter's independent problems; complete answers are in Appendix G of the Practice Workbook.
• Power BI: Power BI account setup, including the Fabric-trial path to Copilot-ready capacity if your tenant does not have one.
• Chapter 1, 2, 3, 4, 5, 6: the Part I chapter companion pages that supply evidence for the readiness checks.
• Chapter 8 companion: the next chapter — introduces the CSAR loop, the operational protocol Part II rests on.
• Prompt Library: eleven canonical prompt packages for the Part II workflow.
• Appendix E — BRD Field Guide: if the BRD check was where you scored Partial, the template plus completed exemplars are the fastest way to close the gap.

Cited in the book

Chapter 7’s bibliography lives in the book’s Appendix C (living version in errata). The chapter’s operative references:

• The Verification Habit (sister book). Chapter 9 introduces the cognitive concern ladder in its general form; Ch 7 applies it to visualization work.
• Kahneman, D. (2011). Thinking, Fast and Slow. Farrar, Straus and Giroux. The System 1 / System 2 framing underlying the tacit-vs-explicit verification-cost distinction.