Business Execution Canvas® Foundations · Lesson A5
Articulate
Articulate is the second pillar: making sure what the organisation knows about its customers reaches everyone who acts on it, inside the organisation, along the value chain and out to customers and other stakeholders. Knowledge that stays with sales is knowledge the rest of the organisation works without.
Three directions
| Component | Who needs to understand customer needs | Good looks like |
|---|---|---|
| Internally | Every level, from executives to the front line | Everyone understands the customer factors that affect their role, and work is aligned to meet them |
| Across | Everyone along the value chain, team to team and out to partners | Teams and partners agree what they need from each other at the main handoffs, and are measured on it jointly |
| Externally | Customers and wider stakeholders, such as regulators, investors and the market | Customers understand how the service helps them, and what is said is tested with them and refined |
The three directions fail in different ways. Internally fails when customer insight stays with customer-facing staff. Across fails at the handoffs, where one team knows what the customer needs and the next team only receives a specification. Externally fails when the organisation talks about what it sells rather than what the customer gets.
Across: where Harbourline is weakest
Across is Harbourline’s weakest component, at 34 in round 3, and the one where its managers disagree most. Executives score it 49; team leads score it 20.
| Component | Harbourline, round 3 | Change since the baseline |
|---|---|---|
| Externally | 74 | +4 |
| Internally | 55 | +9 |
| Across | 34 | +17 |
The gap shows up in one number from Harbourline’s sales process: 1 in 4 deals was sold without delivery’s sign-off. The account team knew what the client needed; the delivery team heard about it after the contract was signed. Every promise made that way becomes a handoff problem later.
Across also moved most, up 17 points since the baseline. Most of the gain came after the March 2026 operating model put a handoff agreement on every team canvas. That is the cause the sample report suggests testing, not a proven fact, but it is the right kind of evidence: a design change followed by a real change in the score.
Why executives and team leads see it differently
A 29-point gap between executives and team leads is a finding in itself. Executives see the agreements that exist on paper. Team leads live with the handoffs every day and see where they still break. Neither group is wrong; they are looking at different parts of the same system.
The practical step is to ask team leads which two handoffs cause the most escalations or meetings, and whether each has agreed expectations on both sides. The answer usually tells you where to start.
Making articulation work
- Say it in the receiver’s terms. A service desk needs to know which client systems are critical and when, not the contract’s value.
- Agree both sides of every critical handoff. What is handed over, to what standard, by when, and what the receiver needs to do its job.
- Include partners. Harbourline’s partners do not want to hear about an escalation from the client first.
- Check it landed. A briefing given is not a briefing understood; ask the receiving team to play it back.
What management can learn from software
- An interface contract is agreed by both the system that calls and the system that answers; a handoff is agreed by both the team that gives and the team that receives.
- Requirements that live only in a product manager’s head get built wrong; customer insight that lives only in sales gets delivered wrong.
- Integration tests catch the breaks between components that unit tests miss; team-to-team reviews catch the breaks between teams that team reviews miss.
Try it
Harbourline’s team canvases
Choose Try the example: Harbourline’s project-to-service handoffs, with team canvases for Bids and Proposals, the Kraków Salesforce practice, Service Transition and the Pune Service Desk, and every handoff checked from both sides. It is free. Allow about 15 minutes.
- On the Teams tab, read the interface map. Rows supply, columns receive; a tick means the handoff is recorded on both teams’ canvases.
- Open the Bids and Proposals canvas and find what it hands over to the Salesforce practice and to Service Transition.
- Find the handoff marked with a question mark: needed by the receiving team, but not confirmed by the team that supplies it. Which two teams is it between, and what could go missing?
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
Customer insight reaches every team, but partners only receive orders. Which component is weak?
Question 2
“1 in 4 deals sold without delivery’s sign-off” is a symptom of…
Question 3
Executives score Across 49 and team leads 20. Who is right?
Question 4
What makes a handoff agreement real?
Question 5
Across rose 17 points after the new operating model. What should Harbourline conclude?
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.