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 Flywheel.
Growth
Flywheel
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Purposedifferent
Growth often breaks down where a reinforcing mechanism builds up too much friction. A Flywheel shows the cycle of value, repetition, and reinforcement meant to sustain growth.ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.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
MediumMediumLowMedium
Timedifferent
60-120 min2–4 h review as a planning range; preparation and evaluation additional1-4 h60-120 min
Participantsdifferent
3-8Designers, developers as users, and facilitation1-52-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Flywheel Map, Friction Points, Growth Levers, Experiment BacklogPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsContext Diagram, Container Diagram, Component DiagramCommunication Canvas, Stakeholder Messages, Architecture Communication Plan
Tagsno overlap
GrowthRetentionConversion
ArchitectureEngineeringFeedbackValidationTasks
ArchitectureCommunicationVisualization
ArchitectureCommunicationStakeholdersCanvas
Add more methods