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 | ![]() Operations Ivy Lee Method | ![]() Product Discovery Jobs to Be Done | ![]() Product Discovery Kano Model |
|---|---|---|---|---|
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. | 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. | When switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought. | When features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-3 h Setup, laufend | 5-10 min daily | 1-3 Wochen | 1-2 Tage |
Participantsdifferent | 1 | 1 | 5-12 Interviews | 10-50 |
Formatdifferent | Async | Async | Workshop + async | Workshop + async |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | Daily Priority List, Completion Notes | Job Stories, Outcome Statements, Opportunity List | Kano Matrix, Feature Classes, Priority Themes |
Tagsno overlap | KnowledgeProductivityOrganization | PrioritizationProductivityExecution | CustomerOutcomesNeeds | SatisfactionPrioritizationCustomer |



