methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Four paper collections for projects, responsibilities, resources and archives.
Knowledge Modeling
PARA Method
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration of Spotify Model Mapping with its method-specific working model.
Team Design
Spotify Model Mapping
Purposedifferent
The PARA Method organizes knowledge into Projects, Areas, Resources, and Archives. It creates order when digital notes, files, and tasks no longer cleanly fit current work.When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible.When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.When a team landscape has grown without clear grouping, it maps roles and relationships onto the Spotify model. It clarifies responsibility, interaction, and load between teams. The result is captured as a Spotify model map and action list.
Complexitydifferent
MediumLowLowMedium
Timedifferent
1-3 h Setup, laufend30-60 min45-90 min90-180 min
Participantsdifferent
13-103-125-15
Formatdifferent
AsyncWorkshopWorkshopWorkshop
Outputdifferent
PARA Structure, Project Notes, Knowledge ArchiveEmotion Board, Themes, Action ItemsExpectation Map, Alignment Notes, AgreementsSpotify Model Map, Action List
Tagsno overlap
KnowledgeProductivityOrganization
RetrospectiveTeamReflection
AlignmentStakeholdersTeam
TeamOrganizationAlignmentDiagnosis
Add more methods