Capital One R249772 — The Mandate Is the Design Org Itself

Phase 1 — The Moment

Capital One reposted this role on August 21 under a new requisition number. The earlier search (R243245) ran through July; the Timeline Reconstruction in this issue covers that sequence. The slate reset yesterday. The first review batch has not formed yet.

What the posting assigns is unusual for a Director title at this company: tooling roadmaps, process evolution, talent upskilling, workforce transformation. It assigns no product surface, customer journey, or design team. Compare Capital One's Customer Acquisitions Director posting, which hands the hire revenue-generating experiences and customer-facing designers. This one hands the hire an internal capability.

The real mandate: define how Capital One's several-hundred-person Experience Design organization works with AI. The object being designed is the organization's practice.

Geography: McLean, San Francisco, or New York. Hybrid, three days in-office. SF clears.

Urgency: Act within 7 days. Posting is one day old. Enterprise first-batch review typically begins in week two, which leaves roughly six days at full positioning advantage.

Phase 2 — Portfolio Mapping

Positioning archetype: Enterprise Design Org Transformation. Trust essay and Agentic Labs lead. Case studies are secondary enterprise credibility.

The renewed posting adds workforce-transformation language the earlier version didn't carry, which supports the Persona Decoder's read: Jorge evaluates operating-model understanding before she evaluates conventional product-case strength.

Lead with the Trust essay, framed as an operating methodology this org could adopt. Watch, Verify, Delegate gives an individual designer a decision framework for AI output and gives a design leader a maturity ladder for measuring where teams currently sit. The five handoffs are concrete enough to structure training, design reviews, and tool-adoption criteria across several hundred people. That is the specific translation to make in every artifact: the framework was written for user-agent interfaces, and you are applying it to designer-AI workflows.

Agentic Labs is the production proof. Brand Pulse, Retail Velocity, Carrier IQ — solo-built, live, real APIs and live agents — show the methodology produces working systems, not a position paper.

Forward-looking artifacts demonstrate what you'd install at scale, and the Human-Agent System Design domain maps directly onto the designer-AI workflow problem. Check junochen.com for current artifact status before you send. If published, reference alongside the Trust essay. If in progress, move now with what you have. The first-batch window is worth more than a complete artifact set.

Alibaba carries enterprise credibility: you diagnosed a structural gap on a $50B+ GMV platform, built the mandate yourself, and moved daily transactions +20% and NPS +2.2pt. It proves you can move a large organization through diagnosis into cross-functional execution.

Thermo Fisher (Product Design Director, BCG Digital Ventures) covers regulated-environment navigation: six pharma partners, 100% adoption, $20M+ margin recovered inside compliance constraints.

TinyFish is technical currency. Most recently as Head of Product, you shipped AI-native enterprise tools in production and worked through agent traces, auditability, and governance. That production history is what makes the Trust essay credible as practitioner methodology rather than commentary.

Objection. You have not transformed a several-hundred-person design organization's AI practice, and the posting asks for exactly that. The answer is that the Trust essay supplies the methodology, Agentic Labs shows it running, and Alibaba shows you moving a large org through structural diagnosis. No external candidate will have done this specific job before, because it barely exists yet. What the committee can evaluate is the quality of a candidate's framework and their record of driving organizational change.

Competitive landscape.

Internal XD leader (archetype confidence: high; any individual candidacy: speculative). Capital One's bench is deep — Jen Cardello runs Research and Design Operations at Managing VP level. An internal candidate arrives knowing the risk partners, the security approval path, and the XD network. Your differentiation is a published framework built from production AI work. Your exposure is that you have no proof of navigating their compliance paths or their politics. The requisition reset may itself indicate the committee concluded it wanted an outside view.

Enterprise DesignOps / AI-enablement operator (confidence: high). People like Red Hat's Mike Franke, who ran AI enablement for a 150+ person design org through tooling pilots, company-wide rollout, and legal coordination. They bring measured adoption numbers. Your differentiation is that you built the systems these operators are adopting. Your exposure is that their evidence maps more literally onto the posting's workforce-transformation deliverables. A regulated-enterprise AI/design hybrid is a plausible third archetype; the published framework differentiates you there too.

Phase 3 — The Outreach Package

Route: Patrick Dohan first. He's VP, Design, Premium, one level above this role. He promoted the earlier search publicly in first-person hiring language and placed himself in the role's working group alongside Jorge. He is the operational buyer. Hold Jorge for escalation if Dohan goes quiet past day 10.

Warm path: check your connections against both names before sending. Three or more mutuals with either, and you reference them in the close. The draft below is written cold.

First Contact Message

Subject: Minding the seams between designers and AI — at org scale

Patrick — your post about hiring someone to help determine how designers work in the future stuck with me, because that's the problem I've been building toward from the practitioner side. Capital One XD talks about minding the seams. The most consequential seam right now sits between a designer's judgment and AI output, and an org of several hundred needs a shared decision model for where that line falls before it needs tooling.

I published a framework called "Trust Is the New Interface" that maps five decision points, from intent-setting through output review to the gate where a designer trusts AI enough to delegate. It came out of shipping enterprise AI agents in production at TinyFish, where I worked through governance and auditability firsthand. I've since built three applications (Agentic Labs) that implement the full framework.

Would you have 20 minutes to walk through how Watch-Verify-Delegate maps to what you're building? I'm in SF, and hybrid works.

— Juno Chen

Cover Letter

The hardest problem inside the AI-in-Experience-Design mandate is giving several hundred designers a shared framework for when to trust what AI produces — one that scales through your existing leadership structure without requiring every designer to become an AI specialist. I built that framework, tested it in production, and published it.

"Trust Is the New Interface" maps five handoffs where a designer's relationship with AI output changes: Intent-Setting, In-Progress visibility, Output Review, Decision Gate, and Loop Feedback. The trust ladder — Watch, Verify, Delegate — gives design leaders a maturity model and a progression path for moving teams along it. Through Agentic Labs I built three enterprise applications (Brand Pulse, Retail Velocity, Carrier IQ, all live at junochen.com) that implement the full framework with real APIs and production agents. Most recently as Head of Product at TinyFish, I shipped the agentic platform from 0 to 1 in three months, working daily with agent traces, auditability, and governance in enterprise deployments. The methodology is a byproduct of building these systems.

The organizational half of this work is where I've spent most of my career. As Head of Design and Research for North America at Alibaba.com, I diagnosed a structural gap across a $50B+ GMV platform, built the mandate for a cross-functional redesign, and led three sprints that moved daily transactions +20% and NPS +2.2 points. As Product Design Director at BCG Digital Ventures, I built Thermo Fisher's digital supply chain from zero across six pharma partners, working through compliance, partner governance, and risk review to reach 100% adoption and $20M+ in recovered annual margin.

I'd welcome the chance to walk through how Watch-Verify-Delegate maps to the XD org's adoption challenge. My published work is at junochen.com.

Resume Emphasis Guidance

Director+ at an enterprise company, AI exposure quality 2 (editorial classification 3; same positioning lead either way). Methodology and org-transformation proof go on top.

1. Lead: Trust essay framework (five handoffs, Watch-Verify-Delegate) plus Agentic Labs, three live implementations. Top of the experience section, or a dedicated "Published Work" header.
2. Second: Alibaba.com, Head of Design and Research, North America. Emphasize structural gap diagnosis, mandate building, cross-functional execution at organizational scale.
3. Third: Thermo Fisher mySupply, Product Design Director at BCG Digital Ventures. Emphasize regulated environment, multi-stakeholder governance, 0→1 inside compliance constraints.
4. TinyFish header line: "Most recently, Head of Product at TinyFish (enterprise web agent platform, Series A). Shipped agentic platform 0→1 in 3 months. Agent traces, auditability, governance in production." One line, past tense.
5. Move down: Equinox+, Allē, Red Cross.
6. Attribution: every BCG DV project reads "Product Design Director at BCG Digital Ventures."
7. Transition line near the top: "Moved to product to build AI-natively from zero; returned to design to apply practitioner depth to organizational AI transformation at scale."

Post-Outreach Signals

• A reply from Dohan inside 5–7 business days is normal enterprise pace. Past day 10, follow up once. Still silent at day 20, go to Jorge.
• If anyone asks for a portfolio walkthrough: Trust essay, then Agentic Labs, then Alibaba. Methodology, production proof, org-scale evidence, in that order.

In Conversation

• Ask: does this role hold budget authority for tooling decisions, or does it recommend to existing DesignOps leadership? The answer tells you whether this role has real authority or is advisory.
• Ask: how is success measured at 12 months — adoption metrics across XD, shipped methodology, or both?
• Don't say: anything that frames this as a stepping stone toward a customer-facing product surface. The mandate is organizational. Keep your stated ambition inside it.
• Non-obvious: this posting assigns no product surface, customer journey, or design team, unlike Capital One's peer Director postings in Customer Acquisitions and Consumer & Developer Experience. Raise that difference to find out whether "player-coach" here means direct pattern work or methodology demonstration.

Phase 4 — Window Summary

September 18, 2026.