View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:RAID LogSoft Systems MethodologyLASR (Lightweight Approach for Software Reviews)CATWOE Analysis
| Criterion | ![]() Delivery RAID Log | ![]() Systems Thinking Soft Systems Methodology | ![]() Architecture LASR (Lightweight Approach for Software Reviews) | ![]() Systems Thinking CATWOE Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | Soft Systems Methodology helps explore unclear or politically charged problems systematically. Instead of forcing a quick answer, the method builds a shared understanding of perspectives and room for action. | 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. | 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. |
Complexitydifferent | Low | High | Medium | Medium |
Timedifferent | 30 min Setup, dann laufend | 0.5-3 Tage | 3–4 h for initial assessment; preparation and deeper analysis additional | 45-90 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 5-15 | 1 or a small team; particularly suitable for 3–4 people | 3-8 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Rich Picture, Root Definitions, Conceptual Models, Change Agenda | 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 checks | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints |
Tagsno overlap | RiskTrackingStakeholdersGovernance | Soft systemsComplexitySensemakingSystems thinking | ArchitectureQualityRiskAssessmentLean | Systems thinkingFramingStakeholders |



