How Compare and Contrast Decisions Lead to Better Product Outcomes

Teresa Torres recounts a 2008 product story in which her team at an alumni community startup fixed on an engineer's Google Maps idea while the real problem was unwanted spam. She argues teams fall in love with their first idea and rarely compare enough ideas or opportunities, which turns decisions into hard "whether or not" judgments instead of easier "compare and contrast" choices. To fix this she proposes the opportunity solution tree, a visual map that starts from a desired outcome, lists customer-grounded opportunities, groups and restructures them, and then generates and tests solutions against one target opportunity at a time. The approach matters because it gives teams a shared picture of their thinking and a disciplined way to make product choices.

01Key takeaways

• Start every brainstorm by aligning the team on a clear desired outcome and a specific target opportunity.
• Replace "is this idea good?" with "which of these options looks best?" to get more reliable decisions.
• Build opportunities from customer interviews and observations, phrased as things customers would actually say.
• Group similar opportunities into one level before prioritizing, so you compare comparable items.
• Generate many solutions for a single opportunity, narrow them with dot voting, then test each idea's key assumption to choose among them.

02Key sections

Falling in love with ideas

Teams quickly commit to the first solution that comes to mind, then stop examining whether it is any good. The story shows how an appealing but irrelevant idea can take over a brainstorm.

Compare and contrast over whether or not

Asking whether one idea is good treats quality as absolute and is hard to answer. Comparing several options against each other makes relative judgments easier and better.

Aligning on opportunities

Teams often brainstorm before agreeing on the problem, and each person may solve a different one. Considering many opportunities, not just one, prevents solving unimportant problems.

Building the opportunity solution tree

Start from a clear outcome, list opportunities drawn from customer research, group similar items, and restructure the tree until it reflects what customers say. The structure makes prioritization and disagreement easier to resolve.

Narrowing and testing solutions

Pick a target opportunity row by row, generate many solutions for it, use dot voting to reduce them, then run experiments on each idea's key assumptions to choose among good options.

03From the post

“This past week I was in London speaking at Mind the Product. As usual, the Mind the Product team hosted a phenomenal event. You can watch the video here: Full Transcript This transcript is the script of the talk as it was written. It is not word-for-word the”

04Frameworks mentioned

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