Discovery reports

Aim

Understand who the product is for, what they are trying to do, and what gets in their way.

Method

• Interviews with people from the intended audience
• Reviewing existing feedback, support queries or data you hold
• Observing current tools and workarounds

What you get

• A summary of findings in plain language
• Audience descriptions grounded in what people said
• A list of open questions

Aim

Turn findings into a small number of clear problems worth solving.

Method

• A workshop with your team to review evidence
• Writing problem statements and hypotheses
• Agreeing what success would look like

What you get

• Prioritised problem statements
• Testable hypotheses
• Agreed measures of success

Aim

Try ideas cheaply before committing to build them.

Method

• Clickable prototypes of key journeys
• Short test sessions with real users
• Iterating between rounds

What you get

• Tested prototype
• Notes on what worked and what didn’t
• Recommendation on whether to proceed

Aim

Decide what to build first and what can wait.

Method

• Mapping features against evidence and effort
• Identifying a sensible first release
• Flagging technical and organisational risks

What you get

• A roadmap shaped around outcomes
• A defined first release
• A risk list