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
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Purposedifferent
The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.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 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.When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.
Complexitydifferent
MediumLowLowLow
Timedifferent
60-120 min30 min Setup, dann laufend1-2 h20-40 min initial, dann laufend
Participantsdifferent
2-81-3 maintaining, briefing for everyone3-83-15
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
Communication Canvas, Stakeholder Messages, Architecture Communication PlanRAID Log, Status Report SourceInception Canvas, Risks, Goal List, Open QuestionsROAM Board, Owner List
Tagsno overlap
ArchitectureCommunicationStakeholdersCanvas
RiskTrackingStakeholdersGovernance
AlignmentArchitectureCanvas
RiskAgileTrackingAlignment
Add more methods