Design Strategy, Vision, and Leadership Questions

Definition — Design advocacy
Design advocacy is the active practice of promoting user-centered thinking inside a product organization. As a UX Designer I surface user insights, translate them into clear recommendations, and build shared ownership so decisions reflect real user needs rather than gut or politics.

Why I practice it

• Ensures designs are grounded in evidence, speeding alignment and reducing rework.
• Builds trust with PMs, engineers, and execs so UX work is prioritized and adopted.
• Scales user empathy across teams rather than keeping insights siloed.

Typical activities

• Research briefs and synthesis reports that summarize findings and clear next steps
• Personas, journey maps and decision-focused artifacts for product planning
• Workshops (co-creation, prioritization, design crits) to align stakeholders
• Office hours / brown-bags to answer questions and review trade-offs
• Quick guerrilla testing or demo sessions to validate assumptions

Two direct business outcomes

1. Reduced support costs — clearer flows and content reduce user errors and tickets; research-driven fixes eliminate repeat problems, lowering support volume and SLA expense.
2. Improved conversion — evidence-based UX changes (simpler signup, clearer CTA, reduced friction) increase task completion and conversion rates, directly lifting revenue or activation metrics.

One‑Page Research Brief — Overview
A one‑pager should make the what, why, who, how, and when obvious so non‑designers can approve, recruit, or act quickly.

Essential sections (with suggested word counts)

• Project / Objective (20–30 words): Single sentence stating the decision this research will inform (e.g., “Validate onboarding flow changes to reduce time‑to‑first‑task for new users”).
• Primary Research Questions (30–50 words): 2–4 clear questions (e.g., “Can first‑time users complete X in Y minutes?”).
• Target Users (20–40 words): Persona labels / recruitment criteria (e.g., “New users <1 month, mobile‑first, non‑technical”).
• Methods (30–60 words): Short list: moderated remote usability testing, 5–8 participants, task list, optional survey.
• Timeline & Milestones (20–40 words): Dates for recruitment, sessions, synthesis, and stakeholder review.
• Success Criteria (20–40 words): Measurable thresholds (e.g., task success ≥ 80%, SUS > 70).
• Deliverables (20–30 words): Outputs: recordings, 1‑page findings, prioritized recommendations, raw data.
• Risks / Dependencies (optional, 15–25 words): Any constraints (recruitment difficulty, platform access).

Formatting tips

• Use bullets, bold key numbers/ dates, and icons for quick skimming.
• Keep total length ~250–350 words.

Distribution & Follow‑up to increase uptake

• Share in advance via email + single PDF link; tag stakeholders and call out decisions needed.
• Present a 10‑minute readout at kickoff; invite brief feedback within 48 hours.
• Offer 30‑minute walkthrough of findings and 1‑pager synthesis within 48–72 hours after testing.
• Use a short feedback loop: capture alignment as a single checklist (agree / adjust / block) and log decisions in product tracker.
• Attach clear next steps and owner for each recommendation to convert insights into action.

Situation
At my last company I proposed a redesign of the onboarding flow for a B2B analytics app to reduce time-to-first-value. Research showed new users dropped off at setup (40% abandonment within first 7 days).

Task
My goal was to get product and engineering buy-in to invest ~6 weeks to build a guided, progressive setup with contextual tooltips and a lean checklist.

Action
I advocated by:

• Presenting qualitative quotes from 12 user interviews and quantitative funnel metrics
• Building a clickable Figma prototype showing the reduced steps
• Running a 5-person guerrilla usability test to demonstrate faster completion
• Proposing an A/B test plan with success metrics (activation rate, 7-day retention)
• Mapping estimated engineering effort and ROI

Result / Why it failed
Leadership prioritized a revenue-focused feature and rejected the initiative. Their concern: uncertain impact on top-line in next quarter and limited dev bandwidth. My advocacy failed because I focused more on usability data than business impact and I hadn’t aligned stakeholders early.

Response & Learnings
I accepted the decision, documented research, and ran a smaller low-effort experiment: an in-app setup email sequence tied to analytics tracking. It improved activation by 7%—evidence I later used.

Structural changes implemented

• Started co-creating success metrics with PMs at project kickoff (activation > revenue correlation)
• Began briefing stakeholders with a 1-page business case plus prototype
• Instituted weekly “design sync” with PM and Eng to surface trade-offs earlier
• Built a lightweight experimentation plan for small wins before asking for large investments

These changes increased stakeholder alignment and led to two later UX initiatives being funded after I demonstrated measurable lift.

One‑Page Evidence-Based Storyboard — Required Elements

• Title: concise outcome-focused headline (one line)
• One‑sentence problem: crisp statement of user pain
• Customer vignette: 1–2 short sentences/persona quote illustrating the pain
• Key data points: 1–3 metrics (qualitative + quantitative) with sources and sample sizes
• Business impact: estimated impact on KPIs (conversion, retention, NPS, cost) and monetary estimate if possible
• Root cause: brief UX diagnosis (where in flow the friction occurs)
• Recommended action: specific fix, effort estimate (S/M/L), and owners
• Risk of inaction: short consequence statement
• Success metrics & timeline: 2–3 measurable outcomes and when to expect them
• Ask: clear decision requested (approve prototype, allocate dev sprint, fund research)

Example (three sentences):
Title: "Checkout Dropoff from Confusing Promo Flow Costs $1.2M/yr." One customer report: ‘I abandoned payment because entering two promo codes crashed the page’—in a usability test 7/10 users failed to complete checkout and production analytics show a 12% higher abandonment rate on promo screens (N=18 tests, 30k sessions/month). Fix: collapse promo input into one validated field + add inline error messaging (effort: 1 sprint, owner: Product + Eng); expected 4–6% lift in conversion within 8 weeks, recovering ~$400–600k/yr—requesting approval to prioritize for next sprint.

Situation & Task (S/T)
At a fintech startup, product leadership resisted redesigning the onboarding flow after quantitative drop-offs — they believed users abandoned for pricing, not UX. I was tasked with convincing them to act on user research to improve activation.

Action (A)

• Ran 6 moderated usability sessions and captured screen recordings and verbatim quotes in Dovetail.
• Reframed the problem from “pricing” to “first-time task friction” using a clear customer quote: “I can’t find where to link my bank — I give up.”
• Built a quick Figma prototype with a streamlined bank-linking flow and ran a 2-week A/B test (n=1,200) vs. control.
• Presented results in a short demo, highlighting session clips, heatmap evidence, and statistical lift.

Result (R)
A/B variant increased successful onboarding completion by 18% (p < 0.05) and reduced support tickets about linking by 42%. Leadership approved the redesign rollout and allocated dev resources for full implementation.