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.

Selected:ChatOps5-Minuten VC-CheckAssumption MappingARID (Active Reviews for Intermediate Designs)
Criterion
ChatOps workspace showing the question, observations, and next decision.
DevOps
ChatOps
Paper illustration of Five-Minute VC Check with its method-specific working model.
Business Strategy
5-Minuten VC-Check
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Purposedifferent
For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together.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.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.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
Ongoing5-15 min45-60 min2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
2-201-52-8Designers, developers as users, and facilitation
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Chat Transcript, Action Log, AutomationsVC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation stepAssumption map, Test backlog, Risk rankingPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
CollaborationEngineeringIncident
StartupValidationCompetition
AssumptionsRiskExperimentsValidation
ArchitectureEngineeringFeedbackValidationTasks
Add more methods