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 Design Sprint with its core stages and visible working result.
Innovation
Design Sprint
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
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
Purposedifferent
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.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.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.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.
Complexitydifferent
HighMediumLowHigh
Timedifferent
4-5 Tage2–4 h review as a planning range; preparation and evaluation additional1-4 h1 Tag bis mehrere Wochen
Participantsdifferent
5-8Designers, developers as users, and facilitation1-54-10
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Prototype, Test Findings, Decision RationalePrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsContext Diagram, Container Diagram, Component DiagramProblem Statement, Prototype, Test Learnings
Tagsno overlap
Design sprintPrototypeValidationInnovation
ArchitectureEngineeringFeedbackValidationTasks
ArchitectureCommunicationVisualization
InnovationPrototypeResearch
Add more methods