The one in the governing documents.
Your policies, standards, delegations, and procedures. Assumed tidy, coherent, and designed - until you read them as a single connected system.
A graph-based decision architecture diagnostic for AI implementation risk. It reads your governing documents as one connected system and tells you whether your organisation can absorb the decisions your AI generates. Built on twenty years in safety-critical engineering, senior consulting, and institutional execution.
AI didn't create the gap between what your organisation knows and what it can do. It removed the slack that used to hide it.
Recommendations now move faster than authority can ratify them. Information moves faster than accountability can follow. Models produce answers faster than the organisation can test whether those answers are usable, legitimate, or safe to act on. That gap is what kills AI initiatives after readiness has passed, and fixing the model won't close it, because the model was never the problem.
Your policies, standards, delegations, and procedures. Assumed tidy, coherent, and designed - until you read them as a single connected system.
The decisions, escalations, and overrides that emerge from people, history, and political weight.
Are authority boundaries clear, or does the real decision depend on who's in the room? Where rights are ambiguous, AI doesn't resolve the ambiguity: it encodes it, then runs it at speed. The test shows where rights are clean enough to build on and where they have to be settled first.
Do the words that matter, qualified, approved, complete, escalated, mean the same thing across the functions that depend on them? Divergent definitions coexist quietly for years. When an AI imposes one, the disagreement surfaces at the execution layer and looks like the system is broken.
When a rule says X must happen before Y, does it, or does political weight routinely override it? Enforceability is the hardest condition to see from documentation and the most reliably predictive of whether the programme lands.
Fixed scope. Two to four weeks. The governing document set agreed up front. The deliverable is a decision the sponsor can act on, chained to the clauses it rests on, not a slide pack of theory.
Your governing documents - policies, standards, delegations, procedures - read as one connected system and rebuilt as a directed graph: authority, obligation, escalation, record. The documents that are supposed to run the organisation, not the org chart.
Run the pattern scan across the graph. Surface where authority diffuses, obligations are delegated but never enacted, records dead-end, and shared terms diverge - and flag where the documented chain can't be how the work actually happens.
Confirm the separation against practice: operating evidence - decision logs, escalations, override and exception data - and, where it's needed, a small number of targeted interviews. This is where documented-versus-actual is measured, and it can run as a second phase once the document findings are in hand.
A sponsor working session. Each finding graded for confidence and chained to the clause it rests on, its consequence for the programme, and its severity. The output: scale, conditional, or rebuild, with the structural reasons.
Pilot succeeded, scale is stalling, and the explanation is drifting toward "adoption problem." WorkLattice diagnoses the structural cause, identifies what is recoverable, and tells you which parts of the design need to change before the next sprint. The output is a decision a sponsor can act on.
Where a board paper is being prepared and the sponsor privately suspects the organisation can't absorb the rollout. The diagnostic identifies the right starting boundary, the conditions that must hold for the boundary to expand, and the specific structural risks that will manifest if scale proceeds without remediation.
Where a restructure or transformation isn't landing. The diagnostic distinguishes what's working from what is structurally preventing delivery, before the next redesign is built on top of the same constraints.
See it run: a worked example on a stacked-framework governance suite →
Two to four weeks, fixed scope, fixed fee. Typically one to three percent of the AI programme cost it is testing.
A first conversation establishes whether WorkLattice fits your situation, the structural questions worth answering, and how the work would be scoped. Thirty minutes.