Design Strategy, Vision, and Leadership Questions

Decision rubric — ICF (Impact × Confidence) / Effort

• Impact (1–5): business / user benefit if answered (reduced churn, conversion, accessibility).
• Confidence (1–5): how likely research will give a clear action.
• Effort (hours or points): recruitment, study type, analysis time.
• Priority score = (Impact × Confidence) / Effort — higher = prioritize.

How I apply it (hypothetical scale: Impact/Confidence 1–5; Effort in points: 1 low–5 high)

1. "Why do new users drop off during onboarding?"

• Impact = 5 (affects activation/churn)
• Confidence = 5 (qual surveys + 5 usability sessions will reveal clear fixes)
• Effort = 3
• Score = (5×5)/3 = 8.3 → High priority
• Method: 5 moderated usability sessions + funnel analytics.

2. "Does the new pricing layout increase purchase intent?"

• Impact = 4 (revenue-related)
• Confidence = 3 (needs A/B + qual follow-up)
• Effort = 4
• Score = (4×3)/4 = 3.0 → Medium priority
• Method: remote A/B test + post-test survey.

3. "Are our forms accessible to screen-reader users?"

• Impact = 3 (legal + inclusivity, affects subset)
• Confidence = 4 (expert audit + 3 sessions with assistive tech)
• Effort = 2
• Score = (3×4)/2 = 6.0 → Medium-high priority
• Method: accessibility audit + targeted testing.

Rationale: this rubric balances user/business impact and likelihood of actionable insight against cost. I re-evaluate after quick discovery (2–3 quick sessions) to avoid sunk-cost decisions.

Overview — approach
I convert raw qualitative data into actionable, ranked recommendations in three phases: Synthesis, Framing, Scoring. I work collaboratively with PMs and engineers to ensure feasibility and ownership.

1) Synthesis

• Gather artifacts: transcripts, notes, session clips, affinity clusters.
• Create evidence cards: quote, user, context, severity, frequency tag.
• Build patterns: cluster evidence into themes and opportunity statements.

2) Framing

• For each theme write: Problem statement, who it affects (persona & scenarios), observable behavior, success metric (quantifiable).
• Suggest 1–2 solution directions and implementation risks.

3) Scoring (prioritization)

• Use three axis: Impact, Confidence, Effort. Score 1–5 each.
• Compute Priority = (Impact * Confidence) / Effort; sort descending.
• Review with PMs for business alignment.

Recommendation template

• Title:
• Problem statement (1 line):
• Evidence (3 strongest quotes / observations):
• Affected personas & frequency:
• Proposed recommendation:
• Success metric (KPI + target + measurement method):
• Risks & dependencies:
• Score: Impact / Confidence / Effort — Priority value:
• Owner & next steps:

Scoring criteria

• Impact: degree to change core metric or user retention (1 low — 5 high)
• Confidence: quality & quantity of evidence (1 anecdote — 5 replicated + quantitative)
• Effort: engineering + design + infra complexity (1 trivial — 5 large)

Example

• Finding: "Many new users abandon onboarding at step 3 because they can’t find their company code." (observed in 8/12 sessions)
• Recommendation: Add inline helper + auto-detect org by email domain; show progress + error hint.
• Success metric: reduce onboarding drop-off at step 3 from 40% → 20% in 6 weeks (A/B test).
• Evidence: three quotes, session clips.
• Score: Impact 5 / Confidence 4 / Effort 2 → Priority = (5*4)/2 = 10 (high)
• Owner: PM + Designer; next step: prototype & 2-week test.

Overview / Approach
I’d implement a hybrid model: a small central Research Ops team for governance and shared infrastructure, and embedded UX researchers/designers assigned to product squads for contextual depth and speed.

Operational model

• Central Research Ops (3–5 FTE): strategy, recruitment panel, tooling, repository, QA, metrics.
• Embedded researchers (1 per 2–3 squads) rotate across squads quarterly to retain context.
• Governance board (PM + Eng + Design leads) for prioritization and ethics.

Staffing

• Research Ops Lead, Recruiter, Data Analyst, Repository Admin, Researchers embedded in squads.
• Pool of contract moderators for peak studies.

Tooling & Templates

• Tools: UserZoom/Lookback, Dovetail, Airtable for panels, Figma for prototypes, Slack + Notion for comms.
• Templates: study plan, screener, consent, discussion guide, synthesis brief, reusable persona and JTBD templates.

Training

• Bootcamp: research fundamentals, recruiting, bias mitigation, rapid guerrilla testing.
• Monthly brown-bags, office hours with Research Ops, playbooks for common methods.

Incentives & Reuse

• KPI: time-to-insight, reuse rate of artifacts, cross-team impact stories.
• Incentives: credit system for using shared assets (allocates Ops support), recognition in OKRs, shared library with contributors’ attribution.
• Regular “Show & Tell” demos and synthesis clinics to surface reusable insights.

This balances rigor (central standards, panel management, QA) with contextual relevance (embedded roles, rotation, squad alignment).

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.

Learning objectives

• By end: identify journey-map components (persona, stages, touchpoints, emotions, moments of truth), read insights vs. assumptions, and apply one change to a backlog item.

Facilitation script (5–7 mins)

• Intro (30s): "I'm [Name], we'll learn to read journey maps to inform engineering decisions."
• Walk the map (4 mins): Point to persona, timeline/stages, channels, actions, painpoints, emotion curve. Explain evidence sources (research quotes, metrics).
• Show one example: call out a tech constraint that caused a friction and a proposed fix.

Micro exercise (10 mins)

• Split into 3 pairs. Give each pair a printed 1-page map + ticket list.
• Task (7 mins): Mark top 2 engineering-impacting painpoints and write one concrete acceptance criterion to reduce friction.
• Share (3 mins): One pair reads theirs.

Follow-up

• Share annotated map and participants' criteria in Slack + Confluence template.
• Offer 30-min office hours for sprint planning integration.
• Two weeks later review one implemented change's metric or qualitative feedback in a retro.