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 for Pareto Analysis
Decision Making
Pareto Analysis
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration for Eat the Frog
Operations
Eat the Frog
Paper illustration for Ivy Lee Method
Operations
Ivy Lee Method
Purposedifferent
In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle.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.The method protects energy and attention for the task that creates the largest progress and is often postponed.With a restless workday full of too many open items, the method creates radical simplicity. It directs attention to a short sequence instead of a broad, still-open field.
Complexitydifferent
LowMediumLowLow
Timedifferent
30-60 min2–4 h review as a planning range; preparation and evaluation additional15-90 min daily5-10 min daily
Participantsdifferent
1-6Designers, developers as users, and facilitation11
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncAsync
Outputdifferent
Pareto Chart, Top Causes, Focus ListPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsPriority Task, Completion Note, Daily FocusDaily Priority List, Completion Notes
Tagsno overlap
PrioritizationQualityFocusRoot cause
ArchitectureEngineeringFeedbackValidationTasks
PrioritizationProductivityFocusExecution
PrioritizationProductivityExecution
Add more methods