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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Design Thinking as a learning loop: an observation notebook, a focused problem statement, different idea sketches, a cardboard prototype and user-test notes. Feedback leads to new understanding.
Innovation
Design Thinking
A paper-based illustration representing Design Sprint with its core stages and visible working result.
Innovation
Design Sprint
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.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.For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service.When the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess.
Complexitydifferent
LowMediumHighHigh
Timedifferent
1-4 h2–4 h review as a planning range; preparation and evaluation additional1 Tag bis mehrere Wochen4-5 Tage
Participantsdifferent
1-5Designers, developers as users, and facilitation4-105-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Context Diagram, Container Diagram, Component DiagramPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsProblem Statement, Prototype, Test LearningsPrototype, Test Findings, Decision Rationale
Tagsno overlap
ArchitectureCommunicationVisualization
ArchitectureEngineeringFeedbackValidationTasks
InnovationPrototypeResearch
Design sprintPrototypeValidationInnovation
Add more methods