

What Leadership Wanted, What the Team Built: Making Initiatives, Scope and Progress Visible
Leadership sets priorities. Teams plan and deliver the work. But somewhere between those two points, the connection can get lost.
People can be busy, initiatives can be progressing and reports can look reassuring — yet what gets delivered doesn't necessarily reflect what leadership intended.
The problem isn't always poor execution. Often, the organisation has lost visibility of what's happening between the original intent and the work being done.
In this free, live 60-minute session, we'll look at three common reasons this happens, why they matter, and some practical ways to address them.
This session draws on more than 20 years of working inside software delivery, including leading complex, multi-team initiatives. I'll use practical examples from that experience to show where things go wrong, what the consequences look like, and what can be done differently.
What we'll cover
1. Leadership intent isn't visible below the leadership team
How priorities that seem clear at the top can become less clear as they move through the organisation. Different people end up with different interpretations of what matters most and why.
The fix: Make priorities and their rationale explicit. Establish a shared view of initiatives, their intended outcomes, ownership, relative priority and the constraints that matter.
2. Scope drifts as work is broken down
How an initiative can change as it moves into planning and delivery. Work gets added, removed or expanded, sometimes without anyone having a clear view of the cumulative impact.
The fix: Make scope changes visible. Reconcile what was originally agreed with what is being planned and delivered, so additions, removals and changes are understood and their impact can be considered.
3. Progress reports say green, but the reality is different
How reporting based on activity or simple status measures can give leadership a reassuring picture without revealing the issues that matter. Problems surface late, often when they have already affected delivery expectations.
The fix: Report progress against the intended outcome, not just activity. Make confidence, changes, risks and decisions needed visible, and raise issues when they emerge rather than waiting for the next reporting cycle.
You'll leave with
A way to identify where the connection between leadership intent and delivery is breaking down.
Practical approaches to making priorities, scope and progress more visible.
A one-page Alignment Audit to help you assess your own environment.
A specific first action you can take away and put into practice.
Before the session
You can download the one-page Alignment Audit in advance. It's a working document we'll use during the session, so feel free to print it or have it open alongside Teams.
Download the Alignment Audit (PDF)
There's no need to complete it beforehand. You won't be asked to share your individual answers — it's there to help you reflect on your own circumstances.
Who should attend?
This session is aimed at people responsible for setting priorities, shaping initiatives or making sure delivery stays on track, including:
CTOs, CPOs and other technology or product leaders
Heads of Product and Engineering
Product Managers and Product Leaders
Engineering Managers and Technical Leads
Delivery Managers and Programme Leads
Whether you're responsible for setting direction, managing delivery or reporting progress, the session should give you something practical to take away.
Format
60 minutes, live and online via Microsoft Teams.
A mix of presentation, anonymous polls and practical reflection.
Opportunities to ask questions and join the discussion.
No requirement to turn your camera on.
The session will not be recorded.
You'll receive the Teams joining details after registering.
If you register but can no longer attend, please cancel your place so someone else can take it.
About the host
I'm Gary Joyce, Founder and Principal Consultant at Predictable Progress.
I work with product and engineering teams to make software delivery visible, align priorities and ensure that what gets built reflects what the business actually needs.
I've spent more than 20 years working in software delivery, including leading complex, multi-team initiatives where dependencies, competing priorities and delivery expectations need to be brought together.
Predictable Progress helps organisations get a clearer view of what's happening, what's getting in the way, and what needs to change.
Website: https://www.predictableprogress.co.uk
Code of Conduct
This is intended to be a constructive, inclusive and respectful discussion.
Everyone attending is expected to:
Treat other participants with respect, regardless of their role, experience, background or point of view.
Challenge ideas and approaches constructively, without making personal remarks or attacks.
Give others space to contribute and avoid dominating the discussion.
Avoid discriminatory, harassing, abusive or intimidating behaviour.
Respect the confidentiality of examples and experiences shared by other attendees. Please don't attribute comments to individuals or share identifiable details outside the session without their permission.
Keep contributions relevant to the session and avoid unsolicited promotion or selling.
The host reserves the right to remove anyone whose behaviour is disruptive, disrespectful or otherwise inconsistent with this Code of Conduct.
By registering for and attending the session, you agree to follow these guidelines.