The prior Maven battlecard framed this as a governance mandate. That framing holds. What's changed since July is the recoverable timeline underneath it — and what it tells you about where the search stands today, 80 days after the requisition went public.
Five events that changed Maven's design trajectory
June 2021. Maven announces Jason Lee as SVP of Product, weeks before the $110M Series D that pushed the company past $1B. He describes the product group as "small but mighty." His operating principle: "do fewer things, better."
July 2023. A Maven interview identifies Lee as Chief Product Officer. His org now includes designers, PMs, marketers, content, ops, and data. Eli Horne's portfolio dates his Maven tenure to 2023–2026, covering product design, brand design, and research under one leader reporting to Lee. His June 2026 departure post says "two and a half years," placing his actual start in late 2023 rather than at the time of this interview. The July 2023 event is Lee's title change; Horne's arrival followed.
October 2024. Maven's $125M Series F names Lee as Chief Product and Operating Officer. Axios reports a $1.7B valuation. Weeks later, Maven cuts 60 employees — roughly 10% of headcount. No public source establishes whether the design team was affected. If it was, the successor may be rebuilding rather than inheriting a stable team. Worth asking directly.
March 2026. Maven launches Maven Intelligence, an AI orchestration layer across its virtual clinic and care programs. Fierce Healthcare confirms it uses OpenAI and Google models with guardrails, automated evaluations, and ongoing human review. Shipped and in production.
June 2026. Horne posts his departure, says he wrote the job description, and links Greenhouse requisition 8594275002 as his own backfill. Posted June 16 as Head of Design. By late August, the same requisition reads VP of Design with a $250K–$350K base range. LinkedIn's applicant counter shows 200+, though that figure is directional and fluctuates by check date.
Everything else in Maven's public record confirms this trajectory rather than altering it.
The buyer pattern
Read Lee's title changes in sequence: SVP Product → CPO → Chief Product and Operating Officer. Each title change pulled more of the company's operational surface under his authority. Over five years he absorbed product, design, marketing, content, operations, and data.
The VP Design hire is the first time in his Maven tenure that Lee is handing a function off rather than absorbing one.
A buyer who has been consolidating for five years and is now choosing to distribute will screen hard for someone who will protect what he built. His public language is consistent: patient trust under vulnerable conditions, clinical collaboration, disciplined prioritization, measurable health outcomes. He wants a design leader who holds the standard he set while he focuses on the operational half of his dual title. Your outreach should mirror his vocabulary before introducing yours — the language-mapping piece from Issue 5 covered this.
Three ambiguities resolved
When did the search open? The requisition was first published June 16, updated July 8, re-presented with a VP title by late August. Horne describes writing the job description himself — an orderly handoff, not a sudden vacancy. Internal approval likely preceded his departure by several weeks. The search has been running approximately 80 days.
Is this building or inheriting? Inheriting. Horne ran product design, brand design, and research for roughly two and a half years and describes building Maven's AI practice "from zero," creating design infrastructure, and shipping Maven Intelligence. The successor inherits roughly 15 designers — that figure comes from the current posting, though it may not account for the November 2024 layoff's impact on the team. The function exists. But the posting asks the new leader to establish AI-native workflows, design-system consistency, and operating standards. That language describes either continuation of incomplete work or a reset after Horne's departure. The public record doesn't resolve which. Treat it as a function that exists but needs its operating layer rebuilt under new leadership.
How fast will they move? The 80-day elapsed window already answers this: deliberately. The title change from Head to VP tells you more. The first round of candidates either didn't clear the bar or the hiring committee recalibrated what seniority level the role required. Either way, the bar moved up during the search. Lee has been at Maven for five years and has never hired this role before — Horne is the only VP Design recoverable from Lee's tenure. He is distributing authority he has held personally for five years. First-time delegations take longer.
Prediction
The search is in its second phase. The title upgrade, the July 8 update, and the 80-day elapsed time all point to a committee that has seen candidates, learned what it actually needs, and reset. The VP re-presentation with renewed applicant volume suggests they are actively sourcing again.
October through mid-November. Lee is a scheduled speaker at Maven's Onward conference on September 30 — a search that has run through the summer without closing will face internal pressure to resolve before Q4 planning.
What would have to be true for this to be wrong: Maven pauses the search to restructure the role again, or Lee decides to absorb the function back under a direct report rather than hiring externally. The first is unlikely given the VP upgrade — you don't relevel a role to attract more senior candidates and then pause. The second contradicts the entire trajectory of the posting.
Contact recommendation
Move this week. The search is not new despite the LinkedIn timestamp. Waiting for more signal means waiting through the close window.
Before sending, check your LinkedIn connection graph to both Horne and Lee. The recommendations below assume cold outreach. If you share mutual connections with either, reference them in the close of your message, not the opening.
1. Eli Horne via LinkedIn. He wrote the job description, called this his own backfill, and described Lee as the executive who gave him room to operate. Ask for a direct introduction to Lee. Horne is the closest available path to the decision-maker and the person most likely to brief you on what the committee learned from the first round.
2. Jason Lee via LinkedIn, paired with the Greenhouse application. The role reports to him. Your message hook should mirror his language — patient trust under vulnerable conditions, clinical collaboration, measurable outcomes — before introducing your framework.
Lead with Thermo Fisher and Red Cross. This is a healthcare company where clinical outcomes are the product metric. The 0→1 regulated-environment proof — $20M+ margin recovered at Thermo Fisher, $847K disbursed at Red Cross, both as Product Design Director at BCG Digital Ventures — maps directly to Maven's design mandate: high-stakes decisions, vulnerable users, compliance-first environments. Alibaba is secondary credibility for enterprise scale. Agentic Labs and the Trust essay are your AI-fluency signal — Maven already has a shipped AI practice and wants someone who can govern it.
The question to ask in the first conversation: Who does the VP Design interact with on Maven's clinical team, and how does that interaction currently work? Lee's public statements emphasize that product and clinical teams work closely, with repeatable feedback loops. Whether the VP Design has a direct clinical counterpart or routes through Lee tells you whether this is a peer seat or a nested function — the authority question from Issue 5 that remains unresolved.
A second question, specific to this search: ask whether the design team's current headcount reflects the November 2024 reduction or predates it. The answer changes whether you're stabilizing an inherited team or rebuilding one.
What competing candidates will miss: The Head-to-VP title change. Most applicants will read the current posting at face value. You know the search recalibrated mid-flight, which means the committee has a sharper picture of what it needs than the posting language reflects. Your outreach should speak to the recalibrated bar — governance of an inherited function with a live AI practice — not the generic design-leadership framing of the original posting.
- Lee speaks September 30: Maven's Onward 2026 conference includes sessions on clinical product roadmap and predictive care — his language there will give you the freshest buyer vocabulary for a follow-up message if your initial outreach hasn't converted by then.
- Maven Intelligence evaluation model: Fierce Healthcare's independent reporting confirms Maven uses automated evaluations, guardrails, and sampled human review of AI conversations — ask Horne or Lee how design currently participates in that review loop, because the answer reveals whether the VP owns quality standards or inherits them from clinical.
- Horne's AI-practice claim needs testing: His portfolio says he built Maven's AI practice "from zero," but the current posting asks the successor to establish AI-native workflows and operating standards — probe in conversation whether the practice was institutionalized or left with him.
- November 2024 layoff exposure: Endpoints reported a 60-person cut weeks after the Series F, and no public source clarifies whether the design team's current ~15 headcount reflects that reduction or predates it.