Skip to content

References: Defining the Real Problem

  1. Five whys - Wikipedia - Explains the iterative "why" questioning technique for finding root causes, the exact method this chapter uses to trace a customer's first complaint down to the underlying condition actually producing it.

  2. Root-cause analysis - Wikipedia - Covers systematic methods for distinguishing a fault's fundamental cause from its symptoms, supporting this chapter's discipline of not stopping at the first explanation a customer offers.

  3. Problem statement - Wikipedia - Describes how a problem statement identifies a gap and facilitates communication of an issue, directly relevant to this chapter's guidance on writing the finished problem statement that goes in the canvas's Problem block.

  4. The Mom Test - Rob Fitzpatrick - Self-published - Fitzpatrick pioneered a question format for customer conversations that avoids leading questions and false-positive validation, the exact discipline this chapter needs to tell a real problem from a perceived one.

  5. Competing Against Luck - Clayton M. Christensen, Taddy Hall, Karen Dillon, and David S. Duncan - Harper Business - Christensen pioneered Jobs to Be Done theory, reframing a problem around the functional task a customer is trying to accomplish, exactly the reframing this chapter uses to look past a stated symptom.

  6. Know Your Customers' "Jobs to Be Done" - Harvard Business Review - Explains how focusing on the underlying job a customer is hiring a product to do produces more predictable innovation, reinforcing this chapter's distinction between a symptom and the job to be done beneath it.

  7. The Customer Profile - Strategyzer - Breaks a customer down into jobs, pains, and gains, a practical tool for the same root-cause and unmet-need thinking this chapter applies to move past a customer's first-stated complaint.

  8. Validate Customer Demand - Harvard Innovation Labs - Outlines three validation questions, including budget and priority, and explicitly recommends The Mom Test's non-leading interview approach, directly reinforcing this chapter's willingness-to-solve and problem-validation concepts.

  9. Every Successful Business Solves a Pain Point — Does Yours? - Entrepreneur.com - Argues that products fail without a genuine, validated pain point behind them and recommends manual testing before building, reinforcing this chapter's distinction between a real problem and a merely perceived one.

  10. Five Whys Technique in User Research - Dovetail - A practical walkthrough of applying the Five Whys to a real product problem, showing how repeated "why" questions can reveal an audience mismatch rather than a surface-level defect, mirroring this chapter's root-cause drill-down.