Verified against live HTML, July 3, 2026.
Delta Summary
Resolved since last audit: None on this page. Open: Title tag, eyebrow label, architectural insight placement, case-number mismatch (03 vs. 04), missing meta/OG tags, mobile grid behavior.
Your other four teasers have been upgraded. Alibaba leads with "$50B+ GMV." Thermo Fisher leads with "$20M+ Margin." Red Cross leads with "0→1 Build." Allē leads with "30M Members, 40K Practices."
Equinox+ still reads: "Equinox+ · Teaser · Juno Chen."
The only teaser in your portfolio that communicates nothing in the browser tab. The rest of the page is unchanged since the prior pass: no meta description, no OG metadata, the architectural insight buried below the screens grid, and a case-number mismatch persisting in the final CTA section. The page functions. It underperforms its own evidence at every scan-speed checkpoint that matters.
The Core Risk, Briefly
A CPO at an enterprise platform, a VP Design in regulated health tech, an AI-native hiring committee: all of them see "Equinox" and "Consumer Fitness" and their pattern-matching fires before they read your headline. Lifestyle app. Brand-driven. Visual-design showcase. That pattern is wrong here, but you have roughly eight seconds to override it.
The override material exists on this page. Five brands from one component system. Followership data as the navigation architecture's foundation. Zero-to-MVP in three months. 600K+ premium members. 4.8-star App Store rating at launch. That is a constraint-solving, data-informed, multi-brand platform architecture story. It reads as Director+ evidence if it surfaces at scan speed.
Right now, the strongest material surfaces after a twelve-image grid that, without context, confirms the lifestyle-app assumption instead of breaking it.
Six dimensions follow. Each one: current state, problem, fix.
1. Page Title
Current state: Equinox+ · Teaser · Juno Chen
Problem: A hiring manager with six portfolio tabs open during a Friday-afternoon review will deprioritize this one. Your other four tabs tell them what the case proves. This tab tells them a brand name and the word "Teaser."
Fix: Match the pattern you've already established across the portfolio. Lead with the architectural constraint.
Recommended title:
5 Brands, 1 Platform, 0→MVP in 90 Days — Equinox+ — Juno Chen
Three things land in a browser tab: the multi-brand architecture problem, the speed constraint, and the brand as context for the story being told. While you're in the <head>, add a meta description and OG tags. Every teaser page may have this gap, but this page is the most vulnerable to being dismissed before it loads.
Recommended meta description:
Product Design Director · 5 fitness brands unified on one platform from shared components · 0→MVP in 3 months · 600K+ premium members · 4.8★ App Store at launch
2. First Screen
Current state: Hero fills the viewport. Eyebrow reads "Equinox · Consumer Fitness · iOS, Android · 2020." H1: "Five brands. One platform. No compromise." Intro paragraph surfaces 600K members, five brands, Juno's design leadership, the three-month timeline. Sidebar lists Role (Product Design Director), Team, Scale (600K+ premium members, 200+ clubs), and Outcome (0 to 1 in 90 days, 4.8★ App Store). CTA reads "Request the full case study."
Problem: The H1 is strong. The sidebar is strong. The intro paragraph does real work. But the eyebrow undercuts all of it. "Consumer Fitness" is the first categorization label a scanner processes, and it anchors everything that follows in the wrong frame. A CPO reads "Consumer Fitness" before they read "Five brands. One platform." You've handed them the dismissal lens before they've seen the picture.
Fix: Change the eyebrow from domain label to mandate label.
| Eyebrow text | |
|---|---|
| Current | Equinox · Consumer Fitness · iOS, Android · 2020 |
| Recommended | Equinox · Multi-Brand Platform Architecture · iOS, Android · 2020 |
| Alternative | Equinox · 5 Brands, 1 Component System · iOS, Android · 2020 |
Either version tells the scanner what kind of design problem this was before they read the headline. "Consumer Fitness" tells them what industry the client is in, which they already know from the brand name, and which triggers the exact pattern-match you need to prevent.
3. Architectural Insight Visibility
Current state: The followership-as-navigation insight and the brand-token architecture appear in the final CTA section, after the twelve-image screens grid. That section names "navigation architecture and the instructor-as-primary-object model" and explains that "retention data showed members who followed an instructor returned, while members who did not follow an instructor churned." It describes "token architecture giving each brand distinct visual DNA from a shared component base" and distinguishes format-specific interface languages across live cycling, audio meditation, and VOD yoga.
Problem: This is the best material on the page, and it lives where the fewest readers will see it. The screens grid is visually rich, but without architectural framing it reads as "here are some nice screens from a fitness app." The followership insight is the single strongest Director+ signal on this page: a design decision driven by retention data, grounded in observed member behavior. That evidence separates a design director from a senior designer. Burying it after twelve images is putting the thesis at the end of the abstract.
Fix: Insert a compressed version of the architectural framing above the screens grid. Three lines, max. Give the scanner the lens before they see the screens.
Recommended insertion (above screens grid):
The architecture insight: Retention data showed members who followed an instructor came back. Members who didn't, churned. That finding became the navigation's foundation: instructor-as-primary-object over class-as-primary-object. Five brands got distinct visual DNA through a token system built on shared components. Four format-specific design languages (live cycling, audio meditation, VOD yoga, in-club) from one underlying system.
With this block in place, the scanner sees the SoulCycle screen and understands it as one expression of a multi-brand token system. Without it, they see a fitness-app card.
4. Speed Framing
Current state: The hero intro mentions "three-month MVP shipment." The sidebar lists "0 to 1 in 90 days." The final CTA section connects the timeline to "75 hours of research, 4 member archetypes, 5 architecture decisions."
Problem: The speed claim appears twice in the hero, which is good for scan visibility. But "0 to 1 in 90 days" without constraint context can read as rushed. The material that proves rigor lived inside the speed sits below the grid where most scanners won't reach.
Fix: Compress the constraint-under-speed framing into the hero sidebar's Outcome line. Watch the density, though. The sidebar is a metadata slot, not a paragraph container. If the expanded line wraps to four or five lines on screen, it defeats the scan-speed purpose.
Primary recommendation (if the sidebar format supports it):
0→1 in 90 days · 75 hrs research, 5 architecture decisions inside that window · 4.8★ App Store at launch
Fallback (if the sidebar line wraps too far): Keep the sidebar tight at 0→1 in 90 days · 4.8★ App Store at launch and add one sentence to the hero intro paragraph: "Seventy-five hours of research, four member archetypes, and five architecture decisions fit inside that three-month window." The constraint-under-speed evidence needs to live above the fold. Where exactly depends on what the layout can hold without breaking.
5. Craft Signal
Current state: Twelve-image screens grid spanning SoulCycle, Precision Run, Pure Yoga, HeadStrong, and Equinox core. Inline CSS defines separate brand-color tokens (yellow, red, blue, purple, teal). The grid includes animation logic for cell entrances, waveform bars, progress rings, heartbeat animation, streak calendars, and QR scan animation, with reduced-motion overrides.
Problem: Minimal. This is the dimension where the page performs best. A design leader scanning the grid will recognize the craft altitude: brand-token differentiation visible across screens, interaction patterns specific to format, reduced-motion consideration signaling production-grade thinking. The grid is strong evidence.
The gap is that without the architectural framing above it (dimension 3), the craft reads as execution quality alone. The dimension 3 fix resolves this by giving the scanner the leadership-judgment context before they encounter the screens.
One structural flag: The grid's six-column layout works on desktop. At 768px the CSS switches to single-column, which means the visual comparison between brands disappears on phone screens. If a hiring manager opens this on their phone over the holiday weekend, they see a vertical scroll of individual screens with no visible system logic. The brand-differentiation story requires side-by-side comparison to land.
Fix: At the mobile breakpoint, switch to a two-column paired grid that keeps at least two brand expressions visible together. Pair them intentionally: a SoulCycle screen next to a Pure Yoga screen, a Precision Run card next to a HeadStrong card. If even two-up is too tight at small widths, add a visible brand label (SoulCycle, Pure Yoga, etc.) above each screen in single-column so the system logic survives even when the side-by-side comparison doesn't. The scanner needs to understand "these are different brands from one system" without scrolling back and forth to compare.
6. CTA
Current state: Two CTAs reading "Request the full case study," both linking to cs-04-equinox.html. One in the hero, one in the final section.
Problem: Two issues. "Request" implies a gate. If the full case is publicly accessible, "Request" adds friction language that costs you clicks. More important: the final CTA section uses case-study number 03 in its watermark and eyebrow while the sidebar and page identity label this as case 04. A copy-paste artifact from the Red Cross teaser. A detail-oriented hiring manager will notice, and at Director+ level, artifact errors in your own portfolio create a credibility tax you should not be paying.
Fix: Correct the case-number mismatch from 03 to 04. Change "Request" to "View" if the full case page is publicly accessible. If it's gated, keep "Request" but weigh whether the gate justifies the drop-off.
Prioritized Action Stack
Fix today (15 minutes):
- Change the browser title tag. The recommended title is ready to paste.
- Fix the 03→04 case-number mismatch in the final CTA section.
- Change the eyebrow from "Consumer Fitness" to "Multi-Brand Platform Architecture."
Fix this weekend:
- Add the architectural-insight block above the screens grid.
- Expand the Outcome line in the hero sidebar (or the intro paragraph, per the fallback) to include constraint-under-speed framing.
- Add meta description and OG tags.
- Add mobile brand labels or switch to a two-column paired grid at the 768px breakpoint.
Evaluate next week:
- CTA language ("Request" vs. "View").
The first three fixes take fifteen minutes and change what a hiring manager sees before they make the click-or-close decision. The rest take a working session and change whether the page's strongest evidence actually reaches the reader.
Inboxes are quiet. People who do open portfolios this weekend have uninterrupted attention. They might open all five of your teasers in tabs. Four of those tabs will tell them what you proved. One will say "Equinox+ · Teaser · Juno Chen."
That tab gets closed. And with it goes the data-driven navigation decision, the multi-brand constraint story, and the strongest speed-under-rigor evidence in your portfolio. The material is there. It just needs to be visible before the tab gets closed.
- Multi-brand maps to Suno: Suno's Head of Product Design posting names Product Design, Design Engineering, and UX Research under one leader at a $5.4B valuation, making Equinox+'s multi-brand-from-shared-components story a relevant speed and architecture proof if the teaser fixes land first.
- Headway tests speed under consequence: Headway's Provider Experience director role describes AI-powered clinical workflows across scheduling, documentation, and billing, where the "0→1 in 90 days with 75 hours of research" framing from Equinox+ directly addresses their implicit question about whether you import process or dissolve constraints.
- Full-case gating still client-side: The full case pages including
cs-04-equinox.htmlstill rely on client-sidelocalStoragechecks rather than server-side access control, which means "Request the full case study" may promise a gate that the HTML doesn't actually enforce. - Holiday weekend portfolio traffic: H2 headcount typically unlocks mid-July, and messages sent Tuesday or Wednesday before holidays land in quieter inboxes, so the teaser fixes in the action stack are timed to catch the first wave of post-holiday portfolio reviews.