/
Opportunity-solution tree (OST)

Opportunity-solution tree (OST)

As discovery is conducted, opportunities will arise - fashioned as pains the customer goes through, needs and desires (whether they tell you explicitly or not). Now they could be listed out in a typical backlog and prioritized from there, but what an OST does is that it allows the team to see interrelationships between problems. If done correctly, the team will build a tree knowing that if they solve parent nodes, they can deliver actual value to the customer - this follows the agile methodology of delivering value every sprint.

The team will also discover some opportunities that you can work on outside the current business objectives. As new objectives come up, the team will not be starting from scratch because you would have seen these opportunities.

Not all opportunities need to be worked on. Some opportunities discovered might belong to another team. Some do not even need product solutions. 

Sample:

https://www.figma.com/board/IvyPPDxGyzx4FZQqZTIgP5/Opportunity-Solution-Tree?node-id=0-1&t=I5tM7X0UKCsrmExH-1

Add label

Related content

Solution ideation
Solution ideation
More like this
Executing discovery activities
Executing discovery activities
More like this
The product discovery process guide
The product discovery process guide
More like this
Product prioritisation guidelines
Product prioritisation guidelines
More like this
Product prioritisation and development
Product prioritisation and development
More like this