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 ALPEN Method
Operations
ALPEN Method
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Purposedifferent
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.After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement.The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.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.
Complexitysame
LowLowLowLow
Timedifferent
10-20 min daily20-45 min1-2 h1-2 h
Participantsdifferent
13-123-83-10
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Daily Plan, Time Estimates, Review NotesLessons learned, Action items, Event summaryInception Canvas, Risks, Goal List, Open QuestionsArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
PlanningTime managementProductivityOperations
LearningOperationsImprovement
AlignmentArchitectureCanvas
CanvasArchitectureAlignmentWorkshop
Add more methods