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 Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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 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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.
Complexitydifferent
MediumLowLow
Timedifferent
1-3 h Setup, laufend45-90 min30 min Setup, dann laufend
Participantsdifferent
13-121-3 maintaining, briefing for everyone
Formatdifferent
AsyncWorkshopAsync
Outputdifferent
PARA Structure, Project Notes, Knowledge ArchiveExpectation Map, Alignment Notes, AgreementsRAID Log, Status Report Source
Tagsno overlap
KnowledgeProductivityOrganization
AlignmentStakeholdersTeam
RiskTrackingStakeholdersGovernance
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of Spotify Model Mapping with its method-specific working model.
Team Design
Spotify Model Mapping
Paper illustration of Stakeholder Salience Model with its method-specific working model.
Facilitation
Stakeholder Salience Model
Paper illustration of Team Topologies Interaction Modes with its method-specific working model.
Team Design
Team Topologies Interaction Modes