View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Contradiction AnalysisMorphological AnalysisLASR (Lightweight Approach for Software Reviews)TRIZ
| Criterion | ![]() Innovation Contradiction Analysis | ![]() Innovation Morphological Analysis | ![]() Architecture LASR (Lightweight Approach for Software Reviews) | ![]() Innovation TRIZ |
|---|---|---|---|---|
Purposedifferent | When a system should improve while another measure suffers as a result, the method makes the underlying conflict precisely formulable. It separates the desired effect from its side effect. This makes solutions possible that address the contradiction deliberately instead of half-heartedly. | For a search for solutions with many degrees of freedom, a grid emerges for systematic combinations. The method separates features, variants, and exclusion criteria, so the space gets explored deliberately. | 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 technical contradictions or trade-offs, the method looks for solutions that resolve opposing requirements at the same time. It translates limits into an explicit picture of conflict that becomes workable. This produces not just compromises but more elegant principles. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 60-120 min | 1-3 h | 3–4 h for initial assessment; preparation and deeper analysis additional | 1-4 h |
Participantsdifferent | 2-8 | 2-8 | 1 or a small team; particularly suitable for 3–4 people | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Contradiction Statement, Abstraction Notes, Solution Principles, Concept Ideas | Morphological Box, Concept Combinations, Idea Shortlist | 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 | Contradiction Statement, Inventive Principles, Solution Concepts |
Tagsno overlap | ContradictionsInnovationProblem solving | IdeationInnovationCreativity | ArchitectureQualityRiskAssessmentLean | InnovationProblem solvingContradictionsCreativity |



