Before the build,
make the decisions.
A focused first engagement to clarify the product, test the main journey and define a realistic development scope.
A useful fit
A founder or team with an app idea, an operational problem or an important uncertainty before development.
The shape of the scope
What we would
work through.
- Product goals, users and existing workflow
- Core journeys and first-release priorities
- A prototype or technical investigation where needed
- A delivery outline with dependencies and assumptions
A bounded question, with a practical output.
The sprint begins by agreeing what the team needs to decide. That might be the shape of an MVP, whether a mobile app is required or how a critical integration would work.
We review the available evidence and work through the main journey. Research, prototypes and technical checks are selected for the question rather than included as a fixed list of workshop activities.
An informed next commitment.
The outcome is a product brief and a prioritised next step, with the important assumptions still visible. If the evidence suggests changing the idea or postponing development, that is a useful result.
You can use the agreed deliverables to commission development with Ardager-B or another team. The sprint does not require a commitment to a larger build.
What to bring.
- A decision-maker and access to relevant users
- Existing research, sketches or workflow examples
- Known constraints and external dependencies
- Time for focused reviews and decisions
At handover
A product brief, agreed design or investigation outputs and a delivery outline that distinguishes evidence, assumptions and open questions.
Begin with the situation.
Describe the app, the people who will use it and the task it should make easier.
Prepare a project outline