Business Execution Canvas® Foundations · Lesson A1
Why good people struggle in poorly designed organisations
Most execution problems are design problems wearing a people costume. When the same failure keeps happening with different people in the seat, the cause is usually the system they work in, not the people. This lesson shows how to tell the difference, and why the Business Execution Canvas® exists.
The same problem, different faces
Every manager knows the pattern. A handover goes wrong, a client complains, and a meeting is called to find out who dropped the ball. Someone is coached, a checklist is added, and three months later the same thing happens again with someone else.
The instinct to look for a person is understandable. People are visible; the design they work inside is not. But a problem that survives a change of people is telling you something. It lives in the way the work is arranged, not in the people doing it.
Three signs point to a design problem rather than a people problem:
- It repeats. The same failure comes back after the people involved have changed.
- It sits at a join. It happens where work passes from one team, function, site or partner to another.
- Everyone is busy and nobody is wrong. Each team can show it did its part, yet the customer still got a poor result.
How organisations end up undesigned
Few organisations are designed as a whole. They grow a piece at a time. A team is added when demand rises, a function forms around a skill, a system is bought to fix one department’s problem, a firm is acquired and bolted on. Each decision makes sense on the day it is made.
What nobody designs are the joins: what passes between teams, to what standard and when; who owns the result from start to finish; how what the organisation learns gets back to the people who can act on it. Those gaps are filled by goodwill, escalation and heroics. That works until the organisation grows past the point where everyone knows everyone.
Harbourline: good at every step, poor at the joins
Harbourline Services · the fictional organisation used throughout the course
Harbourline Services, the fictional IT company used throughout this course, is a good example. It has 250 people in Cork, Kraków, Pune and Hartford. It builds software, connects systems and runs them for its clients under multi-year service contracts. It grew by buying a Kraków integration firm in 2022 and a Pune service-desk firm in 2023, then opened Hartford in 2024: three ways of working under one name.
In March 2025 a CRM go-live for a client, Calder General, went wrong over a weekend. The support team in Pune had no run-book and no monitoring for the new system. The client received US$250,000 in service credits and put its contract under review. In June, Northlight Financial, Harbourline’s largest client, complained of repeat incidents after each project handover. By the end of 2025, service credits and project overruns had reached US$0.9 million.
Nobody at Harbourline was careless. The project team delivered what it was asked to deliver. The service desk worked hard with what it was given. The problem sat at the join between them, the handover from a project to the people who would run it, and nobody had designed that join.
Update management, don’t replace it
The answer is not to throw out budgets, functions, managers and reviews. They exist for good reasons, and organisations that discard them usually rebuild them a year later under new names.
The answer is to add what traditional management leaves out: a design for how the parts fit together, made visible so people can see it, agree it and improve it. That is what the Business Execution Canvas does. It sits alongside the tools leaders already use to decide what to sell, and describes the organisation that has to deliver it.
What management can learn from software
- A large system works when each part has a defined interface; an organisation works when teams agree what passes between them. Telecom engineers learned this early, in switching systems such as Ericsson’s AXE. They were built from blocks that talked to each other only through defined interfaces, so each block could change without breaking the rest.
- Software is designed before it is built and tested before it ships; most organisations are reorganised without a design or a test.
- Good engineering teams fix the cause of a defect, not the person who reported it; good managers fix the design behind a repeat failure, not the person who happened to be holding it.
Is it the person or the design?
Before you act on the next problem that lands on your desk, ask four questions:
- Has this happened before, with different people involved?
- Does it happen where work passes from one team, site or partner to another?
- Does anyone own the result from start to finish, or only their own step?
- Would a new, capable person in the same seat do any better within a month?
Two or more answers pointing at the system mean you are looking at a design gap. Coaching the person will not close it.
Try it
Harbourline in the Builder
It is free and needs no account. Allow about 10 minutes.
- Read the canvas once without stopping, foundations first, then the five pillars from Understand to Adapt.
- Find Structured Collaboration among the foundations and read what Harbourline has written about how its teams hand work to each other.
Pause and think · your notes
Bring the lesson back to your own organisation.
Keep this note. Lesson A9 asks you to come back to it.
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
A handover fails three times in a year, each time with a different person involved. What is the most likely cause?
Question 2
Where do design problems most often show up?
Question 3
Harbourline’s 2025 go-live failure happened because…
Question 4
What does the Business Execution Canvas do to traditional management?
Question 5
Which of these is the strongest sign of a design problem?
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.
You have finished lesson A1
Keep your notes and progress
The whole course stays open and free. A free Structured Collaboration account keeps your notes, progress and check scores on every device, and the same sign-in works in every tool. What you have written on this device so far comes with you.
Already have an account? Sign in. No password: we email you a sign-in link.
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.