Verified: July 3, 2026, against live page.
Current State
- Page title — ✅ RESOLVED. Now reads
Thermo Fisher / mySupply — 0→1 Pharma Supply Chain, $20M+ Margin — Juno Chen. Mandate-forward, outcome-loaded, correctly leveled. - Meta description — ✅ RESOLVED. Surfaces 0→1, six partners, nine sites, twelve months, $20M margin, 100% partner adoption, 83% IRR.
- OG tags — ✅ RESOLVED. Title, description, and dedicated
og-cs-02.jpgall carry the leadership framing into Slack previews and email cards. - Outcome metrics in hero — ✅ RESOLVED.
$20M margin opportunity · 100% partner adoption · 83% IRRvisible without scrolling. - Delivery-gate diagnosis — ✅ RESOLVED. The exceptions-at-delivery-gate mechanism and 3–5× cost multiplier appear in the hero intro.
- Full-case gating — ❌ STILL OPEN. The full case study returns HTTP 200 with the complete HTML, then runs a client-side
localStoragecheck to redirect unauthenticated visitors. The login page contains the password hash in delivered JavaScript.
This page is outreach-ready. The metadata and hero fixes alone change how this case registers when a VP Design opens a shared link. H2 headcount budgets start unlocking in the next two weeks (standard enterprise hiring-cycle pattern), and anyone scanning hiring-manager inboxes over a Fourth of July weekend is doing so with fewer competing messages. Use this window. What remains below is one structural issue and two refinements, none of which should delay outreach.
The 2-Second Window
A hiring manager opens the tab. The browser title reads Thermo Fisher / mySupply — 0→1 Pharma Supply Chain, $20M+ Margin — Juno Chen. Before they look at the page, the tab has pre-qualified the case: known enterprise brand, pharma (regulated), 0→1 (builder), $20M+ (real money). A CPO at a regulated platform company or a VP Design at a growth-stage fintech registers all four signals from the tab alone.
The hero eyebrow confirms: Thermo Fisher Scientific · mySupply Digital Supply Chain · 2021. The headline reads The supply chain six partners never had. A product-outcome headline. The design-leadership signal lives in the eyebrow and the role row (Product Design Director), which handle the level while the headline handles the "so what." The split works.
Nothing to fix.
The 8-Second Window
By eight seconds the reader has registered the hero intro and the right-column brief. Both are doing real work.
The intro delivers the business diagnosis: no platform existed, six pharma partners ran nine manufacturing sites on spreadsheets and phone calls, exceptions surfaced at the delivery gate where resolution cost 3–5× more than catching them upstream. A design-leadership read of a business problem. It says: I understood where the money was leaking before I opened Figma. For a regulated-platform hiring manager, that sentence is the one that earns the next thirty seconds.
The brief stacks the proof: client, role, team (1 designer · 2 engineers (BCG DV)), scale (12 months · 6 partners · 9 sites · EU + NA + AU), outcome ($20M margin opportunity · 100% partner adoption · 83% IRR). The BCG DV parenthetical is doing double duty. It explains the small team (consulting engagement, not skeleton crew) and anchors the work to a known entity. For regulated-platform targets, BCG DV reads as serious enterprise engagement. For growth-stage targets where durability is the decoded criterion, the consulting frame can trigger a "did this ship and stick?" question. The teaser doesn't answer it. The full case study is where that evidence lives. Know that the question is forming by second eight if your target is a growth-stage company.
The hero CTA reads Request the full case study and sits at the bottom of the hero's left column. Placement is correct. Copy implies a human-mediated handoff, which creates a natural contact trigger.
The 30-Second Window
Past the hero, the reader hits an app showcase labeled Live Platform · mySupply Dashboard that renders a live iframe of the actual platform interface alongside a phone mockup showing batch detail.
The craft signal is strong. The iframe loads a functional dashboard with KPI cards (OTD, RFT, OTIF, Customer OTD), order exceptions, forecast review, capacity alerts. Real data labels. Real interaction patterns. Real domain vocabulary. LATE, AT RISK, ON TRACK, HOLD, RESOLVED are the language of pharma supply chain operations, rendered in a live component rather than a static screenshot. A hiring manager at a regulated platform recognizes immediately that this person has shipped production software in a domain where the terminology carries operational weight. Visual comps never communicate that.
Below the showcase, a bento section delivers design-system evidence: color tokens, status badges, type scale, KPI components, a partner scorecard, a manufacturing-utilization heatmap, a regulatory-framework module. Each component includes a one-line annotation connecting the design decision to a business mechanism. The partner scorecard: first time all six pharma partners saw each other's delivery performance in one place. The utilization heatmap: Ferentino ST2 at 107% was the conversation that recovered $2M. Those annotations are what keep the bento section from reading as a design-system dump. Strip them and you have a component library. The annotations turn every module into business-justified evidence at scan speed.
The closing section reinforces the core mechanism: Five failure modes. Five modules. Zero spreadsheets. Second CTA. Footer navigation to adjacent cases. Density is appropriate for a teaser. Enough to establish credibility and create curiosity without giving away the narrative arc.
The Gating Problem
Both CTAs link to cs-02-supply-chain.html, which returns the full case study HTML with HTTP 200. A script then checks localStorage.getItem("pf_access_v1") and redirects unauthenticated visitors to a login page. The login page contains the SHA-256 password hash in client-delivered JavaScript.
Will a hiring manager notice during a scan? Almost certainly not. They'll click, see the login screen, email you or enter a password. The flow functions.
It matters anyway. This portfolio's strongest positioning argument for regulated-platform companies is that you understand trust as a design material. The Thermo Fisher case is about making exception data visible to the right people at the right time with the right permissions. The Red Cross case involves multi-role permission-aware architecture. If a technical evaluator or a security-minded CPO inspects the gating mechanism and finds that "private" means "the HTML is fully delivered and a client-side script hopes you don't look," the portfolio's positioning claim and its own implementation are saying different things.
Move gating server-side. Return a 401 or 302 before the HTML body is delivered. Remove the password hash from client-delivered JavaScript. If the full case content should not be publicly accessible, do not deliver it publicly and rely on JavaScript to hide it.
Outreach can go today. The contradiction erodes narrative consistency for the specific audience segment where this case is strongest.
Punch List
P0 — Do before next outreach
Nothing. The page converts at scan speed. The title, metadata, hero structure, outcome placement, and craft evidence are all working. Go.
P1 — Do this week
- Move full-case gating server-side. Return 401 or 302 before delivering HTML. Remove the password hash from client JavaScript. The current implementation contradicts the trust-design positioning that makes this case valuable to regulated-platform targets.
P2 — When convenient
-
Add a "still live" or "in production" date stamp to the app showcase. The iframe loads a functional platform. Nothing on the teaser page explicitly says this is production software still running. A single line like
Platform live since 2021 · Last data sync [date]converts the craft signal into a durability signal. That matters when the team line says BCG DV and the reader is wondering whether this shipped and stuck. -
A/B a design-leadership headline against the current one. The current headline works as a product-outcome hook:
“"The supply chain six partners never had."
For outreach to VP Design or Head of Design roles at regulated platforms, test:
“"Thirty-two interviews. Five failure modes. One platform."
This foregrounds the diagnostic act (the warehouse-floor research that converted five failure modes into five modules) rather than the product outcome. The current headline lands on what was built. The variant puts the research methodology in the first line. For regulated-platform outreach where the decoded criterion is "does this person treat domain constraints as the design material," the variant hits that criterion before the reader scrolls.
Three items. The page earned a short list.
- Headway's Provider Experience posting explicitly combines EHR workflows, AI-powered clinical documentation, and insurance verification, making it the cleanest regulated-platform bridge to this Thermo Fisher case in the current Headway design director opening.
- Gusto's payroll design role names automation and AI initiatives that reduce manual work without compromising accuracy or trust, language that maps directly to the exception-upstream mechanism in this case, as visible in the Senior Product Design Manager posting.
- The Trust essay's Thermo Fisher section ties the Decision Gate to continuous agents plus a non-negotiable human QA release gate, giving you a ready-made verbal bridge between this teaser and the AI-native positioning in Trust Is the New Interface.
- Ramp's Director, Product Design posting describes design building tools and agents, designing memory, and shipping PRs, and its adjacent Agentic CX role describes a human-operator-plus-AI-agent model that rhymes with the multi-role permission architecture in this case and Red Cross.