Managing chaos, feature bloat, and other listener questions

What It Covers

37signals cofounders Jason Fried and David Heinemeier Hansson answer listener questions about preventing workplace chaos through compartmentalization, applying ShapeUp methodology beyond software development, and combating feature bloat in mature products.

Key Questions Answered

• •Project compartmentalization: Assign people to single projects for defined periods like six weeks, eliminating noise from multiple simultaneous responsibilities. This boundary prevents chaos at the individual level by creating clear focus areas rather than constant context switching across five or six separate initiatives.
• •ShapeUp cycle structure: Implement six to eight week work cycles with two week cooldown periods, creating two month intervals where teams work uninterrupted. This protects companies from founder impulses and constant direction changes while preventing both chaos and rigid eighteen month roadmaps that kill creativity and responsiveness.
• •Resource allocation ratios: Operations teams split time fifty-fifty between planned projects and reactive work that appears unexpectedly. Other departments like finance and people operations determine their own ratio of scheduled versus unplanned work, recognizing not every role operates purely in project mode with full schedule control.
• •Fighting feature bloat: Redirect engineering energy toward simplification rather than constant expansion by combining redundant features, surfacing buried functionality, and improving navigation directness. Software lacks physical constraints that naturally limit growth, requiring conscious decisions to tighten products and leave features unchanged for extended periods.