How to sync eye-tracking data with DOM events?
WHAT IT TESTS: ability to fuse two real-time data streams with different timestamps and frequencies. OUTLINE: record gaze points with millisecond precision, map to DOM via bounding box lookup, correlate with click events via shared timestamp.
Making D3.js visualizations accessible to screen readers?
WHAT IT TESTS: holistic a11y thinking beyond static fallbacks. OUTLINE: dual-render strategy (viz + semantic table), ARIA live regions for dynamic updates, keyboard event handlers, focus management.
How to diagnose and fix ignored sidebar navigation?
WHAT IT TESTS: ability to connect UX data to technical solutions. OUTLINE: form testable hypotheses (contrast, layout, blocking), propose specific CSS/DOM changes, sketch A/B test plan. RED FLAG: generic suggestions without linking to heatmap patterns.
Fixing text overflow from long localized labels
WHAT IT TESTS: Localization-aware responsive CSS. OUTLINE: Avoid fixed widths, use flexible layouts, allow wrapping or word-break, ellipsis as last resort, pseudo-localize to test.
Translating a Job Story into mobile features
WHAT IT TESTS: Reading context, motivation, outcome from a Job Story. OUTLINE: Decompose situation, motivation, expected outcome; map commute constraints to offline, audio, quick-scan features.
Scaling one researcher across three squads
WHAT IT TESTS: Scaling research without becoming a blocker. OUTLINE: Triage by impact, enable democratized research with guardrails, build reusable templates and a shared repository.
Defining and instrumenting UX KPIs for a feature
WHAT IT TESTS: Translating UX goals into trackable KPIs. OUTLINE: Tie KPIs to user goals via a framework like HEART, define events before building, validate tracking pre-launch.
Tracing a research insight to shipped code
WHAT IT TESTS: Traceability across tools. OUTLINE: Give insights stable IDs, link them through tickets to commits and feature flags via tool integrations, measure outcome metrics.
Architecting a multi-tenant ResearchOps platform
WHAT IT TESTS: Multi-tenant design balancing isolation and sharing. OUTLINE: Tenant isolation model, RBAC plus governance and classification, searchable metadata and a taxonomy for cross-team synthesis.
Privacy compliance in a participant management system
WHAT IT TESTS: Privacy-by-design engineering. OUTLINE: Versioned consent records, data classification and minimization, anonymization or pseudonymization, deletion workflow across stores and backups.
Automating research participant recruitment and scheduling
WHAT IT TESTS: Workflow system design with third-party integrations. OUTLINE: Screener intake, eligibility matching, calendar booking, notifications, incentive payout; handle no-shows and idempotency.
Re-evaluating personas when engagement is low
WHAT IT TESTS: Data-driven challenge to assumptions. OUTLINE: Bring behavioral evidence, separate persona-wrong from execution-wrong, propose joint research to validate or invalidate.
Instrumenting a feature to validate a qualitative insight
WHAT IT TESTS: Turning qualitative pain into measurable signals. OUTLINE: Restate the pain as a hypothesis, define a primary behavioral metric plus guardrails, instrument events, compare against baseline.
Extracting actionable insights from a long report
WHAT IT TESTS: Efficient synthesis and prioritization. OUTLINE: Start with executive summary and recommendations, trace findings to evidence, filter for engineering-actionable items, confirm with the researcher.
Using personas to drive technical decisions
WHAT IT TESTS: Connecting user context to engineering choices. OUTLINE: Derive constraints like device, network, accessibility from personas; let them shape framework, payload shape, performance budgets.
Comparing skewed task-time data without a t-test
WHAT IT TESTS: Knowing test assumptions. OUTLINE: t-test assumes normality and is mean-sensitive to outliers; use Mann-Whitney U on ranks; trade-off is it tests distribution shift, not means.
Checking if a 5% A/B lift is significant
WHAT IT TESTS: Hypothesis-testing fundamentals. OUTLINE: State hypotheses, check predetermined sample and power, run the right test for the metric, read p-value and confidence interval.
Designing an in-house A/B testing platform
WHAT IT TESTS: System design plus statistical rigor. OUTLINE: Config service, deterministic bucketing SDK, metrics pipeline, analysis engine; fix peeking with fixed samples or sequential tests.
Sampling 5% of users for a one-time survey
WHAT IT TESTS: Deterministic sampling plus durable seen-state at scale. OUTLINE: Hash user ID for the 5% gate, persist a 'shown' flag, race-safe single display.
Consistent A/B bucketing across sessions and devices
WHAT IT TESTS: Deterministic, identity-based bucketing. OUTLINE: Hash a stable user ID with experiment salt, not random or cookie-only; beware caches keyed without variant.