This article is a collection of Opportunity Solution Tree (OST) patterns we at Vistaly have observed teams use in their day-to-day work. Taking advantage of the patterns below does not require Vistaly to get started. While some can easily be applied using free-form tools like Miro or FigJam, others may require some maintenance to gain the benefits.
“We have very different kinds of users in our product. How do we account for user segments in the Opportunity Solution Tree when they have vastly different needs?”This question is common and impacts many teams, especially in B2B products or services. We have observed (and tested) several of the following approaches for segmenting the opportunity space. Done right, it can create focus and simplify your mapping. The best approach will be context-dependent on the outcome and product.
“We have multiple teams (squads/trios), each with their own OST. How should we structure work in Vistaly, and how do we operationalize it across teams?”This is a question we hear from teams who have reached a point where discovery is integrated into their company’s work culture or ones in the process of establishing better practices. Vistaly supports two ways of making larger-scale coordination easier, each with its own set of trade-offs.