View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Knowledge Modeling PARA Method | ![]() Business Strategy 5-Minuten VC-Check | ![]() Operations Family Tree Analysis | ![]() Operations MORT Analysis |
|---|---|---|---|---|
Purposedifferent | The PARA Method organizes knowledge into Projects, Areas, Resources, and Archives. It creates order when digital notes, files, and tasks no longer cleanly fit current work. | 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 a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring. | For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | 1-3 h Setup, laufend | 5-15 min | 2-4 h | Mehrere Tage bis Wochen |
Participantsdifferent | 1 | 1-5 | 2-6 | 2-6 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | VC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation step | Family Tree Diagram, Pattern Notes, Systemic Measures | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | KnowledgeProductivityOrganization | StartupValidationCompetition | Root causePatternsIncidentSystemic | Root causeSafetySystemicIncident |



