How to use the Opportunity Solution Tree Generator.
An opportunity tree connects a target outcome to observed needs and testable solutions. Avoid drawing every feature idea directly from the outcome.
Make the workflow fit your task.
Start with a measurable outcome and attach opportunities grounded in observed needs. Explore alternative solutions under each opportunity, then design tests that could distinguish them instead of drawing a tree of preferred features.
- What you provide
- Target outcome and research findings.
- What you get
- Opportunities, possible solutions and experiment branches.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Outcome: fewer failed imports. Research finds unclear required fields.
Completed example
Opportunity: understand required fields. Solutions: preflight checks or better templates. Experiments: observe whether either reduces the specific failure.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Can an opportunity be written as a feature request?
Translate it into the underlying need where evidence supports that interpretation. Multiple solutions should remain possible beneath the opportunity.
Why does the tree contain solutions with no research connection?
Trace each branch to an observed need or mark it as a hypothesis. Remove unsupported links that make the diagram look more certain.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑