When execution struggles, organisations often respond by asking people to try harder — more follow-up, reporting, governance, or accountability.
Sometimes effort is the issue, but often it’s not. Execution is shaped by design.
Consider a team responsible for an important outcome but dependent on six other groups, or a product leader accountable for results yet unable to influence funding, or a programme with twenty priorities all labelled critical. Or an organisation where decisions routinely travel upward because authority was never clearly defined. People can work very hard in these systems and still struggle to deliver.
This is why execution should be designed, not just managed. Good execution requires conditions like clear priorities, visible ownership, sensible decision rights, manageable dependencies, access to necessary capabilities, quick feedback, and leadership willing to trade off when reality shifts. None guarantee success, but their absence makes execution harder.
The best teams are often not those with complex processes, but those where everyone understands the goal, knows who decides, and sees how their work links to the overall outcome. Sometimes, adding another governance layer worsens execution. Governance should improve decisions; if it mainly increases reporting, waiting, and escalation, it harms instead.
Before questioning why progress is slow, observe the environment around the work — where does work pause, which decisions delay, where are priorities conflicting, which dependencies are structural, and what information reaches decision-makers too late?
Execution issues often leave clues; organisations just need to look in the right places.