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
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 for Incident Timeline Analysis.
DevOps
Incident Timeline Analysis
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.For an incident with an unclear sequence, the method makes the timeline precisely visible. It separates perception, reaction, and delay so cause and effect become more clearly readable.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 min60-180 min2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
2-201-53-10Designers, 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 stepIncident Timeline, Evidence Log, Delay Analysis, Improvement ActionsPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
CollaborationEngineeringIncident
StartupValidationCompetition
IncidentTimelineSite Reliability Engineering
ArchitectureEngineeringFeedbackValidationTasks
Add more methods