Turn an Engineering Contradiction into a Testable Direction

When improving one aspect makes another worse

A seal needs enough compression to work in service, but increasing the closing force can make the enclosure harder to assemble. Reducing compression may ease assembly while putting sealing performance at risk. Asking for “a better seal” leaves the engineering team choosing among ideas before it has explained why the requirements conflict.

Mechanical and product-development engineers often face this kind of problem: the current design links a desired improvement to an unwanted consequence. Before accepting a compromise, it is worth asking whether that link can change. Could a different load path, interaction or operating sequence allow both requirements to be met?

TRIZ provides tools for investigating that question. This guide follows a hypothetical sealed enclosure from the initial conflict to a proposed mechanism and an engineering test. It does not assume that the cause has already been established or that the proposed change will work.

What is TRIZ?

TRIZ is a Russian acronym commonly translated as the Theory of Inventive Problem Solving. Developed by Genrich Altshuller and collaborators through the study of patents, it is a systematic approach to generating inventive solutions. Its central insight is that similar problems and solution patterns recur across different technical fields. Describing what a system does, rather than only naming its parts or industry, can reveal approaches that an engineer might otherwise overlook.

For a design conflict, the practical sequence is to express the specific problem in a more general form, use a relevant TRIZ pattern to explore alternatives, then translate a promising alternative back into a physical design. Tools such as inventive principles, contradiction analysis and function modeling help with different parts of that work. They suggest directions to investigate; engineering evidence determines whether a direction is feasible.

Two kinds of contradiction are particularly useful:

• Technical contradiction: improving one parameter makes another worse. In the enclosure, increasing compression to improve sealing may increase assembly effort.
• Physical contradiction: the same property of an element faces opposing requirements. The seal contact pressure may need to be low while the cover is positioned and high when the enclosure is in service.

The second formulation invites a different question: can those requirements be separated by time, location or operating condition? That is one reason the distinction matters. It can shift the search from finding a tolerable compromise to changing when or how the function is delivered.

Understand the system and the cause of the conflict

Begin with the enclosure, cover, seal, closing mechanism and the surfaces that carry the load. Include relevant external influences and operating stages. Assembly and service may place different demands on the same parts.

Work through four views of the system:

• Components: What is present, and what falls outside the system boundary?
• Interactions: Which components contact, constrain, support or load others?
• Functions: Which actions achieve their purpose, which are insufficient, and which cause an unwanted effect?
• Structure: Where do those interactions occur in the actual arrangement?

Listing a closing mechanism does not establish how its force reaches the seal. Drawing contact between two parts does not establish that the contact performs the intended function under load. For the enclosure, trace how closure force is applied and how seal compression is maintained. Check whether a temporary assembly contact has mistakenly been treated as a permanent service contact.

The same distinction between parts and functions applies in other systems. In the thermal-system example below, follow the useful heat-transfer paths, then compare them with the red heat-loss paths to ambient air. The map makes different interactions visible for review; it does not establish their measured effect on performance.

Next, connect the observed symptom to possible causes. “Assembly effort is excessive” is an observation only if the team has established it against a requirement. “The seal is too stiff” is a possible explanation. Friction, alignment or the closing mechanism could also matter.

A useful initial hypothesis is:

Check that relationship before changing the seal or closure. Measure the relevant assembly force and seal compression under defined conditions, and examine whether alignment or friction explains the difficult assembly. If the evidence supports the hypothesis, state which improvement causes which deterioration. If it does not, revise the causal explanation.

The output is a system model and a contradiction grounded in the actual design. A causal diagram can organize the reasoning, but measurements are needed to distinguish plausible explanations.

Use TRIZ models to explore different mechanisms

Different TRIZ models direct attention to different aspects of the same problem. The following four views help move from a general conflict to specific questions an engineer can investigate.

For the enclosure, separation in time suggests one candidate: position the cover with little seal compression, then use a separate closing action to apply and retain the required compression. This is a hypothetical concept, not a tested solution. It would need a physical mechanism and enough space to operate; the added action might also complicate assembly.

Compare that direction with changing the seal material or changing the load path. These options depend on different mechanisms and assumptions. Two ideas that both rely on increasing closing force offer less variety, even if their descriptions sound different.

Keep the actual constraints visible: available space, allowable parts, manufacturing methods, operating conditions and failure consequences. An option that needs an unavailable actuator cannot become feasible merely because it fits an inventive pattern.

Turn a direction into an engineering test

A direction is ready for evaluation when another engineer can explain what changes physically, why it could help and what evidence would reject it.

For the stage-separated closure, the test must assess both sides of the original conflict. Measuring only the force needed to position the cover would miss the effort required by the new compression action. Measuring compression alone would not establish sealing performance.

Agree on those criteria before interpreting results. A concept might reduce peak force yet add enough assembly time to miss the production requirement. It might achieve the target compression initially but fail to retain it over repeated use. Either result changes the decision about whether to pursue the direction.

Keep calculated, suggested and measured values distinct. A dimension in an AI-generated proposal remains a proposal until its basis is established. Patent examples and papers can help explain a mechanism, but their materials, geometry and operating conditions may differ from yours.

How Patsnap Eureka supports TRIZ problem-solving

Patsnap Eureka's Find Solutions with TRIZ helps structure this process from the initial problem to candidate solutions. Start with the technical subject, observed problem, performance target and constraints. You can also provide supporting files, such as a component list or design file, where the product flow supports them.

The workflow helps clarify the problem, map components and their interactions, and examine a causal chain. It then uses TRIZ-guided reasoning to generate solution directions that you can review, select and refine, with supporting patents and technical literature.

Review the system model before developing a selected idea. Correct missing components or inaccurate interactions, then examine the proposed mechanism, implementation assumptions and validation needs. The resulting solution path supports an engineering decision; it still needs evaluation against your design and test requirements.