Equinox+ Full Case Audit — What Passes, What Doesn't, What to Fix First

Gating Status (as of July 10, 2026)

The server returns all 153,030 bytes of case content at junochen.com/cs-04-equinox.html before the client-side access check executes. The body script reads localStorage.getItem("pf_access_v1") and redirects unauthenticated visitors to a login page that stores the SHA-256 hash of the correct password in a visible CORRECT_HASH constant. On match, it writes to localStorage and redirects back.

Teaser numbering error: The teaser page labels this as "Case Study 03" in its final CTA and watermark while the URL and sidebar say case 04. Small. Easy for a detail-oriented buyer to notice. Fix it.

Hero and Scope Strip

The hero leads with the right numbers: 600K premium members, five brands, Product Design Director, 0→MVP in three months. A buyer who reads nothing else gets the headline. The stat row repeats these as scannable callouts without feeling redundant. Fine.

[Criterion 5: IC+Manager] — Pass, with a structural note below in the decisions section.

The operating-scope strip immediately below the hero is the strongest structural element on the page. It names four designers (two hired mid-project as scope expanded), one researcher, five brand PMs, two engineering leads, five brand Creative Directors, and data science partners. The decision-rights cell separates what you owned (IA, cross-brand navigation, design system, token architecture) from what you influenced (roadmap sequencing, MVP scope, brand-team sign-off).

Director+ evaluators scan for exactly this. The owned/influenced distinction proves you understand organizational authority, the thing they're actually evaluating at this level. Most candidates list who they worked with. You listed what you could decide versus what you had to negotiate.

One thing to surface: the mid-project hiring detail. "Hired two of the four designers as scope expanded to all five brands" is currently buried in the strip. Hiring during execution is a leadership proof point that reads differently from inheriting a team. Bold it or pull it into its own line.

The pressure-call cell deserves separate attention. Six weeks left, engineering capacity for only three brand worlds, and you prioritized SoulCycle, Equinox, and Pure Yoga based on instructor-followership density in retention data. Precision Run and HeadStrong followed in the first post-MVP update. This cell is doing triple duty: speed-with-sacrifice, data-driven prioritization, and the kind of scope call only someone with real decision rights can make. It's strong. But it's sitting in a metadata strip a buyer might skim past. I'll flag this again in the action list.

The Brief: "Beat Peloton Without Becoming Peloton"

[Criterion 1: Strategic Constraint Coherence] — Partial pass.

The constraint is stated clearly and given three rules: no leaderboard-first engagement, no single generic content taxonomy, no separation of physical club access from the digital product. Four platform moves follow from these rules: instructor-followership as primary navigation, unified activity record, brand-led doorways, QR club credential.

The framing is specific enough to be falsifiable. A buyer can check each decision against the three rules and see whether it holds. That's what separates a real design constraint from a mission statement.

Here's the problem. The brief says "no leaderboard-first engagement." Later, in the live-class modality section (Decision 01), the page describes wattage, RPM, leaderboard, and live mic as part of live class energy.

A sharp buyer will catch this. And a sharp buyer who catches a contradiction in your strategic constraint and has to resolve it themselves will hold it against you, even if your answer is good.

The resolution is probably that "leaderboard-first" means leaderboard as the organizing principle of the product (Peloton's model), while competitive elements within a live class are a feature of that class format. Defensible. But the page doesn't make the distinction.

Recommendation: Add one sentence in Decision 01. Something close to:

Resolve the contradiction before the buyer has to flag it. This is the highest-risk gap on the page because it undermines the strategic frame that holds the entire case together.

Research Section and the Analytical Move

[Criterion 2: Data-to-IA Derivation] — Partial pass.

Four personas (Maestro ~40%, Attendee ~30%, Striver ~20%, Scorechaser ~10%) sourced from BCG Design Ventures field research across 75 hours and four cities. The Attendee card identifies this high-churn-risk segment's need for social anchoring as the reason instructor-following became the primary architecture.

Decision 02 makes the analytical chain explicit: members who followed at least one instructor within their first 30 days retained at nearly double the rate of those who didn't. You spent a week in the data before the architecture became obvious. Instructor follow, instructor profiles, and feed reshaping became central to the flow.

The chain is visible. Retention data → instructor followership behavior → IA decision. The "nearly double" retention claim is specific enough to be credible. But it's all verbal. No chart, no cohort visualization, no before/after retention curve.

At Director+ level, "I spent a week in the data" is a claim about process. A simple visualization turns it into evidence of analytical capability.

Recommendation: Add one visual. A simplified retention curve showing the divergence between followers and non-followers in the first 30 days, with exact numbers removed if needed for confidentiality. If Equinox data can't be visualized at all, add a sentence explaining the constraint directly:

A buyer who understands why the data isn't shown respects the judgment. A buyer who wonders why it's missing doesn't.

The Five Decisions — IC Proof and the Brand Tradeoff

[Criterion 5: IC+Manager, continued]

The five decisions (modality, instructor, browse/commitment, brand architecture, club loop) each show hands-on design judgment. Decision 02 shows you reading retention data and translating it into navigation architecture. Decision 04 shows you designing a token system that let five Creative Directors own their brand expression without fragmenting the codebase. These are IC decisions with system-level consequences.

The IC evidence is here. The manager evidence is in the scope strip above. The problem: they're separated by the entire research section. A buyer reading top-to-bottom encounters the manager proof first, then personas, then IC proof. The two halves of the IC+manager story never appear in the same visual frame.

Don't restructure the page. The reading order works narratively. Instead, add a single bridging line at the top of the decisions section:

That connects the two halves without disrupting the flow.

[Criterion 3: Multi-Brand Architecture Tradeoff] — Partial pass.

Decision 04 states the model clearly: shared navigation, activity history, scheduling, and account infrastructure; variable color, typography, photography, motion, and class-card expression by brand through token architecture. One component base, one deployment. SoulCycle's Creative Director could own SoulCycle visual DNA without affecting Pure Yoga.

The what is clear. The tradeoff is absent. What did brand teams give up? Were there moments where a Creative Director wanted something the shared component base couldn't support? What was the governance cost of maintaining token consistency across five brands?

The current copy presents the architecture as a clean solution. Director+ evaluators know that multi-brand systems involve real sacrifices. They want to see that you understood the cost.

Recommendation: Add two to three sentences about what was constrained. Something like:

Add the governance cost and the Creative Director pushback, and the architecture reads like something you actually shipped across five brands. Clean solutions without friction read like pitch decks.

Speed/Scope and the Cut List

[Criterion 4: Speed-with-Sacrifice] — Pass.

The page provides a clear three-column breakdown: what shipped at launch, what was cut for MVP, and what was sequenced post-launch. The cut list is specific and strategic: Precision Run and HeadStrong brand worlds, personalized recommendations, third-party tracker integrations, and social/challenge mechanics. The pressure-call cell in the scope strip adds the six-week decision and the data-driven rationale for which three brands shipped first.

This is the strongest criterion on the page. The cut list names real features that real stakeholders probably wanted. The sequencing shows that cuts were strategic, not panicked. "Precision Run and HeadStrong followed in the first post-MVP update" proves the deferred items weren't abandoned. They were staged. A buyer reads this and understands that three months was a scoped bet with a clear follow-up plan.

Launch and Outcome Attribution

[Criterion 6: Outcome Attribution] — Partial pass.

The launch section states a 4.8★ App Store rating and says top review themes mapped to the five decisions, naming instructor discovery/followership, live class quality, and cross-brand navigation as review themes.

The attribution structure is right. Tying the rating to specific review themes that map to specific decisions is exactly the move that separates "I worked on a product that did well" from "my decisions contributed to measurable outcomes." But the evidence is your claim, not the reviewer's words. No review excerpts, no rating-count context, no baseline comparison.

Recommendation: Pull two or three actual App Store review quotes that reference the specific design decisions. "Love how easy it is to follow my favorite instructor" ties to Decision 02. "Switching between SoulCycle and Pure Yoga feels seamless" ties to Decision 04. Direct quotes from users are the cheapest, most credible form of outcome evidence available. A 4.8★ rating means these reviews exist. Find them and place them next to the decisions they validate.

Also: add the review count or a rough order of magnitude. "4.8★ across 12,000+ ratings" is a different claim than "4.8★ across 200 ratings." The number matters. Its absence lets a skeptical buyer assume the smaller number.

Prioritized Action List

Fix before any interview share:

1. Resolve the leaderboard contradiction. One sentence in Decision 01 distinguishing "leaderboard within a live class" from "leaderboard as product organizing principle." Highest-risk gap. It undermines the strategic constraint that frames the entire case.

2. Add App Store review quotes to the launch section. Two or three real quotes tied to specific decisions. Include the review count. This converts the 4.8★ from a floating metric to attributed evidence.

3. Fix the teaser case-number label. Case Study 03 → Case Study 04. Trivial fix, real credibility cost if noticed.

Fix before the case gets heavy rotation:

4. Add a retention-divergence visual to Decision 02. Even a stylized chart showing the follower/non-follower gap. If the data can't be visualized, add the NDA-acknowledgment sentence drafted above. This is the analytical proof point that separates you from designers who say "data-informed" but show no data.

5. Add tradeoff language to Decision 04. What brand teams couldn't customize. Where friction occurred. What the constraint cost. Two to three sentences.

6. Add a bridging line at the top of the decisions section connecting IC proof below to manager proof in the scope strip above.

Lower priority:

7. Resolve the password gate. Server-side authentication or remove the gate. The cosmetic lock is a credibility liability with technically literate buyers, but most won't inspect the implementation.

8. Surface the mid-project hiring detail in the scope strip. Hiring two designers during execution is a leadership signal that's currently easy to miss.

The case is structurally sound. The reading order works. The constraint framing, the cut list, and the scope strip are doing real work. The gaps are addressable without a rewrite. Fix the contradiction, add the quotes, add the visual, and this case does what it needs to do at Director+ level: prove you made hard calls under real constraints, with data, at speed, while leading people. Hiring committees anchor in the first five minutes of a portfolio review. These fixes make sure the anchor they set is the right one.