From software problem to a clear next step.
Choose a topic and what you need to do next. Add a search phrase to find a specific problem.
Browse 20 topics
Explore the playbooks
1500 guides · Page 17 of 60
-
Triage Discovery Assumptions Before Building
Scope discovery assumptions with observable evidence, affected users, and open questions before a team commits to a feature or product direction.
-
Prioritize Discovery Assumptions by Learning Value
Rank discovery assumptions by consequence, uncertainty, and learning value so research effort reaches the bets that could change the product direction.
-
Investigate a Discovery Assumption With Evidence
Build a reproducible discovery brief by testing an assumption against observed behavior, competing explanations, and the context in which the decision matters.
-
Verify a Discovery Assumption With a Clear Test
Define an observable pass condition for a discovery assumption, compare results with the planned baseline, and record the boundary of what the test supports.
-
Turn Assumption Tests Into Discovery Practice
Capture what an assumption test changed, convert it into a reusable discovery habit, and set a signal for revisiting similar bets later.
-
Triage Competing Product Opportunities
Scope competing product opportunities by user, context, evidence strength, and the decision each opportunity could change next.
-
Prioritize Opportunities With Evidence and Tradeoffs
Rank product opportunities by user consequence, reach, confidence, and reversibility so the next discovery investment has a defensible reason.
-
Investigate Which Opportunity Matters Most
Build an evidence brief that compares opportunity statements through observed user outcomes, context differences, counterexamples, and unresolved assumptions.
-
Verify an Opportunity Before Solution Selection
Set outcome checks for a product opportunity, compare the evidence across affected users, and state how far the result supports a solution decision.
-
Turn Opportunity Comparisons Into Better Discovery
Record what an opportunity comparison revealed, improve the team's framing practice, and preserve a trigger for revisiting the ranking as evidence changes.
-
Triage Bias in User Interview Evidence
Find leading prompts, social pressure, and recall risks in interview evidence before using participant statements to make a product decision.
-
Prioritize Interview Bias Fixes Before More Sessions
Rank interview-bias risks by how much they could distort a decision, how often they appear, and how cheaply the research team can correct them.
-
Investigate Whether Interview Questions Led Participants
Compare prompted interview answers with behavior and neutral probes to determine which findings remain trustworthy and which need corroboration.
-
Verify a Neutral User Interview Guide
Pilot revised interview prompts, compare participant responses with expected evidence, and verify that the guide supports open discovery without coaching.
-
Turn Interview Bias Findings Into Better Research
Capture how interview bias entered the study, update the team's facilitation practice, and set a review signal for future discussion guides.
-
Triage a Product Experiment Before Launch
Scope a product experiment by hypothesis, eligible users, comparison condition, guardrails, and the decision the result is meant to inform.
-
Prioritize Which Product Experiment to Run
Choose the next product experiment by decision value, uncertainty, user consequence, and the cost of obtaining a trustworthy comparison.
-
Investigate a Product Experiment Result
Build an evidence brief for an experiment result by checking assignment, exposure, behavior changes, guardrails, and competing explanations.
-
Verify a Product Experiment Against Its Hypothesis
Check whether a product experiment met its predeclared outcome and guardrails while preserving the limits of its sample, duration, and comparison.
-
Turn Product Experiment Results Into Learning
Preserve the reasoning behind a product experiment, improve future test design, and create a recurrence signal for similar measurement mistakes.
-
Triage a Feature Request Into a User Problem
Scope a feature request by user situation, blocked outcome, evidence, constraints, and exclusions before the proposed solution shapes discovery.
-
Prioritize Which Product Problem to Frame Next
Rank candidate product problems by blocked outcomes, affected people, evidence confidence, and the value of clarifying the frame before solution work.
-
Investigate the Problem Behind a Feature Request
Build a reproducible problem brief by following the current journey, comparing user accounts with observed work, and testing alternative explanations.
-
Verify a Product Problem Frame Before Building
Check that a product problem frame names an observable user outcome, reflects evidence from relevant contexts, and leaves solution choices open.
-
Turn Problem Framing Lessons Into Discovery Practice
Record how a feature request was reframed, improve future discovery briefs, and set a signal for detecting solution-led framing early.