Design sprint

디자인 스프린트

A five-day compressed process — from framing the problem to testing a prototype — codified by Google Ventures.

Also known as: 5-day sprintGV Sprint
···
html
<div class="stage">
  <div class="days" id="days"></div>
  <div class="panel" id="panel">
    <div class="day-name" id="dayName">Monday</div>
    <div class="day-act" id="dayAct">Map</div>
  </div>
</div>
css
.stage{width:94%;height:88%;display:flex;flex-direction:column;gap:14px}
.days{display:flex;gap:6px;height:40%}
.day{flex:1;border-radius:8px;background:var(--line);display:flex;align-items:flex-end;justify-content:center;
  padding-bottom:6px;font:700 9px/1 monospace;color:var(--muted);transition:background .4s,color .4s}
.day.on{background:var(--accent);color:#fff}
.panel{flex:1;display:flex;flex-direction:column;align-items:center;justify-content:center;gap:4px;
  border:1px solid var(--line);border-radius:10px}
.day-name{font:700 11px/1 monospace;color:var(--muted)}
.day-act{font:800 20px/1 sans-serif;color:var(--fg)}
js
const names = ['Mon', 'Tue', 'Wed', 'Thu', 'Fri'];
const full = ['Monday', 'Tuesday', 'Wednesday', 'Thursday', 'Friday'];
const acts = ['Map', 'Sketch', 'Decide', 'Prototype', 'Test'];
const days = document.getElementById('days');
const dayEls = names.map((n) => {
  const d = document.createElement('div');
  d.className = 'day';
  d.textContent = n;
  days.appendChild(d);
  return d;
});
const dayName = document.getElementById('dayName');
const dayAct = document.getElementById('dayAct');
let i = 0;
function step() {
  dayEls.forEach((d, k) => d.classList.toggle('on', k === i));
  dayName.textContent = full[i];
  dayAct.textContent = acts[i];
  i = (i + 1) % names.length;
}
step();
setInterval(step, 1100);

Refined at Google Ventures by Jake Knapp and documented in the book Sprint. Monday sets the long-term goal and sprint question, then maps the problem. Tuesday, each person sketches solutions alone. Wednesday, the team critiques every sketch and commits to one storyboard. Thursday builds a prototype that looks and feels real in a single day. Friday tests it in five one-on-one interviews with real users.

The core idea is refusing to let decisions drag out. Discussion, decision-making, and validation that would normally sprawl across weeks get compressed into one forced week, so the team hears real reactions before it gets too attached to an idea. A single pre-appointed Decider is also part of the format — specifically to stop debate from running indefinitely.

If the double diamond is the conceptual shape of a design process, a design sprint is one diverge-converge cycle from it pinned to an actual runnable schedule — five days, specific activities on specific days.

When to use

Use it for a big, risky decision where debate keeps dragging on — to force it through building something real and showing it to users within a single week.