The Red Cross Teaser Has the Right Evidence Under the Wrong Headline

Current-State Verification

Fetched junochen.com/cs-03-red-cross-teaser on July 24, 2026. Page is live, last modified July 19.

What's working. Title tag and meta description are mandate-forward: 0→1, six legacy systems replaced, national deployment, 1,689 cases. The brief panel on the right side of the first screen lists role (Product Design Director / GM), team composition, scale (6 months, national, 6→1), and outcomes ($847K disbursed, 1,689 cases in 2 weeks). Six act sections organize by operational role. If a CPO read only the metadata, they'd get the right story.

What's still open. The platform-consolidation vs. decision-architecture framing risk flagged in the prior audit has not been resolved. "Decision architecture" appears nowhere in the teaser HTML. Neither does "trust." The Trust essay frame ("a disaster-relief platform where the wrong caseworker decision was not a UX error") is absent entirely. The CTA still links to a gated full case page behind a client-side password wall, which I flagged in Issue #3 as contradicting your trust-architecture positioning. Still contradicts it.

The humanitarian framing actively triggers the wrong buyer category. A regulated-platform CPO scanning teasers is running one filter: "has this person built systems like mine." A headline about the worst day of someone's life matches to nonprofit, empathy-led design culture. That is a real hiring archetype, but it is not the one Ambience or PointClickCare is filling. The teaser has the evidence a regulated-platform buyer needs. The headline tells that buyer to keep scrolling.

Everything below follows from this.

First-Screen Hierarchy (P0)

The H1 says this is a story about displaced families. The buyer at a regulated platform company needs it to be a story about a sole design leader who built decision architecture for a national system in six months, where caseworker errors carried federal consequences.

The brief panel does the heavy lifting: role, team, scale, outcomes. But the H1 anchors the read. A CPO scanning in 8 seconds registers the headline and maybe one metric. Right now they register empathy and a number. They should register scope and consequence.

Replace the H1. Move the humanitarian frame to a subhead. The mission is the setting, not the headline.

Current H1:

Replacement H1:

Replacement subhead:

The emotional weight of "worst day of someone's life" is real. It belongs in the intro paragraph, after the mandate is established. The setting is a disaster shelter. The headline is the scope of what you built and the constraint you built it under.

Decision-Architecture Language (P0)

The teaser uses all the components: eligibility checks, identity verification, approval queue, exception approval, fraud detection, audit record. It never names the pattern they add up to. So it reads as a feature tour when it should read as a story about designing the moments where humans make consequential calls under time pressure.

Your buyers use this vocabulary explicitly. PointClickCare's VP Design posting says "decision rights," "high-confidence decision-making," "accountability models." Ambience's Staff Designer posting says "complex workflows," "high-stakes workflows." Both describe the same design problem: who decides, with what evidence, under what constraint. Your teaser shows the answer. It never names the question.

Add one sentence to the first-screen intro:

That sentence reframes the entire teaser from platform consolidation to decision architecture. And it creates vocabulary continuity with the Trust essay. A PointClickCare VP who reads the Trust essay and then hits this teaser should recognize the same mind at work. Without it, they see a platform-consolidation case that happens to involve caseworkers. With it, they see a design philosophy applied to a specific domain. That is the difference between "interesting background" and "she thinks the way we need someone to think."

Outcome Proof at Scan Speed

Metrics work. $847K disbursed, 6→1 system consolidation, 1,689 cases in 2 weeks all appear in the brief panel. A scanning buyer registers at least one without scrolling.

P1: Add one metric and reorder. The full case HTML includes 98.7% FEMA compliance. That number does more work than $847K for a regulated-platform buyer. $847K proves throughput. 98.7% FEMA compliance proves the decision gates held under real volume. A VP at PointClickCare or a risk-systems buyer at Stripe does not care how much money moved. They care whether the system prevented the wrong money from moving. Lead with governance:

Craft Signal in the Act Sections

The six acts organized by operational role (Field Volunteer, Caseworker, Finance Officer, Supervisor, Program Director) show role-specific decision surfaces, not generic screens. Act 03 (Verification) and Act 05 (Eligibility / Approval Queue) are the strongest because they show where the system enforces human judgment gates.

The framing undercuts them. Each act describes what the surface shows rather than what design decision it embodies. Act 05 says the design move was queue-based prioritization instead of case-by-case sorting. That is a real decision with real consequence: it removed a caseworker choice that introduced bias and delay. But the copy treats it as a feature description, not a design argument.

P1: For Acts 03 and 05, add one sentence naming the design decision and its consequence. Act 05 example:

That language already exists in the closing section. Move it up into the act where it belongs. A scanning buyer has stopped reading by the closing.

Density (P1)

Six acts plus a closing section plus two CTAs. Too long for a teaser. A teaser earns the click-through. The current structure gives enough that a buyer might feel they've seen the work without requesting access. That defeats the gate.

Collapse to three decision tiers: field intake (low-consequence, speed-optimized), caseworker verification (high-consequence, evidence-gated), supervisor oversight (system-level, exception-driven). Six acts organized by role is the full case's job. The teaser's job is to prove you designed a decision hierarchy. Three tiers tell the buyer: she thinks in systems of escalating consequence. Six role-based acts tell the buyer: she organized a lot of screens by persona. A PointClickCare VP hires for the first framing.

CTA and Destination

CTA copy ("Request the full case study") is fine. The destination is the problem. The gate requires a password via a client-side localStorage check. I covered the security and positioning problems in Issue #3: the full HTML ships before the redirect fires, and a client-side gate on a trust-architecture portfolio is a contradiction the wrong buyer will notice.

P1 (carried forward). Replace the bare password field with a professional access-request form. Add a line: "The full case includes the data model, the design system constraints, the FEMA compliance architecture, and the 2026 agentic redesign."

Homepage Card

Outside the six audit dimensions, but it matters. The homepage card is the buyer's first encounter with this case before they reach the teaser. The card tags (Case Management, Financial Services, Regulatory Compliance, Mission Critical) are in the right register. The description frames the work as six legacy systems unified into one crisis-response platform. Close.

Here is the problem: if the homepage card primes "platform consolidation" and the teaser opens with "worst day of someone's life," the buyer has been told the wrong story twice before reaching the brief panel that actually tells the right one. Prime the same story the revised teaser leads with.

P2: Revise the card description:

Priority Summary

Priority	Recommendation	Impact
P0	Replace H1 with mandate-scope headline; move humanitarian frame to subhead	First-screen read changes from empathy story to leadership-scope story; stops triggering wrong buyer category
P0	Add decision-architecture sentence to first-screen intro	Connects teaser to buyer vocabulary at PointClickCare, Ambience; creates vocabulary continuity with Trust essay
P1	Add 98.7% FEMA compliance to outcome row, reorder to lead with governance	Proves decision gates held under volume, not just throughput
P1	Surface design-decision language in Acts 03 and 05	Moves craft signal to where the buyer is still reading
P1	Collapse six acts to three decision tiers	Tightens teaser for scan speed; frames the work as decision hierarchy, not persona tour
P1	Improve gated-page landing experience	Carried forward from Issue #3
P2	Revise homepage card description	Primes the buyer correctly before they reach the teaser

The brief panel, the metrics, the role-specific surfaces: all strong. All defensible. The hierarchy is wrong. You lead with empathy and let the buyer discover the mandate. Lead with the mandate. Let the empathy give it weight. A CPO at a regulated platform company does not need to feel moved by disaster relief. They need to see, in 8 seconds, that you built consequential decision architecture under constraint, at speed, at national scale, and that it held. That proof is on this page. It is underneath a headline that tells the buyer to look somewhere else.