The purpose of Discovery is to find out if an idea is viable. The techniques used during Discovery are designed to reduce the risk of building the wrong thing, whilst swiftly determining how to deliver the solution (or not). To do this we establish whether the idea is: Feasible, Usable and Valuable.
Usually lasting up to 5 days, Discovery helps the Product Owner choose the right solution to invest in next. This avoids pre-determined solutions by gaining early feedback from end users.
During Discovery, we ask and propose answers for:
What is the problem?
Is there an alternative / workaround?
Who is it for?
Who could it be done by?
What is the business / user impact?
How do we measure it?
UX / UI Wireframes
Focuses on End-to-end user flows to shows how customers will use the concept by answering questions such as:
Who are the users?
How will they interact with this product?
What are they doing now?
Why is this an improvement?
Through which channels will they interact, e.g. Web, Mobile, Native App, SMS, Call Centre etc.
Do all users need all functionality to be available prior to launch? What do they really need? What’s the MVP?
Defines the functional scope of the concept, and answers questions such as:
Why build this?
Who is involved in its inception, build, launch, operation and evolution?
How are all actors impacted by the solution? What changes and do we need and do we need to deliver all of it to achieve the key goals?
What are the key solution deliverables, including changes to business processes, team structure etc.
Looks at the technical impact of the idea to identify which systems are impacted and to what extent. Answers questions such as:
What do we need to build?
New / Deprecated services
Tech debt, etc
PoCs / Spikes identified
Business Capability Heat Map
Shows the ripple effect of introducing the concept within the business. It answers questions such as:
How will the business operations change?
Areas of new capabilities
Disruption to current working practices
Functions to be removed
Teams & departments involved
Business processes impacted.
A one page summary to review the product idea, business driver, customer base, solution, key metrics. The Concept card looks as decisions around the what it is we intend to build, why and what's the benefit
Capture the high-level benefits, key metrics, hypotheses