What Does It Take to Actually Deliver?
Why execution depends on finishing what matters, not simply keeping everyone busy.

Most organizations don’t lack initiatives.
They have strategic priorities, transformation programs, improvement projects, technology implementations and organizational change efforts.
And they’re often quite good at getting them started.
Energy surrounds a new initiative. Leadership communicates its importance. Teams mobilize. Plans are developed. Milestones are established. Progress starts appearing on dashboards.
But somewhere along the way, something happens.
The work continues. Meetings take place. Updates are provided. People remain busy.
Yet months later, the organization is still talking about what needs to be done.
The work is moving. But is anything actually being delivered?
As we move further into the final quarter of the year, I think that’s a question worth asking.
Organizations don’t struggle only because they lack good ideas, clear priorities, or committed people.
Sometimes they struggle because too much important work never makes it across the finish line.
And we don’t always make an important distinction.
Progress isn’t the same as completion. And completion isn’t always the same as delivering results.
We’re Often Better at Starting Than Finishing: What It Takes to Actually Deliver
Starting something new can be exciting.
A new strategy creates direction. A transformation initiative generates momentum. A new technology promises to improve how work gets done.
And people usually focus heavily on getting things underway.
But finishing requires a different kind of leadership discipline.
It requires making trade-offs when priorities compete.
It requires resolving issues that have been sitting between teams.
It requires maintaining attention when the initial excitement has faded.
And sometimes it requires acknowledging that the work we’ve been doing isn’t producing the results we expected.
That’s not always easy.
It’s often more comfortable to report progress than to confront what’s preventing completion.
It’s easier to launch another initiative than to make the difficult decisions needed to finish an existing one.
When organizations continually add new priorities without closing out existing commitments, the work underway grows faster than their ability to deliver it.
The result?
More activity. More coordination. More reporting.
But not necessarily more impact.
How much of your organization’s energy is going into starting things versus finishing them?
Activity, Output and Outcome Aren’t the Same Thing
One execution challenge is that we often use activity as evidence of progress.
We completed the workshops.
We held the meetings.
We developed the plan.
We launched the program.
And those things may all be necessary.
But they don’t necessarily mean we’ve achieved what we set out to accomplish.
I find it useful to distinguish between three things:
ACTIVITY → OUTPUT → OUTCOME
ACTIVITY: What are we doing?
These are the actions we take to move an initiative forward.
Meetings, planning sessions, project updates, training, analysis and implementation activities.
Activity tells us that work is happening.
But it doesn’t necessarily tell us whether that work is creating value.
OUTPUT: What have we delivered?
These are the tangible things produced through the work.
A new system. A redesigned process. A leadership development program. A delivered project. A new policy. An organizational structure.
Outputs matter. They’re often necessary steps toward achieving a larger goal.
But delivering something isn’t always the same as delivering the intended result.
OUTCOME: What actually changed?
This is where we begin to understand whether the work made a difference.
Did the new system improve productivity?
Did the redesigned process make it easier for customers to get what they need?
Did the leadership development program improve how people lead?
Did the culture initiative change what employees experience every day?
These are different questions from whether the project was completed.
And they’re often the most important.
An organization can successfully implement a new technology without improving performance.
It can deliver a leadership program without changing leadership behaviour.
It can complete a culture initiative without meaningfully changing the culture.
Finishing the work matters. But realizing the intended outcome matters more.
That distinction should shape how leaders define success, set accountability, and evaluate progress.
Finishing Requires More Than a Deadline
As year-end approaches, it’s tempting to focus on deadlines.
What needs to be completed before December?
Which milestones are at risk?
What’s behind schedule?
Those are reasonable questions.
But a deadline doesn’t necessarily create the conditions needed to deliver.
If the outcome is unclear, accountability is fragmented, or important decisions remain unresolved, simply increasing the pressure may not help.
In fact, it can create more activity without moving the organization any closer to the result.
Leaders can approach this differently.
Instead of asking everyone to work harder to finish everything, start by clarifying what actually needs to be delivered.
A simple framework can help.

1. DEFINE — What Does Done Actually Mean?
One reason important initiatives linger is that organizations aren’t always clear on what completion looks like.
Teams understand their activities.
They know their milestones.
They may even be able to tell you what percentage of the project is complete.
But can they clearly describe what success looks like?
What specifically needs to be true for us to say we've delivered this priority?
Consider a leadership development initiative.
Is it finished when the program has been delivered?
When participants have completed the training?
Or when leaders are demonstrating the behaviours the organization needs?
Those are very different definitions of success.
The same applies to technology implementations, product development, organizational redesigns, process improvements and culture initiatives.
If the intended outcome isn’t clear, organizations can spend considerable time delivering outputs without knowing whether they’ve solved the underlying business problem.
Leaders should be able to answer three questions:
What result are we trying to achieve?
What will be different when we’ve succeeded?
What evidence will tell us we’ve delivered?
This doesn’t mean every outcome will be fully realized by year-end. Some changes take longer to produce measurable results.
But leaders should know what needs to be completed now, what early evidence of impact they expect to see and what remains to be achieved.
If you can’t define what done looks like, it’s difficult to know when you’ve arrived.
2. OWN — Who Is Accountable for the Result?
Most important organizational priorities require people to work across functions, teams and areas of responsibility.
That’s necessary.
But it can also create a challenge.
Everyone has a role in the work.
Multiple leaders are involved.
Different teams own different pieces.
Yet when something gets delayed, it isn’t always clear who is responsible for getting things moving again.
This is where the distinction between participation and accountability becomes important.
Who is accountable for ensuring this actually gets delivered?
That doesn’t mean one person needs to do everything.
And it certainly doesn’t mean collaboration matters less.
It means someone needs to own the overall outcome.
Someone who can see the dependencies between teams.
Someone who knows which decisions are outstanding.
Someone who can spot when the work drifts away from its intended result.
And someone who can bring the right people together to resolve issues before they become bigger problems.
Accountability also needs the right authority.
Making someone responsible for delivering an outcome matters little if they can’t influence the decisions, resources, or priorities needed to achieve it.
Leaders need to ensure ownership is clear and that those accountable for delivery have the support and authority they need.
Shared effort is essential. Clear accountability is what keeps it moving.
3. DELIVER — What Must Happen Next?
This is where execution becomes practical.
As we near year-end, most organizations don’t need another comprehensive review of everything underway.
They need to know what will make the biggest difference in the time remaining.
For each important priority, I’d suggest asking:
What must happen in the next 60 days for us to say we’ve delivered?
Then work backward.
What decisions need to be made?
What dependencies need to be resolved?
What resources or capabilities are required?
What could prevent us from reaching the finish line?
And perhaps most importantly:
What needs to stop or wait so we can finish what matters?
This last question is particularly important.
Organizations often struggle to finish because they continue adding work without reconsidering existing commitments.
Every new initiative competes for the same leadership attention, resources and organizational capacity.
Finishing requires protecting the time and attention needed to deliver.
It also requires recognizing when something is no longer worth completing.
Not every initiative should cross the finish line simply because it was started.
Sometimes the right leadership decision is to stop work that no longer supports the organization’s priorities.
The objective isn’t to finish everything.
It’s to finish what matters and deliver the results that make a difference.
The Finish-Line Test
Here’s a practical exercise I’d encourage leadership teams to try.
Identify the three most important priorities to deliver before year-end.
Not every initiative underway.
Not everything people are working on.
The three priorities that will make the greatest difference to the organization.
For each one, answer four questions.
1. What does done look like? | Be specific about the outcome you’re trying to achieve. What needs to be completed? What needs to change? What evidence will demonstrate progress toward the intended result? |
2. Who owns the result? | Identify the person accountable for delivering the priority. Make sure they have the authority, support and visibility needed to do so. |
3. What could prevent delivery? | Look beyond the project plan. What decisions are outstanding? What dependencies remain unresolved? What competing priorities are creating pressure? Ask the people closest to the work. They often have the clearest view of what’s blocking progress. |
4. What’s the next critical action? | Not the next meeting. Not the next status update. The next action that will materially move the priority toward completion. |
Then ask one final question: If we met again in 60 days, what evidence would convince us that we actually delivered? | That question changes the conversation. Instead of focusing on how busy people have been, it shifts attention to what's been accomplished and the difference it's made. And it gives leaders an opportunity to intervene while there’s still time to make a difference. |
Finishing Is an Organizational Capability
I think there’s a tendency to view execution as something that happens after strategy has been developed.
Leadership sets the direction.
Teams develop plans.
Then the organization gets to work.
But execution isn’t simply the final step in the strategy process.
It’s an organizational capability.
It depends on how the organization sets priorities, makes decisions, coordinates work, and supports people.
It depends on whether the organization has the discipline to maintain focus when new opportunities emerge.
Whether people understand how their work contributes to the bigger picture.
Whether leaders remove obstacles instead of simply asking for more progress reports.
And whether accountability extends beyond completing activities to achieving meaningful results.
These are not just project management challenges.
They’re leadership and organizational effectiveness challenges.
Organizations that consistently deliver don’t simply have people who work harder. They’ve created the conditions that make delivery possible.
Leaders can deliberately build that.
Bringing the Execution Sprint Together
Over the past month, we’ve explored four questions that sit at the heart of strategy execution.
FOCUS: What Actually Matters?
When everything is a priority, nothing really is.
Leaders must choose where to direct the organization's attention and resources.
ALIGN: Does Everyone Know What Winning Looks Like?
A priority isn’t really a priority until the people doing the work understand what it means for them.
Strategy needs to translate into meaningful outcomes, contributions, and choices.
UNBLOCK: What’s Getting in the Way?
Sometimes people are already moving as quickly as the organization allows.
Leaders need to remove unnecessary friction, clarify decisions and make important work easier to accomplish.
FINISH: What Will It Take to Actually Deliver?
Progress isn’t the same as completion.
And completion isn’t always impact.
Leaders need to define success, establish accountability and maintain the discipline required to deliver meaningful results.
Together, these four questions reinforce something I believe is fundamental to organizational performance:
Strategy tells people where to go. Execution depends on whether the organization can get there.
And leadership has a responsibility to ensure the organization actually arrives.
The Question Worth Asking
As the year draws to a close, many leadership teams will be reviewing their progress.
They’ll look at dashboards, project updates, milestones and performance measures.
All of those things matter.
But the most important question may not be how much work we’ve done.
It’s what we’ve actually delivered.
What changed?
What improved?
What became possible that wasn’t possible before?
And what still needs to happen before we can genuinely say we’re finished?
Because execution isn’t ultimately measured by how much activity an organization generates.
It’s measured by the results it delivers.
And sometimes the most important leadership decision isn’t what to start next.
It’s what we’re going to finish.



Comments