Scheduling emails started landing again the Tuesday after Labor Day. Conversations that went quiet in August are reactivating. Before you walk back into any of them, you need a way to test something nobody on the other side of the table will test for you: whether the role has been structurally equipped to deliver the outcomes it advertises.
Every Director+ design posting makes claims — build the team, raise the craft bar, earn design a strategic seat, scale the practice. What the posting almost never specifies is whether the role comes with the budget, hiring authority, decision rights, or executive sponsorship required to produce any of them. Executive search firms build success profiles specifying what the candidate must bring. Nobody in that process audits whether the role itself has been resourced to succeed. That audit is yours to run, inside the conversation, while they're evaluating you.
Five failure patterns predict a design leadership mandate will underdeliver more reliably than anything else I track. For each one below: what the posting typically says, what must structurally exist for the outcome to be real, and a question that surfaces whether it does. Every question is framed so it sounds like you're trying to understand how to succeed in the role. You are. You're also testing whether success is possible.
Pick the two or three that match the posting language you've already read:
- Function-building title without hiring authority or budget
- Strategic seat without decision rights that survive disagreement
- "Hands-on" language masking capacity relief
- Scope expansion promised without a named trigger
- Accountability for joint outcomes without control of the inputs
Ask early in the conversation, while the interviewer is still in assessment mode and giving you operational answers instead of recruiting answers.
1. Function-Building Title Without Hiring Authority or Budget
The posting says: "Build and lead a world-class design team." "Grow the design function from X to Y." "Establish design as a core capability."
What must exist: Approved headcount with positions attached to a timeline. A budget you control or have committed access to. Final hiring decisions, or at minimum veto power over candidates. A connection between team growth and business milestones that someone above you has already signed off on.
Without these, you hold the title and spend the next year asking someone else's budget owner for permission.
Ask: "What does the approved headcount plan look like for this team over the next twelve months, and who signs off on new roles?"
You're asking so you can plan. The answer tells you whether headcount is committed or aspirational. If it comes back as "we'll figure that out together" or "it depends on how the business does," the hiring authority is not real. Scope expandability: 1.
If the answer is vague, follow with: "Can you walk me through how the last design hire on this team got approved — who initiated it, how long from request to offer?"
A company that has done it can describe it concretely. A company that hasn't will generalize.
Tier note: Growth-stage companies produce this pattern constantly. The ambition is genuine. The budget mechanism hasn't been built yet.
2. Strategic Seat Without Decision Rights That Survive Disagreement
The posting says: "Partner with Product and Engineering leadership to shape product strategy." "Represent the design perspective in executive planning." "Drive design-led product decisions."
What must exist: A recent instance where design's input changed a product decision that Product or Engineering initially owned. Not a case where everyone agreed and design happened to be in the room — a case where design's view conflicted with another function's preference and design's view prevailed or substantively altered the outcome.
A seat where your input is heard but routinely overridden by roadmap priorities is a courtesy, not a decision right. The cost extends past the current job. Two years of presence without demonstrable influence on product direction leaves you with the title, the tenure, and nothing you can point to in your next search.
Ask: "Can you tell me about a recent product decision where design's perspective was different from the initial direction, and how that played out?"
You want to understand how influence works here. Listen for specifics: who was involved, what changed, what shipped. If the answer stays abstract ("we really value design input") or redirects to a case where everyone already agreed, design influence ceiling: 1.
This is the mandate checksum applied to one specific failure mode. The recent real decision remains the most diagnostic of the three readings.
Tier note — enterprise: Enterprise platforms overindex here. Design has a title, a reporting line, a team, and a ceiling where product management makes the calls that matter.
Tier note — AI-native: The competing function is often ML or research rather than product management. Design influence on model behavior or output quality runs through teams that evaluate input on different criteria than a PM would. The disagreement test still applies. Listen for whether the example involves a technical team, not just a product one.
3. "Hands-On" Language Masking Capacity Relief
The posting says: "This is a hands-on leadership role." "You'll be in the work alongside your team." "We need someone who can lead and do."
What must exist: Clarity about which design decisions you make versus which you review. "Hands-on" compresses at least three different jobs. You set the quality standard through your own work — craft authority. You review and approve the team's output — quality governance. Or you personally produce deliverables because the team is too small or too junior to cover the workload — capacity relief.
The first two are leadership functions. The third is a staffing gap with a leadership title on it. I flagged this in Issue #4 as the deviation where reading the signal correctly might change whether you want the role at all.
Ask: "When you say hands-on, can you give me an example of what I'd personally be designing versus what the team would own? And how would that balance shift over the next year?"
If every example is deliverable-level — you'd own the checkout redesign, the onboarding flow, the dashboard — and nobody mentions the balance shifting, this is capacity relief. Craft depth may look high on paper. The role's actual function is individual contribution at a leadership price point.
The other four patterns describe roles that underdeliver on their promise. You can diagnose them and take the job anyway if the company is compelling enough. This one hands you a different job than the one you interviewed for.
Tier note — growth-stage: Small team, urgent work, aspirational title. It shows up here more than anywhere else.
Tier note — AI-native: When the design surface is conversational or generative, "hands-on" may mean prompt engineering, evaluation design, or conversation architecture. Same test, different-sounding deliverables, and a harder line to read from the posting because leadership-level craft decisions and production work blur together. Press for the same specificity: what would you personally decide versus personally produce.
4. Scope Expansion Promised Without a Named Trigger
The posting says: "This role will grow as the company grows." "Opportunity to expand into adjacent product areas." "We see this becoming a VP-level position."
What must exist: Issue #8 broke this into five elements: a named trigger for the expansion, a grantor with authority to approve it, the specific resources or territory that transfer, precedent for comparable expansion at this company, and some durability if priorities shift. Promised expansion without those elements is aspiration, not structure.
Ask: "You mentioned this role could grow into [X]. Has someone in a comparable role here expanded their scope that way before? What triggered it?"
You're interested in the growth path and want to understand how it works. If there's a precedent — the Head of Product Design started with mobile and took over web after the platform unification last year — the path has a mechanism behind it. If the answer is "we're a fast-growing company and there will be lots of opportunity," scope expandability: 1.
Tier note: Growth-stage again. The promise is usually made in good faith; they believe the role will grow. They haven't built the mechanism that makes it happen, and when growth slows or priorities move, the promise goes with them.
5. Accountability for Joint Outcomes Without Control of the Inputs
The posting says: "Own the end-to-end user experience." "Accountable for [conversion / retention / engagement / NPS]." "Drive measurable impact on [business metric]."
What must exist: If you're accountable for a metric, you need to affect the variables that move it. Conversion is a function of design, copy, pricing, funnel architecture, page speed, and a dozen other inputs. Own the design layer but not the prioritization of engineering resources to implement your recommendations, not pricing, not copy, and you are accountable for something you can influence but cannot control.
What makes that workable is a cross-functional mechanism that gives your recommendations a path to implementation. A shared OKR that both design and the adjacent function report against. A joint planning cadence where design participates in prioritization rather than review. A dotted line to the engineering or data team that owns the other inputs. A recurring cross-functional review where design recommendations either get resourced or get explicitly deprioritized with a stated reason. Without at least one of these, your influence runs on personal relationships, and personal relationships don't survive a reorg.
Ask: "When you say the role owns [metric], what are the main inputs that move that number, and which of those does this role directly control versus influence?"
A strong answer names the inputs and is honest about which sit outside design: you'd own the experience layer and work closely with the pricing team, but pricing decisions go through the GM. A weak answer treats the question as a lack of ambition — "we expect this person to drive results across the full experience." If accountability significantly exceeds control and no mechanism exists to bridge the gap, design influence ceiling: 1.
If the answer is vague, follow with: "When a design recommendation requires engineering prioritization to ship, how does that trade-off get made? Who's in the room?"
A company with a working process will describe it. A company without one will describe aspiration.
Tier note: AI-native companies produce this pattern. The outcomes that matter — model behavior, trust calibration, error recovery — are jointly produced by design, engineering, ML, and policy. Posting language rarely specifies which slice the design leader actually controls.
Failed Mandate or Undefined Role Worth Building?
Some of these questions will come back vague. Expect that. What you then have to decide is whether the vagueness means a mandate advertised without structural support, or a role that's genuinely early — the company knows it needs design leadership, hasn't defined the shape, and wants someone to define it with them.
The best way to tell the difference is the recent-incident test from the mandate checksum.
Ask: "Can you walk me through a recent product or strategy decision where design's input materially changed the outcome?"
If they can describe one — who participated, when design entered the process, what evidence got considered, what changed — design has operative influence even where the role's formal structure is still forming. That's an undefined role with real organizational muscle behind it, and it might be worth building.
If they can't produce a single example, the mandate is absent. The title exists but the authority doesn't. The vagueness in their earlier answers wasn't early-stage ambiguity.
If they do describe an incident, ask what happened afterward. Did the decision stick? Did it become precedent? Did it create a reusable process? Decision durability tells you whether the influence is structural or episodic.
Using This
Scan the posting before the conversation. Identify which failure patterns match the language, pick two or three questions, and ask them early.
One score-1 answer is a risk factor. Two in the same conversation is a pattern. Three means the mandate as advertised does not exist, and you're evaluating a different role than the one on the page.
You may still want the role for reasons that have nothing to do with the mandate: compensation, brand, what you'd learn. Take it knowing which one you're taking.
- Interim as mandate test: Heidrick & Struggles recommends using an interim leadership appointment to clarify scope, decision rights, reporting lines, and resources before making a permanent hire — the closest thing to a formalized outcome-authority audit I found in executive search.
- McKinsey on design authority: McKinsey's design-leadership research found that vague mandates leave design leaders relying on persuasion and contrasts that with organizations that grant independent budgets or product-development vetoes, supporting the distinction between advertised influence and operative control.
- Formal versus real authority: Aghion and Tirole's foundational paper distinguishes the formal right to decide from effective control over decisions, explaining how information asymmetry and delegation create gaps between who holds authority on paper and who exercises it in practice.
- Realistic job previews reduce churn: A meta-analysis of 40 studies found that realistic job previews — communicating both positive and negative aspects of a role — were associated with more accurate expectations, lower turnover, and somewhat higher performance, which supports treating two-way assessment as a structural part of the hiring process rather than an afterthought.