Design Strategy, Vision, and Leadership Questions

Clarify goals & constraints
Maintain consistent UX, accessibility, and brand while enabling each squad to move fast and own local product decisions. Low friction reviews, clear ownership, measurable outcomes.

High-level process

• Design Guild (cross-squad designers + 1 lead) sets principles, patterns, and guardrails.
• Squad Owners (designer + PM) run local reviews for feature fit and implementation.
• Periodic Gate Reviews for high-impact changes (every sprint for major launches).

Core components

• Design System + component library (Figma + Storybook) as source-of-truth.
• Lightweight Request flow: Squad files a “Design RFC” template in Confluence + Figma link.
• Async review first (Slack thread + Loom), followed by 30-min synchronous review if needed.

Decision rights

• Squad-level: routine UI/UX, low-risk experiments, A/B tests.
• Guild-level: shared components, patterns, accessibility, branding changes.
• Product Council (PM + Design Lead + Engineering Lead): product direction, blocking cross-squad changes.

Conflict resolution

• 1. Evidence-first: user research, analytics, accessibility tests.
• 2. Escalate to Design Lead if unresolved; they arbitrate within 48 hours.
• 3. If still contested, Product Council decides on business trade-offs; document ruling and rationale.

Tooling & metrics

• Figma + Abstract/Branches for versioning, Storybook for dev parity, Jira RFC tickets, Slack + weekly sync.
• Track consistency via periodic UX audits, component usage metrics, and experiment outcomes.

This balances autonomy (fast local decisions) with governance (guild + council) and uses async tooling to scale.

Definition — Design advocacy
Design advocacy is the active practice of representing users’ needs, design principles, and research evidence across the product organization so decisions prioritize usable, coherent, and valuable experiences. As a product designer I translate user insight into clear recommendations, coach teams on UX trade-offs, and keep design visible in planning and delivery.

Why it matters

• Product: Improves roadmap prioritization by grounding features in user value.
• Engineering: Reduces rework by specifying clear interactions and acceptance criteria.
• Business: Increases conversion/retention by aligning product with real user problems.

Three immediate, concrete benefits + one-line day-to-day examples

1. Faster alignment — Example: A 5‑minute demo of user research at sprint kickoff prevents disputed requirements.
2. Fewer costly reworks — Example: Early interactive prototype uncovers a workflow issue before engineering starts.
3. Stronger metrics focus — Example: Designer-proposed success criteria (drop-off rate target) guide A/B test setup.

Situation & goal
I run exec-facing critiques to get rapid, outcome-oriented decisions while protecting design quality and user needs. My objective is alignment on trade-offs and a clear next step.

Preparation

• Speak with PM/engineering ahead to surface business constraints and decision criteria.
• Distill research into 1–2 key user problems and measurable success metrics (eg. conversion lift, task time).
• Prepare a 1-slide TL;DR with ask, success metrics, and options.

Artifacts to bring

• 1-slide summary (ask + KPIs)
• 2–3 high-fidelity journeys or prototypes showing primary flow + alternate option(s)
• Short evidence snippets: one quote, one usability finding, and quantitative signal.

Framing the discussion

• Start with the ask and metric-oriented success criteria.
• Show user problem, evidence, then proposed solution(s).
• Present options as trade-offs: impact, confidence, cost, time-to-ship.

Tactics to stay outcome-oriented

• Timebox: 5 min TL;DR, 10–15 min discussion, 5 min decision.
• Use a decision framework (RICE or simple Impact vs Risk matrix) on-screen.
• Surface values by asking: “Which trade-off matters most here — speed, revenue, or long-term UX?”
• If debate stalls, offer a lightweight experiment (A/B or prototype test) and recommend guardrails for launch.

Preserving design integrity

• Anchor suggestions to user evidence and the chosen metric.
• Offer phased approach: ship minimal change that protects core UX, iterate with data.
• Document the decision, rationale, and follow-up experiments.

Result: executives make faster, metric-aligned decisions; design retains user-centered rationale and a clear plan for validation.

One‑Slide Executive Brief — Template (Product Designer POV)

Headline — single sentence summary of finding and business outcome

• Why execs care: fast signal on importance and direction for decisions.

One Key Metric — one KPI and current vs. target (e.g., Conversion: 3.2% → 4.5%)

• Why execs care: quantifies impact and prioritizes attention.

Short User Story — 1–2 lines: who, need, pain (e.g., “Busy shoppers abandon at checkout due to shipping surprise”)

• Why execs care: humanizes metric and links to customer retention/revenue.

Recommended Action — concise proposal (what to do, MVP scope, owners, timeline)

• Why execs care: shows a clear path and resource implications.

Estimated Impact — projected benefit with confidence and assumptions (e.g., +$1.2M ARR, 70% CI)

• Why execs care: ties action to financial outcomes and risk.

Ask — specific request (budget, headcount, experiment approval) and deadline

• Why execs care: makes decision simple and timebound.

Example headline (revenue): “Reducing checkout surprises could lift conversion 1.3pp and drive $1.2M ARR.”

Situation / Brief
I led a redesign of our mobile onboarding (goal: increase 2-week activation from 18% → 30%). After launch KPIs fell to 12%. I ran a structured post-mortem to learn why and fix it.

Root-cause analysis

• Discovery: user research sample biased toward power users; we missed new-user pain points (assumptions about attention span).
• Design: flow added progressive disclosure that hid critical affordances; cognitive load increased.
• Engineering: performance regressions (first-render +600ms) from unoptimized animations; A/B flags misconfigured so some users saw mixed variants.
• Launch/ops: rollout cadence too fast (100% in 48h) with inadequate monitoring and rollback plan.

Metrics analyzed

• Activation conversion (day 1, day 7, week 2)
• Time-to-first-success, task completion rate per step
• Drop-off funnel by screen, heatmaps, session recordings
• Performance: TTFB, first-contentful-paint, animation frame times
• Variant exposure logs and error rates

Corrective actions taken

• Rolled back to prior flow for 60% of users, paused rollout.
• Hotfix to remove heavy animations and restore affordances; fixed A/B targeting bug.
• Ran rapid moderated usability tests with true new users; iterated flow to surface core action earlier.

Process changes implemented

• Discovery: mandated representative recruiting (new users + quotas) and prototype validation with low-fidelity tests before visual design.
• Design: required measurable hypothesis for every change + success criteria; added pre-launch usability checklist.
• Engineering: performance budget and pre-release perf gate; stricter feature-flagging controls and canary rollout (10% → 50% → 100%).
• Launch/Monitoring: real-time dashboards for key metrics and automated rollback thresholds; weekly cross-functional post-release reviews.

Outcome & learning
Within six weeks the revised flow recovered to 25% activation; team adopted the new processes and prevented similar regressions in subsequent launches.