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
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
Purposedifferent
The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes.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.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 group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time.
Complexitydifferent
LowMediumLowMedium
Timedifferent
1-4 h30-90 min1-2 h1-3 h
Participantsdifferent
1-53-123-105-30
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Context Diagram, Container Diagram, Component DiagramPostmortem Doc, Action Items, TimelineArchitecture Canvas, Goals, Constraints, Quality AttributesConsensus Clusters, Theme Titles, Priority Areas
Tagsno overlap
ArchitectureCommunicationVisualization
Site Reliability EngineeringIncidentLearningReliability
CanvasArchitectureAlignmentWorkshop
FacilitationConsensusWorkshopAlignment
Add more methods