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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration for Teach-back.
Knowledge Modeling
Teach-back
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Purposedifferent
ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.Teach-back checks whether an explanation actually got through to the other person. The method makes misunderstandings visible early and strengthens shared understanding in advisory and learning situations.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.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.
Complexitydifferent
MediumLowLowLow
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional5-20 min15-45 min1-4 h
Participantsdifferent
Designers, developers as users, and facilitation2-81-31-5
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsUnderstanding Check, Clarification Notes, Learning GapsADR File, Decision Log, RationaleContext Diagram, Container Diagram, Component Diagram
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
LearningUnderstandingCommunication
ArchitectureRationaleDocumentationGovernance
ArchitectureCommunicationVisualization
Add more methods