Design Sprint

A design sprint is a work format for teams who want to test a new idea. It usually lasts five working days and follows a fixed process. It starts with an open question, for example: Would people use an app that organizes carpools for the school commute? At the end there is no finished app, but a mock-up and the reactions of real users to it. The format was invented at Google, where it was first used for new product ideas. Today it is used equally by corporations, government agencies, and small companies.

One week instead of half a year

The usual path to a new product is long. People discuss for months, then build something, and only afterward does it become clear whether anyone wants it. Often it turns out that the idea missed the needs of the users. Then a lot of work time is lost.

The design sprint reverses this order. User feedback comes at the beginning, not at the end. A team thus risks five days instead of six months. If the test turns out badly, that was not a failure, but cheap information.

A second effect is decision speed. In many companies, debates drag on for weeks because no one is allowed to decide alone. In the sprint, all participants sit in the room at the same time, including the person with decision-making authority. What would otherwise be negotiated over ten meetings is settled here in one afternoon.

The five days in sequence

On the first day, the team clarifies the problem. It gathers what is already known, talks to experts within the company, and sets a goal. Narrowing the scope is important: not the whole app is worked on, but a single part, such as the login. On the second day, all participants sketch solutions, first alone on paper. This prevents the loudest voice from setting the direction.

On the third day, selection takes place. The sketches hang on the wall, everyone distributes sticky dots, and then the responsible person decides. From the winning sketch a storyboard for the test is created. On the fourth day, the team builds a prototype, that is, a model that only works as far as necessary for the test. Often these are linked screen images without any real technology behind them.

The fifth day belongs to the users. Five people who are not part of the team try out the prototype individually and think out loud while doing so. The team watches via video and notes patterns. Experience shows that already five tests reveal most serious flaws in thinking. The prototype should not be confused with an MVP: the prototype is a mock-up for the test, whereas an MVP is a stripped-down but real version for the market.

Sprints in AI projects and everyday work life

Design sprints crop up everywhere digital products are created. Agencies sell them as a service, banks use them for new apps, administrations for online forms. In job postings the term appears as an expected experience, often alongside roles like product manager or UX designer.

The format is now especially widespread for AI features. Whether a chat assistant in an online shop really helps is hard to answer at a desk. A sprint can test this without training a model: a human types the answers in the background, and the test person believes they are the AI. Such tricks reveal early on whether the idea holds up at all.

A common misconception is to treat the sprint as a cure-all. It answers a single, clearly stated question. Questions about technology, cost, or legal matters remain open and require other procedures. The term itself is also often used imprecisely: anyone who calls every fast work week a sprint usually does not mean this format.