Managing chaos, feature bloat, and other listener questions
Episode
22 min
Read time
2 min
Topics
Career Growth, Productivity, Startups
AI-Generated Summary
Key Takeaways
- ✓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.
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.
Notable Moment
David reveals 37signals built the first Basecamp version using just ten hours weekly of his time as side project work, demonstrating that constraint produces better results than throwing twenty people at a product, which inevitably creates bloat and deterioration.
Episode Transcript
Welcome to Rework, podcast by thirty seven signals about the better way to work and run your business. I'm Kimberly Rhodes from the thirty seven signals team with Jason Fried and David Heinemeier Hansen, our company cofounders. This week, we're gonna knock out a couple of more video submissions that we got to the Rework podcast. So let's start with one from Jacob. Hello, Jason, David, and Kimberly. My question is about managing order and chaos. How do you create structure at a workplace without creating a bureaucracy? How do you maintain free flow without everything becoming a mess? What have been your strategies for walking this tightrope, and how do you personally discern when you're leaning too much one way or the other? Thank you. There's probably a lot of ways to answer this. One way I would start with is just like compartmentalization. People are assigned to a project for, let's say, a few weeks, whatever it might be, and, like, that's, like, all they have to worry about. So this idea that, like, there's so much going on and there's so many things happening, like, I don't know where the chaos is coming from, but if you're focused on just one thing, on one project, and that's your responsibility and that's kind of the only responsibility you have, I feel like that's kind of enough usually to keep all that noise away. I think if you're constantly bouncing around, if you're constantly involved with five or six separate things across the company in different places, it is gonna feel like chaos. It is gonna be hard. There's always stuff bubbling up to do. So I think what we try to do is we try to draw some borders around people, give them a project, whatever it might be, give them a a time frame essentially to get it done within, and then that's their only responsibility. I think that's maybe the best way on an individual level I I can think of. At a company level, if you're changing your direction constantly, if you're changing your mind all the time on big picture things, that's gonna drip down and affect everybody else. It's gonna feel like there's chaos everywhere. It's like this. Partially, it's just about, like, committing to something and and doing the thing and seeing it through versus constantly, like, never quite finishing, getting 80, 90% done, then moving on to something else. That can create a lot of chaos and a lot of loose ends and untied knots that just people start to trip over eventually. I don't know really where to go with that, but that's kind of a couple of things that come to mind. And I think the way we've tried to do that in a structured way is by following ShapeUp. ShapeUp is our software methodology that speaks exactly to this problem of thrashing because I actually think that's the default state when especially founders are close to the product …
Get the full transcript (4,606 words) + summary by email — free
One-time email with the complete transcript and AI summary of this episode. No account needed.
One email, no spam. We’ll also show you what SignalCast does.
You just read a 3-minute summary of a 19-minute episode.
Get The Rework Podcast summarized like this every Monday — plus up to 2 more podcasts, free.
Pick Your Podcasts — FreeKeep Reading
More from The Rework Podcast
One-way Doors
Aug 26 · 18 min
David Senra
David Heinemeier Hansson (DHH), Co-founder of 37signals
Jul 26
More from The Rework Podcast
Competing with giants, the end of SaaS & other listener questions
Aug 19 · 26 min
My First Million
DHH: $100M+ Advice That'll Piss Off Every Business Guru
Mar 17
Books, tools, and gear mentioned in this episode
SignalCast may earn commission on purchases via these links. As an Amazon Associate, SignalCast earns from qualifying purchases.
Books
by 37signals
“Implement six to eight week work cycles with two week cooldown periods... This boundary prevents chaos at the individual level by creating clear focus areas rather than constant context switching across five or six separate initiatives.”
Tools
by 37signals
“David reveals 37signals built the first Basecamp version using just ten hours weekly of his time as side project work, demonstrating that constraint produces better results than throwing twenty people at a product.”
More from The Rework Podcast
We summarize every new episode. Want them in your inbox?
Similar Episodes
Related episodes from other podcasts
David Senra
Jul 26
David Heinemeier Hansson (DHH), Co-founder of 37signals
My First Million
Mar 17
DHH: $100M+ Advice That'll Piss Off Every Business Guru
David Senra
Feb 15
Jason Fried, 37signals (makers of Basecamp, HEY and ONCE)
The Diary of a CEO
Aug 31
Top White House Advisor: The US Empire Is DYING And Socialism Is Coming Next! | David Friedberg
This Week in Startups
Aug 21
Open source is going to win it all: Harvey proves it | E2328
Explore Related Topics
This podcast is featured in Best Business Podcasts (2026) — ranked and reviewed with AI summaries.
Read this week's Startups & Product Podcast Insights — cross-podcast analysis updated weekly.
You're clearly into The Rework Podcast.
Every Monday, we deliver AI summaries of the latest episodes from The Rework Podcast and 192+ other podcasts. Free for one show.
Start My Monday DigestNo credit card · Unsubscribe anytime