View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations Accountability Ladder | ![]() Systems Thinking Rich Picture | ![]() Agile 4Ls Retrospective | ![]() Operations Learning Review |
|---|---|---|---|---|
Purposedifferent | With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on. | A Rich Picture brings an unclear situation onto a shared drawing. It captures actors, tensions, information flows, and blind spots before the team jumps to solutions too early. | When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 20-45 min | 30-90 min | 45–75 min | 1-3 h |
Participantsdifferent | 1-8 | 2-10 | Team members involved | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Ownership Reflection, Action Commitment, Coaching Notes | Rich Picture, Problem Framing Notes | 4Ls Board, Learning Themes, Improvement Actions | Learning Review Notes, System Factors, Improvement Actions |
Tagsno overlap | ResponsibilityLeadershipTeam | Systems thinkingSoft systemsFramingVisualization | RetrospectiveLearningReflectionTeam | LearningRetrospectiveIncidentOperations |



