Proceed
The central assumptions have enough support to scope implementation.
Explore MVP BuildTest the assumptions. Then plan the build.
Research, prototypes and technical exploration before you commit to development.
Who needs this?What do they do today?What would make them switch?
Evidence briefKnown / Unknown
Tools & technologies
- Figma
- Interactive prototypes
- OpenAPI
- Database modelling
- Architecture decision records
A finding can change the feature.
Assumption
Customers need a live tracking map.
Illustrative research
Separate a feature request from the underlying task.
Reveal a fictional observation to see how it changes the next prototype.
Evidence not yet reviewedWhat you receive.
Research brief
Journey prototype
Evidence log
Technical feasibility notes
Release backlog
Decision summary
Decide what happens next.
Rework
Adjust the audience, journey or technical approach and test again.
Pause
Keep the evidence and avoid a build commitment that it does not support.
Projects shaped from the brief
Urbanface
An opening film, image-led scrolling and a dedicated mobile experience.
View project
ABS Stays
A shared-hosting application with encrypted document storage and a staff review console.
View project
Sinzo
Supplier-data scraping and AI engineering for a cross-border shopping and warehouse platform.
View project- Founded in
- 2013
- Projects delivered
- 550+
- Client countries
- 43+
- Global offices
- 3
FAQs
What do we need before starting?
A customer problem, access to relevant stakeholders and any existing research or product material. A detailed specification is not required.
Do you recruit research participants?
Participant access and recruitment responsibilities are agreed in scope. We identify which user groups need to be represented before planning sessions.
Is the prototype production software?
No. A discovery prototype is used to test interactions and assumptions. Production implementation, hosting and operational work are scoped separately.
What if the findings challenge our idea?
The decision may be to narrow the scope, change the journey, investigate further or stop. Discovery should make that choice more informed, rather than guarantee a build recommendation.
Can another team use the output?
Yes. The agreed handover can include the evidence, prototype, backlog and technical decisions needed by your internal team or another delivery partner.
How is the sprint sized?
The number of user groups, uncertainty in the workflow, access to evidence and technical questions determine the scope. Dates and milestones are agreed after reviewing those inputs.
What do you need to learn?
Bring the idea, your intended users and the assumption you are least certain about.
