View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Systems Thinking Polarity Mapping | ![]() Operations Process Mapping | ![]() Architecture Architecture Decision Record | ![]() Operations Gemba Walk |
|---|---|---|---|---|
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. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | 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 there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-2 h | 1-3 h | 15-45 min | 30-120 min |
Participantsdifferent | 3-12 | 3-10 | 1-3 | 2-6 |
Formatdifferent | Workshop | Workshop | Async | Workshop |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | Process Map, Handoff List, Improvement Backlog | ADR File, Decision Log, Rationale | Observation Notes, Improvement Ideas |
Tagsno overlap | Systems thinkingTradeoffsLeadership | ProcessOperationsImprovement | ArchitectureRationaleDocumentationGovernance | LeanObservationProcessOperations |



