methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Purposedifferent
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.For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.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
LowHighMediumMedium
Timedifferent
30 min Setup, dann laufend1-4 h1-3 Tage60-120 min
Participantsdifferent
1-3 maintaining, briefing for everyone3-81-42-8
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
RAID Log, Status Report SourceChallenge Findings, Risk Register, Mitigation PlanArchitecture Views, Cross-view Notes, RationaleCommunication Canvas, Stakeholder Messages, Architecture Communication Plan
Tagsno overlap
RiskTrackingStakeholdersGovernance
RiskDecisionSensemaking
DocumentationStakeholdersArchitecture
ArchitectureCommunicationStakeholdersCanvas
Add more methods