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
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Purposedifferent
When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions.In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving.After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.
Complexitydifferent
LowLowLowMedium
Timedifferent
30-120 min45-90 min20-45 min1-3 h
Participantsdifferent
2-63-123-123-10
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Observation Notes, Improvement IdeasForce Field Map, Change Levers, Risk NotesLessons learned, Action items, Event summaryProcess Map, Handoff List, Improvement Backlog
Tagsno overlap
LeanObservationProcessOperations
ChangeDecisionStrategy
LearningOperationsImprovement
ProcessOperationsImprovement
Add more methods