Verified against junochen.com/cs-04-equinox-teaser.html and junochen.com, fetched July 9, 2026.
Current state: The homepage has resolved its leadership-positioning problem. Title tag reads "Juno Chen — Design Leadership for High-Stakes Systems." OG tags carry the frame into Slack unfurls and LinkedIn shares. Hero copy targets Head of Design searches. That work is done.
CS-04 has not caught up. The page body carries real mandate evidence: Product Design Director, 600K+ premium members, five brands, 0→MVP in 90 days. But the metadata layer is empty. No description tag. No OG tags. No Twitter cards. The browser tab reads "Equinox+ · Teaser · Juno Chen." When a recruiter drops this link into a hiring-committee Slack channel, the preview shows a fitness app and a name. Nothing about multi-brand platform architecture. Nothing about Director-level scope.
The body is working. The metadata is defeating it before anyone clicks.
One positive to note before we get into fixes: "Product Designer" does not appear anywhere in the fetched source. The role is consistently labeled "Product Design Director." Title-level positioning is clean.
Every recommendation below serves one goal: making this page read as multi-brand platform architecture under extreme time constraint. If the first signal a hiring manager at Anthropic, Ramp, or Salesforce registers is "workout app," the architecture story never gets heard. You have two seconds before that pattern locks in. Every fix below is about winning those two seconds.
1. Page Title
Finding: <title> tag is Equinox+ · Teaser · Juno Chen. No meta description. No Open Graph tags. No Twitter card tags. High confidence this is the single highest-leverage fix on the page.
Risk: Every surface where this URL appears without a click shows a fitness brand and a name. Browser tab, Slack unfurl, LinkedIn share, recruiter email preview, bookmarks bar. A VP Design at Ramp sees "Equinox+" and moves on. The strategic complexity of the work is invisible at the only moment it matters: before the click.
Fix: Replace the title. Add metadata.
- Title tag:
Equinox+ — 5 Brands, 1 Platform, 0→MVP in 90 Days | Juno Chen, Product Design Director - Meta description:
Led product design for Equinox Holdings' multi-brand digital platform — 600K+ premium members, five distinct brand identities, shared component architecture. Zero to MVP in 90 days. 4.7★ App Store (see rating note below). - OG title: Same as title tag.
- OG description: Same as meta description, minus the parenthetical.
- OG image: A platform-architecture diagram or multi-brand screen composite. A single-brand fitness screenshot works against you here.
Note on the rating: the page currently says 4.8★. The current App Store listing shows 4.7 from 41K+ ratings. I address this fully in Section 5, but flagging it here because the meta description is copy you'll ship today and it needs to be defensible today.
Fifteen minutes of work. Changes how the page performs in every context except direct viewing.
2. First Screen
Finding: The hero fills the first viewport (CSS sets it to calc(100vh - 200px), min 500px). The H1, "Five brands. One platform. No compromise," is strong. The hero intro surfaces 600K members, five brands, Product Design Director, and 0→MVP in 3 months. The hero brief reinforces with structured data: team composition, club scale, App Store rating. Good architecture for scan speed. High confidence the hero content is doing its job.
Risk: The eyebrow. It reads Equinox · Consumer Fitness · iOS & Android · 2020. "Consumer Fitness" is the first category signal on the page, landing before the H1. Category labels anchor harder than headlines at scan speed. The hiring manager's pattern-matching system registers "fitness app" before "five brands, one platform" gets a chance to land.
This is the positioning problem in miniature. The same case study, categorized differently, is a different case study to the reader. "Consumer Fitness" tells them what industry you were in. "Multi-Brand Platform" tells them what problem you solved. They're evaluating you on the problem.
Fix: Change the eyebrow to Equinox Holdings · Multi-Brand Platform · iOS & Android · 2020.
The first image after the hero is a SoulCycle Live photo, which reinforces the fitness anchor. If the teaser format allows you to lead with a multi-brand composite or architecture visual instead, do it. If it constrains image choice, the eyebrow fix alone moves the needle significantly.
3. Platform Architecture Signal
Finding: The hero names five brands and one platform. Right signal, right altitude. But the specific architecture decisions that make this case Director-level live in the final CTA section, below the screen grid. That's where instructor-as-navigation, token architecture for brand-specific visual DNA from a shared component base, and modality-specific interface languages all appear. High confidence these are the strongest signals on the page, and high confidence they're in the wrong location.
Risk: The screen grid between the hero and the final CTA is dominated by fitness imagery and brand names: SoulCycle, Precision Run, Yoga, HIIT, Cycling, Meditation. A hiring manager scrolling through this section sees a fitness app showcase. The architecture story disappears. The case is bookended (H1 at top, decisions at bottom) but the middle of the page undermines both ends with consumer-fitness visual language.
Fix: Pull one architecture insight into the hero section. The strongest candidate: instructor-as-navigation. The published case evidence shows that retention data revealed members who followed an instructor returned while members who didn't churned, and that instructor became the primary navigation object. That's a design-leadership decision grounded in behavioral evidence, and it reads as one.
Add one sentence to the hero intro, after the MVP line:
"We restructured navigation around instructor followership after retention data showed it was the strongest predictor of return."
A Director making a structural call based on data. It gives the scan-speed reader an architecture signal before they hit the fitness imagery, and it gives a CPO something to remember when they're comparing you to three other candidates later that week.
Additionally, if the screen grid section can carry brief architectural annotations, even a single line under each brand screen naming the design decision that brand required would transform the middle of the page from fitness showcase to architecture evidence.
4. Speed Framing
Finding: Three variants across the page: "0 → MVP in 3 months" (hero intro), "0 → 1 in 90 days" (hero brief), "zero to MVP in three months" (final CTA). Low confidence this is a real risk. At this scope, five brands and 600K members, the timeline reads as disciplined constraint-solving regardless of phrasing.
Fix: Standardize on "0→MVP in 90 days" everywhere. A number signals measurement; a round month count signals approximation. "90 days" reads as someone who tracked the timeline. "3 months" reads as someone telling the story afterward. Minor, but consistency signals care, and care is a proxy for judgment at this level.
5. Craft Signal
Finding: The final CTA section carries three named design decisions: Navigation architecture, Brand identity system, Modality design language. Each has a one-sentence rationale. "Token architecture gave each brand its own visual DNA from a shared component base" is the kind of sentence a VP Design registers. "Live cycling, audio meditation, and VOD yoga required different interface languages while still feeling like one product" demonstrates systems-level judgment. These are genuine craft signals. High confidence they work.
Risk: They're at the bottom. A hiring manager who gives this page fifteen seconds never reaches them. The hero intro fix in Section 3 partially solves this by surfacing one architecture decision early.
The hero brief lists "4.8★ App Store." The current Apple App Store listing shows 4.7 (precisely 4.71652) from 41,479 ratings, checked today. Either update to 4.7★ or qualify as "4.8★ at launch" if accurate and defensible in conversation. A hiring committee at Director+ level will check. Someone always checks.
6. CTA
Finding: Both CTAs read "Request the full case study" and link to cs-04-equinox.html. The gating mechanism is appropriate. It signals the full case contains proprietary detail worth requesting, which is the right frame for Director-level positioning. High confidence the CTA structure works.
Risk: The final CTA eyebrow reads "Case Study 03" while the sidebar and the homepage card both identify this as Case Study 04. Small, but the kind of inconsistency that reads as carelessness to a panel evaluating your attention to detail. At this level, details are a proxy for judgment.
Fix: Change the final CTA eyebrow from "Case Study 03" to "Case Study 04."
Homepage Card — The Entry Point Is Underselling the Case
Outside the six criteria, but worth flagging. The homepage Equinox+ card reads: title "Equinox+", description "5 brands, one platform, zero to production", tags "Consumer Tech, iOS & Android, Omnichannel, User Journey." Missing: Product Design Director, 600K+, 90 days, rating. A card description like "Product Design Director · 5 brands, 1 platform, 600K+ members, 0→MVP in 90 days" would carry the mandate signal from the homepage hero into the click.
Fix Order
- Metadata (title, description, OG tags). Fifteen minutes. Changes every non-click surface. Do this today.
- Eyebrow swap ("Consumer Fitness" → "Multi-Brand Platform"). Two minutes. Removes the category anchor that downgrades the page before the H1 lands.
- Case study number ("03" → "04"). One minute. Credibility.
- Rating (4.8 → 4.7, or qualified). One minute. Verifiability.
- Hero intro architecture line (instructor-as-navigation). Five minutes of writing. Gives the scan-speed reader a craft signal before the fitness imagery takes over.
- Homepage card description. Five minutes. Carries the mandate into the entry point.
The body of this page is doing real work. The metadata and the eyebrow are letting it down. Fix the frame, and the content inside it starts performing at the level it deserves.
- Ramp's Director posting language: Ramp's current Director, Product Design role explicitly says design is now "building tools and agents, designing memory, and defining how design works in an AI-native world," which makes the Alibaba trust-at-scale case plus Trust essay the natural lead pairing if Equinox+ serves as secondary consumer-speed proof.
- Suno's scale and stage: Suno's Head of Product Design search sits at 100M+ users, 200 employees, and a $5.4B valuation after a $400M Series D, making it a live case where Equinox+ consumer craft evidence could answer the "can she make this feel good?" objection after leading with Agentic Labs.
- Headway's consequence framing: Headway's Design Director, Provider Experience posting names clinical documentation, insurance verification, and billing as AI-centered workflows where designers are expected to prototype with Claude Code and Cursor, reinforcing that Thermo Fisher or Red Cross should lead over Equinox+ for regulated-workflow roles.
- App Store rating drift: Apple's iTunes API reports the Equinox+ rating at precisely 4.71652 from 41,479 ratings as of July 2026, so confirming whether 4.8 reflects a launch-window figure or needs updating is worth resolving before any outreach that links to CS-04.

