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)
Paper illustration of Stakeholder Salience Model with its method-specific working model.
Facilitation
Stakeholder Salience Model
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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.When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.
Complexitydifferent
HighMediumMediumLow
Timedifferent
1 Tag bis mehrere Wochen3–4 h for initial assessment; preparation and deeper analysis additional60-90 min30 min Setup, dann laufend
Participantsdifferent
4-101 or a small team; particularly suitable for 3–4 people3-61-3 maintaining, briefing for everyone
Formatdifferent
WorkshopWorkshop + asyncWorkshopAsync
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 checksSalience Diagram, Strategy per ClassRAID Log, Status Report Source
Tagsno overlap
InnovationPrototypeResearch
ArchitectureQualityRiskAssessmentLean
StakeholdersFacilitationAlignmentGovernance
RiskTrackingStakeholdersGovernance
Add more methods