View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Architecture Risk Storming | ![]() Systems Thinking Leverage Points | ![]() Decision Making Force Field Analysis | ![]() Business Strategy Business Model Stress Test |
|---|---|---|---|---|
Purposedifferent | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy. | 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. | A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario. |
Complexitydifferent | Low | High | Low | High |
Timedifferent | 60-90 min | Half day | 45-90 min | Half day |
Participantsdifferent | 4-12 | 3-12 | 3-12 | 3-8 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Leverage Map, Action Strategy | Force Field Map, Change Levers, Risk Notes | Stress Test Report, Action Plan per Scenario |
Tagsno overlap | RiskArchitectureWorkshopValidation | Systems thinkingChangeStrategy | ChangeDecisionStrategy | StrategyBusiness modelRiskDiagnosis |



