UX Research & Discovery

Designs unbiased surveys - question types, Likert and frequency scales, screener-to-demographics flow, and a cognitive pilot plan - that produce trustworthy quantitative data. Use when someone says "write survey questions about X", "review my survey for bias", "how long should this questionnaire be", or wants to quantify attitudes, behaviors, or satisfaction. Do NOT use for full study design with hypotheses, sampling method, and power analysis - use primary-research instead; for qualitative interview scripts, use interview-guide-builder; for segment profiles built from the results, use user-persona.

Plans a usability study - research questions, realistic task scenarios with success criteria, metrics (completion rate, time on task, SEQ, SUS), a recruiting screener, and moderated vs. unmoderated guidance. Use when someone says "plan a usability test", "write task scenarios for our prototype", "how many participants do we need", or is about to put an interface or prototype in front of users. Do NOT use for open-ended discovery interview guides - use interview-guide-builder instead; for analyzing quantitative A/B experiments, use ab-test-analyzer.

Turns raw interview notes into themed, evidence-tagged insights via a two-pass affinity-mapping procedure, with frequency and confidence ratings and stakeholder-ready quotes. Use when someone asks "synthesize these interviews", "what themes came out of our research round", "turn these transcripts into findings", or has finished a qualitative round and needs actionable output. Do NOT use for synthesizing published papers or mixed documents - use research-synthesis instead. Do NOT use for building the personas themselves - use user-persona instead. Do NOT use for consolidating hiring-interview scorecards - use interview-debrief-synthesizer instead.

Extracts Jobs To Be Done from qualitative research data - job stories in the "When I…, I want to…, so I can…" form, a forces-of-progress map (push, pull, anxiety, habit), and functional, emotional, and social dimensions, each backed by verbatim quotes. Use when someone says "extract the jobs from these interviews", "run a JTBD analysis on this diary study", "why do users switch to or from us", or has transcripts and wants solution-agnostic goals rather than feature requests. Do NOT use for clustering findings into themes across a study - use interview-synthesis instead; for building persona profiles from research, use user-persona; for planning the interviews themselves, use interview-guide-builder.

Synthesizes interview notes, surveys, support tickets, and analytics into evidence-based user personas that drive design decisions, with every claim traced to source data. Use when someone asks "build personas from our research", "turn these interview notes into personas", "how many personas do we need", or "are our personas evidence-based". Do NOT use for sales-targeting ideal customer profiles with filterable firmographics and buying committees - use icp-persona-builder instead. Do NOT use for extracting jobs-to-be-done from research - use jtbd-extractor instead.

Turns synthesized research findings into a crisp stakeholder readout - so-what up front, 3-5 confidence-tagged findings each following the finding-evidence-implication rule, and owned recommendations. Use when someone says "present these research findings", "turn this study into a readout for leadership", "our research isn't landing with the product team", or needs a deck or brief that gets findings acted on. Do NOT use for building a narrative around quantitative metrics and charts - use data-story instead; for the upstream analysis that produces the findings, use interview-synthesis or research-synthesis; for slide craft itself, use slide-deck-builder.