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 Five-Minute VC Check with its method-specific working model.
Business Strategy
5-Minuten VC-Check
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Purposedifferent
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 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.When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.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
LowLowHighMedium
Timedifferent
5-15 min1-4 h1-4 Wochen2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
1-51-51-6Designers, developers as users, and facilitation
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
VC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation stepContext Diagram, Container Diagram, Component DiagramExperiment results, Decision log, Learning summaryPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
StartupValidationCompetition
ArchitectureCommunicationVisualization
ExperimentsGrowthAnalyticsValidation
ArchitectureEngineeringFeedbackValidationTasks
Add more methods