Problem
01
We are not sure anyone wants this.
02
Stakeholders disagree on what to build.
03
We keep adding features and losing focus.
Outcomes
- A validated direction
- A shared, evidence-backed plan
- Less wasted build
Scope
In scope
- Discovery and validation
- Prioritisation
- Product direction and plan
Not included
- Detailed UI design, which sits under UX and UI design
- Engineering, which sits under custom software engineering
Approach
Discovery
We agree the users, the problem and the constraints, and how success will be judged.
Delivery planning
We shape the approach, sequence the work and set out costs, risks and a definition of done.
Build and test
We build in the open, test with real users and real data, and prove it before release.
Operational readiness, hypercare and closure
We hand over, support the first weeks of use, and confirm the outcome before we close.
Deliverables
Validated problem and audienceProduct directionPrioritised backlog
Technologies
Research and synthesis toolsPrototyping toolsBacklog tooling
Controls
Research participants give informed consent, handled under the privacy notice. Findings separate what users said from what the team inferred. Prototypes are tested with a range of users, including people with access needs. The recommendation states its evidence and confidence.
Frequently Asked Questions
What if discovery says do not build it?
Then we have saved you a far more expensive mistake, and we say so plainly.
How long does discovery take?
Usually a few weeks, ending in an evidence-backed direction.
Ready to scope this?
Tell us the idea and we will help you find out if it is worth building.