Posts tagged product.
54 posts from the Talkful blog.
How to run a design sprint that ships a decision
How to run a design sprint from Monday's map to Friday's test, plus the 4-day 2.0 variant and the failure modes that turn the week into theatre.
How to run a Wizard of Oz test before you build
How to run a Wizard of Oz test on a feature you have not built yet: what to simulate, how to script the wizard, and what to synthesize.
How to run user research on AI features
How to run user research on AI features: what to test, seed questions around observable behavior, probe depth, placement, and reading the synthesis.
How to build an assumption map for product discovery
How to build an assumption map that changes decisions: the four hypothesis types, the importance-vs-evidence 2x2, and the tests that follow it.
How to prepare for user interviews
How to prepare for user interviews that hold up: anchor to a decision, sharpen the question, recruit tight, write a real guide, plan probes, pilot once.
How to run a fake door test that gives real signal
How to run a fake door test that returns real demand signal, not just clicks. The setup, the CTR thresholds, and how to capture the why behind every tap.
How to build a user story map that ships
How to build a user story map: frame the job, lay the backbone, cut the walking skeleton, and let real participants fill the ribs under each step.
How to run in-depth user interviews
How to run in-depth user interviews that produce evidence, not opinions. The six steps, the failure modes, and how async voice scales the same depth.
How to write a problem statement that holds up
How to write a problem statement anchored to participant verbatim, ranked by evidence, and tied to a decision the team is going to make this sprint.
How to build a service blueprint that survives
How to build a service blueprint that survives the quarter: pick one journey, draw the three lines, and fill the swimlanes with real customer talk.
Generative vs evaluative research: when to use each
Generative vs evaluative research: how to tell the modes apart, when each pays off, and how to pick the method that fits the decision you owe.
Qualitative vs quantitative user research: when each wins
Qualitative vs quantitative user research: what each measures, when each wins, and how AI synthesis collapses the depth-vs-scale trade-off for product teams.
How to run a first-click test that explains the click
How to run a first-click test that captures the click and the reasoning behind it, then turns both into a navigation decision the team can ship.
How to run a heuristic evaluation that finds real friction
How to run a heuristic evaluation: Nielsen's 10 heuristics, who to recruit, how to score severity, and where the method pairs with user research.
How to choose a user research method
How to choose a user research method by the question you're trying to answer. A decision frame for product teams who need signal fast.
How to scale user research without scaling researchers
How to scale user research with async capture, AI synthesis, and per-surface probing depth, so the program grows without the team having to.
How to validate a startup idea with user research
How to validate a startup idea with user research: the founder's playbook for finding real demand, not polite approval, before you write any code.
How to run a 5-second test without ignoring the why
How to run a 5-second test that captures the first impression and the reasoning behind it, then turns both into a design decision the team can ship from.
Moderated vs unmoderated user research, when to use each
Moderated vs unmoderated user research: when each one wins, where each one quietly breaks, and the hybrid pattern most product teams end up on.
How to write effective screener questions
Write screener questions that filter participants to the people who can actually answer your research question. Templates, traps, and prompts to avoid.
How to run a contextual inquiry
How to run a contextual inquiry: scope the work, observe in context, probe in the moment, turn the field notes into a decision the team ships.
How to identify customer pain points that matter
How to identify customer pain points by anchoring each one to a verbatim from a real participant, then ranking by frequency, severity, and reach.
How to run an affinity diagram for user research
How to run an affinity diagram that ends in a decision, not a wall of sticky notes: the KJ method, why workshops stall, and what real synthesis looks like.
How to write a user research brief
How to write a user research brief that aligns stakeholders: one decision, one research question, the hypotheses, segments, and synthesis cadence.
How to run tree testing without faking the task
How to run tree testing that validates IA: the method, the failure modes, and what reasoning probes catch that pass/fail tools miss.
How to run a Kano model analysis
A practical guide to a Kano model analysis: the functional and dysfunctional question pair, the classification grid, and the follow-up that surfaces the why.
How to build an empathy map from real participants
How to build an empathy map from real participant talk, not a workshop room: scope, the four quadrants, evidence, and what to ship from it.
How to reduce researcher bias in user interviews
A working guide on researcher bias in user interviews: the seven distortions to watch for, the protocol that holds, and what AI changes.
How to present user research findings to stakeholders
How to present user research findings as a one-page call stakeholders ship from, not a 38-slide deck that gets archived inside Notion.
How to run card sorting without losing the why
How to run card sorting that maps real mental models: the method, the failure modes, and what reasoning probes catch that drag-and-drop tools miss.
How to build a customer journey map that survives
How to build a customer journey map that survives the quarter: pick a job, place links at each stage, and let real participants fill the columns.
How to run a beta test that ships the right product
How to run a beta test that shapes the product instead of just collecting bug reports. A working methodology guide for product teams in 2026.
How to build a user research repository
How to build a user research repository that survives a quarter: structure, intake, synthesis, retrieval rituals, and governance.
How to run customer discovery interviews
How to run customer discovery interviews that test a falsifiable hypothesis instead of validating a wish, with the rules that hold up async.
How to build an opportunity solution tree
How to build an opportunity solution tree that holds up: the outcome, the opportunities, the solutions, and the discovery rhythm that keeps it alive.
How to write NPS follow-up questions that work
How to write NPS follow-up questions that surface the real reason behind a customer's score. Placement, prompts, probing depth, and synthesis.
How to run AI moderated user interviews
How to run AI moderated user interviews: seed questions, configurable probe depth, placement, and when to keep a human in the loop.
How to apply the Mom Test in user interviews
How to apply the Mom Test in user interviews so participants reveal real behavior, not the polite version they think you want to hear.
How to run a win-loss analysis that finds signal
How to run a win-loss analysis: where to place the prompt, what to ask, and how AI synthesis turns deal interviews into roadmap decisions.
How to build user personas without inventing them
How to build user personas grounded in real participant evidence, not invented from imagination, with the steps to keep them honest after launch.
How to run stakeholder interviews before you build
How to run stakeholder interviews async: one link, every viewpoint (legal, security, engineering, support), a synthesized brief before you ship.
How to run pricing research that holds up at launch
How to run pricing research that returns a price band, not a flattering number: the method, the traps that hide demand, and what voice catches.
How to run usability testing that surfaces real friction
How to run usability testing that returns real friction: the method, the failure modes, and what voice catches that screen recording misses.
How to run concept testing without faking the result
How to run concept testing that predicts whether a product will work: the method, the traps that fake the result, and what voice catches that text loses.
How to run a product-market fit survey
How to run a product-market fit survey that returns a roadmap, not just a score: who to survey, the four questions, and how to read the open answers.
How to run churn interviews that find signal
A working playbook for running churn interviews: where to place the prompt, what to ask, and how to synthesize what customers say on the way out.
How to write a user research plan
How to write a user research plan that survives contact with the team: one decision, one research question, the right method, and a synthesis cadence.
How many user interviews do you need?
How many user interviews do you need? A working answer by study type, with the saturation evidence, and what changes when interviews are async and cheap.
How to build a customer feedback loop that closes
How to build a customer feedback loop that closes: where to place the link, what to ask, and how AI synthesis turns responses into decisions.
How AI follow-up questions work in user research
What AI follow-up questions are, when an AI moderator should probe, and how to choose the right depth for each question in async user research.
AI-powered async user research, defined
What AI-powered async user research actually is, why the AI part is load-bearing, and where it beats a calendar invite or a long survey.
How to synthesize user research
How to synthesize user research into one decision-grade artifact: cluster themes, weight frequency against importance, and keep the voice in the room.
How to run jobs to be done interviews
How to run jobs to be done interviews that surface the real switch: the four forces, the timeline, and what voice catches that writing erases.
How to run continuous discovery interviews
How to run continuous discovery interviews every week without scheduling live calls: cadence, prompts, recruitment, and async voice synthesis.