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
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)
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
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Purposedifferent
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.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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.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
MediumHighMediumLow
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional1 Tag bis mehrere Wochen60-120 min1-4 h
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people4-102-81-5
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Lean 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 checksProblem Statement, Prototype, Test LearningsCommunication Canvas, Stakeholder Messages, Architecture Communication PlanContext Diagram, Container Diagram, Component Diagram
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
InnovationPrototypeResearch
ArchitectureCommunicationStakeholdersCanvas
ArchitectureCommunicationVisualization
Add more methods