Our discovery sprint template: two weeks that save six months

The most expensive code is the code you build for the wrong problem. A focused two-week discovery sprint is the cheapest insurance you can buy against six months of misdirected engineering.

Week one: understand

Stakeholder interviews, user interviews, a competitive teardown, and a brutal prioritisation of what actually matters for the first release. The output is a shared, written understanding of the problem — not the solution.

Week two: shape

Now we shape a solution: user flows, a clickable prototype of the riskiest path, a technical architecture sketch, and a scoped roadmap. We test the prototype with real users before committing to a build.

The deliverables

• A one-page problem statement everyone agrees on.
• A prioritised feature list for v1 (and an explicit "not now" list).
• A clickable prototype of the core journey.
• An architecture and effort estimate.
• A roadmap with milestones, not just a backlog.

Slow down at the start so you can move fast for the rest of the project.

Every project we have regretted skipped this. Every project we are proud of started here.