Gating status
The full case page returns HTTP 200 with the complete HTML payload before any client-side localStorage check runs. The redirect to login.html fires after the browser has already received every word, every annotation, every outcome metric. A panelist who opens DevTools sees the entire case in the network response.
The risk profile here is different from a private essay. A private essay behind this same gating model exposes confidential content to anyone who reads the network tab. A portfolio case study exposes something else: evidence that you shipped a security model that does not actually secure anything. The content itself is material you share post-booking, so the exposure is low. What matters is what it says about your implementation judgment to a technically literate buyer who inspects the access model and finds it decorative. That question lands with particular weight when you're interviewing for a role where you'd own product quality. Flag it for your engineer. Server-side auth or accept the exposure.
One detail that will bother a careful reviewer: the URL says cs-01-alibaba but the sidebar navigation labels this as case 02. Pick one numbering scheme. Make it consistent everywhere.
The through-line a panelist will find missing
Before the dimension-by-dimension read, here is the single finding that matters most.
Strong research inputs. Clear design moves across three sprints. Specific outcome metrics. The case proves you can do the work. And nowhere in it does a decision carry a visible cost. There is no moment where two viable paths existed and you chose one at a price. A skeptical Director+ panel will probe that absence immediately, because it is the thing that separates a redesign story from a leadership story.
Everything below maps to a single structural absence: the case never shows what a decision cost. Five or six sentences distributed across the case close that gap and move you from "strong designer" to "design leader I'd hire to run my org."
1. Problem diagnosis — who owns the insight?
The hero section does the right thing. It says you named the 25%/80% gap, built the research case, secured the mandate, redesigned the experience. Ownership language. A panelist scanning the top of the case gets the signal: Juno saw something the organization had not articulated and turned it into a program.
The diagnostic section immediately below softens that ownership. The 32 interviews, Baymard audit, and gaze tracking converge on a conclusion. The three discovery cards organize the failure pattern cleanly. But the framing shifts from "I named this" to "the evidence showed this." The analytical step connecting raw data to the 25%/80% executive framing disappears. The hero claims you made the move. The evidence section reads like the move made itself.
Add one sentence at the top of the diagnostic section that narrates the analytical step. Something close to: "The raw data showed fragmented symptoms. I reframed them around a single number: desktop carried 80% of transaction value on 25% of traffic, and we were designing it like a consumer browse channel." That sentence bridges the ownership claim and the evidence. Without it, a panelist will spend interview time asking whether you identified the problem or inherited it. The case should answer that before the interview starts.
2. Research-to-mandate chain — where is the executive decision?
You name the research inputs. You state the conclusion. You say you secured the mandate. The mandate moment itself is a black box. Who approved it? Was it a deck to a VP, a quarterly planning negotiation, a Slack thread with a GM? What did the org deprioritize to fund three sprints of desktop redesign on a platform investing heavily in mobile?
A panelist evaluating you for Director+ assumes you can do research. They want to see whether you can convert research into organizational permission to act. That conversion is the hardest part of senior design leadership and the part most portfolios skip. Right now the case jumps from "evidence converged" to "three sprints." The panelist has to take on faith that you drove the transition.
Insert a two-to-three-sentence mandate block between the diagnostic section and Sprint 01. Name the audience for the research case. Name what you asked for. Name the constraint or tradeoff leadership accepted. If the mandate came easily, say so and say why. If it required negotiation, say what you traded. Senior judgment lives here, and right now it is invisible.
3. Design decisions per sprint — rationale versus output
Sprint 01 is your strongest sprint. Named stakeholder concern: the PM worried sign-in would drop when the EIN wall was removed. Design bet: browse-first entry without the credential gate. Result that resolved the concern: +4% sign-up rate. Problem, bet, concern, resolution. Sprint 01 proves you can hold a position against internal resistance and be right.
Sprint 02 is weaker. The design move is clear. Trust signals and sourcing criteria move from PDP-level inspection to card-level visibility. Response-rate sorting becomes a first-class control. The 34% adoption of response-rate sorting in month one is strong validation. But the rationale reads as "buyers had to open too many PDPs," which stays at the level of problem statement and never reaches design rationale. Why card-level trust badges rather than a comparison-table view? Why response-rate sorting rather than a composite trust score? The sprint documents what you built. The choices you rejected stay invisible.
Sprint 03 has the same gap. Moving from inquiry-only pricing to inline tier pricing with a live calculator is significant. The 47% reduction in buyer-reported security concerns is a strong outcome. But the sprint reads as before/after, as output without decision narrative. A panelist will ask: "Why a calculator instead of a quote-request flow? Why tier pricing above the fold instead of behind a qualification step?"
For Sprints 02 and 03, add one sentence each that names the alternative considered and why you rejected it. "We considered a composite trust score but found in testing that buyers wanted to weight criteria differently depending on order size" is one sentence that turns a sprint from output documentation into decision documentation.
4. IC+manager proof — who did you lead?
The role block says Head of Design & Research, North America. The team block says Design, Research, PM, and Engineering. First-person authorship throughout.
None of this tells a panelist what you led versus what you personally did. Did you manage the researchers who ran the 32 interviews, or conduct them yourself? Did you direct a design team through three sprints, or produce the work as primary IC? Did you coordinate with a PM partner, or did PMs report to you? The single PM mention in Sprint 01 is the only moment where a cross-functional partner appears with a specific point of view. Even that partner is unnamed and uncontextualized.
At Director+, a panelist is answering two questions simultaneously: Can this person still do the work? Can this person get the work done through others? Your case answers the first well. The second is unaddressed.
Add role-credit specificity in two places. First, in the hero or diagnostic section, state team size and composition. "I led a team of X designers and Y researchers" is concrete. Second, in at least one sprint, name a moment where you directed rather than executed. "I assigned the gaze-tracking study to a researcher and used the findings to reframe the Sprint 03 hypothesis" shows management. "I partnered with the PM lead to negotiate sprint scope against the mobile roadmap" shows cross-functional leadership. You do not need to name every person. You need to name enough to prove the team was real and you were running it.
5. Tradeoffs — the single biggest gap
Sprint 01's PM concern is tradeoff-adjacent. It shows someone pushed back and you held your position. But the framing stays at concern-resolved-by-results. A genuine decision where you accepted a real cost would land harder.
Sprint 03 is the natural home for a real tradeoff narrative. You moved from inquiry-only pricing to transparent tier pricing above the fold. That decision has an obvious cost: it reduces the supplier's ability to price-discriminate by buyer intent. It potentially commoditizes suppliers who previously used the inquiry wall as a qualification filter. If suppliers pushed back, say so. If the business team worried about supplier churn, say so. If the supply-side team accepted the tradeoff because transaction volume would compensate, say so. A Ramp panelist will hear "transparent pricing above the fold" and immediately connect it to their own pricing surfaces, their own tension between buyer clarity and business flexibility. Show them you've lived inside that tension and made a call.
If Sprint 03 does not have a clean tradeoff, Sprint 02's decision to surface response rate as a primary sort criterion also carries cost: it penalizes suppliers in different time zones or with smaller teams, and it creates incentive to game response metrics. If you weighed that and decided the buyer-side benefit outweighed the supply-side risk, that is worth showing.
Pick one. Write it as a short paragraph that names the viable alternative, the cost of your chosen path, and why you accepted that cost. This is distinct from the "why this and not that" rationale I flagged in Section 3. Rationale shows why your direction was the better bet. A tradeoff shows what you knowingly gave up. Both matter. A panel will probe the tradeoff harder, because it proves you understand second-order consequences.
6. Agentic sourcing vision — grounded but ungoverned
The closing vision is structurally sound. It maps directly onto the three surfaces you redesigned. Chat captures intent. Search qualifies suppliers against trust and price parameters. PDP confirms pricing and lead time before order completion. The 500-custom-bottles scenario is concrete and testable. The vision earns its place because it grows from the case's logic rather than arriving from outside it.
Two problems.
First, the vision shows autonomous completion but never shows where the agent pauses for human judgment. The scenario ends with a primary "place order" action and secondary options to request a sample or compare more suppliers. You don't need to design a full enterprise procurement governance model in a portfolio vision section. But you do need to signal that you've thought about the trust-loop problem. Add one moment in the scenario where the agent surfaces a decision point back to the buyer. Something as simple as the agent flagging that a supplier's lead time is tight against the buyer's deadline and asking whether to proceed or widen the search. One moment of human re-entry shows you understand when AI should stop and ask. An enterprise design org evaluating you for Director+ will care about that instinct more than the automation itself.
Second, the vision does not connect back to the trust architecture you built in the case. You spent three sprints proving that trust signals, transparent pricing, and Trade Assurance reduce buyer anxiety and increase conversion. The agentic vision uses those same signals as machine-readable inputs. Say the quiet part loud: the reason an agent can make this decision is because you already structured the data it needs. Add one sentence making that link explicit. The trust infrastructure you built for human buyers is the same infrastructure that makes agentic sourcing possible. That sentence turns the vision from speculation into the logical conclusion of the case.
Punch list, ranked by panelist conviction impact
Hiring committees reconvene the week of July 7. The long weekend is your window.
-
Add one tradeoff narrative in Sprint 03 (or 02) and add design-rationale sentences to both. Two related but distinct moves. The tradeoff shows what you knowingly gave up by choosing your path. The rationale shows why your path beat the alternative on its own terms. Sprint 03's transparent-pricing decision is the cleanest place for the tradeoff. Sprints 02 and 03 each need one sentence of "why this and not that." Highest-impact change. Do it first.
-
Insert a mandate block between diagnostics and Sprint 01. Name who you presented to, what you asked for, what the org traded. Proves you convert research into organizational action.
-
Add role-credit specificity. Team size, composition, at least one directed-not-executed moment. Without this, a panelist cannot distinguish Head of Design from senior IC with a generous title.
-
Add one sentence narrating your analytical step from raw signals to the 25%/80% executive framing. The hero claims it. The evidence section should show it.
-
Connect the agentic vision back to the trust infrastructure, and add one human-judgment moment to the scenario. Two sentences total. Turns speculation into conclusion and signals governance awareness.
-
Fix the case numbering inconsistency between URL and sidebar. Minor, but a detail-oriented panelist will notice.
-
Flag the client-side gating to your engineer. Not urgent for conviction. Real credibility risk if inspected.
The research evidence is substantial. The outcomes are specific. Sprint 01 holds up under scrutiny. The agentic vision earns its place. What the case is missing is proof of the thing that separates a strong designer from a design leader: the willingness to show what the decision cost, who you brought along, and why you chose this path when another was available. That proof is five or six sentences distributed across the case. Write them before panels resume next week.
- Ramp's agentic CX role: Ramp's live Product Manager, Agentic CX posting defines the human-operator and AI-agent division of work, which means the tradeoff narrative you add to Sprint 03 could directly feed Ramp outreach positioning.
- Capital One's AI-in-design-org role: The live Director, AI in Experience Design posting asks for someone to change how an entire design organization works with AI tooling, so the agentic vision's governance gap matters even more if Capital One is on your list.
- Suno's Head of Product Design: Suno's Head of Product Design role spans product design, design engineering, and UXR, making the IC+manager proof fix in this case directly relevant to how you'd present Alibaba in that conversation.
- Client-side gating across all cases: The same localStorage vulnerability confirmed on cs-01-alibaba also affects cs-02, cs-03, cs-04, and cs-06, so the engineering fix should cover the full set rather than one page at a time.