methodatlas
Session Builder

Plan my session

Plan a concrete work block with agenda, roles, preparation, and a copyable result artifact.

Method session90-180 minWorkshopSpotify-Modell-Karte

Session: Spotify Model Mapping

The plan translates the method into a concrete facilitated work block. Your inputs flow directly into the session brief and work artifact.

Derived automatically

Method session with 5-15. The plan uses the existing method logic and the runsheet.

Runsheet
Participation logic
Team round, shared work and alignment

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome logic
Finish artifact

The session works directly toward Spotify-Modell-Karte. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Phase 1: Define terms

    20 min

    Discuss each term and define it for own org. Squad: autonomous team with mission. Tribe: 30-150 people with shared area. Chapter: skill group (for example frontend) across squads. Guild: voluntary interest group. Hint: Spotify myth: the model was idealized. Spotify itself evolved it. Copying the model without clarifying own meaning creates buzzword org.

    FacilitatorSpotify-Modell-Karte
  2. 2

    Phase 2: Position squads

    20-30 min

    Place current teams as squads. Note mission, size, responsibility per squad. Mark squads without clear mission. Hint: If squad has no mission or is too large (>10 people), it is not a squad in the Spotify sense. Mark honestly instead of applying label.

    FacilitatorAktionsliste
  3. 3

    Phase 3: Tribes and chapters

    30-40 min

    Group squads into tribes by shared area. Identify chapters: which skill groups exist (frontend, backend, mobile, data, QA). Name chapter lead per chapter. Hint: Tribes have scaling limits (Dunbar number ~150). In smaller orgs, tribes are redundant. Chapters need a lead, otherwise they are nominal, not functional.

    FacilitatorSpotify-Modell-Karte
  4. 4

    Phase 4: Name guilds explicitly

    15-20 min

    List active guilds (voluntary interest groups). Examples: ML guild, security guild, accessibility guild. Per guild: meeting frequency and format. Hint: If no guilds exist, the model is incomplete. Guilds emerge organically, not by order. If nobody is interested, there is no guild.

    FacilitatorAktionsliste
  5. 5

    Phase 5: Gaps and actions

    20-30 min

    Mark friction points and gaps in model: squads without tribe, chapters without lead, missing cross-cutting topics. Actions with owner and deadline. Hint: Actions can be: sharpen squad mission, name chapter lead, found guild, or deliberately drop Spotify terms because they do not fit.

    OwnerSpotify-Modell-Karte
  6. 6

    Publish artifact

    10 min

    Check the artifact for completeness, define location, set version or status, and name review recipients.

    OwnerSpotify-Modell-Karte
Usable artifact

Session Brief

For invitations, boards, tickets, PR descriptions, or workshop notes.

session-brief.md

Session Brief: Spotify Model Mapping

Goal

Artifact: Spotify-Modell-Karte

Working Question

How is our engineering org actually structured into squads, tribes, chapters and guilds, and where do friction or gaps emerge?

Context

Team list with size and responsibility; current reporting lines; existing chapter structures (for example frontend chapter, backend chapter); guild activities; comparison with real Spotify model from literature.

Setup

  • Format: Method session
  • Duration: 90-180 min
  • Mode: Workshop
  • Participants: One facilitator with org-design experience; CTO or engineering director as sponsor; engineering leads; HR partner for human-capital perspective; scribe for actions.
  • Owner: One facilitator with org-design experience
  • Participation mode: Team round, shared work and alignment
  • Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward Spotify-Modell-Karte. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Whiteboard or Miro board with Spotify model template (squads, tribes, chapters, guilds as sections); current team list; org chart as reference; list of known frictions; pens; confidential area for diagnosis.

Preparation

Template with four sections: Squads (autonomous teams), Tribes (group of squads with shared area), Chapters (skill groups across squads), Guilds (interest groups). Definitions visible. Critical note: Spotify itself no longer uses it in this form.

Agenda

  1. Phase 1: Define terms (20 min) Owner: Facilitator Action: Discuss each term and define it for own org. Squad: autonomous team with mission. Tribe: 30-150 people with shared area. Chapter: skill group (for example frontend) across squads. Guild: voluntary interest group. Hint: Spotify myth: the model was idealized. Spotify itself evolved it. Copying the model without clarifying own meaning creates buzzword org. Output: Spotify-Modell-Karte

  2. Phase 2: Position squads (20-30 min) Owner: Facilitator Action: Place current teams as squads. Note mission, size, responsibility per squad. Mark squads without clear mission. Hint: If squad has no mission or is too large (>10 people), it is not a squad in the Spotify sense. Mark honestly instead of applying label. Output: Aktionsliste

  3. Phase 3: Tribes and chapters (30-40 min) Owner: Facilitator Action: Group squads into tribes by shared area. Identify chapters: which skill groups exist (frontend, backend, mobile, data, QA). Name chapter lead per chapter. Hint: Tribes have scaling limits (Dunbar number ~150). In smaller orgs, tribes are redundant. Chapters need a lead, otherwise they are nominal, not functional. Output: Spotify-Modell-Karte

  4. Phase 4: Name guilds explicitly (15-20 min) Owner: Facilitator Action: List active guilds (voluntary interest groups). Examples: ML guild, security guild, accessibility guild. Per guild: meeting frequency and format. Hint: If no guilds exist, the model is incomplete. Guilds emerge organically, not by order. If nobody is interested, there is no guild. Output: Aktionsliste

  5. Phase 5: Gaps and actions (20-30 min) Owner: Owner Action: Mark friction points and gaps in model: squads without tribe, chapters without lead, missing cross-cutting topics. Actions with owner and deadline. Hint: Actions can be: sharpen squad mission, name chapter lead, found guild, or deliberately drop Spotify terms because they do not fit. Output: Spotify-Modell-Karte

  6. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Spotify-Modell-Karte

Closeout

  • Update result artifact: Spotify-Modell-Karte
  • Define location, version, and review recipients.
  • Define owner, next step, and review date.
Usable artifact

Work artifact

Pre-filled starting point based on the matching template.

work-artifact.md

Spotify-Modell-Karte: Spotify Model Mapping

Working Question

How is our engineering org actually structured into squads, tribes, chapters and guilds, and where do friction or gaps emerge?

Context

Team list with size and responsibility; current reporting lines; existing chapter structures (for example frontend chapter, backend chapter); guild activities; comparison with real Spotify model from literature.

Participants

  • Owner: One facilitator with org-design experience
  • Participants: One facilitator with org-design experience; CTO or engineering director as sponsor; engineering leads; HR partner for human-capital perspective; scribe for actions.

Input

Whiteboard or Miro board with Spotify model template (squads, tribes, chapters, guilds as sections); current team list; org chart as reference; list of known frictions; pens; confidential area for diagnosis.

Template

Spotify Model Mapping Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

  • Area 1:
  • Area 2:
  • Area 3:
  • Relationships / patterns:

Output artifacts

  • Spotify model map:
  • Action list:

Open questions

  • ...

Next step

Owner, date, success signal.

Completion Check

  • Spotify-Modell-Karte is complete enough for review:
  • Location:
  • Version / status:
  • Review by:
  • Next step:

Next Step

  • Review result
  • Mark open questions
  • Schedule review or decision
Template base

Spotify Model Mapping Working Template

View templateCompact working template for Spotify Model Mapping with context, input, output artifacts, and next step.
canvas

spotify-model-mapping-working-template.md

Compact working template for Spotify Model Mapping with context, input, output artifacts, and next step.

Spotify Model Mapping Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

  • Area 1:
  • Area 2:
  • Area 3:
  • Relationships / patterns:

Output artifacts

  • Spotify model map:
  • Action list:

Open questions

  • ...

Next step

Owner, date, success signal.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Spotify-Modell-Karte.
  • Reassess every six months. Immediately on reorganization. Archive previous version. Document explicit migration when switching model (for example to Team Topologies).
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet