# UX Sprint

> Test the riskiest flow before the team builds it

- URL: https://www.digitaltableteur.com/engagements/ux-sprint
- Price: €7–14k
- Timeline: 2 weeks
- Book: https://www.digitaltableteur.com/contact?mode=book&package=ux-sprint

A new flow is about to absorb months of build time and nobody has seen it work. A UX Sprint turns the open question into a working prototype of the key flow, an eval plan to test it with users and a handoff your team can build from.

## Use a sprint when a decision is waiting on evidence

- A new feature or flow is about to go into a long build
- Stakeholders disagree about how the key flow should work
- Usability problems keep surfacing late, after release
- An AI feature needs a defined way to judge whether its output is good enough

## What the sprint covers

The sprint focuses on one key flow: the one where the product decision carries the most risk. It is framed with the people who own it, built as a working prototype in your own components where possible and paired with an eval plan that says how users will test it and what counts as success.

## Not included unless scoped separately

- Production implementation of the flow
- Running the full user study
- Visual identity or brand work

## How the sprint runs

1. Frame the decision, the users and the success criteria with the team that owns the flow.
2. Map the flow and sketch the alternatives worth testing.
3. Build a working prototype of the key flow.
4. Write the eval plan and hand over the prototype, findings and next steps.

## What you receive

- A working prototype of the key flow
- An eval plan with tasks, participants and success criteria
- A decision record of the options considered
- A handoff your team can build from

## How the price is set

2 weeks, fixed scope. Final scope depends on the complexity of the flow, the number of user groups and how much of your existing design system the prototype can reuse.

## About the sprint

**Is a UX Sprint the same as a design system audit?** No. The sprint answers one product question with a working prototype. The Design System Audit reviews the system you already have and ends in a 90-day roadmap. They are booked separately.

**Who runs the user tests?** The eval plan is ready for your team or a research partner to run, with tasks, participants and success criteria written out.

**Can the prototype become production code?** It is built to test the decision, not to ship. Parts built with your design system's components carry over, and Design System Lift-Off or an embedded partnership can take the flow to production.