Design Sprint

The Design Sprint is a step by step system for bringing a group of people together to solve big problems WITHOUT endless discussion. Withing 4 days, a team using Sprints can go from some vague ideas and challenges to a high fidelity prototype in their hands. This can save months of misalignment before jumping into the real design and development work.


What problems does it solve?

Especially products that are a combination of the digital and phisical world the product development often suffers from the following problems:

  • Focus and enthusiasm is lost in endless meetings and discussions.

  • Products are built on assumptions instead of user tested concepts.

  • Lack of alignment between cross functional teams towards shared objectives.

  • Project scope changes repeatedly due to the absence of a clear goal.

What’s in it for you?

In four days you’ll have an prototype that is tested with real users. You’ll find out if your idea is worth developing and if your value proposition is really valid.

  • Enthusiasm and alignment of your team towards a shared goal.

  • Validated solution in a week.

  • Reduced risk when bringing products to market.

  • Less talk. More action. No more endless meetings and discussions.


How does the sprint solve this?

It’s like your personal timemachine: The sprint allows you and us to look into the future and see the finished product and customer reactions before building and launching it.


Monday & Tuesday “Workshop Time”

This is where we need you to sprint with us. On monday, we will define the challenges and produce a mass of possible solutions. Tuesday will be all about prioritizing solutions and creating a storyboard to prototype. This is the most exciting and intense fun you’ll ever have while working, promise!



This is where the absolute madness starts. Our prototypers will go underground, bring out their mojo and some frozen pizza. By the end of the day they will have an interactive prototype, ready to be tested.



Today we will test the prototype with real users to find out if the product is worth developing. This is where the rubber hits the road.