View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Knowledge Mapping |  Decision Making Constraint Analysis |  Architecture arc42 |  Decision Making Pre-Mortem |
|---|---|---|---|---|
Purposedifferent | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 30-90 min | 1-2 Tage | 20–45 min |
Participantsdifferent | 3-12 | 2-8 | 1-4 | Small cross-functional group |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Architecture Document, Context View, Runtime View, Deployment View | Risk list, Mitigation plan, Assumption log |
Tagsno overlap | KnowledgeMappingRisk | ConstraintsDecisionPlanningOptions | ArchitectureDocumentationCommunication | RiskDecisionFailurePlanning |