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
Paper illustration for Risk Storming.
Architecture
Risk Storming
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
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)
Purposedifferent
Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.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.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.
Complexitydifferent
LowHighHighMedium
Timedifferent
60-90 min1 Tag bis mehrere Wochen4-5 Tage3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
4-124-105-81 or a small team; particularly suitable for 3–4 people
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Annotated Diagram, Prioritized Risk List, Action BacklogProblem Statement, Prototype, Test LearningsPrototype, Test Findings, Decision RationaleLean 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 checks
Tagsno overlap
RiskArchitectureWorkshopValidation
InnovationPrototypeResearch
Design sprintPrototypeValidationInnovation
ArchitectureQualityRiskAssessmentLean
Add more methods