Business Execution Canvas® Foundations · Lesson A7
Operationalise
Operationalise is the fourth pillar: running the design day to day. Its six components build on each other from the bottom up, from being in control of the workload to using automation and AI. Skip a level and the one above it rests on nothing.
Six components, bottom up
Read the pillar from the bottom. Each component needs the ones below it to be in place first.
| Component | The question | Good looks like | |
|---|---|---|---|
| 6 (top) | Automation & AI | Does automation and AI take on work so people spend time where their judgement adds most? | Most unnecessary tasks are automated or handed to AI, with clear human oversight |
| 5 | Digitalisation | Does digital technology improve how customers and staff are served? | Customers and staff reach products, services and processes remotely; no paper processes that digital tools would serve better |
| 4 | Agility | Can the organisation change course at short notice? | Every team understands its workload pattern and can flex capacity to keep its service levels |
| 3 | Efficiency | Does the work use people’s and customers’ time well? | Productivity is reviewed weekly and failure demand is actively reduced |
| 2 | Effectiveness | Is the work the work that matters? | Activities are reviewed against customer value and the organisation’s goals, and low-value work is stopped |
| 1 (base) | Control | Is demand matched to capacity? | Process owners own core end-to-end processes; process managers run them to agreed measures; teams use visual management and meet daily |
The order follows one rule: simplify, standardise, digitise, then automate. A team that is not in control of its workload cannot tell what is worth doing. A process that is not worth doing should be stopped, not made faster. A process nobody has standardised should not be digitised, and a process nobody has digitised and defined cannot be safely handed to AI. Automating a broken process produces the same mess, faster.
Harbourline, bottom up
| Component | Harbourline, round 3 | Change since the baseline |
|---|---|---|
| Automation & AI | 41 | +5 |
| Digitalisation | 66 | +7 |
| Agility | 38 | +10 |
| Efficiency | 59 | +6 |
| Effectiveness | 55 | +6 |
| Control | 68 | +4 |
Three things stand out.
- Control is solid at 68. Teams mostly know their demand and capacity, so the base is there to build on.
- Agility is the weakest at 38, though it rose 10 points. Quaylight, the fast-growing payments client, wants weekly releases; Harbourline’s change process was built for banks. Speed is where Brackenfield, its competitor, is winning.
- Automation & AI is low at 41, while Digitalisation is high at 66. Work is digital but not yet defined well enough to automate. Harbourline’s goal is to resolve 40% of tickets without a person by 2028, up from 8%. The rule above applies: the goal is only safe once the processes underneath are standardised.
Process owners and process managers
Control rests on two roles most organisations blur. A process owner owns a core end-to-end process: its design, its standards and its results, across every team it passes through. A process manager runs it day to day against agreed measures. At Harbourline, Declan Moore owns the project-to-service process and Fiona Grant, the Service Transition Manager, runs it as its process manager, across Service Transition, the Service Desk and the support teams.
Without a process owner, each team optimises its own step and nobody owns the customer’s result. Without process managers, the owner’s design stays on paper. The Practitioner course covers both roles in depth.
Failure demand
Efficiency is not cost-cutting. The largest waste in most service organisations is failure demand: work caused by not doing something, or not doing it right, the first time. A repeat incident, a chased invoice, a client calling to ask what is happening. Harbourline’s run-services stream shows it plainly: 18% of incidents are repeats. Every one of them is work the service desk should never have had.
What management can learn from software
- Continuous delivery only works once builds and tests are stable and repeatable; automation only works once the process underneath is stable and standard.
- Teams that track how much of their time goes on rework find their real capacity; organisations that measure failure demand find theirs.
- Every service has an owner who is paged when it fails; every core process needs an owner who answers for its result.
Try it
Operationalise in the Builder
It is free and needs no account. Allow about 15 minutes.
- On the Build tab, open Operationalise and read the six components from Control at the bottom to Automation & AI at the top.
- On the Results tab, find the gap between Digitalisation and Automation & AI.
- Decide which of the lower components Harbourline must strengthen before its automation goal is safe.
Pause and think · your notes
Bring the lesson back to your own organisation.
Check your understanding
Five questions on this lesson. Choose an answer to see straight away whether it is right, and why. Your score is saved with your progress.
Question 1
Which component sits at the base of Operationalise?
Question 2
Why does Automation & AI sit at the top?
Question 3
A client calls to ask why a ticket was closed but the problem remains. This is…
Question 4
Who owns a core end-to-end process across every team it passes through?
Question 5
Harbourline scores Digitalisation 66 and Automation & AI 41. What is the likely reason?
The term failure demand comes from John Seddon’s work on service systems. Harbourline Services is a fictional company used as the worked example in every Structured Collaboration tool. Its figures come from the sample diagnostic report.
© 2026 Alex McDonnell. All rights reserved. Business Execution Canvas® is a registered trade mark of Alex McDonnell. Structured Collaboration Canvas™ is a trade mark of Alex McDonnell.
Your progress
When you have worked through this lesson, mark it as complete. Sign in to keep your progress on every device.
Course contents · This is the open version of the course. Your notes, progress and check scores are saved on this device, and in your account when you are signed in.