Skip to content
Strategy 1 min read

How we run a two-week design sprint

From a blank page to a clickable prototype in ten working days - the cadence we use to de-risk new products.

The otterdev team
How we run a two-week design sprint

A two-week sprint isn’t about rushing. It’s a forcing function: a fixed window that turns endless debate into concrete decisions you can put in front of real people.

Week one: diverge

We map the problem, gather references, and sketch widely. The goal is options, not polish - quantity early makes the right direction easier to recognize.

Week two: converge

We pick a direction, build a clickable prototype, and test it with a handful of users. Five conversations surface the majority of problems worth fixing.

  • Day 6–7: high-fidelity prototype.
  • Day 8–9: usability sessions.
  • Day 10: synthesis and a clear recommendation.

Two weeks in, you don’t have a finished product - you have something far more valuable: confidence about what to build next.

Back to all articles
Share

Say hello

Let's make something
you're proud of.

Tell us what you're working on - even a rough idea is plenty. We read every message and reply like actual humans, usually within a day.

[email protected]

Based in

Podgorica, Montenegro

Working with people here, and anywhere the wifi reaches.

© 2026 otterdev. Built by hand in Montenegro.