The Persona Decoder — The Expanded-Scope Design Executive

The consolidation

A design leader absorbs product authority. The title changes, the org chart changes, and the evaluation criteria shift in ways the executive will not name publicly.

Three current examples:

• Loredana Crisan at Figma stepped into product leadership alongside design and is now hiring a Director of Product Design for AI & Context.
• Banu Guler at Midjourney arrived as CDO through the Co-Star acquisition to build a cross-functional product, design, and frontend organization at an AI lab that previously had no formal design leadership.
• Daniela Jorge at Capital One holds a CDO mandate spanning craft, business acumen, and AI-enabled organizational transformation across a massive enterprise design org.

Different companies, different stages, but a shared condition: a design executive whose accountability now extends beyond design quality into product outcomes, organizational change, or both. The first senior hire they make under that expanded mandate is the one that proves the consolidation was the right call. To their board, their CEO, their engineering counterparts.

You are interviewing for the role. You are also being evaluated as evidence that the consolidation works.

What they say versus what they evaluate

Leslie Witt, formerly Headspace's Chief Product and Design Officer, described the transition more honestly than most. She said she learned that some problems didn't merit the same craft investment, that she had to lead with data rather than use data to support a design argument, and that prioritization happened with a business number in mind. She owned the consumer P&L.

Compare that to the public vocabulary. Crisan writes about taste, discernment, and creative energy. Midjourney's careers page says it examines portfolios more heavily than resumes. Jorge's Capital One article emphasizes craft, business acumen, and cross-functional leadership. All accurate, all incomplete.

When a design executive absorbs product authority, the criteria they've always valued — taste, craft, vision — become assumed baseline. They still care. They will reject a candidate whose portfolio lacks quality. But those criteria stop differentiating. What differentiates is product judgment, technical fluency, revenue awareness, and the ability to operate across design and product without requiring a product manager as translator.

The executive cannot say this publicly. They got product because they're a design leader. If they start sounding like a product leader, the rationale for the consolidation weakens. So stated criteria and actual criteria diverge. The candidate who reads only the stated criteria — who walks in leading with taste and craft — passes the baseline but never reaches the real evaluation.

By company tier

AI-native startup

Anchor pattern: Guler at Midjourney.

Stated frame: Craft, intuition, portfolio quality, prototypes over presentations. Midjourney's Design Lead posting asks for interaction refinement, daily work in Figma, and "intuitive and human experiences."

Actual frame: Product direction, engineering and research partnership, comfort with AI coding tools (the posting names Claude Code and Cursor), team recruitment, and the ability to shape product decisions in an organization that may not have a PM function at all. At many AI-native companies, the expanded-scope design executive doesn't absorb an existing product org. There isn't one. They're building the product-thinking muscle inside a research-led culture. If the first senior design hire can't operate without a PM layer, a design-systems team, and a research function already in place, the executive has hired a dependency. The board sees a CDO who can't convert headcount into product velocity.

Tells: They ask about your process for making product decisions without a product manager in the room. They probe how you've worked with ML engineers or researchers, not product managers. They spend more time on the problems you chose to solve than on how you solved them. Watch for the interrupt pattern during a portfolio walkthrough — if they cut in to ask why you chose that problem, or what you would have cut to ship faster, you've entered the real evaluation. If they let you finish a ten-minute walkthrough without interrupting, you're still in the baseline.

What wins: Evidence that you've operated in the product-decision seat, not adjacent to it. Forward-looking design artifacts — interaction models for intent-setting, agent supervision, trust calibration — that demonstrate you're already thinking about their frontier problems before you've been hired. The Trust essay's five handoffs framework, mapped to their specific product surface, shows synthesis they need but haven't done.

What loses: A portfolio walkthrough that assumes someone else defined the problem. Craft-first framing that positions you as the person who makes it beautiful after someone else decides what to build. Any signal that you'd need a PM layer installed before you could operate.

Your move: TinyFish is your strongest signal here. You shipped an agentic platform from 0 to 1 in three months, working directly with agent traces, auditability, and governance — without a PM org. Lead with that operating context and the forward-looking artifacts that grew out of it.

Growth-stage platform

Anchor pattern: Crisan at Figma.

Stated frame: Taste, discernment, coherent experience, hands-on product judgment. Crisan's public writing emphasizes that AI expands exploration without replacing human judgment.

Actual frame: The Director posting tells a different story. It requires multi-team strategy across design systems, code, MCP, CMS, and Community. Management of managers. Direct execution alongside strategic leadership. Partnership across deeply technical product surfaces. This is a role where you're accountable for product outcomes in areas — developer tools, protocol integrations, content management — that don't resolve to traditional design-craft evaluation at all. The consolidation can be reversed. Growth-stage boards granted expanded scope because the previous structure wasn't working — product and design were misaligned, shipping was slow, the CEO was tired of mediating. If the first director hire under the new structure doesn't produce visible product-velocity improvement within two quarters, the board revisits. The executive knows this timeline even if they don't name it.

Tells: They reference their public writing about taste or craft early in the conversation. This is the baseline check. Then they shift to operational questions: how you've managed competing priorities across multiple product areas, how you've partnered with engineering leadership, how you've made scope tradeoffs. When they stop talking about taste and start asking about tradeoffs, you've passed the baseline and entered the real evaluation.

What wins: Showing that you understand the political dimension of their expanded scope. They need a director who makes the consolidation look smart — someone who can operate across design and product surfaces without requiring the executive to translate between the two functions they now own. Alibaba's scale and cross-functional complexity maps here: $50B+ GMV, three cross-functional sprints, measurable business outcomes. The bridge narrative answers the product-judgment question before they ask it.

What loses: Leading with team-building narrative alone. They need a builder, but one who builds product outcomes, not design organizations as an end in themselves. Pure-craft positioning that ignores the product-accountability layer they can't publicly name.

Your move: Lead with Alibaba's scale. Let TinyFish answer the product-judgment question in one sentence of context, not as portfolio evidence.

Enterprise software

Anchor pattern: Jorge at Capital One.

Stated frame: Design excellence, human-centered experience, accessibility, research rigor.

Actual frame: Capital One's Director, Product Design — AI in Experience Design posting assigns AI-tooling roadmaps, process evolution, workforce transformation, executive partnership, and measurable business value. As I covered in the Capital One battlecard, the implementation buyer and the accountability buyer are different people with different concerns — but the expanded-scope executive at the top needs both satisfied. At enterprise scale, the risk is different: the AI transformation mandate produces organizational motion without product impact. The CDO can reorganize, retool, retrain — and still not change what ships. Their first senior hire needs to connect the transformation narrative to measurable outcomes, because the executive's credibility depends on showing that design-led AI adoption changes the product, not just the process.

Tells: They ask how you've influenced people you don't manage. They ask about measurement — not whether you believe in it, but what you've measured and what changed as a result. They ask about AI not as a product feature but as an organizational capability: how do you get 200 designers to work differently?

What wins: Alibaba leads. Cross-functional sprints, measurable business outcomes (+20% daily transactions, +2.2pt NPS) — this is the language of someone who has operated at enterprise scale with business accountability. The Trust essay adds AI-transformation credibility. Thermo Fisher adds regulated-industry proof: $20M+ margin recovered, six pharma partners, 100% adoption.

What loses: AI-native positioning that lacks enterprise-scale evidence. The enterprise expanded-scope executive doesn't need someone who can build an agent. They need someone who can change how an organization of hundreds thinks about AI-enabled design. Technical fluency alone doesn't solve that problem.

Your move: Alibaba first, Thermo Fisher second, Trust essay for AI credibility. TinyFish establishes currency in one line.

Why the bridge narrative works differently here

With most design buyers, the TinyFish chapter — Head of Product at an AI startup — raises a question you have to manage: did she leave design?

With the expanded-scope executive, that chapter answers the question they can't ask publicly: can this person operate across both domains without needing me to translate?

You moved into product deliberately. You shipped. You came back to design because you want to apply that technical depth to a specific vertical domain. That narrative, told to a design buyer who just absorbed product authority, is proof that you already operate the way they now need their organization to operate.

Don't defend the transition. Frame it as the same structural event they experienced — a design leader who absorbed product accountability, learned what changes, and brought both capabilities back into a design-led practice.

Match the tier. At AI-native companies, lead with TinyFish's operating context and the forward-looking artifacts. At growth-stage platforms, lead with Alibaba's scale and let TinyFish answer the product-judgment question. At enterprise, lead with Alibaba and Thermo Fisher, and let TinyFish establish AI currency.

Across all three tiers, the bridge narrative is the differentiator — and it's worth understanding specifically who it differentiates you from. The AI-native design leader with Anthropic or OpenAI pedigree has technical fluency but probably can't demonstrate enterprise-scale business outcomes or function-building proof. The enterprise design director with Salesforce or Adobe pedigree has organizational credibility but has likely never held product-decision authority — the exact capability this buyer needs validated. The IC-track senior from a FAANG has deep craft but no evidence of operating in the product seat. Against the expanded-scope buyer, your profile outperforms all three on the dimension that actually matters to this archetype: you held product authority, shipped, and returned to design by choice. That's a structural match for what they evaluate, whether or not they say so.