The work does not start with technology. It starts when an owner can name the part of the business that no longer makes sense from where he carries it.
The first conversation is not a sales call and not a disguised proposal. It decides whether there is a real condition worth examining.
1. Recognition conversation
We locate the felt problem before it becomes a requirement, a project, or a safer version of itself. Three questions are usually enough to find the edge of the conversation:
- Where do you no longer trust what the company is telling you?
- Which decision has become too late, too mediated, or too difficult to own?
- What has grown beyond instinct without becoming reliable as a system?
If there is no recognition, there is no work.
2. Paid diagnosis
If the signal is real, paid work begins with a defined diagnostic phase. It maps current reality, locates the intelligence break, identifies the decision affected, and makes the consequence visible. The phase has its own scope, timeframe, output, and fee.
3. Design
Only when the break is clear does the work become architectural. The intervention may be a decision surface, an owner brief, an operating rhythm, a redesigned process, a software tool, an AI-assisted workflow, or no technology at all.
4. Implementation, if needed
Implementation begins only when diagnosis has established the condition and design has established the form. Some work stops after diagnosis. Some ends with a small correction. Some continues into a bounded build. A project is justified only when the condition, the direction, and the boundary are understood.
The form follows the truth of the problem. Not the other way around.
The Owner-Level Diagnostic Brief explains the boundary. The Method Note explains what the diagnostic must establish.