Product discovery is the process of moving from the problem to the solution. The team responsible for product discovery deals with the problem and the solution spaces in their pursuit of defining solutions. Once they define a solution, the delivery team takes the solutions to the backlog, adding the details to execute them.

The roadmap describes how the ideas are progressing through the discovery process. The roadmap is a snapshot of the process. At any given time, it should describe:

• Ideas currently investigated
• High-level solutions which are validated

The complete discovery process happens in the context of a value-based product strategy. There are four steps to producing solution ideas:

• Problem framing - understanding the problems you're trying to solve and the requirements of the solutions.
• Roadmap planning - prioritising the problems and planning iterations for each.
• Ideation and prototyping - generating ideas and bringing them to life with prototypes
• Solution testing - validating solution ideas against the original problem.

Once you have possible solutions, they must pass a validation criteria.

1. Before you start with ideas, structure your roadmap correctly.
2. Ask if the ideas are worthwhile. A problem describes the gap between where we are now and where we want to be. The items on the roadmap should get us to where we want to be (the product vision).
3. Plan your roadmap. Figure out which ideas should be tackled first.
4. Ideate, prototype and test solutions.

The primary task of the roadmap is communicating the discovery process, as it can be difficult to bridge the gap between the abstract product strategy and the tangible backlog.

The roadmap needs to represent:

• abstract product values (organised into themes)
• tangible and specific ideas, which will become the product goals.

Good values lead to good goals, which leads to a good product.

Ideas on the roadmap should be phrased in terms of problems and opportunities. But how the problems are framed is important. Problems should be framed in their purest form to empower the discovery team to find the best solution possible. 

Problems should be phrased from the point of view of at least one of three product development disciplines: The user, the business, or technology.

You now have clearly articulated goals but may not know which ideas to tackle first. 

Two main factors can help prioritise goals: 

Expected value - the combined measure of expected user value and expected business value, and Complexity.

• Goals should be mapped on an expected user value scale.
• Then add another axis for the expected business value. This should give you a picture of how valuable the goals are.
• Rank the goals by overall value.
• Lastly, contrast the value with feasibility. High value, high feasibility will give quick, short-term wins.

These steps are BYOT (bring your own tools.) General principles to help with the right tools:

• Ideations: Ensure all of the relevant disciplines are present and that the problems are well framed.
• Prototype: show the idea without the frills to get to the root of the proposed solution.
• Test: use realistic tests.

During the documentation of the proposed solution, capture these three things as a minimum:

• Requirements at the epic level.
• UX: visuals of how this solution will manifest.
• Technical specification: The endpoints, integrations and components.