The CEO questions whether the design team is worth its cost, pointing to slow delivery. How do you respond most effectively?
- A. Show a portfolio of the team's most beautiful work to prove design's value
- B. Connect design's work to business outcomes it has moved, own the delivery concerns, and propose concrete improvements ✓
- C. Defend the team and explain that good design takes time
- D. Offer to cut headcount to reduce the cost concern
Correct answer: B. Defending design to executives requires speaking in business outcomes and addressing the real concern with a plan, not showing pretty work or getting defensive.
After a reorg, your team is split so each designer now reports into a separate product pod, and design consistency and craft are eroding. What's the best structural response?
- A. Fight the reorg to get your centralized team back
- B. Establish a strong dotted-line design community — shared standards, rituals, critique, and a system — across the pods ✓
- C. Let each pod's design drift independently since that's the new structure
- D. Personally review every pod's work to hold the line
Correct answer: B. In an embedded model, cohesion is maintained through a strong cross-pod design community and shared systems, not by resisting the org or becoming a personal gatekeeper.
A well-liked senior designer is quietly underperforming and it's dragging the team, but firing them risks morale. What's the right path?
- A. Keep them because letting them go would hurt team morale more
- B. Give honest feedback, a clear improvement plan with support, and be prepared to act decisively if it doesn't improve ✓
- C. Reassign them to less critical work indefinitely to avoid a decision
- D. Let them go quickly before it affects the team further
Correct answer: B. The mature path is a fair, supported improvement process with the resolve to act if it fails — avoiding both indefinite tolerance and premature termination.
You must cut your team's scope by a third due to budget. How do you decide what design work to stop?
- A. Cut whatever the most junior designers are working on
- B. Rank all work by impact and stop the lowest-value efforts, communicating the reasoning openly to stakeholders ✓
- C. Reduce quality across everything to keep all projects alive
- D. Ask each PM to cut their own design requests
Correct answer: B. Scarce capacity is protected by ruthlessly prioritizing on impact and communicating transparently, not by across-the-board dilution or seniority-based cuts.
Leadership wants to measure design's impact with a single metric for the exec dashboard. How do you respond?
- A. Refuse — design impact can't be reduced to numbers
- B. Propose a small balanced set tied to outcomes (e.g., task success, adoption, quality signals) and explain what each does and doesn't capture ✓
- C. Give them a design-output metric like screens shipped per sprint
- D. Accept whatever single metric they choose to stay aligned
Correct answer: B. A lead engages the request constructively with a balanced, outcome-linked set and honest caveats, rather than refusing, offering vanity output metrics, or accepting a misleading single number.
Your team has scaled from 3 to 12 designers and quality is now inconsistent and your review process has broken down. What's the highest-leverage fix?
- A. Personally review more work to recatch inconsistencies
- B. Build a layer of senior/staff designers who own quality in their areas, plus shared standards, so the system scales without you ✓
- C. Slow hiring until you can keep up with reviews
- D. Require everyone to follow rigid templates for everything
Correct answer: B. Scaling quality requires distributing leadership and codifying standards so the system doesn't depend on you, not centralizing review or over-standardizing.
Two of your best designers are both up for one senior promotion; only one slot exists. How do you handle it?
- A. Promote the one who's been on the team longer
- B. Assess both against the level's expectations objectively, promote the one who clearly meets it, and give the other a candid growth path ✓
- C. Promote neither to avoid the appearance of favoritism
- D. Split the impact so it looks like a tie and defer the decision
Correct answer: B. Promotions must be decided against level expectations with a candid development conversation for the other, not by tenure, avoidance, or fudging.
A powerful stakeholder repeatedly overrides your team's evidence-based design decisions with personal preference, and quality is suffering. What's the best long-term move?
- A. Keep complying to preserve the relationship
- B. Build a shared decision framework and evidence practice with them, and escalate with data if the pattern continues to harm outcomes ✓
- C. Go around them to their boss immediately
- D. Let your team quietly ignore their overrides
Correct answer: B. Sustained misalignment is addressed by establishing a shared evidence-based decision process, escalating with data only if needed — not by ongoing capitulation, going rogue, or immediate end-runs.
You realize your own strongest skill — hands-on craft — is now less valuable to the team than your ability to develop others, but you love the craft. How should you resolve this?
- A. Keep taking the best design work because that's where you add most value
- B. Consciously shift your time toward multiplying the team, keeping selective hands-on work for leverage and credibility ✓
- C. Stop doing craft entirely and become a pure manager
- D. Do craft on your own time and manage during the day
Correct answer: B. A player-coach maximizes impact by multiplying the team while keeping selective high-leverage craft, rather than clinging to marquee work or abandoning the craft that grounds their credibility.
Design and product leadership disagree on strategy: product wants speed, you believe the current UX debt will sink the product. How do you make your case?
- A. Insist on a UX-quality freeze until the debt is paid down
- B. Quantify the debt's business cost, propose a phased plan that balances speed with targeted fixes, and align on shared risk thresholds ✓
- C. Defer to product since they own the roadmap
- D. Slow your team's delivery quietly to force attention on quality
Correct answer: B. Executive-level disagreements are won by quantifying impact and proposing a balanced, shared plan, not by ultimatums, silent deference, or passive resistance.
You need to decide whether to hire a senior designer externally or promote from within into a gap. What should drive the decision?
- A. Always promote internally to reward loyalty
- B. Assess whether internal candidates can grow into it with support versus whether the gap needs skills only an external hire brings, weighing team morale ✓
- C. Always hire externally to bring in fresh thinking
- D. Choose whichever is faster to fill the role
Correct answer: B. The build-vs-buy people decision hinges on capability gaps, growth potential, and team impact — not blanket rules or speed alone.
Your team consistently produces high-craft work, but the business isn't seeing the value and design's influence is shrinking. What's the core problem to fix?
- A. The team needs to raise the craft bar even higher
- B. The team is optimizing for polish over outcomes; refocus everyone on measurable user and business impact and tell that story ✓
- C. The team needs to produce work faster
- D. Leadership simply doesn't appreciate design
Correct answer: B. When craft is high but influence is low, the fix is reorienting the team from polish to outcomes and communicating impact — not more polish, more speed, or blaming leadership.
A star designer threatens to quit unless you give them a promotion they aren't yet ready for. How do you handle it?
- A. Promote them to retain them — losing them is too costly
- B. Be honest about where they stand against the level, lay out a concrete path, and accept the risk they may leave rather than promote unfairly ✓
- C. Match a competing offer with a raise instead
- D. Promise the promotion next cycle to buy time
Correct answer: B. Promoting under a retention threat undermines fairness and the level's credibility; the right move is honesty about readiness with a real path, accepting the attrition risk.
You're asked to justify keeping the design team centralized versus fully embedding designers in engineering teams. What's the most balanced position?
- A. Insist on full centralization to protect craft and culture
- B. Recommend a hybrid — embedded for proximity to product, with a central function for standards, growth, and community — based on what serves outcomes ✓
- C. Fully embed everyone since that's what partners want
- D. Let each designer choose their own reporting line
Correct answer: B. Mature org design usually blends embedding for context with a central function for craft and growth, chosen to serve outcomes rather than turf or convenience.
Half your roadmap is being reallocated to a new AI initiative and your designers are anxious about their relevance. As lead, what's your priority?
- A. Reassure them nothing will change to keep everyone calm
- B. Be transparent about the shift, reframe where design adds value in the new direction, and help each designer find their place in it ✓
- C. Wait for clarity from above before saying anything
- D. Quietly start looking to replace those who can't adapt
Correct answer: B. Leading through change means transparent communication and actively repositioning the team's value, not false reassurance, silence, or writing people off.
You have to choose: invest this quarter's design capacity in a big bet that could 10x impact but might fail, or in reliable incremental improvements. How do you decide?
- A. Always take the safe incremental work to protect the team's track record
- B. Weigh the portfolio — balance a de-risked slice of the big bet with reliable wins, based on the business's appetite and stage ✓
- C. Always take the big bet since that's where design leads should aim
- D. Let the team vote on which they find more exciting
Correct answer: B. Allocating scarce capacity is a portfolio decision balancing risk and reliable value against business context, not a blanket bias or a popularity vote.
A retro reveals your team consistently over-invests in polish on low-impact features and under-invests on high-impact ones. How do you correct this systemically?
- A. Tell everyone to spend less time polishing
- B. Build a shared prioritization and 'good enough for this context' framework so the team calibrates effort to impact itself ✓
- C. Personally decide the fidelity level for every project
- D. Add stricter deadlines to force faster work
Correct answer: B. Chronic mis-allocation of effort is fixed by teaching the team to calibrate craft to impact through a shared framework, not by blanket instructions or micromanaging fidelity.
An executive wants design to 'move faster' and suggests skipping research. You believe research is preventing costly mistakes. What's the strongest response?
- A. Agree to skip it to show design can be fast
- B. Show the concrete cost of past decisions made without research, then propose lean research methods that add speed, not drag ✓
- C. Refuse to ship anything without full research
- D. Do the research quietly anyway without telling them
Correct answer: B. You defend a practice by proving its ROI with evidence and adapting it to be lean, not by capitulating, rigidly refusing, or hiding the work.
Your team's impact is real but invisible to leadership, so design is left out of key decisions. What's the most effective long-term fix?
- A. Wait to be invited once leadership notices the quality of the work
- B. Establish a regular narrative — tie design work to outcomes leadership cares about and build relationships with decision-makers ✓
- C. Produce louder, flashier presentations of the work
- D. Ask your manager to insist design gets a seat at the table
Correct answer: B. Sustained influence comes from consistently telling an outcomes-based story and building trust with decision-makers, not from waiting, flash, or borrowed authority.
You must let go of a loyal, hardworking designer whose skills the team has outgrown, despite their effort. How do you handle it best?
- A. Keep them in a diminished role because they try hard
- B. Make the decision with fairness and dignity — clear rationale, support for their transition — once you're confident coaching won't close the gap ✓
- C. Delay indefinitely because they're well-liked
- D. Quietly push them out by starving them of good work
Correct answer: B. When effort can't close a capability gap, the humane and responsible path is a fair, dignified, well-supported exit — not indefinite delay or a passive-aggressive squeeze-out.