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 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
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
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.LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail.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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.
Complexitydifferent
HighMediumLowLow
Timedifferent
1 Tag bis mehrere Wochen3–4 h for initial assessment; preparation and deeper analysis additional1-4 h1-2 Tage
Participantsdifferent
4-101 or a small team; particularly suitable for 3–4 people1-51-4
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Problem Statement, Prototype, Test LearningsLean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checksContext Diagram, Container Diagram, Component DiagramArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
InnovationPrototypeResearch
ArchitectureQualityRiskAssessmentLean
ArchitectureCommunicationVisualization
ArchitectureDocumentationCommunication
Add more methods