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 | ![]() Delivery RAID Log | ![]() Architecture Software Architecture Canvas | ![]() Architecture Architecture Inception Canvas |
|---|---|---|---|---|
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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 30 min Setup, dann laufend | 1-2 h | 1-2 h |
Participantsdifferent | 3-12 | 1-3 maintaining, briefing for everyone | 3-10 | 3-8 |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Knowledge Map, Critical Knowledge Areas, Transfer Plan | RAID Log, Status Report Source | Architecture Canvas, Goals, Constraints, Quality Attributes | Inception Canvas, Risks, Goal List, Open Questions |
Tagsno overlap | KnowledgeMappingRisk | RiskTrackingStakeholdersGovernance | CanvasArchitectureAlignmentWorkshop | AlignmentArchitectureCanvas |



