Move fast when you can

What It Covers

Jason Fried and David Heinemeier Hansson use a HEY Calendar full-year view feature—built overnight by designer Michelle—to examine how shipping within 24 hours captures cultural momentum, why code maintainability enables speed, and how daily one-hour improvements compound into meaningful product progress over time.

Key Questions Answered

• •Momentum windows: Cultural conversations on social platforms have a 24-hour response window before relevance fades. When a viral post about full-year calendar layouts appeared on X, 37signals shipped a working feature the next morning, becoming first to respond rather than the sixth tool to release a similar feature days later. Timing determines whether a launch generates noise or silence.
• •Scope reduction as the primary speed lever: The single most reliable way to ship in one day is cutting scope to the core idea—the "epicenter"—and deferring everything else. When colleagues suggested additions to the calendar feature, 37signals deliberately ignored them to protect the launch window. An imperfect version shipped in 24 hours outperforms a polished version shipped in two weeks.
• •Code maintainability directly enables shipping velocity: Michelle could build the full-year calendar view overnight because she was extending an existing, well-structured calendar codebase rather than starting fresh. David frames clean code as a compounding asset: a 14-year-old Basecamp codebase with low technical debt lets a single developer ship confidently without fear of breaking unrelated systems.
• •Fixed time, flexible scope as an anxiety antidote: Developer anxiety peaks when scope is fixed and deadlines are imposed externally. Inverting this—fixing only the time constraint (one day, one hour) and letting scope shrink to fit—activates what David describes as the mind's natural efficiency under constraints, producing focused output without the death-march pressure common in gaming industry crunch cycles.
• •Daily one-hour improvements as a product strategy: Jason proposes a cadence of at least one visible, before-and-after improvement shipped to Basecamp every single day. These need not be large—adding a timestamp, improving card proportions, increasing data density on a widget. Accumulated daily, small high-leverage changes produce compounding product quality gains without requiring large coordinated releases.