The killer question you need answered before you accept any Director+ role: which of the decision rights being described are encoded in the operating model, and which depend on a specific person continuing to sponsor design?
You will not ask it that way. You will probe it from five angles across five interview stages, and the answers will tell you whether the authority you're being offered survives the next reorg or walks out the door with one executive.
Structural vs. Borrowed
Structural authority means decision rights attached to the role through budget, headcount, planning membership, review gates, and escalation paths. Personnel change. The rights stay.
Borrowed authority means decision rights that exist because a particular executive champions design, brokers your access, and settles disputes on your behalf. It works until that person leaves, gets overruled, or shifts priorities.
Organizational economics draws a related distinction between the formal right to decide and effective control over the decision. A role can hold the right on paper while a superior retains the ability to reverse it at will. Informal delegation — where a superior promises not to intervene — can provide real authority, but only as long as the relationship holds.
You have seen what borrowed authority looks like from the outside. McKinsey surveyed senior design leaders and executives and found vague mandates, missing budgets, only 14% of companies setting quantified targets for their design leaders. In a documented case at an airline, a design initiative stopped after the sponsoring CEO departed. The project didn't fail on its merits. Its authority was one person's enthusiasm, and that person left.
"The Mandate Diagnostic" asked whether design owns a consequential decision surface or decorates one. This piece asks the follow-up: if it owns one, is that ownership durable?
Here is how to test for it, stage by stage.
Stage 1 — Recruiter / Intake Call
The recruiter will not know the operating model. You are listening for whether the role has an approved shape or is still being imagined.
Ask:
-
"What changed that made this role open now?" You want a trigger event: a departure, a reorg, a product launch, a board mandate. If the answer centers on one executive's enthusiasm — "our CPO really believes in design" — note it. Sponsor signal.
-
"Which parts of the role are already approved — reporting line, level, team size, budget?" Structural roles have approved resources. Borrowed-authority roles have a title and a promise that resources will follow.
-
"Which functions will work differently once this person starts?" A role with structural authority changes how other teams operate. If the recruiter cannot name a single function whose workflow changes, the role may be additive rather than consequential.
Reading the answers: A recruiter who names the reporting line, approved headcount, the business outcome the role is accountable for, and the stakeholders whose agreements change is describing a role designed into the operating model. A recruiter who describes the role mainly through one executive's vision — team, budget, and cross-functional changes all in future tense — is describing a role that depends on that executive delivering on promises.
Don't over-read silence here. Recruiters often lack operating details. Route unanswered questions forward to the hiring manager. Absence of information at intake is a reason to probe harder later, not a finding.
Healthcare/Regulated tier: Add: "Which functions have formal sign-off on decisions this role will touch?" If the recruiter can't name Clinical, Legal, or Risk as parties to the role's operating context, the mandate may not account for the regulatory layer that constrains every consequential decision.
Stage 2 — Hiring Manager
Your highest-value stage for authority testing. The hiring manager knows — or should know — what decisions they are transferring and what they are keeping.
Ask:
-
"When this person starts, what decisions will you stop making?" The most direct test. Structural authority involves explicit transfer. If the manager cannot name a single decision they will stop owning, the role is advisory regardless of title.
-
"What will Product or Engineering stop deciding without Design?" Authority over consequential transitions — scope definition, roadmap influence, shipping decisions, quality gates — means other functions lose unilateral control over something. If nothing changes for them, nothing changes for you.
-
"Does this role have approved headcount, and can it hire without making a fresh case each time?" Hiring authority is one of the most concrete forms of structural power. A role with an approved hiring plan and selection authority operates differently from one that must petition for each requisition. If every new hire requires a sponsor to re-approve the need, the team-building mandate is borrowed.
-
"Tell me about the last time Design changed scope, a roadmap commitment, or a release plan." You want a specific precedent. A concrete example tells you the mechanism existed and was used. An abstract answer — "we're very collaborative" — tells you nothing until you know how deadlock closes.
-
"Which decisions can this role close independently, and which come back to you?" The boundary between the role's authority and the manager's retained authority is the actual job description. Everything else is marketing.
Reading the answers:
Structural signal (high confidence): The manager names a current decision holder, describes an explicit transfer, identifies a boundary, and provides an escalation path. They can tell you what happened the last time design and another function disagreed, and the resolution did not require one specific executive to intervene.
Borrowed-authority signal (moderate confidence): The manager promises access, air cover, or personal backing but retains every consequential decision. The language is relational — "I'll make sure you have a seat," "I'll fight for your team" — rather than mechanical. The decisions you will own are described as things the manager will grant, not things the operating model assigns.
Ambiguous: "We decide collaboratively." Follow up: "When collaboration doesn't produce agreement, who closes the decision?" The answer to that question is the actual authority structure.
AI-native tier: Add: "Who controls model-behavior thresholds and evaluation criteria? Who decides go/no-go on a production run?" At AI-native companies, the consequential transitions are often about model behavior, not interface. If design's authority stops at the screen and doesn't extend to the decision logic behind it, the role is narrower than it sounds.
Growth-stage tier: Add: "Does the design function have its own planning cycle and budget line, or do resources come through Product or Engineering?" At growth-stage companies, structural authority often depends on whether design operates as an independent function or draws resources at another leader's discretion. A "Head of Design" whose headcount, tooling budget, and quarterly priorities are all allocated by a VP Product holds a title, not a function.
Stage 3 — Portfolio Review / Design Exercise
This stage belongs to the evaluators. But the conversation around your work reveals the company's operating model if you use your cases as prompts.
Ask, tied to a case you are presenting:
-
"In your operating model, who would own this decision — the scope call, the quality threshold, the release gate?" You are using your own work to surface how the company allocates authority.
-
"Who could override that person?" The override path is the real authority structure. A quality gate that any PM can override is not a gate.
-
"If this case happened here, where would my responsibility end?" You want to know whether design is accountable through to the outcome or only through to the deliverable. Accountability that stops at the handoff tells you where authority stops too.
Reading the answers:
Structural signal (moderate confidence): Interviewers connect your design judgment to production evidence, success measures, a recurring review mechanism, and authority over what happens next. Design owns a loop — the role can observe what shipped, evaluate it against a standard, and act on what it finds without requesting permission.
Borrowed-authority signal (moderate confidence): The panel praises your judgment but maps the local role only to recommendations, prototypes, or screens. Listen for the verbs. "Design would propose…," "the team would take that to Product for a decision…," "we'd flag that and escalate." When every verb describing design's role is advisory and every verb describing another function's role is decisive, the authority allocation is in the grammar.
A craft interviewer may not know the full governance model. Note who they refer you to for operating-model questions — the referral itself tells you where authority knowledge lives in the org.
Stage 4 — Cross-Functional Panel
This is where you test for the signal that matters most: whether different functions describe the same authority allocation.
Korn Ferry's executive-onboarding research documents a case where a new CHRO believed her role was a partnership with the CEO, while the senior team believed she had been hired to serve the CEO. The discrepancy surfaced before she started — but only because someone thought to ask both sides. In most searches, nobody does.
Ask each panelist the same core question in their own language:
-
"When scope, feasibility, and experience quality conflict, how does the decision close?" You want the mechanism. And you want to hear it from Product, Engineering, and Design separately.
-
"What is a recent consequential decision that Design changed here?" If the Product panelist and the Design panelist tell you different stories — or if one cannot name an example — that is a recognition gap.
-
"Who can approve an exception to the experience standard, and how is that recorded?" Exception authority is where structural and borrowed authority diverge most visibly. A structural quality gate has a defined exception process. A borrowed one has "talk to [name]."
-
"What will this role own that your function owns today?" Ask this of Product and Engineering panelists specifically. If they don't know, or their answer contradicts the hiring manager's, the authority transfer has not been socialized. It may not survive first contact with the org.
Reading the answers:
Structural signal (moderate confidence): Product, Engineering, and Design independently describe the same decision domain, the same final decider, the same escalation path. Research on shared mental models finds that cross-functional consistency on these points correlates with team performance. It doesn't prove the model survives a high-stakes conflict, but it tells you the model exists and is recognized across the room.
Borrowed-authority signal (moderate confidence): Design says the role "owns" a decision. Product or Engineering describes Design as advising, supporting, or recommending. Every successful example of design influence involves the same executive intervening. The authority runs through one person.
Ambiguous: Different vocabulary is not the same as disagreement. An engineer saying "design signs off" and a designer saying "design owns the quality gate" might describe the same process. Probe the mechanism, the final decision, and the override path — not the label.
Enterprise tier: Ask: "When two business units want different things from the design system, who decides?" Enterprise authority lives in the ability to hold a standard across organizational boundaries. If every exception requires fresh executive permission, the authority is borrowed from whoever currently controls the escalation.
Healthcare/Regulated tier: Ask: "When Design, Clinical, and Legal disagree about a release, what happens?" Consequential transitions in regulated environments involve multiple authority holders with formal sign-off rights. You need to know whether design has a defined role in that process or participates at someone's invitation.
Stage 5 — Executive / Skip-Level
Your last and most direct opportunity. Executives can describe the operating model because they designed it — or because they are the sponsor it depends on.
Ask:
-
"What will you and the executive team stop deciding once this person is in the seat?" Same logic as the hiring-manager question, one level up. If the executive cannot name a decision they are releasing, the role reports to them but does not reduce their decision load.
-
"Which parts of this mandate are encoded in budget, headcount, planning, review, or governance?" You are asking them to name the mechanisms. Structural authority has mechanisms. Borrowed authority has intentions.
-
"What happened the last time a senior design call delayed a launch or changed a roadmap commitment?" You want a precedent where design authority was tested under pressure and the operating model held. If the only precedent involves the executive personally intervening, that is your answer.
-
"If the reporting line changed, which parts of this remit would stay with the role?" This is the closest you can get to the killer question directly. A structural mandate survives a reporting-line change because the rights are attached to the role. A borrowed mandate does not, because the rights are attached to the relationship.
Reading the answers:
Structural signal (high confidence): The executive names specific recurring mechanisms — planning rights, budget authority, headcount, review membership, standards ownership, a defined decision lane — and provides a precedent where the arrangement survived disagreement without their personal intervention.
Borrowed-authority signal (moderate confidence): The answer centers on personal access, chemistry, or "I'll make sure you're heard." The executive is the route through which every conflict passes. They may be entirely sincere. The problem is the architecture: when they leave, the route closes.
Structural authority is more durable than borrowed authority, but it is not permanent. Research on CEO successions shows that new leaders reconfigure organizational structures. Structural authority remains attached to the role without requiring a particular sponsor's continuing personal permission — until the organization formally changes that allocation. That "until" is real, but it is a different risk profile than discovering Monday morning that your authority evaporated because one person left.
AI-native tier: At founder-led AI companies, the founder often does not distinguish between structural and borrowed authority because they are the structure. The question "if the reporting line changed" may not register — there is no scenario in the founder's mind where they are not the reporting line. Shift the probe: "If this company is three times its current size, which of these decision rights would still belong to this role without your direct involvement?" You are testing whether the founder can imagine the role operating independently of them. If they can't, the authority is personal regardless of how permanent the founder feels.
Enterprise tier: Enterprise executives may describe elaborate governance — decision matrices, review boards, escalation protocols — that exists in documentation but functions differently in practice. The test is the precedent question: "What happened the last time a senior design call delayed a launch?" If the governance is structural, the executive can name an instance where the process worked as designed. If the answer requires them to narrate their own intervention, the governance is a diagram and the authority is theirs to lend.
Scoring What You Find
Two dimensions from your rubric absorb what this protocol surfaces:
Design influence ceiling. Record the highest consequential transition — scope definition, roadmap influence, shipping decisions, quality gates, cross-functional tradeoffs, hiring authority — the role can close through recognized authority without sponsor-specific intervention. If the role can set quality thresholds but cannot change scope, that is the ceiling. If it can recommend but not close anything independently, the ceiling is advisory regardless of title.
Scope expandability. Record whether the role's rights are supported by recurring mechanisms and resources that can extend across teams and surfaces, or whether each expansion requires fresh personal permission from the same executive.
"Where Design Authority Actually Lives Right Now" gives you the public-signal layer. "Classify the Role First" gives you the archetype. This protocol gives you the durability test.
Public signal first, then archetype classification, then this live authority protocol across interview stages. By the time you reach Stage 5, you should know whether the mandate is structural or borrowed — not hope to find out after you start.
The company will not volunteer the distinction between structural and borrowed authority. They may not see it themselves. Surface it before you are inside, because from inside, the only way to learn the difference is to watch the sponsor leave.
- Titles that mislead about scope: Gusto's "Head of Design" governs three designers inside an 80-plus-person design organization, while Stripe's Senior Staff IC carries category strategy and executive access — a reminder to run the authority test before the title anchors your expectations.
- "Hands-on" hiding accumulated vacancy: Amplitude's Head of Product Design posting explicitly says the role is not for an executive who manages up and delegates down, but the panel discussion flagged that "player-coach" can also mean a company has underfunded design and wants one person filling several open seats.
- Design mandates retracted after reorgs: Fast Company reported Johnson & Johnson closing its corporate design office and IBM and Expedia eliminating executive design positions, with interviewed leaders describing roles whose influence sounded substantial while ownership of outcomes remained vague.
- Cross-functional consistency as authority evidence: A meta-analysis on shared mental models finds that when affected functions independently describe the same decision domain, escalation path, and final decider, team performance correlates positively — the closest research gets to validating the cross-functional panel test in Stage 4.