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 notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration for ALPEN Method
Operations
ALPEN Method
Purposedifferent
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.After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time.
Complexitydifferent
MediumMediumLowLow
Timedifferent
1-2 h Setup, laufend30-90 min1-2 Tage10-20 min daily
Participantsdifferent
13-121-41
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Action Lists, Project List, Review RoutinePostmortem Doc, Action Items, TimelineArchitecture Document, Context View, Runtime View, Deployment ViewDaily Plan, Time Estimates, Review Notes
Tagsno overlap
ProductivityPlanningTasksExecution
Site Reliability EngineeringIncidentLearningReliability
ArchitectureDocumentationCommunication
PlanningTime managementProductivityOperations
Add more methods