CS-04 Equinox+ Full Case Audit — Where the Constraint Goes Quiet

Verified State: July 24, 2026

junochen.com/cs-04-equinox.html returns HTTP 200 with 154K of full case-study HTML. Password-gated by client-side JavaScript only: a localStorage check for pf_access_v1 fires after the browser has already handed over every section, every mockup reference, every metric. The full content sits in the response body before authentication even runs.

Before the audit: the teaser page carries a generic title tag and no meta description. I flagged this in the homepage audit three weeks ago. The visible content on the teaser is strong. Product Design Director, 600K+ members, 4.8★, 75 hours of research, five architecture decisions. None of that surfaces when the link is shared or previewed. Add a mandate-forward title and a one-sentence meta description.

The teaser's final CTA labels this "Case Study 03." The hero and sidebar say "04." A hiring manager who catches that will wonder what else is approximate. Fix it today.

The Governing Question

This case was correctly exempted from the trust/agentic coherence retrofit applied to your other cases. It earns its place on different terms: speed as disciplined constraint-solving, data-to-IA derivation, multi-brand architecture as a systems problem.

Here is the problem. "0 → MVP in 3 months" appears in the hero stats, the scope strip, the brief, the launch/cut lists, the outcome cards. It frames the opening. It closes the narrative. Then in the five design decisions section, the constraint vanishes. Each decision reads as an insight-to-solution pair that could have taken three months or twelve. The reader who arrived skeptical about speed finds no constraint evidence in the section where they're evaluating craft most closely.

The constraint needs to stay visible where the reader is paying the closest attention. Not louder. Visible.

Where the Case Is Strongest

Data-to-IA derivation (Criterion 2): Pass. The best analytical move in the case. Four member archetypes from 75 hours of BCG Design Ventures field research. The Attendee persona, 30% of members and highest churn risk, connects directly to the instructor-following navigation model. Members who followed at least one instructor within their first 30 days retained at nearly double the rate of those who didn't. Then the sentence that earns the whole section:

The IA was derived from data that contradicted the brief's assumptions. The click-to-focus persona interaction reinforces the structure, letting the reader see how each archetype's needs mapped to specific decisions. This reads as an analytical move, not a post-hoc rationalization. That distinction matters at Director+ evaluation.

One fix. "Juno spent a week in the data before followership became the architecture" uses third person in a case that otherwise reads as first-person leadership narrative. Rewrite to first person. Third person creates distance from the decision at the exact moment you want the reader to see you making it.

IC + manager proof (Criterion 5): Pass. IC evidence: you owned IA, the cross-brand navigation model, the design system, token architecture. Five decisions show hands-on craft reasoning. Manager evidence: you led 4 designers and 1 researcher, hired 2 designers mid-project as scope expanded, coordinated with 5 brand PMs, 2 engineering leads, 5 Creative Directors, data science, and BCG Design Ventures. The decision-rights row explicitly separates "owned" from "influenced." Most Director-level cases collapse into pure craft showcase or pure leadership narrative. The decision-rights row prevents that collapse, and the mid-project hiring detail converts differently depending on the buyer: a CPO reads operational independence, a VP Design reads function-building instinct. No changes needed.

What was cut (Criterion 4): Pass, with one upgrade available. The "Cut for MVP" block names four exclusions. The "Sequenced post-launch" block lists four deferrals. The 6-weeks/3-brands prioritization call is the strongest cut narrative on the page: you chose SoulCycle, Equinox, and Pure Yoga based on instructor-followership density in retention data. Precision Run and HeadStrong shipped in the first post-MVP update.

The upgrade. The cut list reads as a list. The 6-weeks/3-brands decision reads as a story. Convert one more cut into a story. Why were personalized recommendations cut instead of the QR club credential? Both are features. One shipped, one didn't. Personalized recommendations required a data pipeline that didn't exist yet. The QR credential required one API call and made the app a daily-carry object. Two sentences showing that reasoning would do more for the constraint narrative than the four-item list does by itself. Discipline shows in the logic behind a cut, not in the fact that cuts were made.

Where the Case Needs Work

Strategic constraint as protagonist (Criterion 1): Partial pass. The timeline and scope appear in the right places structurally. "One call under pressure" is the strongest constraint moment on the page. But the five design decisions section presents each decision as insight-to-solution with no visible relationship to the timeline. Decision 04 presents the token-based brand architecture as a systems principle:

Clean reasoning. No mention of the timeline. A reader who just processed "3 months, 5 brands" in the hero now encounters a design rationale that could belong to any timeline. The constraint disappears where the reader is evaluating the work most closely.

Add one sentence per decision that names how the timeline shaped that specific choice. Not a paragraph. One sentence. Something like: "With 3 months to ship, we chose token-driven brand expression over bespoke screens per brand, trading visual ceiling for deployment speed." The constraint should be visible in every section, not just the bookends.

Multi-brand architecture tradeoffs (Criterion 3): Partial pass. Decision 04 states the systems principle clearly. Navigation, scheduling, and account infrastructure are shared. Color, typography, photography, motion, and class-card expression are variable, defined per brand by token architecture. The principle is sound. But where did it break?

Name one concrete tradeoff. One moment where the token system forced a compromise a brand team didn't love. Maybe SoulCycle's Creative Director wanted full-bleed instructor photography on the class card. The shared card component supported brand-token color and typography but not layout variation at that level. You shipped the constrained version and sequenced layout-level token support post-launch. Whatever the real example is, put it on the page. A hiring manager evaluating a multi-brand system wants to know you felt the friction of the abstraction, not just that you designed it.

4.8★ outcome attribution (Criterion 6): Partial pass. The attribution structure is right. You connect the rating to specific design decisions rather than letting it float as a vanity metric. Two problems.

First: "top review themes mapped directly to the five decisions" is asserted, not shown. Show one mapping. "The most frequent positive review theme was instructor discovery, which mapped to Decision 02's followership-first navigation." One line. Converts assertion into evidence.

Second, and this matters more than it looks: the 4.8 was a launch-state metric. Apple metadata as of late June 2026 shows approximately 4.7 after six years and version 11.35.0. A hiring manager who checks the App Store and finds 4.7 won't think you rounded up. They'll think you don't track your own outcomes. Label the metric "4.8★ at launch" everywhere it appears. The outcome card copy already carries this qualifier. The hero stat and launch section headline do not. Add it. Five-minute fix that prevents a credibility question you don't want to answer in an interview.

Priority Order

Changes that affect how a hiring manager evaluates the case:

• Add one constraint-shaped sentence per design decision (Criterion 1)
• Label 4.8★ as "at launch" everywhere (Criterion 6)
• Name one concrete multi-brand architecture tradeoff (Criterion 3)

Changes that remove friction:

• Fix teaser case-number inconsistency and metadata
• Convert one MVP cut from list to reasoning (Criterion 4)
• Fix third-person "Juno" to first person (Criterion 2)

Do the first three first.