A felt problem is a legitimate beginning. It is not yet a design brief.
An owner may first notice delay, distrust, fatigue, or the sense that the company is moving without steering. That signal matters because it points to a place where reality and decision may have become separated.
Recognition becomes useful when discomfort can be connected to a decision the business is no longer making well.
Recognition is not diagnosis
“We need better reporting” may mean that context is missing. “We need AI” may mean that an important decision arrives too late. “Our people do not use the system” may mean that the system never reflected how the work is actually done.
The first description is therefore not accepted as the problem. It is treated as evidence of a problem that still has to be located.
- What is happening that should not be happening?
- Which decision is affected?
- What would have to become visible earlier for action to change?
If those questions do not lead to a real decision, the work should not manufacture one.
Diagnosis finds the break
Diagnosis follows the signal through the business. It asks where context is lost, who must interpret what remains, when the decision becomes possible, and whether the outcome returns as learning.
The result is not a catalog of features. It is a bounded account of the break: what is known, what is assumed, what evidence is missing, and what consequence the business is already absorbing.
Design gives intelligence a place
Once the break is clear, the form can emerge. The answer may be a decision surface, a new operating rhythm, a redesigned handoff, a software tool, an AI agent, or no technology at all.
What matters is placement. The intervention must sit close enough to the decision to preserve context, change action, and capture the result. Otherwise the business receives another layer of output and the original break remains.
The form follows the truth of the problem.
The evidence decides whether work continues
A serious first phase can end without a project. It can also reveal a small correction that matters more than a large implementation. Its value is the return of a clear line between the felt problem, the evidence, the decision, and the next responsible move.
The public route into that phase is described in How a Conversation Becomes Work. The diagnostic method itself is documented in the Strategic Intelligence Diagnostic Method Note.
This essay owns a narrower point: diagnosis becomes design only after the business problem becomes precise enough that a form can be chosen without pretending.