# Asset needs — ferguson-data --- ## Images ### 1. "That's a Job for Data" workshop board (Chapter 01) - **What it is:** Workshop synthesis board with twelve dotted-cloud groupings by department (Strategic Development, Legal, Technology, Supply Chain, etc.), each containing rows of stickies naming data jobs. - **Where it lives:** `ferguson-data-jobs.jpg` in the site repo's public/images folder. Already cleared for use. - **Why the rewrite needs it:** Chapter 01 introduces the service-vs-database reframe. This board shows the before-state — every function doing its own version of data work, separately — which sets up the service-design argument. - **Fallback:** Already available — use as-is. ### 2. "Data Types" enterprise diagram (Chapter 03) - **What it is:** Large purple bubbles representing enterprise data domains (Vendor / Product / Customer / Sales / Pricing / Marketing etc.) with dependencies between them and specific systems tagged. - **Where it lives:** `ferguson-data-types.jpg` in the site repo's public/images folder. - **Why the rewrite needs it:** Chapter 03 describes the twelve-role, 275-step mapping work. This diagram shows the enterprise data architecture the map was surfacing — it grounds the "nobody had seen it end-to-end" claim with a visual that looks like a genuinely complex system. - **Fallback:** Already available — use as-is. ### 3. Future-state blueprint slice (Chapter 04) - **What it is:** A cropped slice of the future-state blueprint showing the supplier-onboarding flow, with swim lanes across roles and at least one orange "big rock" unresolved question visible. - **Where it likely exists:** The `` component in the live MDX renders this as an interactive table. A static export from Miro/Lucid is the primary source; alternatively, a screenshot of the rendered component is an acceptable substitute for the rewrite preview. - **Why the rewrite needs it:** Chapter 04 makes the case that the blueprint was honest about unresolved questions — the big rock visual is the evidence. - **Fallback:** A screenshot of the `` component from the live site. Or a crop from the scenarios storyboard (`ferguson-data-scenarios.jpg` in the site repo) showing the future-state work in progress. ### 4. Evolution map / four-year roadmap (Scaling) - **What it is:** Either the evolution map (capabilities backcasted across three time horizons) or a presentation-grade rendering of the four-year phased roadmap — the artifact that went into the funding conversation. - **Where it likely exists:** Miro/Lucid export; the raw-case-material/ferguson-data/ folder. The existing case's "What I need from you" section flagged this as item 4 in the asset priority list. - **Why the rewrite needs it:** The scaling section argues the roadmap funded itself. The visual needs to show the roadmap as a business artifact — not a process diagram, but something that reads as a plan a leadership team could evaluate. - **Fallback:** A caption-only treatment: "Four-year phased roadmap — 290+ capabilities sequenced across three horizons. Full artifact under NDA." This is the weakest fallback but honest if the export isn't available. --- ## Pull quotes ### Needed: a participant voice from the engagement Both pull-quote slots in the existing case use Whitney's own voice (unattributed). The rewrite preserves the "bottleneck isn't the tool" framing as a pull-quote candidate, but a participant voice — from a vendor, a sales rep, a product-data team member, or an Allied stakeholder — would substantially strengthen the case's evidential weight. **Source to check:** Interview notes or workshop chat transcripts in `raw-case-material/ferguson-data/`. Any reaction from a participant to the 275-step map, the reframe, or the evolution map would serve. --- ## What Whitney needs to confirm 1. **Year, role, team, timeline.** Confirm: (a) engagement dates — August 2022 – January 2023 or correct range; (b) Whitney's role title at the time; (c) Harmonic team composition; (d) Ferguson team counterparts if any are name-able. 2. **Confidentiality level.** The existing case uses Ferguson's name, vendor counts (tens of thousands), product counts (hundreds of thousands), capability counts (290+), and team composition (twelve roles). Confirm these are all cleared for the rewrite preview. 3. **"Data as a service" reframe attribution.** Is this framing Whitney's original contribution to this engagement, or Harmonic's standard data-strategy frame? The answer affects the chapter 02 language. 4. **One scene from the work.** If any notes from a workshop session, a specific moment where the map changed someone's mind, or a participant reaction to the capability count are available, even a paraphrase would substantially improve the case.