# Rewrite memo — ai-lx

**Word count (body):** ~1,090 words · **Hero variant:** V2B · **Anonymisation:** Tier B

---

## 1. The story I found

The case's argument is present and clearly stated in the existing case: AI should be treated as a design material (with properties, constraints, and an appropriate use) rather than a destination. The rewrite's job was to tighten the case so that argument comes through more clearly — and to handle two gaps the critic flagged: the missing business-stakes paragraph and the missing "moment the reframe landed on a participant."

The through-line a reviewer should remember: this is a case about building organizational capacity — giving a 50-person team the vocabulary to have productive conversations about AI before anyone builds anything. The Four Dimensions framework is the case's most distinctive contribution; it was authored for this engagement because no existing taxonomy did the job.

The "what was hard to hold" section in the existing case is the case's best self-aware beat — the messy-middle development period where the framework wasn't connecting to operating decisions. This is preserved in Chapter 04 because it demonstrates the kind of craft judgment that senior reviewers recognize.

---

## 2. What I kept

- **The Dreyfuss analogy** (fit machines to people, not people to the machines). Kept in Chapter 02 — it's the workshop's most memorable framing and the reviewer-facing articulation of the "AI as material" principle.
- **"AI in the corner" placement as the pedagogical move.** Kept in Chapter 02 — this is the case's most concrete design decision. It's memorable and visual.
- **The Four Dimensions framework** (actors, interface, collaboration, control). Kept in full in Chapter 03, compressed from four extended sub-sections to four focused paragraphs. The framework is the case's unique contribution; it needs to be visible without the excessive sub-section structure the original used.
- **The adapted service blueprint** (human + AI actor rows). Kept in Chapter 03 as the framework's most concrete application.
- **"Paper, no laptops" with Whitney's direct quote.** Kept in Chapter 04; it's the case's best participant-voice moment (even though it's Whitney's own words, not a participant's).
- **"What was hard to hold"** — the messy-middle development period. Kept in Chapter 04 as the case's "what I'd do differently" beat. This is the most honest and senior-registering observation in the entire case.
- **Honest outcome framing.** "The internal adoption story is something we don't yet have ground truth on — and the case says so." Kept in the scaling section; it demonstrates exactly the kind of intellectual honesty the content strategy prizes over manufactured success language.

---

## 3. What I cut and why

- **"What I need from you" scaffolding section.** Deleted — placeholder text from visual-director agent.
- **The detailed six-principle listing with explanations.** In the existing case, the six AI design principles each get a one-sentence explanation. In the rewrite, the principles appear in the argument paragraph context but the full listing is compressed — six principles named, no individual explanations. A hiring manager doesn't need all six explained; they need to know they exist and are service-context-specific.
- **The `<InteractionTypesDiagram>` and `<CollaborationModelsDiagram>` components.** Replaced by Placeholders. The framework description in Chapter 03 carries the conceptual content; the diagrams are production assets for the live site, not for the MDX source.
- **The `<BlueprintSlice>` full row-by-row content.** Same reasoning as above — the adapted blueprint is described structurally in Chapter 03, and a Placeholder marks where the visual should go in the HTML build.
- **The business-stakes gap.** The critic flagged that nothing in the case names the economics of automotive retail (high-ticket purchase, credit conditions, trust cost of a misjudged AI rollout). Rather than add a paragraph I'd have to fabricate or approximate, the rewrite adds a single sentence in Chapter 01 about high-stakes, trust-sensitive industry context. The full business-stakes paragraph is a Placeholder and an open question for Whitney in the memo — she may have this context from Patrick's pre-workshop research.
- **The "observed moment of the reframe landing" gap.** This remains a Placeholder in the rewrite. The critic flagged it; the rewrite doesn't resolve it — the Patrick-photographing-a-team's-table moment referenced in the critic's feedback needs Whitney to confirm it's quotable and provide the specifics.

---

## 4. What I added

- **Argument paragraph.** The existing case opened with "The team had grown 5x. The hammer in the hallway was AI." The rewrite opens with a thesis paragraph that names the problem (AI as destination-or-contaminant) and the workshop's response (vocabulary for making the material distinction) before the backstory.
- **Formally named reframe section.** The existing case had an "InsightCallout" with the "AI is in service of value, not the other way around" thesis. The rewrite makes this a named reframe: what the workshop had to do (interrupt the instinct) vs. what the brief said (get comfortable with AI).
- **Formally named scaling section.** "Outcome" in the original was a single paragraph with the re-engagement signal. The rewrite promotes the artifacts-as-practice-tools argument to a full scaling section with honest ground-truth language.
- **Business context sentence** (Chapter 01). One sentence naming high-stakes trust-sensitive context for automotive retail, as a lightweight response to the critic's business-stakes flag. The full paragraph is a Placeholder.

---

## 5. Hero variant choice: V2B (typography-led)

"From 'we should do AI' to a working vocabulary for AI in services" is the case's argument in one phrase. It names the before state and the after state; the displacement is the vocabulary itself. V2B puts this in the hero position. The case doesn't have a sequential arc that benefits from a spine preview — it has a single organizing move (flip the question) followed by the framework that operationalizes it. V2B serves that structure better than V2D.

---

## 6. Open questions for Whitney

1. **Business stakes paragraph.** The critic flagged that nothing in the case names why an automotive retailer in 2025 would pay for this work. Whitney may have this from Patrick's pre-workshop research or from client conversations: specific stakes (credit-default backdrop, trust cost of a misjudged AI rollout on a high-ticket purchase, etc.). Even two sentences would satisfy the critic's flag. Currently a Placeholder in Chapter 01.

2. **Observed moment of reframe landing.** The critic's feedback referenced Patrick photographing a team's table mid-activity and walking them back through the value exchange as the moment the reframe took hold. Can Whitney confirm: (a) does she remember this moment? (b) is it quotable as a participant reaction? (c) if not this moment, was there another moment from the two days where the material-not-destination framing visibly landed on someone? Currently a Placeholder in Chapter 02.

3. **Anonymization check.** The client is described as "a major automotive retailer." Confirm this is the agreed anonymization level, and that no industry-specific detail in the case (lot-reads-license-plate ambient interface example, vehicle matchmaker mention) inadvertently narrows identification.
