Continuous Discovery Habits

• · CD1 — Touch customer reality every week, without exception, even briefly (one interview, one usability test, one support-ticket review session) — consistency beats occasional depth.
• · CD2 — Maintain a visible opportunity solution tree rooted in the team's owned outcome; update it continuously as research produces new opportunities and solution ideas.
• · CD3 — Interview for stories about specific past events, not opinions about hypotheticals or reactions to concepts.
• · CD4 — Explore multiple opportunities before committing to one, and multiple solutions per opportunity before committing to one — visible on the tree, not just in someone's head.
• · CD5 — Map assumptions explicitly before testing. Identify desirability/usability/feasibility/viability/ethical assumptions for a candidate solution; prioritize testing by importance × lack of evidence.

• · Story-elicitation phrasing: "tell me about the last time..." / "walk me through what happened when..." beats "would you..." / "do you think you'd..." — catch and rephrase hypothetical questions during interview prep.
• · Assumption-mapping shortcut: for a candidate solution, ask "what would have to be true for this to fail?" — each answer is an assumption; the one that scares the team most and has the least evidence goes first.
• · Signal vs. noise in interviews: one customer mentioning a pain point is a data point; three unconnected customers mentioning the same pain point unprompted is a pattern worth acting on.
• · Synthesis lag check: how long between an interview and its findings landing on the opportunity tree? If it's weeks, synthesis has become a batch process again — fix by synthesizing within a day of each interview.

• · Ver anti-patrones específicos del dominio en el pack.

• [ ] At least one customer touchpoint occurred this week; gaps tracked, not silent. (CDE1)
• [ ] Opportunity solution tree exists and was updated within days of the latest research. (CDE2)
• [ ] Interview questions elicit stories about specific past events, not hypotheticals/opinions. (CDE3)
• [ ] Assumption map exists for any solution nearing a build commitment, with the top-priority (important + unevidenced) assumption identified. (CDE4)
• [ ] The tree shows genuine breadth: ≥2 opportunities considered, ≥2 solutions per pursued opportunity. (CD4)
• [ ] At least the cheapest viable test was run against the top-priority assumption before full build. (CDE5)

• Continuous Discovery Habits: Discover Products that Create Customer Value and Business Value

Este pack cita las siguientes fuentes registradas en el índice bibliográfico:

• webContinuous Discovery Habits: Discover Products that Create Customer Value and Business ValueTeresa Torres. Product Talk LLC
• webProduct Talk — articlesTeresa Torres