# Rewrite memo — medical **Word count (body):** ~1,190 words · **Hero variant:** V2B · **Anonymisation:** Tier B --- ## 1. The story I found The case has two arguments layered on top of each other and the existing draft doesn't cleanly separate them. The first argument is about research design inside a complex stakeholder environment: when twelve people describe five different engagements, the research has to do double duty — deliver findings and build shared understanding simultaneously. The second argument is about synthesis craft: the first version captures everything; the useful version organizes around implications. Both are present in the existing case. The rewrite separates them into distinct chapters so each argument lands clearly rather than blurring together. The through-line a reviewer should remember three weeks later: the synthesis failed twice before it worked — and the failure wasn't carelessness, it was the natural first pass at organizing research findings. The third version was shorter and did less, and it was the one that worked. That's the case's most transferable intellectual contribution. The structural gap finding (the patient sits between two providers, neither of whom owns the relationship) is the case's strategic payload. It was present in the existing case but landed in the middle of the "What the research found" section rather than being foregrounded as the culminating insight the maps were designed to expose. --- ## 2. What I kept - **"Twelve stakeholders, five different versions of the engagement"** — the strongest contextual frame in the case. Kept and promoted to Chapter 01. - **The dual-brief framing** — the product leader vs. CX leader tension. Kept; it's the design constraint that shaped the entire research approach. - **The scene-prompts distinction** — the insight that the "social meter" and "paint by numbers" quotes came from scene-prompts, not the structural arc. Kept in Chapter 02; it demonstrates research design sophistication. - **The three-synthesis arc** — "first version was a research summary, third was a design brief." Kept verbatim as the chapter's closing beat; it's the case's most quotable observation. - **"They look at the equipment provider as my extension."** Strongest structural-gap quote. Kept in Chapter 04. - **The recruiting-failure honesty** — the internal recruiter pulled, the external firm activated, the sample smaller than designed. Kept with the same candor; compressed from a full section to two honest sentences in Chapter 02. - **The workshop closing on governance** — the explicit session on how the maps would keep living after the engagement ended. Kept as the scaling section's anchor. --- ## 3. What I cut and why - **"What I led and how I led it"** (the bullet-point role list). This is defensive framing — anticipating "what did you specifically do?" by listing every line item. The rewrite answers that question by showing the work: the research design choices in Chapter 02, the synthesis decisions in Chapter 03. The bullet list is gone. One thing that does need to happen: Whitney's specific design moves in the workshop (which sessions she led vs. co-designed) need to surface somewhere, and right now they're still vague. The asset-needs document flags this. - **"Designing the provider research"** as a standalone section header. Absorbed into Chapter 02 — the research design and the dual-brief constraint belong in the same chapter. - **"Synthesis as craft"** as a standalone section. Renamed Chapter 03 ("The third synthesis was the one that worked") and promoted — the synthesis story is the case's most distinctive beat and deserved a more direct header. - **"Three things that traveled with me out of this engagement."** Lessons-learned framing. The substantive content (synthesis is iterated; group sessions surface intent, one-to-ones surface the gaps; reading the business is design work) is real, but it reads as personal reflection rather than case argument. The synthesis lesson is absorbed into the close of Chapter 03. The "reading the business" framing belongs in the About page, not the case. - **"What the work was set up to do next"** as a standalone section. The NDA-limited handoff paragraph is compressed to two sentences in the scaling section and the essential fact (discovery streams handed to product and CX) is preserved. --- ## 4. What I added - **The argument paragraph.** The existing case opened with a StatRow and then "In the first two weeks, twelve stakeholders described five different engagements." The rewrite opens with a 100-word argument paragraph that names both the dual-brief challenge and the structural finding before the reader has committed to the case. - **A formally named reframe section.** The gap between "map the provider experience" and "expose a structural gap neither provider owns" was present in the existing case as a finding, not as a named reframe. The rewrite makes it explicit. - **A formally named scaling section.** The existing case closed with "What the work was set up to do next" — an NDA-hedged summary of the handoff. The rewrite elevates the maps-as-infrastructure design and the workshop's governance framing as the case's scaling story. - **V2B hero.** The case title ("When the deliverable had to do the job the organization wasn't ready to do yet") is strong enough to carry the hero position. The sub-banner names the displacement in one sentence. --- ## 5. Hero variant choice: V2B (typography-led) The case's argument is a single compelling claim: the journey map had to function as decision-making infrastructure for an org that didn't yet have any. That claim is strong enough to be the hero. The case doesn't have a multi-chapter arc that benefits from a spine preview — its chapters are more parallel (stakeholder context → research design → synthesis → findings) than sequential in a way that reads as a spine. V2B lets the title carry the stance; the sidebar metadata and TOC handle navigation. --- ## 6. Open questions for Whitney 1. **Sub-journey maps.** The existing case has a Placeholder asking for sub-journey maps (prescription, setup/fitting, ongoing adherence, troubleshooting, insurance handoff). Are any of these done or partially done? The structural-gap finding in Chapter 04 would be substantially stronger with sub-journey detail showing exactly where the coordination failures happen inside the overall arc. 2. **Whitney's specific workshop design moves.** The existing case has a critic flag: "what did she design?" The rewrite needs one or two named things Whitney specifically owned in the two workshop days — specific activities, facilitation structures, or design decisions. The "off-stage roles" template is named and has a photo; that's one. What's the second? This is the case's biggest remaining gap. 3. **Anonymization level.** The client is described throughout as "a global leader in connected health and medical devices." Is the company name-able (e.g., ResMed)? If the client is actually public-name-usable, the case would benefit from Tier A treatment and the specificity would strengthen several of the findings. If it stays Tier B, the current language is appropriately descriptive.