Diagram template
Opportunity solution tree
PowerA desired outcome opens into customer-opportunity fields. Each explored solution owns its adjacent assumption test, retaining exact four-level membership through measured shared branch enclosures.
Categories
Included in
Power, Max
When to use it
A selective Teresa Torres opportunity solution tree: one desired outcome, two supplied customer needs or pain points, one or two explored solutions per opportunity, and one named assumption test per solution. Suits product onboarding, patient-service discovery or student-support discovery. Unlike a taxonomy or metric driver tree, these are proposed paths and tests of assumptions, not decomposition, observed impact or arithmetic. Not a complete opportunity hierarchy, test-result report or feature roadmap.
Adjust after generating
Change the style, colors, and font, and these options, as often as you like without spending credits.
- Card shape
- Card border
- Card shadow
- Material
- Typography
- Spacing
What you fill in
Describe your topic in plain words and the AI fills these in. You can edit every field afterwards.
- Subject label
- Text
- Goal
- Text
- Columns
- Exactly 3
- Opportunities
- 2 to 3, each with id and title
- Solutions
- 2 to 6, each with id, group, and title
- Experiments
- 2 to 6, each with group, title, and description
Related templates
All framework templates
Anatomy: crowned subjectFor explaining what one thing is made of as a primary part, the part that carries it out and a part that spans both: a service offer (scope, delivery, assurance), a product (core function, how it ships, support), a course (content, format, learner support), an event (program, logistics, hosting) or a team charter (mission, ways of working, backing).
Comparison: principle seamsFor two to four supplied principles, each owning one exact preferred example and one exact example to avoid: brand voice guides, product interface copy, support reply standards, documentation style, naming conventions, inclusive language or meeting etiquette.
Cycle: causalFor a compact qualitative causal-loop view with exactly five variables and two three-link loops sharing one variable: a referral loop against crowding in a membership plan, workload against hiring in a team, adoption against support load in a product, or demand against price in a market.
Cycle: quarter panelsFor four-step recurring loops where each step produces one named output: service improvement, editorial planning, quarterly operating reviews, product discovery or a study-practice-test-reflect learning cycle.
Cycle: stage ledgerFor 3–5 stage recurring loops with named owners, produced work and an explicit final-to-first feedback artifact: customer learning loops, hiring or onboarding routines, editorial cycles, release reviews and continuous-improvement rounds.
Adoption lifecyclePlace a product, technology, internal tool, policy, practice or service on the diffusion of innovations curve: go-to-market planning for a B2B product, rollout of a new internal platform, adoption of a public-health practice, or spread of a teaching method.