The Graveyard of Good Ideas
Every leadership team has them. The whiteboard full of initiatives. The offsite that generated 47 action items. The strategic plan that everyone agreed was brilliant — and that nobody quite executed.
Good ideas are not the bottleneck. In most organisations, there are far more good ideas than the organisation can act on. The problem is what happens between the idea and the outcome.
The gap is not a strategy problem. It is an execution problem. And the way most leaders try to solve it makes it worse.
—
Why Checking In More Doesn’t Work
When execution stalls, the instinctive response is more control. More check-ins. More status updates.
This feels like accountability. It is not.
What it creates is compliance. People deliver to the deadline because someone is watching — not because they own the outcome. The moment the oversight relaxes, so does the progress. You wanted to create accountability. But you have built dependency.
There is a deeper problem with this approach. When the manager becomes the one holding the project together — through reminders, follow-ups, and pressure — the ownership has shifted. It now sits with the person doing the checking, not the person doing the work. The person executing is now working for someone else’s agenda, not their own. That is the opposite of what you want.
—
The Shift: From Holding People Accountable to Holding People Capable
Brian Moran, in his work on execution and ownership, draws a distinction that most leaders miss.
“Holding people accountable” puts the emphasis on the consequences of non-delivery. It implies a one-way relationship: the manager sets the expectation, monitors for compliance, and applies pressure when the target is missed. The ownership lives at the top.
“Holding people capable” shifts the frame entirely. The assumption is that the person doing the work is — or can become — genuinely capable of owning it. The role of the leader is not to watch and judge, but to equip and support.
This is not soft management. It is a harder discipline than constant follow-up. Holding people capable means asking: What does this person need to succeed? What is blocking them? What support, resource, permission, or mindset shift would make the difference?
It requires the leader to do less controlling and more enabling.
—
What Capability Actually Requires
Ownership is not something you can demand. You can demand compliance. You can demand a report. You cannot demand that someone genuinely cares about an outcome.
Ownership grows when people:
Feel they have the means to succeed. Not just the task, but the tools, time, information, and authority to make it happen. Many people fail at execution not because they are disengaged, but because no one gave them access to what they actually needed.
Feel they have the skills. Delegation without development is a trap. If someone lacks a capability — whether technical, relational, or self-regulatory — the answer is not to watch them more closely. The answer is to build that capability. This might mean coaching, pairing with someone more experienced, breaking the task down differently, or naming the skill gap honestly.
Feel they have permission to own it. This is the subtler one. Many organisations talk about ownership while operating systems that punish failure, discourage initiative, and require approval for every minor decision. People learn quickly whether they are really trusted to lead — or just expected to execute instructions.
Have access to their own resources. This last point is less obvious but worth naming. People often have more capability than they are using. Self-doubt, unclear expectations, fear of getting it wrong — these are not competence gaps. They are internal blockers that good support can unlock. A conversation that asks “what’s stopping you?” is often more productive than any amount of pressure.
—
The Supporting Check-In vs. The Controlling Check-In
There is nothing wrong with regular check-ins. The question is what kind.
A controlling check-in asks: Have you done what I asked? Where is the report? Are you on track? It positions the manager as the standard and the person as the subject of evaluation. If the news is bad, the conversation goes sideways.
A supporting check-in asks: What progress have you made? What’s making it hard? What do you need from me? It positions the leader as a resource — someone who holds the person capable of solving the problem, and is there to help remove obstacles, not to apply pressure.
The external behaviour can look similar. The internal dynamic is completely different — and people can always tell the difference.
—
What This Means for Founders
Founders are particularly prone to the controlling check-in pattern — not because they distrust their people, but because they are used to making things happen through personal effort. When something matters, they get involved. When a project stalls, they step in.
This works at the beginning. It does not scale.
As a founder, your job is to build an organisation that executes without you. That means transferring not just tasks, but ownership. And ownership cannot be transferred through pressure or proximity. It transfers through trust, capability, and the right kind of support.
The organisations that execute well are not the ones where leaders check in the most. They are the ones where people genuinely own outcomes — because they have the means, the skills, the permission, and the support to do so.
Good ideas are easy. Execution requires the conditions for ownership. Build those conditions, and the execution will follow.
—
The Question to Start With
Before your next project review, ask yourself: Am I holding this person accountable — or holding them capable?
If you are doing most of the remembering, most of the following up, and most of the worry — the ownership is with you. And that is a design problem, not a performance problem.
—
Author | Andreas Wettstein
