By Teresa Torres · producttalk.org · @ttorres on X · LinkedIn
Teresa Torres wraps a 3-month blog series inspired by Chip and Dan Heath's book Decisive, connecting its decision-making research to product work. Her posts argue that product teams should be prepared to be wrong, ask open-ended questions rather than yes/no ones, and generate many ideas before choosing. The series covers bias traps such as confirmation bias, the inside view versus base rates, familiarity and loss aversion, and escalating commitment to bad ideas. It also stresses that the process used to make decisions matters as much as the decisions themselves. The piece serves as a reading guide and a recommendation to read the book, since better decisions compound into better products.
01Key takeaways
- Accept that your product judgments can be wrong, and design decisions to test that assumption.
- Ask 'what's the best thing we can build to meet our goals' instead of 'should we build this feature'.
- Generate many ideas regularly and look for solutions others have already used on similar problems.
- Actively check for confirmation bias when interpreting user research and customer interviews.
- Set tripwires in advance so you can stop investing in an idea that is not working.
- Document how decisions are made so others can make good ones when you are absent.
02Key sections
- Accepting you may be wrong
- Torres starts by noting that product people like being right, but serving users requires accepting that their own judgments can be mistaken.
- Reframing the questions you ask
- Rather than asking whether to build a requested feature, she suggests asking what the best thing to build is, which opens up more options.
- Generating and evaluating options
- She recommends keeping an idea journal and deliberately producing many ideas, and notes that borrowing solutions from others who solved similar problems can surface better options.
- Mental traps that distort decisions
- The series covers confirmation bias in user research, the pull of the inside view over base rates, and loss aversion and familiarity that cause pushback on changes.
- Process, commitment, and estimation
- Tripwires guard against escalating commitment, better estimates improve planning, and procedural justice shows why the decision process matters.
03From the post
“Over the past 3 months, I've written a number of posts inspired by the book Decisive by Chip and Dan Heath. I'm a big fan of their work and so much of the research from Decisive is directly applicable to building great products. I highly recommend that everyone”
04Frameworks mentioned
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.