TRIZ Contradiction Matrix 40 Principles Lookup
Look up one of the 40 TRIZ inventive principles and return concise contradiction-resolution guidance.
Description
TRIZ inventive principles suggest ways to address design contradictions.
TRIZ inventive principles suggest ways to address design contradictions. Selecting a principle by number is different from looking up a pair of engineering contradictions in a matrix.1
The returned values include Application guidance, Principle name, Principle number. The How section below explains the calculation, input rules and interpretation.
When to use TRIZ Contradiction Matrix 40 Principles Lookup
Use TRIZ Contradiction Matrix 40 Principles Lookup when you need to evaluate the supplied records under the calculation and evidence rules below. This is a concise teaching reference. Verify original publications, context and applicable editions before relying on it; it is not a complete framework or an authoritative evaluation.
Define the question, evidence and scenario assumptions first. Supply the chosen score scales, time horizons or reference selection explicitly. Interpret generated text as a discussion template and screen labels as the stated rules.
How to use TRIZ Contradiction Matrix 40 Principles Lookup and understand its results
- Define the question, evidence and scenario assumptions first. Supply the chosen score scales, time horizons or reference selection explicitly. Interpret generated text as a discussion template and screen labels as the stated rules.
- Enter principleNumber using the field table and calculation rules, then run the tool.
- Read applicationGuidance, principleName, principleNumber. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| principleNumber | Principle number | integer; minimum: 1; maximum: 40 | Required |
Choose the exact enum value or supported integer in the input table and run the lookup. The tool indexes its embedded table, returns the fields shown below and copies list fields where applicable. All supported selections and their actual returned entries are included below. It performs no network request, project measurement or forecast inference.
| Selection | Returned reference entry |
|---|---|
| 1 | applicationGuidance: Divide a whole into independently controllable parts.; principleName: Segmentation; principleNumber: 1 |
| 2 | applicationGuidance: Remove a necessary part from a system and operate it separately.; principleName: Extraction; principleNumber: 2 |
| 3 | applicationGuidance: Make one part highly optimized rather than optimizing everything equally.; principleName: Local quality; principleNumber: 3 |
| 4 | applicationGuidance: Develop different properties for different functions or contexts.; principleName: Asymmetry; principleNumber: 4 |
| 5 | applicationGuidance: Combine functions or objects into a larger integrated whole.; principleName: Merging; principleNumber: 5 |
| 6 | applicationGuidance: Make an object perform several additional functions.; principleName: Universality; principleNumber: 6 |
| 7 | applicationGuidance: Change a quantitative property such as degree, scale, or concentration.; principleName: Quantity; principleNumber: 7 |
| 8 | applicationGuidance: Introduce a limited, deliberately incomplete subsystem.; principleName: Partiality; principleNumber: 8 |
| 9 | applicationGuidance: Remove a harmful or ineffective component without replacing it initially.; principleName: Ineffectiveness; principleNumber: 9 |
| 10 | applicationGuidance: Introduce an action that is easier to reverse or remove later.; principleName: Preliminary action; principleNumber: 10 |
| 11 | applicationGuidance: Use a lower-complexity model that preserves required information.; principleName: Holography; principleNumber: 11 |
| 12 | applicationGuidance: Delay a change so existing conditions can adapt before commitment.; principleName: Inertia; principleNumber: 12 |
| 13 | applicationGuidance: Invert the system or remove the harmful element.; principleName: The other way round; principleNumber: 13 |
| 14 | applicationGuidance: Introduce or strengthen feedback about the result.; principleName: Feedback; principleNumber: 14 |
| 15 | applicationGuidance: Change a fixed property into a continuously adjustable one.; principleName: Dynamization; principleNumber: 15 |
| 16 | applicationGuidance: Use an existing, proven solution rather than inventing anew.; principleName: Copying; principleNumber: 16 |
| 17 | applicationGuidance: Transfer a working solution from another system.; principleName: Analogy; principleNumber: 17 |
| 18 | applicationGuidance: Alternate a parameter or action between states to find or control behavior.; principleName: Oscillation; principleNumber: 18 |
| 19 | applicationGuidance: Introduce a repeating cycle or schedule.; principleName: Periodicity; principleNumber: 19 |
| 20 | applicationGuidance: Remove abrupt transitions and connect adjacent stages.; principleName: Continuity; principleNumber: 20 |
| 21 | applicationGuidance: Change a component to fit new operating conditions.; principleName: Adaptation; principleNumber: 21 |
| 22 | applicationGuidance: Reverse the system's process, function, or location.; principleName: Inversion; principleNumber: 22 |
| 23 | applicationGuidance: Remove a harmful element or perform the complementary action.; principleName: Negation; principleNumber: 23 |
| 24 | applicationGuidance: Place a system inside a larger system that supplies or absorbs effects.; principleName: Envelopment; principleNumber: 24 |
| 25 | applicationGuidance: Insert an intermediate element to carry or translate an action.; principleName: Intermediary; principleNumber: 25 |
| 26 | applicationGuidance: Make the system supply part of its own required function.; principleName: Self-service; principleNumber: 26 |
| 27 | applicationGuidance: Arrange for a component or process to remove or replace itself.; principleName: Self-elimination; principleNumber: 27 |
| 28 | applicationGuidance: Replace a weak or harmful element with a better one.; principleName: Substitution; principleNumber: 28 |
| 29 | applicationGuidance: Combine previously separate parts.; principleName: Integration; principleNumber: 29 |
| 30 | applicationGuidance: Extend a capability or dimension beyond its prior limit.; principleName: Stretching; principleNumber: 30 |
| 31 | applicationGuidance: Increase the degree or scale of an existing function.; principleName: Expansion; principleNumber: 31 |
| 32 | applicationGuidance: Change one property, function, or substance into another.; principleName: Conversion; principleNumber: 32 |
| 33 | applicationGuidance: Reduce variety by making parts or steps alike.; principleName: Homogeneity; principleNumber: 33 |
| 34 | applicationGuidance: Move an action or resource to a favorable local place.; principleName: Locality; principleNumber: 34 |
| 35 | applicationGuidance: Expose or separate a hidden part of a system for inspection or control.; principleName: Unfolding; principleNumber: 35 |
| 36 | applicationGuidance: Remove a weak part before a complete redesign.; principleName: Removing weakness; principleNumber: 36 |
| 37 | applicationGuidance: Repeat an action or component to achieve a cumulative effect.; principleName: Repetition; principleNumber: 37 |
| 38 | applicationGuidance: Separate a coupled part in space, time, or function.; principleName: Separation; principleNumber: 38 |
| 39 | applicationGuidance: Bring contrasting properties or states into productive relation.; principleName: Contrasting; principleNumber: 39 |
| 40 | applicationGuidance: Increase the magnitude or degree of an existing property.; principleName: Strengthening; principleNumber: 40 |
exact selection → fixed embedded reference entry Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| applicationGuidance | Application guidance | string |
| principleName | Principle name | string |
| principleNumber | Principle number | integer; minimum: 1; maximum: 40 |
{
"input": {
"principleNumber": 1
},
"output": {
"applicationGuidance": "Divide a whole into independently controllable parts.",
"principleName": "Segmentation",
"principleNumber": 1
}
}Limitations and assumptions
This is a concise teaching reference. Verify original publications, context and applicable editions before relying on it; it is not a complete framework or an authoritative evaluation.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Missing fields without a declared default, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Morphological Analysis Box Grid Combination Explorer: A morphological box combines one option from each dimension. Multiplying option counts estimates the search space before enumerating it. For a complementary task, use Scenario Consistency Driver Coherence Checker: A scenario coherence check can expose opposing signs assigned to the same outcome within a shared driver group. Neutral signs do not contradict active signs.
References
Similar or alternative tools
- Morphological Analysis Box Grid Combination Explorer
A morphological box combines one option from each dimension. Multiplying option counts estimates the search space before enumerating it.
- Scenario Consistency Driver Coherence Checker
A scenario coherence check can expose opposing signs assigned to the same outcome within a shared driver group. Neutral signs do not contradict active signs.