Business Execution Canvas® Foundations · Lesson A3
The foundations
The six foundations are the ground every pillar stands on: how teams work together, why the organisation exists, where it is heading, how it decides, how its people behave, and how direction becomes work. When a foundation is weak, every pillar above it works harder than it should.
Direction is usually clear; turning it into work is not
Most leadership teams have a mission and a vision. Fewer have principles that settle real decisions, behaviours people are held to, a way of turning strategy into goals each team owns, and agreed handoffs between teams. The foundations score that difference.
Harbourline shows the common pattern. Its managers rate Mission at 78 and Vision at 71 in round 3: the direction is understood. They rate Strategy Deployment at 42 and Structured Collaboration at 46: the way direction becomes agreed work, and the way teams rely on each other, is where it breaks down.
| Foundation | Harbourline, round 3 |
|---|---|
| Mission / Purpose | 78 |
| Vision | 71 |
| Principles | 63 |
| Values and Behaviours | 57 |
| Structured Collaboration | 46 |
| Strategy Deployment | 42 |
Structured Collaboration: the platform everything else runs on
Structured Collaboration is how work passes between people and teams. Each team knows its internal customers, understands what they need, and agrees what it will hand over, to what standard and by when. The amount of structure matches what each handoff carries: a simple request needs little, a go-live needs a lot.
It sits at the base because the other five depend on it. A mission no single team can deliver alone only becomes real through agreed handoffs. At Harbourline, the March 2026 “One Harbourline” operating model put a handoff agreement on every team canvas: sales to delivery, delivery to transition, transition to the service desk, and Harbourline to its partners.
Good looks like this: critical handoffs have explicit, agreed expectations, and teams check whether they are met. The free Structured Collaboration Foundations course covers this foundation in depth.
Mission / Purpose and Vision: why and where
The mission says why the organisation exists and for whom. The vision says what will be true when it succeeds. Both are only useful if they shape decisions.
- Harbourline’s mission: “We build and run the technology our clients depend on, as if it were our own.”
- Its vision: “By 2030, the IT partner mid-sized organisations trust most to build it right and keep it running.”
A simple test: when two options compete, does anyone ask which one serves the mission better? If not, the mission is decoration. Good looks like a mission used to make and explain decisions, and plans and priorities explicitly linked to the vision.
Principles: how to choose between two good things
A principle settles a recurring trade-off before it arises, such as speed against thoroughness or one client’s request against the standard service. Harbourline has four:
- Built to be run.
- One team from first conversation to steady service.
- Every handoff agreed on both sides.
- Decide where the facts are.
“Built to be run” tells a project team that a calm first month for the support team matters as much as the go-live date. Without it, every project manager makes that call differently. Good looks like principles used in decisions, with breaches addressed.
Values and Behaviours: what people actually do
A value is what the organisation cares about. A behaviour is what you can see someone do. Values only work when they are turned into behaviours people are held to, including behaviours the organisation will not tolerate.
Harbourline’s values are Care, Ownership, Openness and Learning. “Ownership” only becomes a behaviour when it is written as something you can see. One way Harbourline could write it: “the team that builds a service stays on call for it during its first 30 days”. The test of a value is whether it holds when results are good and the behaviour is not.
Strategy Deployment: from direction to work
Strategy Deployment turns direction into a few goals, each with an owner and a measure, and carries them down to every team. Progress comes back up, and what teams learn shapes the next revision. Hoshin Kanri, developed in Japanese manufacturing, calls this two-way exchange catchball: goals are passed down, discussed, adjusted and passed back, rather than simply announced.
Harbourline set nine goals for 2026 to 2028. Three of them show the pattern:
| Goal | Measure | From (2025) | To (2028) | Owner |
|---|---|---|---|---|
| Every new service is calm from day one | New services with a priority-1 incident in their first 30 days | 1 in 3 | 1 in 20 | Declan Moore |
| Let automation do the routine | Tickets resolved without a person | 8% | 40% | Tomás Reilly |
| A place people stay | Voluntary staff turnover | 21% | 12% | Helen Brandt |
The goals are clear and owned. The round 3 score of 42 says the gap is lower down: teams do not yet see what each goal means for their own work. That is a common finding, and lesson A9 shows how to act on it.
How the foundations fail together
The foundations lean on each other. A clear mission with weak Strategy Deployment produces agreement in the boardroom and confusion on the floor. Strong values with no principles leave good people making inconsistent calls. Good strategy with weak Structured Collaboration produces goals that each team pursues alone, while the work between them falls through.
What management can learn from software
- An architecture’s principles guide thousands of small design choices nobody escalates; an organisation’s principles do the same for daily decisions.
- A product roadmap only works when each team can trace its sprint back to it; a strategy only works when each team can trace its week back to a goal.
- Coding standards matter only when reviews enforce them; behaviours matter only when people are held to them, whatever their seniority.
Try it
Harbourline’s strategy
Choose Try the example, then Harbourline Services: its 2026 strategy, from nine goals to six objectives and the projects that carry them. It is free. Allow about 15 minutes.
- On the Goals tab, read the nine goals.
- On the Canvas tab, read the purpose, then pick one objective and follow it down through its strategies to its projects. Note who leads each one.
- Find one goal where you cannot see how a front-line team would know what to do differently. That is where a score of 42 comes from.
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
Why is Structured Collaboration the base of the foundations?
Question 2
Harbourline scores Mission 78 and Strategy Deployment 42. What does that tell you?
Question 3
“Built to be run” is a…
Question 4
What does catchball add to strategy deployment?
Question 5
A team leader cannot say which company goal their work supports. Which foundation is weak?
Catchball comes from Hoshin Kanri, the strategy deployment method developed in Japanese industry. 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.