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.
Innovation Analysis method
Contradiction Analysis
Contradiction analysis makes goal conflicts explicit, abstracts them into solution principles, and condenses testable concepts.
Contradiction analysis moves from an observed conflict to structural patterns and principles that can decouple both sides. It opens solution paths beyond immediate compromise.
Which parameter should improve, which one worsens as a result, and how can the underlying physical demand be separated without compromise?
- Participants
- 2-8
- Time
- 90–180 minutes per clear contradiction; concept experiments extra.
The steps form one complete method run.

Function
Function model
Bound system, main function, operating zone, and concrete useful/harmful effects.
Conflict
Technical conflict
Phrase the technical contradiction as one parameter improving while another worsens, in both directions.
Opposites
Physical conflict
Phrase the physical contradiction as opposite requirements on the same characteristic in the same operating zone.
Separate
Solution concepts
Use the Ideal Final Result and available resources; separate in time, space, condition, or system level.
Test
Concept finding
Test the best concept's critical assumption with measure, stop rule, and rollback.
Add new evidence at review and version decisions with the prior state.
A good fit when
Wenn ein System besser werden soll und dabei eine andere Kenngröße leidet, macht die Methode den Zielkonflikt präzise formulierbar. Sie trennt die gewünschte Wirkung von ihrer Nebenwirkung. Dadurch werden Lösungen möglich, die den Widerspruch gezielt statt halbherzig behandeln.
Ideal for
- Technical target conflicts
- Product innovation
- Stalled optimization problems
Not good for
- Simple root-cause analysis
- Problems without a target conflict
- Pure prioritization
Outputs

Concept finding
TRIZ contradiction model with technical and physical contradiction, Ideal Final Result, resources, separation principle, concepts, and test.
Contradiction Analysis · working structure
Fictional example
Fictional values show the actual method fields.
| Model part | Statement | Evidence/assumption | Resource | Resolution logic | Test |
|---|---|---|---|---|---|
| Technical conflictAdd evidence and rationale. | More buffer improves emergency access but reduces regular utilisation; less reverses both. | Four emergencies/month; 10% buffer often unused | Release rule and booking system | Improving versus worsening parameter | Measure both effects in pilot |
| Physical conflictAdd evidence and rationale. | Capacity must be reserved during an emergency and available otherwise. | Same slot capacity, conditional use | Time to slot; emergency signal | Separate by condition and time | Simulate release 60 min before |
| Ideal Final ResultAdd evidence and rationale. | Capacity reserves itself when needed and remains usable otherwise. | Automatic emergency signal is an assumption | Existing slot status | Function without permanent reserve | Test false alarms and missed emergency |
| ConceptAdd evidence and rationale. | Hold 10% until 60 min before, then release automatically. | Booking can represent status change | Scheduler and SMS | Conditional/time separation | Four Saturdays; p80 ≤15 min |
1. Statement
- Technical conflict
- More buffer improves emergency access but reduces regular utilisation; less reverses both.
- Physical conflict
- Capacity must be reserved during an emergency and available otherwise.
- Ideal Final Result
- Capacity reserves itself when needed and remains usable otherwise.
- Concept
- Hold 10% until 60 min before, then release automatically.
2. Evidence/assumption
- Technical conflict
- Four emergencies/month; 10% buffer often unused
- Physical conflict
- Same slot capacity, conditional use
- Ideal Final Result
- Automatic emergency signal is an assumption
- Concept
- Booking can represent status change
3. Resource
- Technical conflict
- Release rule and booking system
- Physical conflict
- Time to slot; emergency signal
- Ideal Final Result
- Existing slot status
- Concept
- Scheduler and SMS
4. Resolution logic
- Technical conflict
- Improving versus worsening parameter
- Physical conflict
- Separate by condition and time
- Ideal Final Result
- Function without permanent reserve
- Concept
- Conditional/time separation
5. Test
- Technical conflict
- Measure both effects in pilot
- Physical conflict
- Simulate release 60 min before
- Ideal Final Result
- Test false alarms and missed emergency
- Concept
- Four Saturdays; p80 ≤15 min
All values are fictional.
First step
Describe system, main function, operating zone, and observed useful and harmful effects with evidence.
Deep dive
The analysis zooms from the observed conflict to general structural patterns and then looks for principles that decouple both sides. Instead of building compromises right away, it checks whether the contradiction can be reframed technically, organizationally, or linguistically. That is exactly where the leverage for unusually strong solutions lies.
Contradiction Analysis helps when a problem feels like an unavoidable trade-off: more security but longer onboarding, or more speed but less quality. Instead of choosing a middle ground too early, the method precisely states which property should improve and which one might worsen. That tension is then abstracted and explored with principles, analogies, or TRIZ patterns. The work shifts from simple optimization to new solution directions that take both sides of the conflict seriously.
State the contradiction concretely and check whether both sides are truly necessary. Use examples, analogies, or TRIZ principles as thinking stimuli, not as a mechanical answer machine. Collect several solution ideas before judging feasibility.
The method guide walks execution through 5 phases, timing, 5 pitfalls, and clear stop criteria.
Open method guideYour perspective
Does this method help with your work?
Your feedback helps shape the next improvements to methodatlas.
Sources and topics
Contradiction Analysis: WorksheetSet subject, evidence, roles, flow, and review.markdown
contradiction-analysis-working-template.md
Set subject, evidence, roles, flow, and review.
Contradiction Analysis: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Complete run Time: 90–180 minutes per clear contradiction; concept experiments extra.
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: System function and boundary, useful/harmful effects, technical parameters, resource map, TRIZ principles, and experiment log
- Roles: Problem owner · system/domain experts · TRIZ facilitator · experiment owner
- Advance information: Describe system, main function, operating zone, and observed useful and harmful effects with evidence.
- Overall time needed: 90–180 minutes per clear contradiction; concept experiments extra.
- Setup: Prepare a workspace with Function · Conflict · Opposites · Separate · Test; separate example from live data.
Prepare for the work steps
Function: Function model
- Describe system, main function, operating zone, and observed useful and harmful effects with evidence.
- System function and boundary, useful/harmful effects, technical parameters, resource map, TRIZ principles, and experiment log
Conflict: Technical conflict
- Function model
Opposites: Physical conflict
- Technical conflict
Separate: Solution concepts
- Physical conflict
Test: Concept finding
- Solution concepts
Contradiction Analysis · working structure
| Model part | Statement | Evidence/assumption | Resource | Resolution logic | Test |
|---|---|---|---|---|---|
| Technical conflict | |||||
| Physical conflict | |||||
| Ideal Final Result | |||||
| Concept |
- Technical conflict: Add evidence and rationale.
- Physical conflict: Add evidence and rationale.
- Ideal Final Result: Add evidence and rationale.
- Concept: Add evidence and rationale.
The blank worksheet contains prompts only.
Reference · original teaching example
Function: Function model
Expected artifact: Function model
Bound system, main function, operating zone, and concrete useful/harmful effects.
Entry:
...
- Are effects observable and assigned to an element or parameter?
Conflict: Technical conflict
Expected artifact: Technical conflict
Phrase the technical contradiction as one parameter improving while another worsens, in both directions.
Entry:
...
- Are improvement and deterioration measurable and causally coupled?
Opposites: Physical conflict
Expected artifact: Physical conflict
Phrase the physical contradiction as opposite requirements on the same characteristic in the same operating zone.
Entry:
...
- Does one characteristic truly require two opposite states?
Separate: Solution concepts
Expected artifact: Solution concepts
Use the Ideal Final Result and available resources; separate in time, space, condition, or system level.
Entry:
...
- Does each concept satisfy both requirements under their conditions?
Test: Concept finding
Expected artifact: Concept finding
Test the best concept's critical assumption with measure, stop rule, and rollback.
Entry:
...
- Does the experiment measure both sides of the original contradiction?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/contradiction-analysis/run-sheet
Alternatives and neighbors
Fitting alternatives with decision guidance, followed by other related methods.

Instead of Contradiction Analysis, choose SCAMPER when you want to deliberately vary an existing idea using fixed change questions.

Instead of Contradiction Analysis, choose Reverse Brainstorming when you want to deliberately generate opposite or harmful ideas to expose risks.

Clarifies ideas, open questions, and testable next steps by framing the contradiction, identifying improving and worsening factors, and checking feasibility.

Alternating divergent and convergent phases keep problem framing and solution design visibly separated for product work.

Expands a core question into topic fields, filters out patterns, and condenses interesting paths into a shortlist.

Brings problem space, prototype, and test findings together in a few days, enabling a well-founded decision.
Constraints and origin
Profile
- Method form
- Analysis method
- Participants
- 2-8
- Time
- 60-120 min
- Maturity
- Established
- Origin
- Genrich Altshuller

