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
Four paper collections for projects, responsibilities, resources and archives.
Knowledge Modeling
PARA Method
Paper illustration of Five-Minute VC Check with its method-specific working model.
Business Strategy
5-Minuten VC-Check
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Purposedifferent
The PARA Method organizes knowledge into Projects, Areas, Resources, and Archives. It creates order when digital notes, files, and tasks no longer cleanly fit current work.The 5-Minute VC Check clarifies opportunities and strategic options at the earliest idea stage. It compares problem quality, customer willingness to pay, alternatives, differentiation, and market potential, and captures the result as a VC-check note, go/sharpen/park decision, and risk list.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.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.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
1-3 h Setup, laufend5-15 min60-120 min2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
11-52-8Designers, developers as users, and facilitation
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
PARA Structure, Project Notes, Knowledge ArchiveVC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation stepCommunication Canvas, Stakeholder Messages, Architecture Communication PlanPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
KnowledgeProductivityOrganization
StartupValidationCompetition
ArchitectureCommunicationStakeholdersCanvas
ArchitectureEngineeringFeedbackValidationTasks
Add more methods