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
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.
Complexitydifferent
MediumLowLowLow
Timedifferent
1-3 h Setup, laufend30-60 min1-2 h30-60 min
Participantsdifferent
13-103-103-12
Formatdifferent
AsyncWorkshopWorkshopWorkshop
Outputdifferent
PARA Structure, Project Notes, Knowledge ArchiveEmotion Board, Themes, Action ItemsArchitecture Canvas, Goals, Constraints, Quality AttributesStart Stop Continue Board, Improvement Actions
Tagsno overlap
KnowledgeProductivityOrganization
RetrospectiveTeamReflection
CanvasArchitectureAlignmentWorkshop
RetrospectiveImprovementTeamReflection
Add more methods