Twenty-one checks across the five foundations, and the three AI Inventory questions that come before any of them. Thirty honest minutes. Nothing you enter leaves your browser.
Why this is a hypothesis, not a score
Before you commit to an AI programme, establish where the payback sits.
The Diagnostic is not automated, and presence is the product. A remote or pre-visit read is a hypothesis layer, labelled as such throughout, never presented as a finished Diagnostic. This self-assessment is that hypothesis layer, offered for a leadership team to run on itself. Its result is the foundation most likely to be binding, hypothesised, awaiting the inside. Thirty honest minutes. Nothing you enter leaves your browser.
Three questions, answered in a sentence each. They are not scored. They are the evidence the Diagnostic finds most revealing, and most leadership teams discover the answer to the first is “we do not know”.
Part one: the AI Inventory, before anything is scored
If the list took longer to assemble than to read, that is a finding. It is usually the first one.
Most professionally run businesses sit at Contain and Prepare on most foundations, read honestly. That is the ordinary resting place, not a poor result, and Ready to Build is earned rather than assumed.
Hypothesised
The lowest-scoring foundation, named as the one most likely to be binding.
By foundation
This is a hypothesis, read from the inside by the people who run the business, and it is labelled as one. The Diagnostic replaces it with evidence: two to three days in the building, the inventory walked rather than recalled, the workflow observed rather than described, and the five foundations scored on what was seen. The self-read tells you where to look. The Diagnostic tells you what is there.
Every opportunity the walk surfaces is tested against the foundation it depends on. Two businesses with an identical opportunity can receive opposite recommendations, because their foundations differ.
