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

Ask the Community: Tracking Opportunities Not Related to Your Outcome

Teresa TorresMar 12, 20255 min
SourceProduct Talk
KindFree post
PublishedMar 12, 2025
Originalproducttalk.org ↗
N:

Teresa Torres addresses a common problem in continuous discovery: weekly customer interviews surface valuable opportunities that fall outside the team's current outcome. She argues against forcing conversations back on track and instead recommends two synthesis practices, interview snapshots for capturing everything and an opportunity solution tree for the active outcome. The post then gathers community practices for handling off-outcome opportunities, including scheduled maintenance weeks for small fixes and parking larger opportunities in a KPI tree or unmapped list linked to their source snapshots. The core value is a system that preserves insights so they are not lost when focus shifts.

01Key takeaways

  • Capture every interview in a snapshot, even opportunities you cannot act on now.
  • Keep the opportunity solution tree limited to opportunities tied to your current outcome.
  • Schedule regular maintenance time to address small customer pain points that are easy to fix.
  • Vet customer feature requests before building them, since customers rarely design solutions for the whole market.
  • Link parked opportunities to a metric or outcome and to their source snapshots so future work need not start from scratch.
  • Avoid flat lists of parked ideas; map them into a model of how the business works.

02Key sections

The Dilemma of Off-Outcome Opportunities
Story-based interviews regularly surface opportunities unrelated to the current outcome, and steering customers back to it often fails. The problem is recurring and needs a deliberate response.
Two Ways to Synthesize Interview Learning
Create interview snapshots right after each interview to capture what was heard, and look across snapshots to select outcome-related opportunities for the opportunity solution tree.
Scheduled Maintenance Weeks
One team alternates outcome work with maintenance weeks to handle easy fixes raised in interviews. Teresa notes a quarterly customer-requested release that builds goodwill, provided requests are vetted.
Parking Larger Opportunities Strategically
Vistaly keeps an unmapped list linked to interview snapshots and places opportunities on a KPI tree above the solution trees, so future work starts from existing evidence.

03From the post

“When you conduct story-based interviews every week, you quickly begin to collect a range of opportunities. And while some of these opportunities might be related to your current outcome, that’s not always the case. It can be hard to know what to do when this happens. You might”

“Customers are rarely the best people to design a solution that will work for most of the market.”Teresa Torres · Product Talk
“Flat lists (to me) always felt like a place where things go to die.”Teresa Torres · Product Talk
“I like associating unrelated opportunities with the metric or outcome that they are related to.”Teresa Torres · Product Talk

04Frameworks mentioned

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