View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordExpectation MappingLASR (Lightweight Approach for Software Reviews)RAID Log
| Criterion | ![]() Architecture Architecture Decision Record | ![]() Facilitation Expectation Mapping | ![]() Architecture LASR (Lightweight Approach for Software Reviews) | ![]() Delivery RAID Log |
|---|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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. | 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 | Low | Low | Medium | Low |
Timedifferent | 15-45 min | 45-90 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 30 min Setup, dann laufend |
Participantsdifferent | 1-3 | 3-12 | 1 or a small team; particularly suitable for 3–4 people | 1-3 maintaining, briefing for everyone |
Formatdifferent | Async | Workshop | Workshop + async | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Expectation Map, Alignment Notes, Agreements | 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 | RAID Log, Status Report Source |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | AlignmentStakeholdersTeam | ArchitectureQualityRiskAssessmentLean | RiskTrackingStakeholdersGovernance |



