Define the operational problem
Agree on the process, recurring issue or proposed use case that matters.
HOW IT WORKS
Start with the real work. Build from there.
The exact scope depends on the business problem. Not every engagement needs every step—and technology is not always the first answer.
Observe the real work
Speak with the people doing the work and see the conditions around it.
Map processes, decisions & exceptions
Make activities, handovers, information, authority and workarounds visible.
Improve & standardise
Reduce unnecessary steps and variation before digitising the process.
Structure operational knowledge
Define the rules, sources, exceptions, ownership and escalation paths.
Assess AI & automation readiness
Identify gaps, risks, controls and decisions that must remain with people.
Prepare & support a pilot
Set the boundaries, requirements, acceptance criteria and test approach.
Measure & govern the result
Connect ownership, KPIs, review cycles and learning to business outcomes.
THE SEVEN-LAYER MODEL
A connected operational system.
01
Operational reality
People, systems, constraints and the conditions where work happens.
→02
Process discovery
Activities, decisions, handovers, delays and recurring exceptions.
→03
Improve & standardise
Remove avoidable complexity and strengthen the process.
→04
Operational Brain
Structure rules, decision rights, knowledge and escalation paths.
→05
AI workers & automation
Add technology only where the operational foundation supports it.
→06
Measurement & governance
Define ownership, controls, review cycles and audit trails.
→07
Business outcomes
Connect the work to service, cost, safety, compliance and resilience.
→The framework is a guide, not a rigid consulting sequence. Work can begin at the layer where the problem is visible, then move backwards or forwards as the evidence requires.
START WITH ONE PROBLEM
What keeps getting in the way of the work?
A useful first conversation can begin with one process, one recurring exception or one proposed automation use case.