Current State: July 9, 2026
Resolved. The meta title now reads Allē · Dual-Surface Loyalty Redesign · 30M Members, 40K Practices · Juno Chen. The "Editorial Mosaic" problem flagged in the prior issue is gone. The title positions the work, signals scale, and names you. It does its job in browser tabs, Slack previews, and search results. No further action. No other prior critiques were outstanding.
Two material gaps remain:
- No product visual in the hero. The first screen shows a dark grid background with a typographic
05watermark. No UI, no design artifact, no craft evidence until the viewer scrolls into Track A. - No CTA in the first screen. The first "Request the full case study" link appears after the entire consumer track and bridge section. A convinced buyer has nowhere to go.
Both gaps come from the same structural choice: the hero asks the viewer to scroll before it proves anything or offers a next step. Everything below the fold is strong. The Track A / Bridge / Track B structure tells the dual-surface story clearly. The metrics are present and well-placed. The closing section reinforces with specificity. But a CPO with fourteen tabs open doesn't get there if the first screen is a dark grid and a paragraph.
Here's the full six-point evaluation.
1. Page Title — Done
The current title packs positioning, scale proof, and attribution into a single string. The meta description reinforces with role, dual-surface scope, and all three outcome metrics. A recruiter sharing this link sees the right words before anyone clicks. No notes.
2. Hero Framing — Working, One Soft Edge
The H1, When the product is someone's face, points aren't enough, earns attention. It's evocative. It's also editorial framing rather than a strategic premise. By the guideline's own criterion, the strategic premise should land before aesthetic or craft context. The H1 technically fails that test.
The hero paragraph compensates within the same viewport: "30 million enrolled members. A loyalty program almost none of them understood." Then the dual-surface declaration: "I redesigned across consumer iOS and provider backoffice — and defined the strategy connecting them." The six-row case brief reinforces with role, team, scale, and outcomes.
The paragraph carries the premise before the viewer's eye leaves the first screen. Low priority. Still worth flagging.
Optional tightening (Low priority). If you want the H1 to carry strategic weight on its own:
"One loyalty system. Two surfaces. 30 million members who never understood it."
This tells the buyer what the case is before they read the paragraph. But the current H1 works well enough. Don't touch it until the two high-priority items below are shipped.
3. Dual-Surface Signal — Clear
The hero paragraph names both surfaces explicitly. The case brief reads Product: Allē Loyalty · iOS & Provider Web. Both appear before scroll on desktop. The bridge section later splits the story into Track A (Consumer iOS) and Track B (Provider Backoffice) with parallel framing.
On mobile, the stacked layout puts the dual-surface sentence early in the reading flow. The brief rows follow. A CPO will not miss this. No action needed.
4. Outcome Proof in First Screen — Desktop Yes, Mobile Uncertain
On desktop, the case brief surfaces all five proof points in the hero: 30M+ members, 40K+ provider practices, 3.2× redemption, 47% reactivation, $42 CAC. The hero's min-height: calc(100vh - 240px) keeps this content within the viewport.
On mobile, the hero switches to a single stacked column with min-height: auto. The H1, paragraph, and earlier brief rows (Company, Product, Role, Team) all precede the Scale and Outcome rows. On shorter viewports, the metrics may push below fold.
One detail worth protecting: the hero brief shows $42 CAC without the industry comparison. The full delta, $42 vs. $92 industry average, appears in the Track B analytics panel. The $42 figure needs the $92 baseline next to it. Together they show a 54% reduction against the industry average. Alone, $42 is just a number on a page. If you condense the mobile brief, make sure the comparison framing survives, not just the figure.
Recommendation (Medium priority). Test on a 375×667 viewport. If the Outcome row falls below fold, condense the mobile brief. Collapse Company and Product into a single row, or pull Scale and Outcome into the paragraph itself on small screens. The metrics, including the CAC comparison, need to land before the scroll on every device a hiring manager uses.
5. Craft Signal — Missing
High priority. This is the most consequential issue on the page.
The hero background is a dark grid with a typographic 05 watermark. Clean, but devoid of any design evidence. The first product visual appears in Track A, below the hero.
For a design leadership portfolio, the hero is where a CPO forms their first impression of your craft bar. Right now that impression is "nice typography, dark background." The actual UI work stays invisible until the viewer commits to scrolling.
Place one high-fidelity product image in the hero. The consumer iOS member dashboard from Track A, ideally alongside a partial provider queue view from Track B. Both assets already exist on the page. You're moving them up.
A single composite communicates three things at once: you designed real product UI, you worked across two surfaces, and the visual quality is high.
Placement. Right column on desktop, replacing or supplementing the case brief area. Full-width below the paragraph on mobile. The case brief metadata can sit beneath or beside the image. The image should not replace the brief. It should precede or accompany it.
If a composite feels forced, lead with the consumer dashboard alone. The member-facing elements already in Track A (progress bar, saved care plan, flash offer card) are immediately legible as thoughtful product design even at thumbnail scale.
6. CTA — Too Deep
High priority. The first "Request the full case study" link appears after the consumer track mosaic and the bridge section. Multiple scroll-depths into the page. A buyer who's sold in the hero has no path to act on it.
Recommendation. Add a CTA to the hero section. After the case brief on desktop, after the brief on mobile.
Recommended copy: View the full case study → linking to cs-06-alle.html.
Keep the existing CTAs after the bridge and in the closing section. They serve viewers who need more evidence before committing. The hero CTA catches the buyer who already knows.
One note on language. "Request" implies a gate. If the full case study is freely accessible, use "View." If it's gated, "Request" is accurate, but gated portfolio cases add friction at exactly the moment a hiring manager is forming their shortlist. Every click that isn't instant access is a moment where they move to the next candidate's tab.
What to Do This Week
- Add a product image to the hero. Promote the consumer iOS dashboard from Track A, ideally with a partial provider queue view from Track B. (High)
- Add a hero CTA.
View the full case study →after the case brief. (High) - Test mobile fold on 375×667. Verify outcome metrics (including the $42 vs. $92 comparison) appear before scroll. Condense the mobile brief if they don't. (Medium)
- H1 tightening is optional. The paragraph carries the premise. Revisit only after the above three ship. (Low)
- Leave the Track A / Bridge / Track B structure as-is. The content architecture below the fold is doing its job. These changes are scoped to the hero. (No action)
The page's problem is concentrated in the first five seconds. A buyer who scrolls will find a well-structured dual-surface story with real metrics and clear strategic framing. Your job is to make sure they never have to scroll to know that.
- Equinox+ title still generic: The Equinox+ teaser browser title still reads "Equinox+ · Teaser · Juno Chen" rather than mandate-forward language, making it the last unresolved teaser metadata item across the portfolio.
- Headway wants this exact proof: Headway's Design Director, Provider Experience posting owns provider EHR strategy across scheduling, billing, and AI-centered workflows, which means the Allē provider backoffice track is unusually direct evidence for that search.
- Suno as consumer-craft route: Suno's Head of Product Design role leads design across core product surfaces for 100M+ users, where the Allē consumer iOS track and Equinox+ together answer the "can she make this feel good at scale?" objection.
- Portfolio boundary risk persists: The private TinyFish essay still delivers full HTML content before the client-side password overlay, meaning any outreach that drives senior buyers to the homepage risks exposing noncanonical evidence alongside the now-stronger leadership framing.