Defining the Opportunity Space

Once you start talking to customers, you will collect a mountain of data. The next step is translating raw customer feedback into structured, size-able opportunities.

What is an Opportunity?

An opportunity is not a feature request. If a customer says, "I want an Excel export button," the opportunity is not "Add Excel export." The opportunity is the underlying need: "I need to share data with colleagues who don't have accounts." or "I need to perform custom mathematical formulas on my sales metrics."

Writing Opportunity Statements

A good opportunity statement is framed from the user's perspective, focusing on the pain point without prescribing the solution. Use this format:

"As a [User Segment], I struggle to [User Need/Pain] because [Root Cause], which results in [Negative Outcome]."

Example comparison:

• Weak Opportunity: "Add PDF invoices." (This is a solution, not an opportunity.)
• Strong Opportunity: "Freelancers struggle to submit invoices in their clients' custom formats, which leads to late payments." (This leaves room for multiple solutions: CSV export, invoice builder, API sync, etc.)

Grouping Opportunities

Group related feedback together. If five users mention trouble finding the save button, and ten mention losing their draft work, they might roll up under a broader opportunity: "Users lose progress when their session unexpectedly expires." This helps you prioritize major themes rather than small, isolated tickets.