Allē Full Case Audit — What the Decision Blocks Prove and Where They Go Silent

Verified State — July 10, 2026

The full Allē case returns HTTP 200 with complete HTML before any access check executes. Same client-side localStorage gate documented for other pages: the browser delivers every section, every mockup, every metric, then a script checks for a flag and redirects to /login.html if it's missing. Password validation lives entirely on the login page via SHA-256 hash comparison. Anyone with a direct URL or a curl command gets the full case without authentication.

Two additional site-integrity issues surfaced. The nav links to human.html, which returns a 404. And the case is numbered inconsistently: the homepage card labels it Case Study 06 while the teaser and full case hero both show 05. A panel member who clicks around will notice. Small inconsistencies create a permission structure for doubting the big numbers.

Six things a Director+ panel evaluates in a case like this, assessed against what's currently on the page.

The Decision Format Is the Asset. Everything Below Protects It.

The A·01 through B·03 notation, with before-state and after-state framing for each decision, is the structural feature that separates this case from every process-narrative portfolio piece a panel has seen this quarter. It signals that you think in discrete, defensible choices rather than linear timelines. A CPO scanning this case registers the format before reading the content, and the format alone communicates a design leader who decomposes complex systems into bounded decisions with traceable rationale.

Every recommendation below preserves this format. The audit is about whether each decision instance delivers on the promise the format makes.

1. Unified Strategic Premise Before the Tracks Diverge

Assessment: Present but underloaded.

The case establishes a premise before splitting into consumer and provider tracks. "Loyalty in medical aesthetics is a trust problem rather than a rewards problem" appears in the problem section, and the before/after diagnostic table maps the old transactional spine against the new relational one. Right instinct.

The gap: the premise tells the reader what the reframe is. It never gets to why the reframe demands two surfaces. A panel member reading this needs to understand, in two sentences, why a trust-based loyalty program structurally requires both a consumer app and a provider dashboard to function. The framing says the program had two user groups with two failure modes. That describes scope. The strategic argument for why the scope had to be shaped this way is missing.

Add one paragraph between the premise and the track split that makes dual-surface scope feel inevitable. Something close to:

That's the strategic sentence the case is missing. It turns "we redesigned two things" into "the system required two surfaces because trust is produced in one and maintained in the other."

The Allē teaser closes with stronger language than the full case has anywhere: "the same loyalty logic runs both surfaces from one information model, not two products sharing a brand." That sentence belongs in the full case's approach section, not buried in a teaser closing. The full case is the artifact the panel reads. The teaser's best strategic framing should live where it matters most.

2. Each Decision Names Rejected Alternatives

Assessment: Before/after is strong. Rejected alternatives are absent.

Every decision block shows what existed (static balance, alphabetical list, generic broadcast) and what replaced it (milestone architecture, urgency sort, provider-voice campaigns). Good. But "what existed before" and "what else we considered" are different questions. The case answers the first and skips the second.

A·01 replaces the static balance with milestone architecture, expiry alerts, and referral modules. Why milestone architecture over a gamified streak system? Over a simple dollar-equivalent display? Over a tier-countdown progress bar without the expiry mechanic? B·01 defaults to expiry-soonest sort. Why not a composite urgency score weighting tier proximity, visit recency, and expiry together? I can't see from the case what alternatives were actually on the table. Neither can the panel.

The design-system explorations (Noir, Blush, Prism, Veranda on consumer; Analytics, Daylight, Ember, Canvas on provider) are the closest the case comes to showing alternatives. Four distinct visual directions with named rationale for each. But they sit in their own section, disconnected from the decision blocks. They show aesthetic alternatives, not structural ones.

For each decision block, add one line: "We considered [alternative] and rejected it because [reason]." You don't need drama. Even "We tested a composite urgency score but providers couldn't explain the ranking to patients, so we defaulted to the single most legible signal: expiry date" is enough. The point is to show the decision was deliberate, that alternatives existed and were weighed. Director+ panels evaluate judgment. Judgment requires evidence of that weighing.

For the design-system explorations, pull one or two into the relevant decision blocks as "direction we explored and moved past" rather than keeping them in a separate gallery. A standalone gallery reads as visual craft showcase. Inside a decision block, the same explorations become evidence of strategic evaluation.

3. IC+Manager Proof Woven Into Narrative

Assessment: This is the largest gap in the case.

The hero identifies you as Product Design Director leading three product designers plus UX research and brand. That is the only leadership signal in the entire case. The narrative doesn't show you directing those designers, making a scope call, convincing a stakeholder, managing an escalation, navigating a tradeoff with engineering or product management, or deciding what not to build.

Every decision block reads as "we did X." The "we" is doing enormous work, and a Director+ panel will notice. They will wonder: did she do the design work, or direct the team that did it? Did she set the strategy, or execute someone else's? Did she fight for the dual-surface scope, or was it handed to her?

The case provides zero answers. And the companies you're targeting at this level evaluate diagnosis, mandate creation, cross-functional influence, and ambiguity handling. A case that shows only design output, however strong, reads as senior IC work. The title says Director. The narrative needs to prove it.

Insert leadership context at three to five specific moments in existing decision blocks. This doesn't require a rewrite. It requires sentences. Examples of what to surface:

• Scope decision. Who decided this was a dual-surface redesign rather than a consumer-only refresh? If you made or influenced that call, say so. If you argued for provider-side scope against a stakeholder who wanted consumer-only, that's a Director-level story.
• Team direction. In A·02 or B·03, name which designer owned the surface and what your role was. "I directed [designer] on the care-plan flow while I owned the provider campaign architecture" is one sentence that changes how the entire case reads.
• Stakeholder navigation. Allergan/AbbVie is a pharmaceutical company. Someone on the business side had opinions about how the loyalty program should work. If you navigated competing priorities between brand, provider relations, and product, that's Director evidence.
• Tradeoff or cut. Any moment where you chose to cut scope, delay a feature, or override a recommendation. These are the decisions that separate directors from senior ICs.

Two or three of these, placed inside existing decision blocks as single sentences, would transform the case's leadership signal entirely. And every one of them must survive the backchannel test: would a former colleague repeat the same version when you're not in the room?

4. Consumer and Provider as One Loyalty Logic

Assessment: Framed at the top and bottom. Missing in the middle.

The approach section says two user groups, two failure modes. The closing says the redesign was built for the relationship. Between those bookends, the two tracks run in parallel with almost no cross-reference. Track A never mentions how a consumer action creates a signal that surfaces in the provider dashboard. Track B never mentions how a provider action (sending a reactivation campaign, applying a birthday offer at checkout) changes what the member sees in the app. The expiry mechanic appears in both tracks, but the case never explicitly says: this is the same data event, surfaced differently for two audiences, because the loyalty logic is one system.

Add two to three cross-references between tracks. After A·01's expiry alert, one sentence: "This same expiry signal surfaces in the provider dashboard as a priority-sort trigger (B·01), so the member and the practice see the same urgency from different angles." After B·02's patient-context checkout, one sentence: "The tier proximity the provider sees here is the same milestone the member tracks in their Progress tab (A·01)."

Connective tissue that makes the dual-surface architecture legible as a single system. A panel reading the current version sees two parallel redesigns that happen to share a client. Add these cross-references and they see one information architecture expressed through two interfaces. The second is a harder, rarer design problem, and it's the one that's true.

5. Outcomes Attributed to Specific Decisions

Assessment: Partially strong, with one critical gap.

The case attaches outcomes to decisions at several points. A·01 ties the 47% open rate to expiry push notifications. A·02 ties 2.4× conversion and the CAC drop from $92 to $42 to in-app planners. The return-mechanics section ties 68% of reactivating members to expiry notifications. Better attribution than most Director-level cases manage.

The gap: 3.2× redemption is the hero metric, the number that appears first, and it floats without attribution. Which decision or combination of decisions drove it? A panel member who sees 3.2× in the hero and never encounters it again in a decision block will wonder whether it's real or aspirational. That's a credibility tax you don't need to pay.

A related credibility risk: the problem section references 18 million enrolled members while the hero and scale fields claim 30M+. Both may be accurate at different points in the program's timeline, but the case doesn't explain the difference. A panel member who catches two member counts in the same artifact will apply that inconsistency to every other number on the page, including the ones that matter most.

Second gap: the provider track carries no attributed outcomes at all. B·01's urgency sort, B·02's patient context, B·03's provider campaigns. None carry a metric. If provider-side metrics exist (practice engagement rate, campaign send rate, provider retention), surface them. If they don't, acknowledge that the provider surface was measured through its effect on consumer-side metrics. That's a legitimate framing, and actually a sophisticated one: it says you understood which surface was the leading indicator and which was the mechanism.

Anchor 3.2× to a specific mechanism or explicitly frame it as compound effect. Resolve or explain the 18M/30M discrepancy with a single clarifying phrase. Add at least one provider-side metric, or explain the measurement-through-consumer-signals logic.

6. Regulated Constraints as Design-Shaping Forces

Assessment: Nearly invisible. This costs you twice.

This case operates inside Allergan Aesthetics under AbbVie. The product involves medical procedures (BOTOX, Juvéderm, Latisse), treatment photography (before/after images of patients' faces), provider-patient communications sent under practice names, and pharmaceutical brand messaging. Every one of these carries regulatory, compliance, or privacy implications that would have shaped design decisions.

The case mentions none of them. HIPAA considerations for treatment photos, pharmaceutical marketing regulations for the provider campaign builder, AbbVie's brand compliance requirements, the consent architecture required for before/after photo capture in a medical context. All absent.

First cost: it removes a layer of complexity that would make the design work more impressive. A before/after photo capture flow is solid design work. Add medical privacy requirements and a first-time patient using it in a clinical setting, and you have a Director-level problem.

Second cost: it removes the speed-under-consequence signal that differentiates your background. Companies acquiring regulatory surface area need leaders who have shipped under real constraints. That's most of the growth-stage companies posting Director+ roles right now. This case proves you have that experience. It just doesn't say so.

Add constraint language to three decision blocks. A·03 (photo capture): what privacy or consent requirements shaped the flow. B·03 (provider campaigns): what pharmaceutical communication regulations constrained the campaign builder. Design-system explorations: if AbbVie brand guidelines limited color, typography, or imagery choices, name the constraint. Even brief references ("AbbVie's pharmaceutical marketing guidelines required [X], which meant we couldn't [Y], so we [Z]") transform background context into evidence of design judgment under real operational pressure.

Priority-Ranked Fix List

P0 — Fix before the next share

• Gating vulnerability. Server-side authentication or remove the implication of protection. Full case HTML is exposed on fetch.
• IC+manager proof. Insert leadership context at three to five points in existing decision blocks. Scope decisions, team direction, stakeholder navigation. This is what Director+ panels evaluate and the case currently provides zero evidence.
• 404 nav link. human.html returns 404. Remove or fix.

P1 — Fix this week

• Regulated constraints. Add constraint language to A·03, B·03, and design-system explorations. Low effort, high signal. Activates the speed-under-consequence positioning that differentiates your background.
• 3.2× attribution. Anchor the hero metric to a specific mechanism or explicitly frame it as compound.
• Cross-track connective tissue. Two to three sentences linking consumer and provider decisions to the same underlying data events.
• Page title. The full case title reads "Allē · Juno Chen." The teaser title carries dual-surface, 30M members, 40K practices. The full case title should carry at least as much signal. This is what appears in browser tabs and Slack previews when a hiring manager forwards the link to a panel. If the tab reads "Allē · Juno Chen" while a competitor's case reads "Enterprise Design System — 40M Users — Director Case Study," you've lost the framing before the page loads.

P2 — Fix before next revision cycle

• Rejected alternatives. One line per decision block naming what was considered and why it was rejected.
• Provider-side outcomes. Add metrics or explain the measurement-through-consumer-signals logic.
• Unified premise paragraph. Make dual-surface scope feel strategically inevitable rather than organizationally given.
• Consistency fixes. Resolve the 05/06 numbering conflict, the 18M/30M member-count discrepancy, and the 2020/2021 date inconsistency between full case and teaser. A panel that catches these will discount the precision of everything else.

The decision-notation format is the right architecture. The metrics are real and distributed well. The dual-surface scope is genuinely impressive at Director level. What the case still lacks is the connective tissue that turns strong design output into legible design leadership. Add the leader to the decisions, and this case does what it needs to do.