Method guideTeam Design

Spotify Model Mapping

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityMedium

Time90-180 min

Participants5-15

FormatWorkshop

MaturityEstablished

Plan Spotify Model Mapping

Prerequisite

What needs to be finished first

Complete firstBounded subject

The scope and purpose of Spotify Model Mapping are stated as a concrete question.

Without scope, organisation mapping becomes arbitrary.

Complete firstAccess to relevant perspectives

Product and value flows, current teams and communities, decision and dependency data and domain decision makers are available.

Without these perspectives, central claims in organisation mapping remain unsupported.

Preparation

What needs to be ready before start

Materials

Product and value flows, current teams and communities, decision and dependency data, shared workspace, source links, and decision log.

People / roles

Leadership · team representatives · Product · People/Organisation

Pre-read

Collect Product and value flows, current teams and communities, decision and dependency data in advance and mark open assumptions.

Time needed

2 × 90 minutes

Setup

Prepare map Spotify terms as hypotheses onto local product flows, communities, and leadership needs visibly and calibrate assessment terms before starting.

Core question

The one question this method answers

Which local structures do we need for autonomy, alignment, and craft exchange?

Flow

Phases with goal, actions, output and pitfall

The published Spotify model describes a historical context, not a copyable framework. Mapping translates terms into local purposes, decision rights, and risks and marks deviations.

organisation mapping

Fictional worked example

map Spotify terms as hypotheses onto local product flows, communities, and leadership needs as a precise working structure with a fictional example.

Local unit

Team/community · purpose · product flow

Billing product team; long-lived product flow.

Spotify analogy

Squad · tribe · chapter · guild · none

Partly squad; no tribe.

Mandate

Decision right · leadership · participation

Security chapter with people responsibility.

Risk and test

Misapplication · measure · review

Review hand-offs per feature after eight weeks.

Spotify Engineering Culture, part 1

1
Establish context
Establish context
Goal
Produce context boundaries so the core question “Which local structures do we need for autonomy, alignment, and craft exchange?” can be answered with stronger support.
Inputs for this step
- Product and value flows
- current teams and communities
- decision and dependency data
Actions
- Make the historical Spotify context and local differences explicit.
- Record source, rationale, and open uncertainty directly in context boundaries.
Output
context boundaries
context boundaries · source · uncertainty · next decision
Quality check
Are terms marked as analogies?
Pitfall
New Spotify labels hide old dependencies and unclear decision rights. Start from product flow, decision rights, and actual responsibility and remove unnecessary labels.
Timing: 10–20 minutes
2
Map product flow
Map product flow
Goal
Produce flow map so the core question “Which local structures do we need for autonomy, alignment, and craft exchange?” can be answered with stronger support.
Inputs for this step
- context boundaries
- current teams and communities
- decision and dependency data
Actions
- Map long-lived teams to products and value streams.
- Record source, rationale, and open uncertainty directly in flow map.
Output
flow map
flow map · source · uncertainty · next decision
Quality check
Does the boundary minimise hand-offs?
Pitfall
New Spotify labels hide old dependencies and unclear decision rights. Start from product flow, decision rights, and actual responsibility and remove unnecessary labels.
Timing: 10–20 minutes
3
Map communities
Map communities
Goal
Produce community map so the core question “Which local structures do we need for autonomy, alignment, and craft exchange?” can be answered with stronger support.
Inputs for this step
- flow map
- current teams and communities
- decision and dependency data
Actions
- Clarify chapter and guild needs, mandate, and participation.
- Record source, rationale, and open uncertainty directly in community map.
Output
community map
community map · source · uncertainty · next decision
Quality check
Are people responsibility and voluntary exchange distinct?
Pitfall
New Spotify labels hide old dependencies and unclear decision rights. Start from product flow, decision rights, and actual responsibility and remove unnecessary labels.
Timing: 10–20 minutes
4
Test hypothesis
Test hypothesis
Goal
Produce change hypothesis so the core question “Which local structures do we need for autonomy, alignment, and craft exchange?” can be answered with stronger support.
Inputs for this step
- community map
- current teams and communities
- decision and dependency data
Actions
- Test the mapping against real decisions and dependencies.
- Record source, rationale, and open uncertainty directly in change hypothesis.
Output
change hypothesis
change hypothesis · source · uncertainty · next decision
Quality check
Is a measurable flow improvement named?
Pitfall
New Spotify labels hide old dependencies and unclear decision rights. Start from product flow, decision rights, and actual responsibility and remove unnecessary labels.
Timing: 10–20 minutes

Artifact

What comes out at the end

Sketch: what the artifact looks like

Spotify Model Mapping · Organisationsbegriffe sichtbar prüfenSquads, Tribes, Chapters und Guilds als Karte zeichnen, um reale Struktur, Reibung und Lücken diskutierbar zu machen

Form

Versioned organisation mapping with date, sources, owners, and next review.

Versioning / ownership

Retain date, source, assumption state, and decision for every version of organisation mapping.

Tool alternatives

organisation mapping as board or document
Source and evidence register
Decision and action log

spotify-model-mapping-working-template.md

Plan Spotify Model Mapping around its domain steps and the concrete decision question.

Spotify Model Mapping: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Full initiative Time: 2 × 90 minutes

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

Materials: Product and value flows, current teams and communities, decision and dependency data, shared workspace, source links, and decision log.
Roles: Leadership · team representatives · Product · People/Organisation
Advance information: Collect Product and value flows, current teams and communities, decision and dependency data in advance and mark open assumptions.
Overall time needed: 2 × 90 minutes
Setup: Prepare map Spotify terms as hypotheses onto local product flows, communities, and leadership needs visibly and calibrate assessment terms before starting.

Prepare for the work steps

Establish context: Establish context

Product and value flows
current teams and communities
decision and dependency data

Map product flow: Map product flow

context boundaries
current teams and communities
decision and dependency data

Map communities: Map communities

flow map
current teams and communities
decision and dependency data

Test hypothesis: Test hypothesis

community map
current teams and communities
decision and dependency data

organisation mapping

Local unit

Team/community · purpose · product flow

...

Spotify analogy

Squad · tribe · chapter · guild · none

...

Mandate

Decision right · leadership · participation

...

Risk and test

Misapplication · measure · review

...

Spotify Engineering Culture, part 1

Establish context: Establish context

Expected artifact: context boundaries

context boundaries · source · uncertainty · next decision

Entry:

...

Are terms marked as analogies?

Map product flow: Map product flow

Expected artifact: flow map

flow map · source · uncertainty · next decision

Entry:

...

Does the boundary minimise hand-offs?

Map communities: Map communities

Expected artifact: community map

community map · source · uncertainty · next decision

Entry:

...

Are people responsibility and voluntary exchange distinct?

Test hypothesis: Test hypothesis

Expected artifact: change hypothesis

change hypothesis · source · uncertainty · next decision

Entry:

...

Is a measurable flow improvement named?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/spotify-model-mapping/run-sheet

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

spotify-model-mapping-beispiel.md

Concrete filled scenario, fictional example

Local unit: long-lived billing product team, partly analogous to a squad. The tribe label is omitted because two products do not share a value stream. Chapter: professional line for security engineering with explicit people responsibility. Guild: voluntary accessibility community without decision authority.

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

Establish contextNew Spotify labels hide old dependencies and unclear decision rights.View in phase
Map product flowNew Spotify labels hide old dependencies and unclear decision rights.View in phase
Map communitiesNew Spotify labels hide old dependencies and unclear decision rights.View in phase
Test hypothesisNew Spotify labels hide old dependencies and unclear decision rights.View in phase