Product Talk · Free post · Execution, roadmaps & process · Discovery & customer research

The Path to Better Product Decisions

Teresa TorresSep 23, 20155 min
SourceProduct Talk
KindFree post
PublishedSep 23, 2015
Originalproducttalk.org ↗
N:

Teresa Torres argues that product managers often fall into a throughput mindset, filling backlogs and keeping engineers busy rather than driving outcomes. She identifies three recurring failures: not starting from a systems view of the problem, considering too few ideas, and assuming ideas will work without testing assumptions. To counter these, she proposes a six-step, outcome-based methodology that moves from mapping the challenge through to investing in or abandoning ideas based on evidence. Because it treats product management as problem solving rather than backlog management, the process offers a repeatable way to make better product decisions.

01Key takeaways

  • Measure your product as a system and identify where intervening would most improve overall outcomes.
  • Generate many candidate ideas for one specific problem instead of accepting the first feasible solution.
  • Rank ideas by expected impact on the current intervention point rather than using complex multi-criteria spreadsheets.
  • Surface and test the hidden assumptions behind your favorite ideas before committing significant resources.
  • Keep re-evaluating the system after each change, since improvements can shift the most important point of intervention.

02Key sections

Shift from output to outcomes
Torres contends that the PM's job is solving problems that drive outcomes, not managing output. She notes that Lean Startup and Agile help with experimentation and iteration but lack an end-to-end decision process.
Map the challenge and find intervention points
PMs should visually map the whole system, such as a customer journey or architecture, and overlay performance data. This reveals where intervening will have the biggest impact on the overall system.
Source and select ideas
Teams should generate many ideas for one specific intervention point rather than settling on the first feasible option. They then rank ideas by expected impact on that single challenge and pick two or three to pursue.
Test assumptions and decide to invest or jump
Each top idea should be examined for the assumptions that must hold, with evidence gathered through targeted experiments. Based on that evidence, the PM either invests further or moves on, continuously re-evaluating where to intervene next.

03From the post

“I spend most of my time helping product teams make better product decisions. I’m starting to notice some patterns. I see three critical areas where we often fall short. First, we don’t always start from a holistic or systems view of the problem we are trying to solve.”

“A product manager's job isn't to keep engineers busy. It's not about output.”Teresa Torres · Product Talk
“We are problem solvers. Not backlog managers.”Teresa Torres · Product Talk
“She doesn't get bogged down in experimenting for the sake of experimenting or building to learn.”Teresa Torres · Product Talk

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.