handbooksMapping and prioritizing opportunities
Turn interview notes into a structured opportunity space, then pick one target. How to size a set of siblings without pretending you have data you do not have.
- Opportunities come from the stories you heard, phrased the way customers phrased them. Group them, remove the duplicates, and give the branch structure.
- Compare siblings, never single opportunities in isolation. One opportunity alone gives you nothing to judge it against.
- Pick one target opportunity and address it fully before moving on. Three in parallel delivers nothing three times as slowly.
- Prioritization here is relative and messy. Resist scoring frameworks that make a guess look like a calculation.
From snapshots to a structured space
After a few weeks of interviews you have a pile of needs and pain points. Left as a list it becomes an opportunity backlog nobody can reason about, which is the same trap as a feature backlog wearing different clothes.
The work is to give it structure:
- Collect every need and pain point from your snapshots, in customer language.
- Group the ones that are the same need described differently. "I could not find it" and "it took me ages to track down" are one opportunity, not two.
- Place each group against the moment in your experience map where it occurs.
- Break down the large ones into the more specific opportunities underneath them.
- Check the branch against the rules below.
The rules for a healthy branch
| Rule | What it prevents |
|---|---|
| Siblings do not overlap | Two nodes describing one need, so comparison means nothing |
| No vertical stacks | One parent, one child, repeating: a single need restated at four levels of detail |
| Exactly one parent per opportunity | The same need duplicated across branches, counted twice when you compare |
| Framed from the customer's side | Your solution ideas leaking into the opportunity space |
| Distinct, not vague themes | "Onboarding" as a node, which cannot be addressed or measured |
| No solutions in disguise | Committing to an implementation before you have compared any |
Read the opportunity and ask how many different things you could build to address it. If the honest answer is one, it is a solution. Ask what the customer was trying to accomplish and use that instead.
Just enough structure
There is a point where organizing the tree becomes a substitute for making progress. Structure is complicated, and it gets done, undone, and redone as you learn. That is normal, and it is not a reason to keep refining.
Aim for a branch you can reason about, not a complete taxonomy of customer needs. The tree is a thinking tool. It will look different next month.
Choosing a target opportunity
The move that makes this tractable is to stop evaluating opportunities one at a time. Take a set of siblings and compare them against each other.
Judging "is this opportunity important?" in isolation is nearly impossible, because there is no scale. Judging "which of these four matters most to the customers we care about?" is a question people can actually answer.
What to weigh
| Factor | The question |
|---|---|
| Opportunity size | How many customers hit this, and how often? |
| Customer importance | How much does it matter to them when it happens? |
| Market factors | Does addressing this differentiate us, or match table stakes? |
| Company factors | Does this fit what we are good at and where we are going? |
| Outcome impact | Would addressing this plausibly move the number at the top of the tree? |
Weigh these together. Leaning entirely on one, usually opportunity size because it feels the most numerical, produces confident bad choices.
The strongest targets tend to be opportunities that produced real frustration, that came up with more than one customer, and that sit clearly under your outcome. Two of the three is often enough to start.
Embrace the messiness
There is a strong pull toward scoring frameworks: weight each factor, multiply, sort by total. The arithmetic feels rigorous and mostly is not. The inputs are estimates, the weights are opinions, and multiplying them produces a number with false authority.
Relative comparison is more honest and usually faster. This one matters more than that one, and here is why, and here is what would change our mind.
- Waiting for more data. The decision is usually reversible. Waiting has a cost you do not see on any dashboard.
- Relying on one factor. Size alone, or loudest customer alone, or strategy alone.
- Deciding first, assessing after. Picking the opportunity you already liked and building the case backward. Compare the set before you form a view.
One at a time
Pick one target opportunity. Work it until you have delivered something, then pick the next.
Splitting across three opportunities feels productive and is not. Each gets a third of the attention, none gets solved, and the tree grows in every direction at once. Sequential work on one branch delivers value sooner and teaches you more, because you see the result of finishing something.
Keep exploring while you build
Choosing a target does not freeze the rest of the tree. Interviews continue weekly, and what you hear keeps reshaping the opportunity space, including the branch you are working in. Sometimes what you learn while addressing one opportunity reveals that its neighbor was the better target. That is the system working.
Look at your opportunity space and find a set of four siblings. Rank them, then write one sentence for each explaining why it sits where it does. If you cannot write the sentence, you do not have enough interview material on that branch yet.