Loading content
Squads, tribes, chapters, and guilds do not create team autonomy on their own. Copying labels and org charts leaves existing dependencies and decision paths in place under new names.
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Theoretical construct: explains a term, principle, or mental model.
Concrete cog in the system that works inside larger relationships.
The concept describes the risk of adopting Spotify labels and team names without redesigning decision rights, product boundaries, and collaboration.
Spotify published its way of working in 2012 with squads, tribes, chapters, and guilds as a context-specific model for a fast-growing product company. Later reporting and statements from people around it stressed that much of it was only approximate and never fully implemented. The risk appears when organizations copy the vocabulary and org chart but leave dependencies, decision paths, and collaboration unchanged.
Think of the pattern as new signs on top of an old operating system. Team and role names change, but goal conflicts, responsibilities, dependencies, and management paths stay the same underneath. Only when product boundaries, decision rights, coordination, and metrics change together does organizational behavior change. Otherwise, the company just gets new vocabulary for old bottlenecks.
The reference model is context-specific; its vocabulary is not automatically transferable.
Autonomy depends on who can set goals, priorities, and exceptions in a binding way.
Teams need a clear scope so responsibility and dependencies do not keep shifting.
Collaboration rules determine how teams handle conflicts, interfaces, and joint work.
Company size, technical dependencies, and leadership structure shape whether a model holds up.
This orientation helps in organizational design, scaling, and restructuring when templates, roles, or team labels from another company are being considered. It guards against pseudo-autonomy and cosmetic renaming. It is most useful before a change; its value drops once decision spaces, interfaces, and responsibilities have already been redesigned cleanly.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.