141: Jason Fried - Running the Tailwind Business on Basecamp
Episode
66 min
Read time
2 min
Topics
Productivity, Remote Work, Startups
AI-Generated Summary
Key Takeaways
- ✓Project Scope Definition: Create separate Basecamp projects for individual features taking two-plus weeks, not monolithic version releases. Each Hey feature like "Big Attachments" or "Avatar Upload" gets its own project with message board, campfire, and to-dos, avoiding undefined two-point-o projects that become scope traps.
- ✓Communication Hierarchy: Use message boards for permanent decisions and announcements requiring everyone's attention, campfires for casual quick questions with screenshots, and to-do comments for work-specific discussions. Almost zero conversations happen at list level—context lives on individual to-do items where the actual work occurs.
- ✓Team Structure Timing: Skip departmental teams until you have two-plus people per function. With four people total, use HQ for company-wide communication and projects for actual work. Teams become relevant at eight-to-nine people when natural divisions emerge requiring separate ongoing communication channels.
- ✓Work Documentation Pattern: Every project starts with a pitch or shaping document on the message board explaining the scope in 400-800 words. Team members then create their own to-do lists and self-assign work—no top-down task delegation. Document only decisions that ship, not exploratory conversations that go nowhere.
- ✓Onboarding Strategy: Pair new hires with experienced team members on real production work immediately rather than floating on unimportant tasks. New programmer Jorge works with veteran Rosa on actual features from day one. Establishing good organizational habits early prevents building a permanently semi-organized company culture.
What It Covers
Jason Fried coaches Adam Wathan on structuring a four-person Tailwind CSS team in Basecamp, covering project organization, communication patterns, HQ setup, documentation practices, and onboarding strategies for remote teams scaling from two to four members.
Key Questions Answered
- •Project Scope Definition: Create separate Basecamp projects for individual features taking two-plus weeks, not monolithic version releases. Each Hey feature like "Big Attachments" or "Avatar Upload" gets its own project with message board, campfire, and to-dos, avoiding undefined two-point-o projects that become scope traps.
- •Communication Hierarchy: Use message boards for permanent decisions and announcements requiring everyone's attention, campfires for casual quick questions with screenshots, and to-do comments for work-specific discussions. Almost zero conversations happen at list level—context lives on individual to-do items where the actual work occurs.
- •Team Structure Timing: Skip departmental teams until you have two-plus people per function. With four people total, use HQ for company-wide communication and projects for actual work. Teams become relevant at eight-to-nine people when natural divisions emerge requiring separate ongoing communication channels.
- •Work Documentation Pattern: Every project starts with a pitch or shaping document on the message board explaining the scope in 400-800 words. Team members then create their own to-do lists and self-assign work—no top-down task delegation. Document only decisions that ship, not exploratory conversations that go nowhere.
- •Onboarding Strategy: Pair new hires with experienced team members on real production work immediately rather than floating on unimportant tasks. New programmer Jorge works with veteran Rosa on actual features from day one. Establishing good organizational habits early prevents building a permanently semi-organized company culture.
Notable Moment
Basecamp runs dozens of simultaneous Hey projects, each named with the product prefix like "Hey Avatars" or "Hey Bundles" in a flat list rather than nested folders. This naming convention keeps projects specific and focused while maintaining searchability across thirty-plus active feature developments.
Episode Transcript
In this episode of Fullstack Radio, I get a one on one coaching session with Jason Fried on how exactly we should use Basecamp to keep the Tailwind business organized as we start to bring on our first team members. This is Fullstack Radio episode one forty one. One. So the reason that, I wanted to have you on the show today and the stuff that I want to talk about is, the company that I run with my business partner, Steve, we create user interface tools for people. So we run open source projects like Tailwind CSS and, we lately have been building, like, predesigned templates and stuff to sort of we've kind of like a commercial branch of the open source business. We also do educational products and stuff, but it's just been the two of us for a long, long time. And we're hitting the point now where it's like we're drowning and we need to bring people on to help us out. And, that's a really crazy kinda turning point in how things are gonna be going for us, I feel like. And I'm a little bit nervous about it because I, up until now, have just been kind of working for myself, managing my own work. Steve works pretty independently too. But we are hiring a couple of people to come on and help us. And, honestly, I feel like I don't know the first thing about making sure, that that all goes, successful. So I attended a workshop that you guys did at the, Basecamp office a few years back where you kinda walked through how you guys use Basecamp, and it was really eye opening and inspiring to me. But I I feel like at the time, not running my own remote company, there's just lots of stuff that just went one ear and out the other that I missed. Right? And I feel like it'd be awesome to revisit some of that stuff, with you today and talk about some of the ways that you guys run the team at Basecamp, how you use Basecamp to do it, and, sort of lessons learned and mistakes that you made along the way. Yeah. That sounds like a good topic. Clearly, I've got a lot to share about that. So, yeah, any way I could be helpful would be my pleasure. I think the first thing that I'd be kind of curious to know which, is kind of tangentially related, but when I came to the workshop that you guys did at Basecamp, I was sort of surprised that the way that you presented the tool, it was not the way it had sort of been pitched to me over the years. Like, I always thought of Basecamp as like a client team communication project management tool, which I think is absolutely how it started and that was a problem you're solving for yourself in the beginning. But watching you kind of walk through …
Get the full transcript (13,697 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 63-minute episode.
Get Full Stack Radio summarized like this every Monday — plus up to 2 more podcasts, free.
Pick Your Podcasts — FreeKeep Reading
More from Full Stack Radio
153: DHH – Omarchy and Designing Your Own OS on Arch Linux
Aug 21 · 76 min
The Rework Podcast
Business beyond profit
Mar 18
More from Full Stack Radio
152: Ben Orenstein - How to Stand Out When Applying for a Job at a Small Company
Jan 28 · 47 min
The Rework Podcast
Talk directly to your customers
Feb 25
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.
Tools
by Tailwind Labs
“Jason Fried coaches Adam Wathan on structuring a four-person Tailwind CSS team in Basecamp, covering project organization, communication patterns, HQ setup, documentation practices, and onboarding strategies for remote teams scaling from two to four members.”
by Basecamp
“Jason Fried coaches Adam Wathan on structuring a four-person Tailwind CSS team in Basecamp, covering project organization, communication patterns, HQ setup, documentation practices, and onboarding strategies for remote teams scaling from two to four members.”
Products
by Basecamp
“Each Hey feature like "Big Attachments" or "Avatar Upload" gets its own project with message board, campfire, and to-dos. Basecamp runs dozens of simultaneous Hey projects, each named with the product prefix like "Hey Avatars" or "Hey Bundles" in a flat list rather than nested folders.”
More from Full Stack Radio
We summarize every new episode. Want them in your inbox?
153: DHH – Omarchy and Designing Your Own OS on Arch Linux
152: Ben Orenstein - How to Stand Out When Applying for a Job at a Small Company
151: DHH – Building HEY with Hotwire
150: Secret Screencasting Tips & Behind the Scenes of Tailwind CSS 2.0
149: Choosing a Payment Processor, Radical Icons & W3C Hype
Similar Episodes
Related episodes from other podcasts
The Rework Podcast
Mar 18
Business beyond profit
The Rework Podcast
Feb 25
Talk directly to your customers
David Senra
Feb 15
Jason Fried, 37signals (makers of Basecamp, HEY and ONCE)
20VC (20 Minute VC)
Aug 13
20VC: Canva Slashes Growth: How Much is it Really Worth | Demis Hassabis and Jeff Dean: Talent Exodus at Google | Revolut's $50BN CEO Pay Package | Elon Musk's $55BN Terrafab
Lenny's Podcast
Aug 9
The playbook for building high talent density teams | Adam Ward, Head of Talent at Cursor
Explore Related Topics
This podcast is featured in Best Cybersecurity 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 Full Stack Radio.
Every Monday, we deliver AI summaries of the latest episodes from Full Stack Radio and 192+ other podcasts. Free for one show.
Start My Monday DigestNo credit card · Unsubscribe anytime