View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Business Strategy Strategy Execution Loop | ![]() Knowledge Modeling Concept Mapping | ![]() Architecture Architecture Decision Record |
|---|---|---|---|
Purposedifferent | The Strategy Execution Loop helps avoid treating strategy as a one-off document. It makes visible how strategic decisions are turned into objectives, initiatives, operational work, measurement, and learning. | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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 | High | Medium | Low |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 1-2 h | 15-45 min |
Participantsdifferent | 5-12 | 1-8 | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Concept Map, Relationship Labels, Knowledge Gaps | ADR File, Decision Log, Rationale |
Tagsno overlap | ExecutionCadenceLearningGovernance | KnowledgeConceptsMappingSensemaking | ArchitectureRationaleDocumentationGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






