By the end of this lesson you can
- Explain the difference between product discovery and delivery.
- Run discovery and delivery work in parallel.
- Know what design does in each.
The idea
Product work has two modes:
- Discovery: deciding what to build. Understanding problems, testing ideas cheaply and reducing risk before committing engineering time.
- Delivery: building it well. Detailed design, development, quality assurance, release and measurement.
Risks discovery reduces
Value risk (will people want it?), usability risk (can they use it?), feasibility risk (can we build it?) and viability risk (does it work for the business?).
Dual-track
Many teams run dual-track work: discovery runs a little ahead of delivery, so validated ideas are ready when engineers need them. Designers often move between tracks during the same week.
Phases in public services
Government services often use named phases: discovery (understand the problem), alpha (try different solutions), beta (build and test with real users) and live (run and improve).
Design in each
In discovery: research, sketching, prototypes, experiments. In delivery: detailed design, states, specs, handoff, build reviews, post-launch measurement.
Why it matters in real projects
Teams that skip discovery build features nobody uses; teams that never deliver learn nothing real. Understanding both modes helps designers plan their time, set expectations with stakeholders and push for evidence before expensive decisions. It also explains why some work should be rough and fast while other work must be precise.
A realistic example
A team is asked to build an in-app chat for a home insurance product. Instead of starting delivery, they spend two weeks on discovery: interviews show customers mainly want claim status updates, not chat. A fake-door test of a "Message us" button gets few clicks, while a prototype status tracker tests well.
They deliver the tracker first. Calls asking "where is my claim?" fall, and chat is deprioritised, saving months of engineering effort.
Step by step
Identify risks
List value, usability, feasibility and viability risks for an idea.
Choose discovery methods
Pick cheap ways to test the biggest risks.
Run experiments
Prototype, interview or test quickly.
Decide
Proceed, change direction or stop.
Prepare for delivery
Detail validated ideas for engineers.
Keep discovery running
Continue discovery for the next ideas while delivery happens.
Common mistakes
Mistake Treating every request as delivery.
Instead Check risks with discovery first.
Mistake Polishing discovery prototypes.
Instead Keep them rough and fast.
Mistake Endless discovery.
Instead Timebox and decide.
Check your understanding
Choose an answer, then check it. There is an explanation either way.
Practice exercise
Exercise · about 45 min
Risk plan
Plan discovery for a feature idea.
Steps
- Choose a feature idea.
- List the four risks.
- Choose a cheap test for the biggest two.
- Define what result would make you proceed or stop.
Deliverable
A one-page discovery plan.
Self-assessment
Tick each item when it is true of your exercise. Be honest; this is for you.
4 items
Summary
- Discovery decides what to build; delivery builds it well.
- Discovery reduces value, usability, feasibility and viability risk.
- Dual-track runs both in parallel.
- Design work differs in each mode.
Further reading
Third-party sources, chosen for reliability. They open in a new tab.
- How the discovery phase works (opens in a new tab)GOV.UK Service Manual
- How the alpha phase works (opens in a new tab)GOV.UK Service Manual
Your notes
Marking complete updates your course and roadmap progress.