Chapters & Squads

Reach for this when the product org is scaling past one team and coordination starts eating delivery. It earned its keep around 40 people at my own startup — before that, it's overhead. Don't squadify too early.

How it works

• A squad is a small cross-functional team — e.g. three engineers, a product manager, a designer, a business analyst — that owns one part of the user journey end to end.
• Squads own journeys, not features: at a banking product that meant one squad for banking & cards, one for trading, one for onboarding & growth.
• Chapters run across squads — engineering, product, design — so each craft keeps shared standards, career paths and peer learning while people sit in different squads.