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 of Team Cognitive Load Assessment with its method-specific working model.
Team Design
Team Cognitive Load Assessment
Paper illustration for CATWOE Analysis.
Systems Thinking
CATWOE Analysis
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 Business Model Stress Test with its method-specific working model.
Business Strategy
Business Model Stress Test
Purposedifferent
When a team juggles too many domains, systems, or handoffs, it measures mental overload as an organizational problem. It clarifies responsibility, interaction, and load between teams. The result is captured as a cognitive-load profile and action list.CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way.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.A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario.
Complexitydifferent
MediumMediumMediumHigh
Timedifferent
60-90 min45-90 min3–4 h for initial assessment; preparation and deeper analysis additionalHalf day
Participantsdifferent
3-123-81 or a small team; particularly suitable for 3–4 people3-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Cognitive Load Profile, Action ListCATWOE Canvas, Root Definition, Stakeholder Perspectives, ConstraintsLean 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 checksStress Test Report, Action Plan per Scenario
Tagsno overlap
TeamComplexityImprovementDiagnosis
Systems thinkingFramingStakeholders
ArchitectureQualityRiskAssessmentLean
StrategyBusiness modelRiskDiagnosis
Add more methods