The Discovery Sprint translates a service, programme, workflow or platform concept into a clearer product definition before development begins. It reduces ambiguity before time and capital are committed.
Structured discovery | Defined outputs | Build engagement subject to separate approval
Appropriate for portals, mobile applications, marketplaces, transaction workflows, case-management systems, data and AI products, healthcare, education, energy, membership, public-service or enterprise platforms where the concept exists but scope, requirements, architecture or release planning remains incomplete.
Question area | What must be resolved |
Problem and outcome | What problem is being solved, for whom and how will success be measured? |
Users and workflow | Who uses, administers and approves; what journey, exceptions and hand-offs apply? |
Scope and MVP | Which capabilities are essential now, later or out of scope? |
Data and integration | What data is collected, who owns it, which systems and external parties must connect? |
Security and compliance | What roles, permissions, audit, privacy, maker-checker and resilience controls apply? |
Operating model | Who owns the product, roadmap, releases, support, data and continuing budget? |
The sprint should include an authorised executive sponsor, business or programme owner, product and operations representatives, technology and data personnel, security or compliance input where relevant, and selected user or customer representatives. Participation should be limited to people able to explain the current process or approve the future operating model.
Provide a summary of the service or workflow to be digitised, intended users, existing systems, data and target timing.
