141: Jason Fried - Running the Tailwind Business on Basecamp

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.