# Asset needs — ferguson-cx

---

## Images

### 1. Counter Experience Principles clustering board (Chapter 01)
- **What it is:** The affinity-clustering board grouping post-its into themes (Ease, TRUST, Speed, We value you, etc.) that became the eight Counter Experience Principles.
- **Where it lives:** `ferguson-cx-principles-clustering.jpg` in the site repo's public/images folder. Already cleared for use.
- **Why the rewrite needs it:** Chapter 01 describes the principles as the rubric for every prototype evaluation. The clustering board makes the synthesis process visible before the prototypes appear.
- **Fallback:** Already available — use as-is.

### 2. Make-It-Happen concept canvas (Chapter 03)
- **What it is:** The Round Rock concept-development canvas for Make-It-Happen, showing description, backstage actions, and the Teams channel + short-pick email + flowchart architecture.
- **Where it lives:** `ferguson-cx-make-it-happen.jpeg` in the site repo's public/images folder.
- **Why the rewrite needs it:** Chapter 03 describes both prototypes. The concept canvas is the artifact evidence — it shows the prototype was designed as a system, not just improvised.
- **Fallback:** Already available. Confirm with Whitney that internal operational details (Teams channel name, Dynamics/Trilogie references) are acceptable to show.

### 3. KnockKnock concept canvas (Chapter 03)
- **What it is:** The Tamarac Cupcake Concept canvas for KnockKnock — the video doorbell system with two-way intercom, mobile device backup, and SOP for staff response.
- **Where it lives:** `ferguson-cx-knockknock.jpeg` in the site repo's public/images folder.
- **Why the rewrite needs it:** Paired with Make-It-Happen, these two canvases show the contrast: one prototype addresses information coordination, the other addresses physical presence. Together they illustrate the two-breakdown structure of the reframe.
- **Fallback:** Already available. Same clearance question as Make-It-Happen.

---

## Pull quotes

### Kevin Sills, Round Rock (Chapter 04)
- **Quote:** "It gives us a better way to look at things and help us along the process. Not telling us what to do, but helping you figure out what you want to do."
- **Attribution:** Kevin Sills, Round Rock branch lead — already in the live MDX. Confirm he's aware this may appear in a new public-facing context.

### Kevin Sills, Round Rock (Scaling)
- **Quote:** "We have gone light years ahead in our communication by not just leaving them to work it out for themselves. We've not had the conflicts that we've had before. It's created a bond with the sales force and our associates."
- **Attribution:** Kevin Sills, Round Rock branch lead — already in the live MDX. Same clearance question.

---

## What Whitney needs to confirm

1. **Design criteria source.** "Met all 5 of its design criteria" (Make-It-Happen) and "met all 7 of its design criteria" (KnockKnock) — where do these criteria come from? Are they the Counter Experience Principles applied to each prototype, or a separate criteria set? A one-sentence source attribution makes these claims much more credible.

2. **Branch name clearance.** Round Rock, TX and Tamarac, FL are named in the existing live case. Confirm this level of specificity is acceptable in the rewrite preview context.

3. **Prototype images clearance.** Both canvas images are already in the live site. Confirm they're cleared for the rewrite preview at `whitney-case-rewrites.pages.dev`.

4. **Process Timeline image.** If Whitney wants to include the 7-phase process timeline as a visual in Chapter 01, the `<ProcessTimeline>` component data from the existing MDX (phases: Monitor & Frame, Explore & Identify, Ideate & Visualize, Prototype & Envision, Experiment, Refine, Optimize) can be rendered as a static image or kept as the component when the MDX is ported to the live site. The rewrite has this as a Placeholder in Chapter 01.
