Full Case Audit: Equinox+ (CS-04) — Evaluated for a Suno Interview Panel

Gating Status

Fetched June 30, 2026. The URL junochen.com/cs-04-equinox returns HTTP 200 with full case HTML before any access check runs. The password gate is client-side: a script checks localStorage for a flag and redirects if it's absent. Every section heading, data point, and image reference ships in the delivered source. Disable JavaScript or view source and you see everything.

For an interview context where you're handing the password directly to panelists, this doesn't matter. But know that the content is technically public to anyone who looks.

The Suno Lens

Suno's Head of Product Design posting asks for someone who drives decisions with qualitative and quantitative insights, influences prioritization with a product and business mindset, and balances speed, experimentation, and polish. Hands-on leadership. Design systems thinking. Comfort with ambiguity at consumer scale. 100 million users, $5.4B valuation, 200 employees, five days a week in office.

This is a company that ships fast and wants a design leader who can make structural calls from behavioral data without needing six months of discovery first.

The Equinox+ case has a direct structural parallel to Suno's product problem: multiple content formats with different emotional registers, a retention challenge rooted in connection rather than competition, and an information architecture that had to be derived from user behavior rather than inherited from an obvious taxonomy. That parallel is the reason to lead with this case. But the parallel only lands if the case proves the analytical reasoning, with the outcome as supporting evidence.

Of the six criteria below, Criterion 2 is the one that will determine whether this case lands or doesn't with this specific panel. Spend your energy there first.

1. Strategic Constraint Driving Decisions

Verdict: Present. Strongest structural element of the case.

"Beat Peloton without becoming Peloton" is the chapter headline, and it does real work. Three explicit constraints flow from it: no leaderboard-first engagement, no flattening five brands into a single content taxonomy, no treating physical club access as a separate product. Every subsequent design decision traces back to at least one. Instructor-first navigation answers "connection over competition." Format-specific design languages answer "no flattening." The QR club credential answers "digital extends the club."

A Suno panelist reading this will see a designer who starts with what the product cannot be and derives what it must be from the negative space. Leave this alone.

2. Retention-Data-to-IA Derivation

Verdict: Partial. The analytical move is visible. The evidence layer is too thin for a panel that tests exactly this capability.

The case states the signal: members who followed at least one instructor within their first 30 days retained at nearly double the rate. It says this signal "wasn't in the brief." It connects the signal to the IA decision: if followership predicts retention, the instructor becomes the primary navigation object. It ties the Attendee persona (highest churn risk, coach-dependent) to the same conclusion from a different angle.

The reasoning chain is correct and legible. A Suno panelist will recognize the move.

Here's the problem. "Nearly double" is doing all the evidentiary work, and it's unsupported. No sample size. No baseline retention rate. No chart. No before/after comparison. For a general design-leadership interview, the narrative framing is sufficient. For a Suno panel where the posting explicitly asks for "qualitative and quantitative insights" driving decisions, the absence of any visible data artifact weakens the single most important signal in the case.

Add one data visualization or a simple annotated stat block. It doesn't need to be a dashboard. A single chart showing 30-day retention for followers vs. non-followers, even with anonymized axes, changes this section from assertion to evidence. If NDA constraints prevent showing actual numbers, say so explicitly and describe the shape of the data: "Retention diverged at day 7 and the gap widened through day 30. The effect was strongest in the Attendee segment." Naming the shape of the curve is almost as convincing as showing it, and it proves you actually looked at the data rather than received a summary from data science.

This same retention data also shaped the launch scope (Criterion 4): you prioritized SoulCycle, Equinox, and Pure Yoga because they had the highest instructor-followership density. One analysis, two strategic outputs. If you add the data artifact here, reference it in the speed section too. The double use strengthens both sections.

Name the tool or method in one sentence. "Spent a week in the data" is good but vague. Was this a cohort analysis in Amplitude? Mixpanel event streams your data science partner ran that you then interrogated? Session logs you pulled yourself? One sentence naming the tool or method separates "I directed the analysis" from "I did the analysis." For a Suno panel, the latter matters more. Five words with significant credibility return.

3. Multi-Brand Architecture Tradeoff

Verdict: Partial. The architecture is well-described. The cost is invisible.

The case names the shared layer (navigation, activity history, scheduling, account infrastructure) and the variable layer (color, typography, photography, motion, class-card expression). It names the mechanism: token architecture, one component base, one deployment. Each brand's Creative Director owned their visual DNA without touching another brand's. Clean systems-design explanation.

What's missing is what it cost. Five brand expressions on one component base with token architecture is not free. The design system is more complex. QA surfaces multiply. Every new component needs validation across five visual contexts. Onboarding a new designer takes longer because they need to understand the token layer, not just the component layer. The case reads as if doing both was a clean win, without acknowledging the real engineering and design-system overhead.

Add two to three sentences naming the cost. Something like: "The token architecture added complexity to every new component. Each addition required validation across five brand contexts, which slowed the design system's growth rate. We accepted that tradeoff because brand fidelity was the premium signal members were paying $40/month for, and a generic system would have erased it." That framing proves you understood the cost and made a deliberate call. A Suno panelist building a design system for a product with multiple creative surfaces will recognize this tradeoff as directly relevant to their own architecture decisions.

4. Speed Claim: 0→MVP in 3 Months

Verdict: Present. Well-handled.

The case does what most cases don't: it shows the cuts. Precision Run and HeadStrong deferred. Personalized recommendations deferred. Third-party tracker integrations deferred. Social/challenge mechanics deferred. It explains the forcing function: six weeks left, engineering capacity for three brand worlds, so Juno prioritized SoulCycle, Equinox, and Pure Yoga based on instructor-followership density in the retention data.

The MVP cuts list and the post-launch sequencing list together prove that speed came from constraint discipline. For a Suno panel that explicitly values "balancing speed, experimentation, and polish," this section already delivers. Leave it.

5. IC + Manager Proof and Cross-Functional Scope

Verdict: Partial. The org scope is clear. The IC craft line is blurry.

The operating-scope strip works. Team of 4 designers and 1 researcher. Juno hired 2 of the 4 mid-project. Cross-functional partners named: 5 brand PMs, 2 engineering leads, 5 brand Creative Directors, data science, BCG Design Ventures. The owned-vs.-influenced distinction is sharp: Juno owned IA, cross-brand navigation model, design system, and token architecture. Influenced roadmap sequencing, MVP scope, and brand-team sign-off process.

What's missing: which artifacts Juno personally designed versus directed. The case shows many UI screens. Did Juno design the instructor profile page? The class booking flow? The token architecture spec? Or did she set the direction and her four designers executed? Suno's posting asks for someone who is "hands-on with tools to push a vision forward." That's a direct request for IC proof. The case currently proves the leadership layer but leaves the craft layer ambiguous.

Tag two or three specific artifacts as your direct IC work. Even a parenthetical works: "I designed the instructor profile and class-card system directly; the brand-world landing pages were designed by [designer's name or role title] under my direction." Name the team member or use a role title, whichever is appropriate for the relationship. This answers the specific question a Suno panelist will have: does this person still make things, or only manage people who make things?

6. The 4.8★ App Store Rating

Verdict: Partial. The connection to design decisions is attempted but thin.

The case says the 4.8★ rating reflected review themes that mapped to the five design decisions: instructor discovery, live class quality, brand movement. Tying a vanity metric to specific decisions is better than claiming the number alone.

Two issues. No review excerpts are shown. Quoting two or three actual App Store reviews that mention instructor discovery or brand navigation would make the claim concrete instead of asserted. And the current App Store listing shows 4.7 stars across 41K ratings. The case frames 4.8 as "at launch," which isn't contradicted by the current cumulative number. But a panelist who checks will see 4.7, and the gap creates a moment of doubt.

Make the "at launch" framing unambiguous and visible. Consider adding the current state: "4.8★ at launch; 4.7★ sustained across 41K ratings as of 2026." The sustained number is arguably more impressive because it shows durability, and it preempts the fact-check. Add one or two verbatim review quotes if you can find archived ones that reference instructor followership or brand navigation.

Priority-Ranked Action List

Fix before sharing with a Suno panel:

• Add a data artifact to the retention-to-IA section. Chart, stat block, or described data shape. This is the highest-leverage change. It converts the case's best analytical move from assertion to evidence. Suno's posting asks for quantitative insight driving decisions. Show it.
• Name the analytical method in one sentence. Tool, data source, whether you ran the analysis or directed it. Small addition, large credibility gain.
• Tag two or three artifacts as your direct IC work. Suno wants hands-on. Prove it with specific screens or systems you personally designed.
• Name the cost of the token architecture. Two sentences on what the multi-brand system made harder. Turns a clean-win narrative into a tradeoff narrative.

Strengthen if time allows:

• Update the 4.8★ framing to acknowledge the current 4.7★/41K state. Add verbatim review quotes.

Strong enough to leave:

• Strategic constraint framing. Best-structured element.
• MVP cuts and speed framing. Already proves constraint discipline.
• Operating-scope strip with owned-vs.-influenced distinction.
• Four-persona research framing.

How to Walk a Suno Panel Through This Case

When you walk a Suno panel through this case, start with the structural problem.

Open with:

A Suno panelist hears that and knows why they should care. Suno's product has the same problem. AI-generated music doesn't fit neatly into traditional music taxonomies. The navigation model has to come from how users actually behave with generated content, not from how Spotify organizes licensed music.

Draw the parallel explicitly. Five fitness brands with different emotional registers map to multiple creative formats with different user intents. Instructor-followership as the retention signal maps to whatever behavioral signal predicts retained engagement with AI-generated music. Maybe it's creation frequency, maybe it's sharing behavior, maybe it's return-to-edit rate. The analytical move is the same: find the behavioral signal that predicts retention, then restructure the IA around it, even when it contradicts the original brief.

Resist the chronological pull. The temptation is to start at the beginning: "I joined Equinox when they were launching a digital product..." The Suno-relevant version starts with the analytical insight and works backward to the context that made the insight necessary. Your recommended opening sentence already sets this up. The panel already assumes you got there. What they're evaluating is whether you can reason this way again, on their product, next quarter.

Spend the most verbal time on the retention-data-to-IA derivation. Walk through the data, the surprise, the week of analysis, the architectural conclusion. This is what Suno is testing for. Everything else in the case is supporting evidence.

On speed: emphasize that the same data insight shaped both the IA and the launch scope. One analysis, two strategic outputs. That's efficiency of reasoning, and it matters at a company shipping as fast as Suno.

On the multi-brand architecture: frame the token system as a design-system scaling pattern. Suno will need to support multiple creative surfaces with consistent interaction patterns but different emotional contexts. The token architecture is a transferable solution.

On the Peloton competitive framing: Suno's panelists will tune out fitness industry dynamics. The analytical reasoning pattern is what holds their attention. Lead with the pattern. Equinox is the proof case, the vehicle for demonstrating the reasoning.