View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Kano Model |  Architecture LASR (Lightweight Approach for Software Reviews) |  Operations Change Analysis |
|---|---|---|---|
Purposedifferent | 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. | LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-2 Tage | 3–4 h for initial assessment; preparation and deeper analysis additional | 45-120 min |
Participantsdifferent | 10-50 | 1 or a small team; particularly suitable for 3–4 people | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Lean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks | Change Matrix, Cause Hypotheses, Validation Questions, Action List |
Tagsno overlap | SatisfactionPrioritizationCustomer | ArchitectureQualityRiskAssessmentLean | ChangeRoot causeTroubleshootingComparison |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
