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 for Communication Plan
Delivery
Communication Plan
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Affinity Diagramming
UX Research
Affinity Diagramming
Empathy Mapping
UX Research
Empathy Mapping
Purposedifferent
When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost.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.When research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer.When a lot is assumed about a target group but little is seen jointly, empathy mapping makes knowledge and gaps directly comparable. The picture also shows which assumptions hold up and where evidence is missing.
Complexitysame
LowLowLowLow
Timedifferent
45-90 min1-2 h45–90 min30–60 min
Participantsdifferent
2-63-103-104-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Communication Plan, Channel Matrix, Message CadenceArchitecture Canvas, Goals, Constraints, Quality AttributesTheme clusters, Insight statements, Opportunity areasEmpathy Map, Assumptions List, Research Gaps
Tagsno overlap
CommunicationStakeholdersDeliveryPlanning
CanvasArchitectureAlignmentWorkshop
SynthesisQualitativeRoot cause
SynthesisQualitativeWorkshop
Add more methods