Business Execution Canvas® Foundations · Lesson A2
The Business Execution Canvas® on one page
The Business Execution Canvas® is a one-page design for how an organisation turns purpose into work that customers value. This lesson walks through it from the foundations up, with Harbourline as the example.
Why execution needs a design
Most organisations are full of good people doing their best inside a system nobody designed. Teams form around skills, functions grow around disciplines, and processes are added when something goes wrong. Each part works; the whole often does not.
The Business Execution Canvas makes explicit what is usually left implicit: who the work is for, how it is explained, how the organisation is built to do it, how it runs day to day, and how it learns.
It updates traditional management rather than replacing it. Budgets, functions, process owners and reviews all stay. The canvas shows how they fit together, so people can see the whole and improve it.
What management can learn from software
- A large system works when its parts have defined interfaces; an organisation works when its teams agree what passes between them.
- Software is designed before it is built and tested before it ships; most organisations are reorganised without a design or a test.
- Good systems are monitored and changed in small, frequent releases; organisations tend to change in large, occasional restructures.
The canvas is not always the answer. Some problems need a decision, a person or a budget, not a redesign. Use it when the same problems keep coming back, because that is usually a sign of a design gap.
The canvas at a glance
The canvas has 27 components: six foundations and 21 components across five pillars. The pillars run left to right in the order work flows, from understanding customers to adapting, and what the organisation learns feeds back into understanding.
↻ Adapt feeds back into Understand: one continuous cycle
- Must Haves
- Must Not Haves
- Delight
- Anticipate
- Internally
- Across
- Externally
- Social System
- Technical System
- Economic System
- Control
- Effectiveness
- Efficiency
- Agility
- Digitalisation
- Automation & AI
- Monitor
- Learn
- Improve
- Respond
- Innovate
Read it from the bottom up and left to right: Structured Collaboration is the base the other foundations rest on, because every pillar depends on teams being able to rely on each other.
The six foundations
The foundations are the platform everything else stands on. When one is weak, every pillar above it works harder than it should.
| Foundation | The question it answers | Harbourline |
|---|---|---|
| Structured Collaboration | How do our teams agree what passes between them, to what standard and when? | Every handoff from project to service is agreed on both sides |
| Mission / Purpose | Why do we exist, and for whom? | “We build and run the technology our clients depend on, as if it were our own.” |
| Vision | What will be true when we succeed? | “By 2030, the IT partner mid-sized organisations trust most to build it right and keep it running.” |
| Principles | How do we decide when two good things compete? | “Built to be run”; “Decide where the facts are” |
| Values and Behaviours | What do we care about, and what does that look like in daily work? | Care, Ownership, Openness, Learning |
| Strategy Deployment | How do goals reach every team, and how does progress come back? | Nine goals for 2026–28, each with an owner and a measure |
Structured Collaboration comes first because the other five only work if teams can rely on each other. A mission no team can deliver alone needs agreed handoffs to become real.
Values, behaviours and principles are easily confused. A value is what we care about. A behaviour is what we can see someone do. A principle is how we choose between two good options, such as speed and thoroughness.
The five pillars
Each pillar closes one execution gap, numbered in the order the work flows. A gap upstream spreads downstream: an organisation that runs well but misunderstands its customers simply gets more efficient at the wrong things.
| Pillar | The gap it closes | Components | Harbourline |
|---|---|---|---|
| 1 Understand | We do not really know what customers need | Must Haves, Must Not Haves, Delight, Anticipate | Managed-service clients must have service levels met every month; they must not get repeat incidents or invoice surprises |
| 2 Articulate | What we know is not shared with the people who act on it | Internally, Across, Externally | 1 in 4 deals was sold without delivery’s sign-off |
| 3 Design | The organisation is not built to deliver what it promises | Social System, Technical System, Economic System | Project teams were rewarded on the go-live date, not on a calm first 30 days |
| 4 Operationalise | The design does not hold up in daily work | Control, Effectiveness, Efficiency, Agility, Digitalisation, Automation & AI | Two go-lives close together swamped the Pune Service Desk, and its backlog is still recovering |
| 5 Adapt | We do not learn fast enough to act while it still matters | Monitor, Learn, Improve, Respond, Innovate | An A3 on missing run-books cut serious incidents after go-live from 1 in 3 to 1 in 8 |
The five Adapt components rise in scale. Monitor and Learn turn signals into insight. Improve is a small local change, Respond a larger change across the system, and Innovate a new way of creating value.
One canvas at every level
The same 27 components apply at every level: the whole organisation, a division, a function, a process or a single team. Each canvas sits under the one above and interprets it for its own work, rather than copying it or starting from scratch.
- Organisation: sets the mission, vision, principles, values and strategy every other canvas builds on.
- Function or division: turns enterprise goals into its own priorities and agrees what it provides to others.
- Process: the process owner uses the canvas to run the work end to end across the teams it passes through.
- Team: shows how the team’s daily work contributes to the strategy and what it needs from, and gives to, its neighbours.
At Harbourline, Ruth Adebayo owns the company canvas. Managed Services has its own canvas under it, and the Project to service process, owned by Declan Moore, crosses three of its teams.
Because every level uses the same language, a weak spot found in one team can be traced up to the design decision that caused it.
Measuring it
Each of the 27 components is scored on five described levels, and each level converts to a score from 0 to 100. Level 1 is 0, level 3 is 50 and level 5 is 100.
Each level describes what the component looks like in daily work, so people score what they see rather than how they feel. Here are the five levels for Across, under Articulate:
| Level | Score | What it looks like | Harbourline, round 3 |
|---|---|---|---|
| 1 | 0 | Teams and partners pass on work, specifications and orders, but no customer insight. | |
| 2 | 25 | Customer needs are shared between teams and with partners informally and inconsistently. | Team leads: 20 |
| 3 | 50 | Key teams and partners are briefed occasionally, and what each needs from the other isn’t agreed. | Executives: 49 |
| 4 | 75 | Customer needs are communicated regularly along the value chain, and teams and partners agree what they need from each other at the main handoffs. | |
| 5 | 100 | Every team and partner understands customer needs as well as we do, agrees what it needs from the others, and is measured on this jointly. |
Harbourline scores Across at 34 overall, between levels 2 and 3. Executives see something close to level 3. Team leads, who work the handoffs every day, see level 2 at best. The next step up is clear from the table: agree what each team needs from the next at the main handoffs.
- A pillar’s score is the average of its components.
- The Foundation Score is the average of the six foundations.
- The Execution Score combines the five pillars as a geometric mean, so one weak pillar pulls it down more than a simple average would.
Read the pattern before the total. A change of 10 points or more between rounds is a real change. A wide spread between management levels on the same component usually means people experience it very differently, which is a finding in itself.
Harbourline’s third round (September 2026) shows the pattern clearly. The Foundation Score rose from 52 at the baseline to 60, and the Execution Score from 48 to 55. Understand is the strongest pillar and Adapt the weakest. The single weakest component is Across, at 34, where executives score 49 and team leads 20.
Every pillar rose since the baseline; Adapt is still the weakest
Round 3, September 2026 Baseline, November 2025 (pillar score, 0 to 100)
The gains are real but uneven: Articulate rose most, by 10 points, and Adapt is still lowest; within it, Respond (36) and Innovate (39) are among Harbourline’s five weakest components.
Where to start
Start where the friction is felt, not at the top left of the canvas. The diagnostic points to it: components scoring below 55 where people disagree by more than 20 points are where to look first.
- Name the problem that keeps coming back and find the component it sits in.
- Look upstream: a delivery problem often starts in Understand, Articulate or Design.
- Fix one thing, measure it, and write the result into the canvas.
- Score again next round and move to the next gap.
Common pitfalls:
- Treating the canvas as a form to fill in. Each entry should record a decision someone owns.
- Scoring generously. A score nobody would defend with evidence teaches nothing.
- Trying to fix all 27 components at once. Two or three at a time is enough.
- Operationalising before designing. New tools and routines on top of an unchanged design usually make the old problem faster.
Try it
Harbourline in the Builder
It is free and needs no account. Allow about 20 minutes.
- On the Build tab, read the six foundations, then the five pillars from Understand to Adapt.
- On the Results tab, find the strongest and weakest pillars in round 3, and the component where executives and team leads disagree most.
- On the Build tab, open Across under Articulate. Read what Harbourline has written and who owns it.
Pause and think · your notes
Bring the lesson back to your own organisation.
To do the same for your own organisation, create a free account and start a new canvas in the Builder. Your first team diagnostic is free.
Check your understanding
Seven 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
In what order do the pillars run?
Question 2
“We answer every client message within two hours” is a…
Question 3
“Decide where the facts are” is a…
Question 4
A team runs efficiently but customers keep complaining. Where should you look first?
Question 5
Why is the Execution Score a geometric mean?
Question 6
Executives score Across at 49 and team leads at 20. What does that tell you?
Question 7
Which change is Respond rather than Improve?
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.