03
Opportunity solution trees, applied to SEO-GEO Optimizer - Product Thinking
Project · SEO-GEO Optimizer
How I stopped jumping to solutions and mapped the AI-search space into opportunities before writing any code.
When to use
When the team is arguing about solutions before agreeing on the outcome, or when a category is new and the mental model is fuzzy.
How I run it
- 01Named the outcome: ‘Sites cited by AI answer engines.’
- 02Mapped opportunities beneath it: structured data, answer-shape prose, llms.txt, freshness signals.
- 03Branched 2–3 solutions per opportunity, killed the ones that already had good OSS.
- 04Ran the riskiest assumption first (‘will devs install a package for this?’) before touching the JSON-LD generator.