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
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Paper illustration for Weekly Review.
Operations
Weekly Review
Purposedifferent
Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic.With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory.In a week with many open loops, the method creates distance from operational noise. It organizes commitments, calendar, and projects so the next week becomes workable.
Complexitydifferent
MediumHighMediumLow
Timedifferent
1-3 hHalber Tag1-2 h Setup, laufend30-60 min
Participantsdifferent
3-125-2011
Formatdifferent
WorkshopWorkshopAsyncAsync
Outputdifferent
Knowledge Map, Critical Knowledge Areas, Transfer PlanSimulation Notes, Gaps List, Updated RunbooksAction Lists, Project List, Review RoutineUpdated Task System, Weekly Focus, Next Actions
Tagsno overlap
KnowledgeMappingRisk
ResilienceOperationsIncident
ProductivityPlanningTasksExecution
ProductivityExecutionPlanning
Add more methods