Problem Framing & Opportunity Mapping

An outcome at the root, an opportunity solution tree built from real evidence, sharp problem statements and a live assumption log, so the team picks the customer problems worth solving on purpose.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Problem Framing & Opportunity Mapping, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

203

Starter tasks

🧩 Product Management

Problem Framing & Opportunity Mapping

Turning research into a clear map of customer opportunities and candidate solutions, so the team picks problems worth solving deliberately.

  1. Shared problem framing vocabulary
  2. Desired outcome at the root of the map
  3. Research evidence inventory
  4. Solution requests rewritten as problems
  5. First opportunity solution tree
  6. Problem statement template and first five statements
  7. Opportunity card wording rules
  8. Evidence strength scale for opportunities
  9. Current workflow experience map
  10. Assumption categories checklist
  11. Weekly opportunity tree update
  12. Interview snapshots linked to opportunities
  13. Monthly opportunity map review
  14. Opportunity map pruning pass
  15. Assumption log upkeep
  16. Quarterly target opportunity choice
  17. Problem brief gate before build
  18. Stakeholder request intake into the map
  19. Framing decision log
  20. Learning the opportunity solution tree method
  21. Five whys root cause practice
  22. How might we question craft
  23. Problem reframing exercises
  24. Affinity clustering of research into opportunities
  25. Generating several solutions per opportunity
  26. Assumption mapping on an importance and evidence grid
  27. Opportunity sizing estimates
  28. Spotting opportunities in usage data
  29. Comparing three solutions for the target opportunity
  30. Breaking a large opportunity into smaller ones
  31. Stop rule for weakly evidenced opportunities
  32. Choosing where the opportunity map lives
  33. Reframing a stalled initiative
  34. Importance and satisfaction survey for top opportunities
  35. Customer needs separated from business goals
  36. Half-day opportunity mapping workshop
  37. Quarterly leadership opportunity readout
  38. Problem pack for a design sprint or hackathon
  39. Annual opportunity landscape refresh
  40. Company-wide customer problem showcase
  41. Founder's first problem hypothesis
  42. Reframing after a failed bet
  43. Inheriting a solution-first roadmap as a new PM
  44. Responding to an executive-mandated solution
  45. Framing for a handful of large B2B customers
  46. Handing framing over to the first product hire
  47. Systems map for a tangled problem
  48. Consequence scanning for chosen opportunities
  49. Opportunity portfolio balance
  50. Framing retrospective on past target opportunities

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Shared problem framing vocabulary

Teams argue past each other when one person's opportunity is another person's feature idea. A one-page glossary defining outcome, opportunity, solution, assumption and experiment, with an example of each from your own product, gives every discussion of the map the same footing and makes solution ideas dressed up as problems easy to spot.

First tasks

  • Draft one-line definitions of outcome, opportunity, solution, assumption and experiment
  • Write one example of each term taken from your current product
  • Walk the product, design and engineering leads through the draft
  • Link the agreed glossary from the top of the opportunity map
  • Reread the glossary and replace examples that no longer fit @recurring(yearly)

Desired outcome at the root of the map

An opportunity map without a clear outcome at the top grows in every direction at once. Picking one product outcome the team can influence, such as the share of new accounts that complete a second project in their first fortnight, decides which customer problems belong on the map and which can wait. Do this before mapping anything else.

First tasks

  • List the product outcomes your team could plausibly influence this quarter
  • Find the current baseline number for each candidate outcome
  • Choose one outcome and write the business result it supports
  • Confirm the chosen outcome with whoever sets the team's goals

Research evidence inventory

Most teams already hold more evidence than they think: interview notes, support tickets, sales call recordings, survey answers and usage data scattered across half a dozen tools. Listing every source, its dates and how to reach it means the first map is built from what customers have already said, not from the loudest opinion in the room.

First tasks

  • List every place customer evidence lives today, from interview notes to ticket exports
  • Record the owner, date range and access link for each source
  • Mark which segments and workflows have no evidence yet
  • Add any new research source to the inventory @recurring(quarterly)

Make it yours.

Install Problem Framing & Opportunity Mapping, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.