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
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration of Five-Minute VC Check with its method-specific working model.
Business Strategy
5-Minuten VC-Check
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic.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.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.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.
Complexitydifferent
MediumLowMediumHigh
Timedifferent
2-6 h5-15 min2–4 h review as a planning range; preparation and evaluation additional1-4 Wochen
Participantsdifferent
2-81-5Designers, developers as users, and facilitation1-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsVC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation stepPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsExperiment results, Decision log, Learning summary
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
StartupValidationCompetition
ArchitectureEngineeringFeedbackValidationTasks
ExperimentsGrowthAnalyticsValidation
Add more methods