View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Teach-back |  Decision Making Pre-Mortem |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|
Purposedifferent | Teach-back checks whether an explanation actually got through to the other person. The method makes misunderstandings visible early and strengthens shared understanding in advisory and learning situations. | In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures. | 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 | Low | Low | Medium |
Timedifferent | 5-20 min | 20–45 min | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 2-8 | Small cross-functional group | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Understanding Check, Clarification Notes, Learning Gaps | Risk list, Mitigation plan, Assumption log | 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 |
Tagsno overlap | LearningUnderstandingCommunication | RiskDecisionFailurePlanning | ArchitectureQualityRiskAssessmentLean |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
