Eleven weeks to a store

Eleven weeks sounds like a boast until you see the calendar. Two weeks of listening. One week of arguing — properly, with prototypes. Six weeks of building in the real stack while design and code sat at the same desk. One bad week (week eight, always week eight). One week of tightening.

The trick is not speed; it is the absence of translation. Nothing was designed in one tool and rebuilt in another. The product page you can visit today is the third prototype, promoted. When the design is the build, every review is a rehearsal on the real stage, and week eight’s crisis was a merge conflict, not a redesign.

The other trick is smaller: we agreed with Veldt on what would not change after week three. The grid, the type scale, the motion rules — frozen. Freedom everywhere else. Constraints agreed early are the cheapest project insurance ever invented.

Could we do it in ten? Probably not. The eleventh week is where a fast project becomes a finished one, and we have never regretted it.