Setting up a nesting Taxonomy for Opportunities and Solutions

Creating Opportunity-Solution trees works best when all teams use the same hierarchy. This guide explains how to set up this hierarchy.

Setting up a nesting Taxonomy for Opportunities and Solutions

The Goals section allows for flexible Opportunity and Solution nesting. To make sure all teams nest Opportunities and Solutions in a consistent way, we recommend formulating a system for nesting or Taxonomy) that everyone can use. Below are some examples of common hierarchies that you can incorporate in your Opportunity-Solution trees:

Default hierarchy

The most simple structure is already provided by default; simply use Goals, Opportunities, and Solutions as they are.

OKR's

If you work with OKRs, we recommend incorporating them in the following way:

• Objectives can be captured using Goals.

• Key results can be captured as metrics that belong to Objectives. Write them down within the details of your Objectives. With time, we aim to enable metrics within Objectives.

Strategic and Tactical Opportunities

Opportunities can often be further split up into Strategic Opportunities and Tactical Opportunities:

• Strategic Opportunities are long-term, high-level opportunities that align with the overall mission and vision of the organization.

• Tactical Opportunities are short-term, specific opportunities that are more operational in nature. They support the implementation of strategic Opportunities. Use Opportunity types to label these different types of Opportunities.

Agile Solutions

If you work with Agile methodology, you can structure Solutions using the “Epics, Stories, Tasks” hierarchy:

• Epics are large bodies of work that can be broken down into a number of smaller tasks (or stories).

• Stories are smaller and more detailed units of work that fall under an Epic. Each story represents a specific requirement or feature from the user's perspective, providing a simplified description of a functionality.

• Tasks are the smallest unit of work and are essentially sub-tasks of a story. They represent the specific work that needs to be done to accomplish the user story.