37signals-way

# The 37signals Product Development Framework A system for building profitable software without bloat, bureaucracy, or burnout, distilled from three books: *Getting Real* (build less), *Rework* (say no by default), and *Shape Up* (fix time, flex scope). Use it to shape work, bet on six-week cycles, run small autonomous teams, and ship on a predictable cadence. ## Core Principle **Build less.** The best products do fewer things exceptionally well — simplicity is the destination, not the starting point. Traditional development adds; the 37signals way subtracts: build half a product (not a half-assed product), say no by default, fix the time and flex the scope. Constraints are what make great work possible — six weeks, three people, and a shaped pitch force you to find the essential version. ## Scoring **Goal: 10/10.** Rate product plans, feature scopes, and team processes 0-10 against these principles. Report the current score and the specific changes needed to reach 10/10. - **9-10:** Fixed-time cycles, shaped pitches, small teams, no backlog, opinionated defaults, clear copy - **7-8:** Mostly shaped work and small teams, but some scope creep or process overhead - **5-6:** Some shaping happens, but backlogs persist, teams are too large, or preferences replace decisions - **3-4:** Heavy process (standups, sprints, story points) with occasional simplicity efforts - **0-2:** Feature factory: long-term roadmaps, large teams, estimation rituals, no shaping ### 1. Build Less,...