The UX Sprint
Over the past years, we have optimized our work processes in various UX projects. During that time, we got inspired by agile methods and design sprints. We consolidated our learnings in what we call the »UX Sprint«.
Tons of features in two weeks.
Each sprint is divided between a week of co‑creation and user testing and a second week of elaboration.
& user testing
In the first week, we prioritize features to work on, discuss and vote for solutions, create interactive prototypes and get feedback from real customers.
& shipping
In the second week, we implement the customer feedback and refine the prototype to rock-solid UI designs and developer blueprints.
Output is shipped biweekly.

Layouts & prototypes
We ship clickable high-fidelity prototypes. They offer the perfect way to run user testing or deliver a more complete pitch for your idea and each one contains the layouts needed to start development.

User stories
We base our planning and scoping on a jointly-created user story map. Use it in your JIRA, Notion, etc. Less work on your side.

Tested & validated
Did you know: Asking five users offers the perfect benefit-cost ratio for user testing. User testing is an integral part of our design process.
But first
Why run a UX sprint?
The days of gigantic project planning and estimations that quickly run out of scope are over. The truth: Most challenges only rear their head after the work has begun.
Sprint-based project planning enables us to quickly update scope according to the insights we gather anlong the way.
Thus, UX sprints are fast and flexible. Design an MVP in 2 to 3 weeks, run design inline with development and output rock-solid designs and blueprints.
Too early?
Sometimes it makes sense to figuring out possible ideas and test them before starting a whole project. We run design sprints for that purpose.