# Rewrite memo — allied **Word count (body):** ~1,050 words · **Hero variant:** V2D · **Anonymisation:** Tier A --- ## 1. The story I found The case has a clear two-layer argument: the surface reframe (dealers weren't the bottleneck — providers were) and the deeper reframe (Allied was treating a multi-actor service as a product it sold, which meant it couldn't see the most important failure modes in its own service). Both are present in the existing case. The existing case calls out both reframes explicitly. What it doesn't do is give them enough structural weight — they're each an InsightCallout in the middle of a longer narrative rather than the organizing principle the case is built around. The through-line a reviewer should remember: the work changed what Allied could see about its own service. The blueprint, the capability inventory, the evolution map — these are all outputs of a process whose actual deliverable was a change in the team's model of what they were running. That's the senior-IC argument. The critical gap: **Whitney's specific Phase 2 contribution is not documented in any source material I have access to.** The critic flagged this as the single biggest issue in the case. The rewrite writes around the gap by focusing on what the work produced (well-documented) rather than which specific pieces Whitney owned (not documented). Before this case publishes, Whitney needs to name two or three specific things she designed, facilitated, or decided in Phase 2. See asset-needs.md. --- ## 2. What I kept - **The four-actor structure** (lender / dealer / provider / Allied) — the case's clearest early orientation device. Kept in Chapter 01. - **The two-misalignment finding from Phase 1** — inside vs. outside views of "the customer"; product vs. service framing. Kept in Chapter 02; essential context for why Phase 2 was designed the way it was. - **The dealer/provider bottleneck reframe** — the working hypothesis was wrong about who was slowing things down. Kept as the Chapter 02 closer; it's the case's first-layer argument. - **The four-artifact description** (blueprint, capability inventory, evolution map, moment briefs). Kept in Chapter 03 with compression. - **The "big rocks" feature of the blueprint** — unresolved questions staying visible rather than being smoothed over. Kept as a standalone beat; it's the case's most distinctive design decision. - **"The blueprint told the truth about what wasn't decided yet, and named who needed to decide it."** Kept verbatim; this is the case's strongest sentence and earns the scaling section's argument. - **The product-to-service vocabulary shift in the retrospective.** Kept in Chapter 04 but tightened — the original paragraph attributed the shift to "specific facilitation choices," which the critic flagged as overclaiming. The rewrite makes a narrower claim: the shift happened across multiple sessions through the blueprint work itself. - **The second Allied engagement commission.** Kept in the scaling section as the case's outcome signal. --- ## 3. What I cut and why - **"What I'm still thinking about."** The final section on "one Allied leader who took the position that service design shouldn't be used for strategy" — this is a real tension and worth carrying, but the case isn't the right place for it. It reads as pre-emptive defensiveness against a specific objection. If Whitney wants to address the service-design-as-strategy question, the About page or a short-form piece is the better home. - **"What Happened Next"** as a standalone section. The activation phase and second engagement details are real outcomes; compressed into the scaling section without their own dedicated real estate. - **The extensive blueprint swim-lane detail.** The live MDX has a `` component with full row-by-row content. In the rewrite, the blueprint is described structurally and the Status Milestone row is called out as the distinctive feature, but the full blow-by-blow is replaced by a Placeholder for a cropped visual. The visual carries more weight here than the prose description. - **The facility-state storyboard details.** The lender-dashboard and funds-status storyboard descriptions were useful in the original for conveying what the future state looked like. In the rewrite, these are referenced in the scaling section as the activation-phase foundation rather than described in detail — the visual Placeholder should carry this. --- ## 4. What I added - **Argument paragraph.** The existing case opened with "A pilot that grew faster than the process behind it." The rewrite opens with a thesis that names both the surface reframe (dealer problem → coordination problem) and the deeper reframe (product → service), so the reader knows what the case is about before investing in the backstory. - **Formally named reframe section.** The two reframes were both InsightCallouts in the original. The rewrite promotes the deeper one (model, not just bottleneck) to its own section. - **Formally named scaling section.** The "big rocks" observation and the second engagement commission are brought together into a scaling section that makes an argument: the blueprint's honesty about what was undecided is what made the next phase of work possible. - **V2D hero.** The case's through-line reads as a sequence (working hypothesis → investigation → design → shift in mental model), which benefits from the spine being visible in the hero. --- ## 5. Hero variant choice: V2D (spine-led) The case moves through four distinct acts: the compliance deadline creating the brief; the research revealing the wrong hypothesis; the collaborative future-state design; and the organizational framing shift. Each chapter represents a different level of understanding Allied reached about their own service. That progression — from "fix the dealer problem" to "design a multi-actor service" — is the case's through-line, and it benefits from being visible as a sequence in the hero rather than collapsed into a title. --- ## 6. Open questions for Whitney 1. **Whitney's specific Phase 2 contribution.** This is the case's single biggest publishing gap. Before the rewrite can be published, Whitney needs to name: (a) which Phase 2 workshops she facilitated vs. co-facilitated vs. attended; (b) which artifacts she owned end-to-end vs. contributed to; (c) at least one specific design decision in the blueprint or evolution map that was hers. The case currently describes the Phase 2 work accurately but reads as if the work happened without an identified designer — which is exactly the gap a hiring manager will notice. 2. **The retrospective line.** The scaling section references "the team's project retrospective named 'the client started to think of RefundPlus as a service, not a product' as one of the engagement's outcomes." Is this line quotable directly? If so, it should be a pull-quote rather than paraphrase — it's the case's best evidence for the product-to-service shift. 3. **Second engagement name.** The case references a "second Allied engagement commissioned later in the year, building on the methods this project established." Can this second engagement be named or described? Even one sentence about what it addressed would strengthen the scaling section's argument that the methods — not just the deliverables — were what Allied wanted back.