LogRocket Blog

Opportunity solution trees: A list of anti-patterns to avoid

thumbnail

Opportunity Solution Trees

Opportunity Solution Trees (OSTs) are a useful tool for mapping out user problems and potential solutions in order to drive desired outcomes. However, there are several common anti-patterns associated with OSTs that should be avoided.

Mistaking solutions for opportunities

One common mistake when creating an OST is mistaking a solution for an opportunity. Instead of focusing on the specific problem that needs to be solved, people often jump to a solution right away. It's important to dig deeper and identify the underlying problem before coming up with potential solutions.

Focusing on features

Another anti-pattern is focusing on features instead of the broader user needs. It's important to think about what users need to accomplish, rather than specific features or functionalities. This will enable you to identify more focused and impactful opportunities.

Not being specific enough

When creating an OST, it's important to be specific and avoid generalizations. Vague problem statements can lead to unclear and ineffective solutions. Breaking down larger problems into smaller, more specific ones will help in identifying meaningful opportunities.

Forgetting that opportunities live in a specific moment in time

Opportunities are tied to specific moments in time and user contexts. It's important to consider the timing and context in which the opportunity exists. This will help in prioritizing and designing solutions that are relevant and effective.

Framing opportunities from a product perspective

A common pitfall is framing opportunities from a product perspective, rather than a user perspective. Opportunities should be framed in terms of the ultimate goal the user wants to achieve, rather than specific features or solutions. This will ensure a user-centered approach to problem-solving.

Building too robust trees

Sometimes people get carried away and create overly complex and robust opportunity solution trees. While it's important to be thorough, it's also important to focus on the most critical and impactful opportunities. Keeping the trees manageable and concise will help in prioritizing and acting on the identified opportunities.

Exploring too few opportunities

On the flip side, exploring too few opportunities can limit the potential solutions and limit the effectiveness of the OST. It's important to explore a wide range of possibilities and consider different angles and perspectives. This will help in identifying innovative and impactful solutions.

By avoiding these common anti-patterns, you can create more effective opportunity solution trees that drive meaningful outcomes for users.