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 MappingRed TeamingLASR (Lightweight Approach for Software Reviews)Assumption Surfacing
| Criterion | ![]() Systems Thinking Polarity Mapping | ![]() Decision Making Red Teaming | ![]() Architecture LASR (Lightweight Approach for Software Reviews) | ![]() Decision Making Assumption Surfacing |
|---|---|---|---|---|
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. | For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments. | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. |
Complexitydifferent | Medium | High | Medium | Low |
Timedifferent | 1-2 h | 1-4 h | 3–4 h for initial assessment; preparation and deeper analysis additional | 45-90 min |
Participantsdifferent | 3-12 | 3-8 | 1 or a small team; particularly suitable for 3–4 people | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | Challenge Findings, Risk Register, Mitigation Plan | 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 | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | Systems thinkingTradeoffsLeadership | RiskDecisionSensemaking | ArchitectureQualityRiskAssessmentLean | AssumptionsRiskDecisionDiscovery |



