By Teresa Torres · producttalk.org · @ttorres on X · LinkedIn
Teresa Torres argues that product teams should treat every idea as a testable hypothesis, which requires explaining why a change matters and how much impact it should produce. Ideas from design, sales, and product managers are endless, so without a clear rationale teams waste time on changes that don't matter and get fooled by false positives. She offers three ways to set an impact threshold: start from your current baseline, look at the results of comparable past changes, and decide how much improvement justifies the full cost of the work. Her closing point is to frame the question as how to maximize impact rather than whether a small gain is enough, since incremental wins carry large opportunity costs.
01Key takeaways
- Turn every product suggestion into a hypothesis that explains why it should change a specific metric.
- Ask why an idea matters and what impact you expect before investing time in building or testing it.
- Measure your current baseline first so you can judge whether a proposed improvement is realistic.
- Review past experiments on similar changes to ground your impact estimates in evidence.
- Set a meaningful threshold that accounts for total cost and opportunity cost, not just any improvement.
02Key sections
- Connect the expected impact to the change
- Every suggestion should be probed for the problem it solves and the reason it should move a metric. Without that rationale, teams chase an endless list of ideas.
- Start with your baseline
- Knowing the current rate makes the size of a realistic improvement clear, since a 50% lift means very different things at different starting points. An A/A test or a control task in usability testing can establish that baseline.
- Look at comparable product changes
- Past experiments on similar changes, or on the same underlying value proposition, provide a grounded estimate of what new work might achieve. Building this knowledge base over time sharpens future estimates.
- Assess how much impact is worth the investment
- A change should be judged by its total cost, including maintenance, user learning, and opportunity cost, not by any positive lift. Setting an aggressive threshold pushes teams toward bigger ideas.
03From the post
“Your design team is excited about a new signup process. They are convinced it will increase registrations. Your sales team keeps asking for the same feature over and over again. They think it’s responsible for lost sales since your biggest competitor features it prominently. Your product manager wants to”
04Frameworks mentioned
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.