2/16 Beyond the Contradiction
The contradiction is clear.
The team is capable.
The project is still stuck.
Hard engineering problems do not stay hard for one reason.
And unless we name the different kinds clearly, we keep reaching for the wrong tool.
I think there are four distinct reasons they stay hard.
I call this the Hardness Landscape:
a map of the different kinds of resistance a hard problem can expose, and a way to decide which method belongs to which kind of hard.
1. Contradiction hardness
This is the kind TRIZ sees best.
One requirement improves only by worsening another.
Higher selectivity only at lower conversion.
Higher resolution only at lower throughput.
Lower cost only at a narrower safety margin.
The difficulty is structural.
The same variable is locked into opposing roles.
2. Search hardness
Sometimes the contradiction is already clear.
The problem is that there are now too many viable-looking paths:
too many designs,
sequences,
parameter combinations,
integration routes.
The question is no longer:
What is conflicting?
It is:
Which of these many paths will actually work in production?
That is a different kind of hard.
3. Epistemic hardness
Sometimes the team is not even aware that a contradiction exists, or what the relevant search space really is.
The mechanism is still unclear.
The team debates whether the bottleneck is residence time or mixing, but no one actually knows yet.
The governing variable has not been identified.
In that state, the contradiction cannot even be stated correctly — if it is visible at all.
You are not solving the wrong contradiction.
You may not yet know what the contradiction is.
4. Decision conflict
And sometimes the technical path is visible, but “better” is no longer one thing.
The stronger process has a longer lead time.
The better route depends on a fragile supplier.
The technically superior option scores worse on timing, access, or resilience.
Is it still better?
That requires a different kind of reasoning again.
One clarification before the closing thought.
These kinds of hardness do not replace one another in a neat sequence. They can coexist.
What matters is which one is governing progress on the route the team is currently pursuing.
In practice, that route often begins at the symptom level and has to descend — through mechanisms and constraints, toward the governing hardness.
How far that descent has progressed shapes which kind of hardness is currently governing the work.
And that route is not neutral.
It is shaped by the choices the team makes:
what boundary to draw,
what assumptions to freeze,
what route to pursue,
and what tool to use next.
That is why diagnosis matters so much.
If a team treats search hardness as contradiction hardness, or decision conflict as if it were still an epistemic problem, the work can stay active while the project stays stuck.
Sometimes the right move is not to push harder on the same path.
It is to ask whether a different path would expose a more tractable kind of hard.
That is what makes problem solving itself a systems problem. Many problem-solving frameworks, including classical TRIZ, treat contradiction as the central unit of difficulty. The Hardness Landscape treats contradiction as one of four major ways hard problems resist progress. That is more than a small adjustment — it changes what we diagnose first.
Which of these four kinds of hardness does your organization most consistently misdiagnose — and what does that say about how it thinks?