Verified state, July 9
I fetched junochen.com today. Here is what I found against the prior cycle's open items.
Resolved. Browser title now reads Juno Chen — Design Leadership for High-Stakes Systems. Hero headline reads Design leader for platforms where trust is the product. Both are leadership-forward. Title issue is closed.
Still open, P0. The "What Do You Count When the Playbook Doesn't Exist?" essay card remains on the homepage. Still tagged Pricing / Strategy. Still linked to what-do-you-count.html. The excerpt copy changed since last cycle but the card and its public link are live. This is still a boundary breach. (The dual feature story diagnosed the gating vulnerability and the private essay leak in detail. I won't re-litigate that analysis here. This piece owns the homepage-specific fix.)
Still open, P1. The lab carousel shows four entries (Carrier IQ, UAT Sentinel, Retail Velocity, Brand Pulse). The section copy reads "Three live agents built solo." A count mismatch on a design leader's portfolio is exactly the kind of detail a VP Design catches in the first scan. Note: the prior baseline reported five homepage lab cards including Creator Scout; the current live HTML contains four. Creator Scout is no longer present. The mismatch is now four-versus-three, not five-versus-three.
The positioning paragraph names TinyFish directly: "Currently: Head of Product, TinyFish." TinyFish is internal-only evidence. This line is live in public HTML right now.
Everything below addresses what is currently visible on the site. Nothing carried forward from assumption.
Why this matters more than it did last cycle
Your headline and title changes raised the evaluative bar. A site that announces "Design leader for platforms where trust is the product" is now being read by evaluators who will hold every structural decision on the page to that standard. The homepage is a design artifact under review by people whose job is reviewing design artifacts. A CPO scanning this page forms a judgment about your systems thinking before clicking a single case study.
Your trust essay argues that the handoff between human and agent is where trust is won or lost. Your homepage has its own handoffs: public to gated, case study to lab, professional to personal. Right now the site contradicts the essay at the access-control boundary. Fix that and the homepage becomes evidence of the thesis. Leave it and the essay's strongest argument gets undercut by the page that hosts it.
P0: Remove the essay card. Delete the TinyFish line.
Private essay card. Remove "What Do You Count When the Playbook Doesn't Exist?" from the homepage. The dual feature story diagnosed the gating vulnerability in full. Short version: the essay contains pricing strategy, product architecture decisions, and operational details that are internal-only. Client-side gating does not protect it. A public link makes it discoverable by any evaluator, any competitor, any crawl. Remove the card. Keep the essay for verbal-only contexts where you control the room.
TinyFish line. The positioning paragraph currently includes: "Currently: Head of Product, TinyFish. The title shift is intentional — understanding how product decisions get made makes me a sharper design leader at the function level." Delete this entire block. TinyFish is internal-only evidence. The reasoning is sound, but the company name does not belong in public HTML. The replacement professional statement below handles the IC-to-manager bridge without naming it.
Professional statement
The current positioning paragraph does real work. It names scale ($50B+ GMV), speed (twelve months, zero to live), and the IC+manager hybrid. It also names TinyFish and spreads the leadership frame across too many sentences. Reads like a compressed bio.
Replace the current paragraph and "Currently" line with two sentences:
"I lead design functions for platforms where the wrong call costs something real, from $50B+ GMV marketplace redesigns to zero-to-production pharma supply chains to agentic AI products shipped from concept through deployment. In early ambiguity I stay close to the work because that's where strategy gets tested; once the system stabilizes, I turn that judgment into team standards, hiring frameworks, and reusable patterns."
Sentence one: what she leads, at what altitude, across what stakes. Sentence two: how she operates. The IC+manager hybrid reads as a sequencing decision, which is accurate. TinyFish is gone. Every scope reference maps to a published case study one click below.
Case study card lines
All five cards should lead with leadership proof and business outcome. Domain labels do not differentiate at this level.
CS 01 — Alibaba.com Current: "Procurement redesign for 40M buyers at $50B GMV, where payment trust and regulatory variance across markets are the design problem."
Close. Names scale and the real constraint. But "the design problem" is a framing phrase — it doesn't tell the evaluator who owned the decisions.
→ "Procurement redesign for 40M buyers at $50B GMV. Led design and research across payment trust and regulatory variance in global markets."
CS 02 — Thermo Fisher Current: "Digital supply chain built from zero inside an organization where every workflow had to displace a process that already worked."
Good constraint framing. No outcome. No leadership signal.
→ "Led design for a pharma supply chain from zero to live across six partners and nine sites in twelve months, displacing entrenched workflows at every location."
CS 03 — American Red Cross Current: "Six legacy systems unified into one crisis-response platform, where downtime means delayed disaster relief and broken compliance chains."
Strong consequence framing. Missing: who led it, what the federal oversight constraint demanded.
→ "Led design unifying six legacy systems into one federally compliant crisis-response platform. Downtime means delayed disaster relief — the compliance architecture had to be built into the product, not bolted on."
CS 04 — Equinox+ Current: "5 brands, one platform, zero to production."
Too thin. This is a Product Design Director role shipping 0→MVP in 90 days for 600K+ premium members across five brands.
→ "Product Design Director. Five brands, 600K+ premium members, zero to MVP in 90 days. 4.8★ App Store."
CS 06 — Allē Current: "Loyalty redesign for 30M medical aesthetics patients."
Scale is there. Leadership signal is absent.
→ "Led loyalty platform redesign for 30M patients across provider and consumer surfaces."
Lab section hierarchy
The count problem. Section copy says "Three live agents built solo." Carousel contains four entries. Both cannot be right.
The canonical set. Three labs constitute external-proof-grade work: Brand Pulse, Retail Velocity, and Carrier IQ. These are published, portfolio-ready agents. UAT Sentinel is not in the canonical external-use set. Remove it from the carousel. The copy then matches reality.
Revised section framing. The current header "When agents do the work" and the framing line are strong. The framing line connects directly to the trust essay's thesis. Tighten slightly:
→ "When agents do the work." (keep) → "Three live agents, built solo, each answering the same design question: when an agent acts on your behalf, what do you need to see to trust it?"
"Built solo" as appositive rather than a separate sentence reduces the self-congratulatory read while preserving the IC proof.
Card order within the lab carousel: Brand Pulse first (76 live signals, strongest decision-surface framing, most direct bridge from the trust essay). Carrier IQ second (operator-trust framing, strongest speed proof). Retail Velocity third (field intelligence, scale proof).
Card ordering — full homepage sequence
The ordering principle: lead with operating altitude, then constraint complexity, then build-from-zero proof, then range.
Case Studies
- CS 01 Alibaba.com — Anchors the evaluator's sense of operating altitude. $50B GMV and 40M buyers set the ceiling.
- CS 03 American Red Cross — Proves constraint dissolution under federal oversight. Most differentiated "speed under consequence" story in the portfolio.
- CS 02 Thermo Fisher — Proves she builds from zero in regulated environments.
- CS 04 Equinox+ — Consumer proof, speed proof (90 days), outcome proof (4.8★). Rounds out the range.
- CS 06 Allē — 30M users, dual-surface. Solid but least differentiated of the five.
Labs
- Brand Pulse — Trust-thesis bridge, strongest decision-surface framing
- Carrier IQ — Operator trust, speed proof
- Retail Velocity — Field intelligence, scale proof
Field Studies
The live section is labeled "03 — Field Studies" with the headline "What stays with me." Both work. Keep them.
- Trust Is the New Interface — The thesis essay. A CPO who reads this before the portfolio evaluates every case study through its lens. That is exactly what you want.
- What Following Taught Me About Leading — Leadership reflection. Personal but relevant. Second position.
What Do You Count When the Playbook Doesn't Exist?— Remove. Verbal-only.
Two essay cards in the Field Studies section. Two strong essays signal selectivity. Three, with one leaking a gated document, signal carelessness.
The Equinox+ teaser page browser title still reads "Equinox+ · Teaser · Juno Chen" with no meta description. Update to "Equinox+ — 0 to MVP in 90 Days · Juno Chen" and add a description matching the revised card line. This is the kind of metadata gap that shows up in link previews when someone shares the page in Slack.
Actions, ranked
Today:
- Remove the "What Do You Count" card from the homepage
- Delete the TinyFish line and "Currently" block from the positioning paragraph
- Remove UAT Sentinel from the lab carousel so the count matches the copy
This week:
- Replace the positioning paragraph with the revised two-sentence professional statement
- Update all five case study card descriptors
- Reorder lab carousel: Brand Pulse → Carrier IQ → Retail Velocity
When you have a focused hour:
- Reorder case study cards: Alibaba → Red Cross → Thermo Fisher → Equinox+ → Allē
- Reorder essay cards, adjust section to two cards
- Update Equinox+ teaser browser title and meta description
- Scroll the full homepage once and check whether the trust thesis reads as a throughline from hero headline to final essay card
The homepage is closer than it was. The headline and title changes from last cycle did real work. But the boundary problems that remain are more conspicuous now precisely because the leadership framing raised the bar. A site that says "Design leader for platforms where trust is the product" and then leaks a gated essay through a public card is contradicting its own thesis at the structural level. The architecture has to prove the argument. Right now it almost does.
- Ramp's Director posting language: Their current Director, Product Design role explicitly says design is "building tools and agents, designing memory, shipping PRs, and defining how design works in an AI-native world," which maps directly to the Trust essay's decision-gate framework and the Agentic Labs proof set.
- Headway's AI-tool expectation: The Design Director, Provider Experience posting names Claude Code, Cursor, and MagicPatterns as expected prototyping tools, which means the AI-native fluency bar is now baked into the job description, not just the culture deck.
- Suno's scale and stage: Their Head of Product Design search comes after a $400M Series D at $5.4B valuation with 100M+ users, making it the highest-ceiling consumer role in the current target set and a strong match for Agentic Labs plus Equinox+ speed proof.
- NIST's expanding trust framework: The AI Risk Management Framework now includes a Trustworthy AI in Critical Infrastructure concept note from April 2026, which gives the trust essay's argument an external policy anchor for regulated-industry outreach at Capital One or Headway.