View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations Time Blocking | ![]() Architecture Architecture Decision Record | ![]() Architecture C4 Model | ![]() Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | With a calendar that grows on request, the method makes available time explicit again. It combines appointments, focus work, and buffer into a more realistic day structure. | 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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 15-30 min Planung, laufend | 15-45 min | 1-4 h | 60-120 min |
Participantsdifferent | 1 | 1-3 | 1-5 | 2-8 |
Formatdifferent | Async | Async | Workshop + async | Workshop + async |
Outputdifferent | Blocked Calendar, Capacity View, Focus Plan | ADR File, Decision Log, Rationale | Context Diagram, Container Diagram, Component Diagram | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | PlanningTime managementFocus | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationVisualization | ArchitectureCommunicationStakeholdersCanvas |



