Will the Mandate Survive the Next Reorg?

Every company hiring a senior design leader will describe a strong mandate: seat at the table, budget, headcount, executive sponsorship. You need to evaluate something they will not volunteer: whether any of it survives if the person describing it leaves.

The distinction worth testing: is the authority structural or sponsor-dependent? Structural authority is budget you control, headcount that reports to you, decision rights documented in operating processes, membership in recurring forums — roadmap reviews, release gates, investment decisions — that keep running regardless of who sits in the C-suite. Sponsor-dependent authority is a senior leader who champions design, verbal commitments about expanding scope, cultural signals with no institutional backing. Both can exist in the same role. Only the structural components survive a leadership transition without requiring you to rebuild from zero. I laid out an interview protocol for probing this distinction in The Gate Test. This piece adds the evidence — companies where mandates collapsed, companies where they held, and the signals that were readable before the outcome was clear.

Four collapses, four structural weaknesses

Twitter, 2021. Dantley Davis held the chief design officer title, running design and research as a centralized function under CEO Jack Dorsey. Four days after Dorsey stepped down, new CEO Parag Agrawal reorganized from functional groups into product divisions. Davis departed as part of the restructuring.

Readable signal: design's executive authority existed in one functional chief role with no equivalent seats inside the product divisions that replaced it. When the operating model changed, nothing in the new structure required a centralized design function to persist.

Expedia, 2022–2023. Doug Powell joined as VP of Design Practice Management, describing CEO Peter Kern as placing experience design at the center of Expedia's transformation. His remit: grow the global design team, define the practice, spread human-centered design through company culture. Roughly a year later, Powell reported that a reorganization had dissolved both his role and its mission. His boss, SVP Rachel Kobetz, subsequently left for PayPal. Fast Company later reported that Expedia eliminated its executive design position entirely.

Readable signal: the mandate was described entirely in future tense. Grow, define, spread. The public description emphasized transformation and CEO commitment but never mentioned independent budget ownership, release authority, or operating procedures that business units were required to follow. Every component of the authority description traced back to what the CEO intended.

IBM, 2021–2023. Katrina Alcorn became general manager of design, leading design for IBM's software portfolio. Her own materials describe responsibility for a $20 billion software portfolio and a $130 million budget. But in a 2022 interview, Alcorn explained that her role differed from IBM's P&L-owning general managers: she controlled a practice budget covering only a fraction of the design organization, while other general managers funded the rest. After Alcorn left in late 2023, IBM eliminated the position.

Readable signal: the title said general manager, but the funding model said practice lead. Most of the underlying resources were controlled by business-unit leaders with their own P&Ls. The distributed designers, the design system, and the design-thinking practices all continued, but the executive role did not.

Apple, 2019–2023. When Jony Ive announced his departure, Apple did not name another CDO. The function split between two VPs reporting to COO Jeff Williams. When one of those VPs later departed, Apple decided not to replace the industrial-design chief role at all.

Readable signal: the CDO role was built around a singular leader's personal authority. When that person left, there was no structural mechanism requiring a successor at the same altitude. Design work continued, but not at the same organizational altitude.

What survival looks like

Logitech. CEO Bracken Darrell departed abruptly in June 2023 after ten years. The board installed an interim CEO through an established succession process. Hanneke Faber became CEO in December 2023. Under Faber, Logitech appointed a new CDO and described the design team as continuing to perform. The CDO title, the function, and the leadership succession all survived the transition.

Readable signal before the transition: the board's own departure announcement described the result of Darrell's tenure — "an award-winning design company" — as a company attribute, not a CEO program. Design's identity at Logitech had been separated from any single executive. The CDO existed as a standing organizational role, not a personal appointment that required the departing CEO's continued advocacy. When Faber arrived, the organizational expectation was already established.

Intuit. Brad Smith stepped down as CEO in January 2019 after making design central to Intuit's strategy. His successor, Sasan Goodarzi, was an internal executive. Before the transition, Intuit had increased its designer headcount by nearly 600 percent and spread its Design for Delight methodology through company-wide forums, training, and practices used by non-design employees. As of 2025, Intuit still presents Design for Delight as the way it innovates.

Readable signal before the transition: Design for Delight was not a design-team methodology. It was an innovation method used by product managers, engineers, and business teams. The training infrastructure existed independently of the design org's reporting line. Recurring forums brought non-design employees into design-led processes. The capability had crossed functional boundaries — it lived in how the company worked, not in who ran the design org. And the successor CEO was internal, meaning he had already operated within a system where design-led methods were part of daily work.

PepsiCo is a useful middle case. CDO Mauro Porcini stayed more than six years after his sponsoring CEO, Indra Nooyi, departed. The 300-person design organization persisted. But when Porcini left in 2025, PepsiCo did not immediately announce a successor CDO. The capability survived, though the executive altitude may not have. PepsiCo shows that these are separable outcomes — and you should be clear with yourself about which one you are evaluating.

What the research confirms

The organizational research supports a narrower claim than you might want. No study ranks budget ownership, headcount control, process membership, or reporting proximity as comparative predictors of design-mandate survival. But one distinction holds up reliably: recurring routines — required planning steps, review gates, staffing cycles, release procedures — retain organizational knowledge through personnel turnover. Authority sustained through personal relationships remains vulnerable when those relationships end, because informal delegation is revocable.

A peer-reviewed study of design-thinking programs found exactly this pattern: senior sponsorship was critical to establishing every program in its sample, and sponsor departures damaged several programs, severely weakening or terminating some. Programs with enough operational momentum — routines, training, distributed participation — sometimes survived. Programs that depended on one executive's protection often did not.

The practical test: does design's authority live in processes that would continue running if the sponsor walked out tomorrow? Or does it live in a relationship that would need to be rebuilt from scratch with whoever replaces them?

Tier patterns

Brief, because the evidence is directional, not definitive.

AI-native companies. Authority structures are still forming. Research on young high-tech firms found that changes to organizational models increased turnover, concentrated among senior employees. Expect sponsor-dependent mandates because there has not been enough time to formalize them. You may be able to shape the structure. You should also expect that whatever you build can be reshaped just as easily by the next executive.

Growth-stage companies. Design leadership roles are frequently created as part of a specific executive's vision for the next phase. The mandate is real, but it is attached to a strategy that may pivot. Look for whether design's decision rights are written into product-development processes or exist only in the hiring manager's description of how things work.

Enterprise platforms. Twitter, Apple, IBM, and Expedia show that company scale does not protect an executive design title from reorganization, distribution, or elimination. Logitech and Intuit show that design capability can persist when it has multiple leaders, routines, and an identity extending beyond one executive. The question at enterprise scale is whether the mandate is distributed across the organization or concentrated in a single reporting line.

Regulated environments. External requirements can anchor design work in ways that internal sponsors cannot. The FDA's quality-management regulation and human-factors guidance require usability engineering and design-related processes for covered medical devices. These rules anchor required activities, not a CDO title or a design-owned budget. But they mean the work itself is harder to eliminate, even if responsibility moves to engineering or quality functions.

Diagnostic indicators

These are the underlying indicators to investigate through whatever channel you have — postings, LinkedIn, recruiter conversations, backchannel references — before you reach the offer stage. The Evaluator's Lens piece covers real-time conversation tactics.

In the job posting

• Present-tense resources vs. future-tense scope. Current team size, approved headcount, named budget responsibility, existing planning-process membership — these describe what you would inherit. "Build the team," "scope will expand," "partner closely with leadership" — these describe what someone hopes will happen. The ratio tells you how much of the mandate exists today.
• Named processes. Does the posting mention specific recurring processes where design participates — roadmap planning, release reviews, investment decisions? Membership in named operating processes is the closest public proxy for routine-embedded authority.
• Negation language. "Not just visual polish" or "more than pixel-pushing" means the company is reacting to a previous state where design lacked authority. That tells you the mandate is recent and may be fragile.

On LinkedIn

• Map the sponsor chain. Identify the hiring manager, their boss, and the executive who created the design function. How long has each been in their role? If the person who created the mandate is still there, the mandate has not yet been tested by their departure. That is not evidence of durability. It is evidence that the test has not happened.
• Track departures around reorgs. Multiple design, research, and practice-operations leaders leaving within a few months of each other, especially near a reorganization, is a pattern. Look at the last two years of the design org's LinkedIn history.
• Check for title persistence. Has the company maintained a VP/Head/CDO of Design through a previous leadership change? If yes, that is the strongest public signal of structural commitment. If the role was created by the current CEO and has never been tested by a transition, weight it accordingly.

In recruiter and hiring-manager conversations

• Pin down what design currently owns. Current approved headcount. Current budget. Current direct reports. Current decision processes where design has a documented role. Planned hires and future expansion are contingent scope — they tell you what the sponsor intends, not what the organization has committed to.
• Ask about precedent. Has design's authority survived a previous leadership change, a reorg, or a strategic pivot? If the answer is "this is the first time we've had a design leader at this level," you are the test case. The mandate's durability is unknown.
• Listen for where the authority description shifts from structure to person. "Design owns the review gate before release" is a process claim. "Our CPO really believes in design" is a relationship claim. Both can be true. Only the process claim survives the CPO's departure.

Through backchannel references

• Investigate a contested decision. The most informative backchannel question is about a time design and product or engineering disagreed on a significant decision — who closed it, and how. The answer reveals whether design has actual decision rights or advisory access.
• Ask what happened when the sponsor was absent. If the executive who champions design was on leave, traveling, or otherwise unavailable for a period, did design's access and authority hold? Or did it quietly contract until the sponsor returned?
• Expect conflicting accounts. One person may accurately describe strong executive access while another accurately describes weak control over funding. Both can be true. The conflict itself is informative — it usually means the authority is real but narrow, or present but not formalized.

Calibration

You will not get certainty on mandate durability before accepting an offer. Some of the most important structural features — budget allocation mechanisms, decision-rights documentation, what happens during conflict — are not visible from outside. But you can distinguish between a role where every description of authority traces back to one person's commitment and a role where authority is distributed across processes, budgets, teams, and precedents.

The cases above point to one question worth returning to, in different forms, through different channels: what would have to be formally reallocated, procedurally changed, or organizationally rebuilt to take this authority away? The longer that list, the more durable the mandate.