Design Advocacy and Influence Questions

Focuses on championing user centered practices and design thinking inside an organization. Includes building buy in for user research, influencing product and engineering stakeholders with evidence and narrative, making the business case for user focus, changing processes to embed research, teaching non designers to use research outputs, handling resistance and trade offs between speed and rigor, measuring the impact of advocacy, and strategies for incrementally growing research and design culture across teams.

EasyTechnical

21 practiced

You have 30 minutes to run a Lunch & Learn for engineers to teach them how to read and use a journey map. Provide an outline with learning objectives, a short facilitation script, a micro exercise (10 minutes), and how you'd follow up to ensure usage.

MediumSystem Design

39 practiced

You are launching a 'research-on-demand' service for engineers and PMs. Define the intake form fields, a prioritization rubric, expected SLAs for common request types, and a short communication plan to set expectations about trade-offs and capacity.

EasyTechnical

35 practiced

Describe a simple, concrete metric you could show to a product manager after a usability test to influence prioritization. Explain how you would compute it, what threshold would trigger action, and how you would present the result visually in a short meeting.

Sample Answer

**Metric — Task Success Rate (TSR) for a critical task**

- What it is: % of users who complete a defined, high-priority task (e.g., checkout, sign-up) without help or error.- Why it influences prioritization: directly ties usability to conversion and customer effort.

**How to compute**1. Define success criteria (e.g., reaches confirmation screen within 3 attempts, no critical errors).2. Count successes and attempts across N participants.3. Formula:

text

TSR = (number of successful users / total users who attempted task) * 100

Plain-English: percent of users who completed the task.

**Threshold to act**- Target ≥ 85%. Flag for prioritization if TSR < 80% or if critical errors occur for >20% of users.

**How I’d present in a short meeting (1 slide, 3 points)**- Headline: “TSR for Checkout: 62% → Urgent UX Fix Recommended”- Visual: single horizontal bar chart showing target (85%) as a marker, actual TSR bar, and sample size (N=10). Right column: 2–3 quick quotes and top 2 error types.- Recommendation: quick next step (A/B fix, prototype iteration) and estimated impact (e.g., potential +X% conversion).

This is concrete, measurable, and directly actionable for PM prioritization.

HardTechnical

24 practiced

Product decisions are currently driven solely by quantitative metrics and leadership is unaware of accessibility issues that affect about 10% of users. Design a step-by-step strategy to influence leadership to invest in accessibility remediation, including which stakeholders to engage, what evidence to collect (qualitative and quantitative), how to frame costs and benefits, and a small pilot plan to start work quickly.

Sample Answer

**Overview / Goal**I would persuade leadership to invest in accessibility remediation by combining targeted stakeholder engagement, paired quantitative + qualitative evidence, a cost/benefit framing tied to business metrics, and a 6–8 week pilot to demonstrate impact quickly.

**Step-by-step strategy**1. Stakeholder map (who to engage) - Product VP, PMs owning affected features, Engineering lead, QA, Legal/Compliance, Customer Support, Sales, and one executive sponsor (e.g., Head of Product). - Bring in users with disabilities and accessibility champion(s) from engineering/design.

2. Collect evidence - Quantitative: analytics showing 10% affected cohort (drop-offs, conversion gaps, task completion rates), accessibility audit scores (WCAG failure counts), customer support tickets related to accessibility, potential revenue at risk. - Qualitative: 5–8 moderated usability sessions with users who have disabilities, annotated recordings, verbatim quotes, and one emotional journey map showing pain points.

3. Frame costs and benefits - Costs: scoped engineering hours, QA, design resources, and potential temporary sprint re-prioritization. Provide a three-tier estimate (quick fixes, medium effort, major refactor). - Benefits: increased conversions, reduced support costs, legal risk mitigation, improved NPS/retention, positive brand value. Model ROI with conservative lift assumptions (e.g., 5% of lost conversions recovered → revenue delta).

4. Messaging to leadership - Start with business impact (revenue, conversion, legal risk), then human stories (short user video clip + quote), then a clear asks (budget, timeline, sponsor). - Offer phased approach to limit risk.

5. Pilot plan (6–8 weeks) - Week 0: Align goals, KPIs (e.g., +task completion, -support tickets), and target pages/components. - Weeks 1–2: Run focused automated + manual audit; recruit 5 users for baseline usability tests. - Weeks 3–5: Implement prioritized quick wins (ARIA fixes, labels, color contrast, keyboard navigation). - Week 6: Re-test with users, measure KPIs, present results and ROI projection.

**Success metrics**- Task completion lift, reduction in abandonment, fewer accessibility-related tickets, NPS changes, and time-to-resolution for fixes.

**Why this works**- Combines leadership’s data-driven preference with emotional, human evidence; low-risk pilot demonstrates measurable impact and builds momentum for broader investment.

MediumTechnical

19 practiced

Design a 90-minute workshop to teach product managers to use personas for prioritization. Provide an agenda, two hands-on exercises (with prompts), required materials, and a follow-up plan to ensure the workshop's outputs are used in sprint planning.

Sample Answer

**Overview (90 min)** Goal: Teach PMs to use personas to make prioritization decisions that align with user needs and business impact.

**Agenda (90 min)** - 0–10 min: Welcome, objectives, quick persona primer (why personas matter for prioritization) - 10–25 min: Review existing personas (3–4) — assumptions & evidence mapping - 25–45 min: Exercise 1 (group) — Persona Impact Mapping - 45–55 min: Break + quick share-outs - 55–75 min: Exercise 2 (team) — Prioritization with Personas (RICE + persona-fit) - 75–85 min: Consolidate decisions into backlog slices - 85–90 min: Next steps & commitments

**Exercise 1 — Persona Impact Mapping (20 min)** Prompt: In groups of 3, pick one persona. List top 5 jobs-to-be-done and pain points. For each proposed feature (provide 6 candidate features), rate expected impact on persona (High/Med/Low) and evidentiary confidence (A/B/C). Deliverable: 1 impact matrix (feature × impact × confidence).

**Exercise 2 — Prioritization with Personas (20 min)** Prompt: Using the impact matrix, apply a lightweight RICE variant where Reach = % of persona affected, Impact = High/Med/Low mapped to 3/2/1, Confidence as multiplier (0.5/0.75/1). Compute scores, pick top 3 items for next sprint, and write one acceptance criterion per item tied to persona outcome. Deliverable: Ranked list + 3 persona-aligned acceptance criteria.

**Materials** - Printed persona one-pagers (or Figma file) - Feature cards (6) per group - Impact matrix templates (A3) or Miro board - Sticky notes, markers, timers, laptop with calculator

**Follow-up / Adoption Plan** - Within 48 hrs: Share consolidated matrix and prioritized list to PMs and dev leads. - Before sprint planning: Require each backlog item to include “Primary persona” and one persona outcome acceptance criterion; PMs present persona justification (2 min). - After first sprint: 1-week async retrospective on persona alignment (what matched user outcomes) and update persona confidence levels. - Monthly: UX owner audits top-10 backlog items for persona tagging and runs quick usability checks for highest-priority persona.

This structure ties personas directly to prioritization scores and sprint criteria, making adoption practical and measurable.

Unlock Full Question Bank

Get access to hundreds of Design Advocacy and Influence interview questions and detailed answers.

Join thousands of developers preparing for their dream job.