Creating an opportunity and solution repository

Creating an opportunity and solution repository

Learn how to organize and prioritize opportunities and solutions across journeys.

The power of TheyDo lies in linking elements together in the customer-centric workflow using the journey as the centerpiece. To support linking everything up, it’s important to create a standardized approach to labeling solutions and opportunities. If you haven’t read about solutions and opportunities yet, we recommend having a look at the workflow guide first.

This guide will tell you:

How a consistent structure helps you stay organized

As more teams adopt the TheyDo workflow, it becomes ever more important to correctly categorize opportunities and solutions. An average journey might spawn up to 10 opportunities, and each of those can spawn up to 10 solutions. As the number of opportunities and solutions start to add up, so does the risk of creating duplicates and losing overview. 

That’s where TheyDo’s categorization system comes in. If you set this up in advance, your teams will be able to use consistent labels for opportunities and solutions from the get-go. This helps prevent duplicates from being created, because teams will be able to look for existing opportunities and solutions more easily instead of creating new ones. It also helps teams to keep overview by making it possible to better search and filter opportunities and solutions in their respective overviews, for example when they want to compare ratings.

Four key elements of categorize opportunity and solution repositories: 

The basic repository for labeling solutions and opportunities is based around four key elements: statuses, owners, groups, and types. 

[gif of sorting opportunities]


Statuses help you to keep track of the development status of solutions and opportunities. TheyDo comes with a basic set of predefined statuses, but you can edit them to your liking. We recommend assigning the same statuses that you already use in your existing way of working. 


Owners help everyone keep track of who’s working on what. An important element of journey management is the ability to work across teams. Knowing who’s responsible for what helps support that.


Groups can be used to specify which groups solutions and opportunities belong to. A single solution or opportunity can belong to multiple groups at the same time. Below you’ll find examples of different groups we often see being used. It is up to you to pick the ones that are most relevant for you, but we recommend picking something that aligns with what you’re currently using to label projects. We also recommend slightly different groups for solutions and opportunities.

Examples of Opportunity groups

  • Domain/division (product/ux/marketing)
  • Budget (who can pay)
  • Strategic priority (OKR / OGSM / Q1 goal)
  • CX Governance (KPI 1 / KP1 2 / KPI 3)

Examples of Solution groups

  • Domain/division (product/ux/marketing)
  • Business level (frontstage/backstage/processes)
  • Roadmap (Q1 / Q2 / Q3) or (Horizon 1 / 2 / 3)


Types help you to distinguish between different categories of solutions. A solution or opportunity can only belong to one type. Here are some examples of the categories we often see organizations using.

Opportunity types

  • Size: bold move, quick win, improvement, hygiene
  • Impact: Business / customer / operations

Solution types

  • Type of deliverable or product category (for solutions): website, app, feature, comms, email, process optimization 

Editing categories

Admins have the power to edit categorization labels. Opportunities and solutions each come with their own separate labeling system. 

Working across journeys with Opportunities and Solutions

While it might sound pretty dry, filtering opportunities and solutions in their repositories can actually be a powerful tool to create different overviews. These overviews can help in a number of scenarios:

Facilitate a prioritization workshop

If you’re hosting a prioritization workshop that focuses on a specific team, product category, or strategic initiative, you can use the overview filter to filter based on those labels, and then rate the filtered opportunities or solutions one by one. Hosting prioritization sessions has never been easier. 

Visualize a roadmap

If you have defined solutions according to their implementation roadmap , you can use the overview to create quick overviews of your potential implementation roadmap, and the best contenders for each.

Sync solutions with the Product teams

TheyDo has integrations with Jira and Azure Devops, but if you use a ticketing system that hasn’t yet been integrated in TheyDo, we recommend creating a ‘pushed to [ticketing tool]’ status for solutions. Don’t forget to add the external link to the relevant Epic in the solution. This tells people all they need to know: that it’s been worked on already, and they should refer to their ticketing tool for an up-to-date status. Furthermore, this also helps you to distinguish which solutions are still optional for implementation.

Continue exploring

If you're just starting out using TheyDo, start here to experience the journey management workflow for yourself.

With Personas, you create lively descriptions of the most important customer types. This guide explains how to create them in TheyDo.

Get a personal demo or try for free