📎 Webclip
How we structure our work and teams at Basecamp
Basecamp organizes product work in six-week cycles. Each cycle includes a few large projects and several smaller ones, with one or two weeks afterward for unscheduled work, context switching, and preparing the next cycle. The company treats its own process as something to keep improving.
Reading notes#
- Work is grouped into six-week cycles.
- Big Batch projects are large enough to fill most of a cycle, while Small Batch projects are shorter, smaller changes.
- Planning happens before a project is scheduled, so the six weeks are for implementation and execution.
- The company aims to fit most important work into a six-week version through scope hammering.
- Big Batch projects each get a team, while Small Batch projects are handled by one team.
- Teams are usually two or three people, with either one designer and one programmer or two programmers and one designer.
- Teams are assembled ad hoc based on people’s interests and preferences.
- There are no dedicated project managers; the designer leads the project and works closely with the programmer or programmers.
- Everyone tracks work and communication in Basecamp 3.
- The company does not track time or compare actuals with estimates.
- Ideas can come from anywhere, including the company and customers, and become pitches when they feel formed enough.
- Pitches are written and posted in Basecamp rather than presented in person.
- The final choice of projects comes from Jason, David, and Ryan after reviewing pitches and debating options.
- Each Big Batch project gets its own Basecamp project, and all Small Batch projects for a cycle live in one project.
- QA is handled by Ann and Michael, who join projects early when teams want checks.
- Jason and David stay involved in most customer-facing work and product updates.
