# Rewrite memo — ferguson-data **Word count (body):** ~1,000 words · **Hero variant:** V2D · **Anonymisation:** Tier A --- ## 1. The story I found The case's argument is present but slightly obscured by its framing. The existing case leads with the context (back office that couldn't keep up) and the reframe (data as a service), but the most distinctive moment — the 275-step map as the first time anyone had seen the system end-to-end — doesn't get enough weight. That moment is where the service design value is most concrete: visibility changed what was possible to decide, and the decisions that followed are what produced the roadmap. The through-line a reviewer should remember: this looks like a data-strategy engagement. It isn't. It's a service design engagement where the service was invisible to everyone running it. Making it visible is the case's argument. The secondary argument — the roadmap funded itself, and the team came out able to advocate for their own transformation — is present in the existing case's closing section and is the case's strongest outcome statement. The rewrite promotes it to the scaling section. **Two unresolved questions from the source material that affect how the case reads:** 1. The "data as a service" reframe — did Whitney bring this framing to the engagement, or was it Harmonic's standard approach for data-strategy engagements? If it was a Harmonic house frame she applied, the first-person "we started here" framing is accurate. If she originated it for this engagement, the InsightCallout and pull-quote language ("The bottleneck isn't the tool. It's that no one in the company sees product data as a service") can be attributed more specifically to her. This question determines whether Chapter 02 is framed as "what I brought" or "what we found." 2. No scene from the work. The existing case has no specific moment — no workshop disagreement, no map-on-the-wall reaction, no vendor or sales-rep observation that re-pointed the engagement. Without one, the case stays methodology-as-march. A scene would also unlock a pull-quote from a named source, which both PullQuote blocks currently lack (both are Whitney's own voice, unattributed). --- ## 2. What I kept - **"The bottleneck isn't the tool."** The case's clearest argument sentence — kept as a pull-quote candidate in Chapter 01 or as the argument paragraph's closing line. - **The twelve-role / 275-step specificity.** Kept in Chapter 03; these numbers are the case's credibility anchors. - **The two-overlapping-workflows finding.** Kept in Chapter 03 as the first concrete cost-out — it shows the map produced immediate decisions, not just future planning material. - **The 290+ capability count with its framing** ("not a backlog — the size of the actual transformation, named so the org could plan against it instead of underestimating it"). Kept verbatim. - **The "didn't need a consultant to explain their situation" closing.** Kept in the scaling section — it's the case's most specific articulation of what the engagement produced for the team. --- ## 3. What I cut and why - **"What I need from you"** scaffolding section. Deleted — placeholder text from visual-director agent. - **The open-content questions list at the bottom of the existing case.** These are carried into the memo and asset-needs instead of living in the MDX. - **The BlueprintSlice component full content** (all row-by-row cells). In the rewrite this is replaced by a Placeholder pointing to a cropped visual export. The component's content is appropriate for the live site's interactive rendering; in the MDX source it reads as over-specified. - **The explicit "InsightCallout" for the reframe.** The reframe content is now the body of Chapter 02 rather than a boxed callout. The callout worked in the existing case because the case was structured around phase labels; the rewrite's chapter structure carries the reframe without needing the callout to signal it. --- ## 4. What I added - **Argument paragraph.** The existing case opened with a context paragraph and then a standalone reframe section. The rewrite opens with a 100-word thesis that names both the surface story (tooling) and the actual story (service visibility) before the backstory. - **Formally named reframe section.** Promoted from an InsightCallout mid-case to its own named section. - **Formally named scaling section.** "A roadmap that funded itself" was the closing section in the original; renamed and framed as the scaling argument (what the team could do after the engagement ended). - **V2D hero with spine.** The case's through-line is a sequence: can't keep up → reframe → map → blueprint → funded itself. The spine makes this visible in the hero. --- ## 5. Hero variant choice: V2D (spine-led) "The system nobody had ever seen end-to-end" is a strong title, but the case's argument is a sequence — each chapter represents a step from burning out under a misdiagnosed problem to having the language and artifacts to fund a transformation. That sequence benefits from being visible in the hero as a spine. V2D reveals the through-line; V2B would put the title in the hero position without showing how the case moves from diagnosis to outcome. --- ## 6. Open questions for Whitney 1. **Year, role, team, timeline.** These are rendered as "CONFIRM" in the frontmatter because the source material lists them as TBD. Whitney needs to confirm: the exact engagement dates (August 2022 – January 2023 is the existing case's timeline), her specific role title (source says "mid-level, part-time"), and the Harmonic team composition before the metadata strip can be finalized. 2. **"Data as a service" reframe ownership.** Did Whitney originate this framing for the Ferguson engagement, or was it Harmonic's standard frame for data-strategy work? The answer determines whether Chapter 02 reads as "what I brought" or "what we found" — and whether the pull-quote can be attributed to her specifically. 3. **One scene from the work.** The critic flagged this in the original. A workshop disagreement, a moment a map on the wall changed someone's mind, a vendor or sales-rep observation that redirected the engagement — any one of these would make the case demonstrably more specific and unlock a second pull-quote from a named source.