View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Polarity MappingLASR (Lightweight Approach for Software Reviews)Architecture Decision Record
| Criterion |  Systems Thinking Polarity Mapping |  Architecture LASR (Lightweight Approach for Software Reviews) |  Architecture Architecture Decision Record |
|---|---|---|---|
Purposedifferent | Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-2 h | 3–4 h for initial assessment; preparation and deeper analysis additional | 15-45 min |
Participantsdifferent | 3-12 | 1 or a small team; particularly suitable for 3–4 people | 1-3 |
Formatdifferent | Workshop | Workshop + async | Async |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | 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 | ADR File, Decision Log, Rationale |
Tagsno overlap | Systems thinkingTradeoffsLeadership | ArchitectureQualityRiskAssessmentLean | ArchitectureRationaleDocumentationGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
