We build products with two people at a time. So every feature we work on in Basecamp, or HEY, or whatever we're building is two people, one programmer, one designer, and they have a maximum of six weeks to deliver the feature that they're working on.
Small focused teams outperform large coordinated ones
Execution → Process & Rituals
I think small teams are better than big ones, period. And forcing the teams to be like super, sort of thoughtful about hitting milestones and actually adding value, because there's this thing people say about like, 'Hey, the startup within a startup, everything's fake.' And the reason I think it's fake is because when you're a startup you actually worry about paying the people who work for you, and when you aren't inside of a company you just don't.
Small teams with clear missions. If there's 300 people trying to work on one thing, the just sheer communication challenges, Dunbar's number, all of those things come into play and it's really, really hard to act quickly.
Do fewer things and try to single thread the team as much as possible.
Single threaded is there's only one goal, one thread, that they're waking up in the morning to focus on. And in order to remove that, you basically need to remove anything else that they're being asked to do to just focus on that thing.