// description
An organisational model for scaling Agile across large companies using autonomous cross-functional Squads (small teams owning a feature area), Tribes (collections of squads), Chapters (people with the same skill across squads), and Guilds (communities of interest).
// history
Henrik Kniberg and Anders Ivarsson published "Scaling Agile @ Spotify" in 2012, describing how Spotify organised its engineering teams. The model went viral in tech circles as a blueprint for maintaining startup agility as organisations grow. Ironically, Spotify itself moved away from the model over time as it faced practical challenges, but the concepts — particularly autonomous squads and communities of practice — remain widely influential in how companies think about team design.
// example
A creator community could apply Spotify Model concepts: Squads are small accountability groups working on the same goal (e.g., publishing KDP books). A Tribe is the broader community working in the same space (e.g., the Smorg community). A Chapter is people with the same specialism sharing knowledge (e.g., Midjourney users comparing prompts). A Guild is an informal interest group crossing all those lines (e.g., a group obsessed with planner aesthetics).
// katharyne's take
I find the Spotify Model most useful as a lens for designing communities rather than companies. When I think about the Smorg community structure, these concepts help me understand why some groups are energised and others go quiet. The Guild concept is particularly useful — informal, interest-driven, nobody's in charge. The best communities I've been part of have had strong guilds. The Spotify Model is worth knowing even if you'd never use the full thing.
// creative uses
- Structure your paid community on Circle or Discord using the Spotify Model: create dedicated Squads (small accountability pods of 5–8 people with a shared goal like "publish 3 KDP books this quarter"), and let Guilds form organically around shared interests like "cosy aesthetic" or "low-content books."
- Use the Chapter concept for your content niche expertise: if your community has both Midjourney users and Canva designers, create separate channels for each skill group to share prompts, templates, and techniques. Cross-pollination of chapters is where the most interesting ideas emerge.
- Design your course alumni community with Squads: after students finish your course, place them in small accountability pods with a shared 30-day goal. Squads dramatically outperform broadcast communities for engagement and results — and results become your testimonials.
// quick actions
- If you run a paid community, look at which channels or groups have the highest engagement. Those are your natural Guilds — informal, interest-driven, self-organising. Stop trying to manufacture engagement in dead channels and invest more support in the ones already alive.
- Create one Squad inside your community this week: a small group of 5–8 people with a shared specific goal and a 30-day window. Use a dedicated channel, a shared Notion doc for tracking progress, and a weekly check-in thread. See if that format produces more results than your general channels.
- If you're building your first paid community, design the structure before launch: what are the Squads (goal-based pods), what are the Chapters (skill-based channels), what Guilds do you want to let emerge? Having the taxonomy mapped before launch makes onboarding dramatically cleaner.
// prompt ideas
I'm building a paid community for [describe your niche — e.g. KDP publishers, Etsy sellers, digital product creators]. Using the Spotify Model as a loose framework, help me design the structure: what should my Squads look like, what Chapters make sense for my audience's skill sets, and what Guilds might form organically? Give me specific channel names and a brief description of each group's purpose.
My [Discord / Circle / Skool] community has [X members] but engagement is low outside of [specific active area]. Diagnose this using the Spotify Model lens — which Squads, Chapters, or Guilds are missing or underserved — and suggest 3 structural changes I could make this week to increase meaningful participation.
Help me design a 30-day Squad accountability challenge for my community of [describe your community — e.g. new Etsy sellers, course creators, KDP beginners]. What should the Squad size be, what shared goal should they work toward, how should they check in, and what does success look like at day 30?