Execution feasibility

Capital feasibility is not about having a budget. It is about having an investment model that can move as execution learns, under governance that still holds.

Most organisations rely on an annual planning cycle to lock in priorities, budgets and delivery commitments. The budget is built, the portfolio is locked, projects are funded, and off the organisation goes. By year end I usually see two patterns. Some initiatives underspend because delivery could not absorb the work once reality hit, with dependencies, capacity shifts and delays. Others keep running because they were funded, not because the value case still stacks up.

That is not a budget problem. It is a funding model problem, and value has been left off the table. Annual funding assumes certainty, and there is nothing certain about execution. Execution is a system of learning.

So the feasibility test for capital is a single question: can your funding model respond to what execution is teaching you, so investment follows evidence and value rather than the original plan?

There is a maturity path here, and it is not agile versus traditional. It is about becoming more adaptable while keeping governance intact. It is also not linear. Most organisations run hybrids across investment types, and in many environments, the public sector especially, appropriation rules, gates, procurement and delegations constrain how far you can reasonably go.

Capital is one of the most misunderstood inputs to execution. When funding is locked to a certainty that does not exist, execution slows, value drifts, and the workforce pays the price.

Headcount is not your workforce capacity. What is left after BAU is.

Most execution plans assume people are available, focused and uninterrupted. Then everyone wonders why delivery slows, priorities slip, and their best people start to look like they are underperforming.

Leaders already know BAU competes with execution. The problem is not awareness, it is that governance does very little about it. And the reason governance does not act is simpler than it sounds: most organisations do not hold an integrated view of the resourcing required to deliver their strategic roadmap. Resourcing happens project by project, in isolation. Every project looks resourced in its own plan, while the same handful of people are stretched across several initiatives and BAU at once.

That is why one project leader cannot see the cumulative load on an individual, and why the individual usually will not raise it until they are already at breaking point.

There is a simple way to see what is happening in your system. Demand is the incoming work: projects, initiatives and the endless quick asks. Capacity is the people and time you think you have. Throughput is what you can actually deliver once BAU, meetings, dependencies and switching costs have taken their cut.

This is where governance most often fails. Leaders govern demand, because approving new work is a decision they are used to making. They do not govern throughput, so nobody protects flow. The result is not progress, it is bottlenecks. When everything is a priority, people do not move faster. They start more things, and starting more things is exactly how the system slows down.

Execution does not break because people do not care. It breaks because we keep feeding demand into a system that cannot absorb it, and the fix is system design rather than a heroic push.

Resistance is not a people problem. It is an absorption problem.

I have watched strategies stall not because they were wrong, but because the organisation was already at the redline. In my research a pattern kept surfacing: leaders consistently underestimated how constrained the organisation already was, made decisions as though capacity was infinite, and then the system choked. When uncertainty rose, the instinct was to add governance, which added drag to the very people who needed to be executing.

Every initiative consumes three things that never appear on a RAG status. Attention, because people can only hold so many priorities before none of them get any depth. Time, because BAU does not pause while a transformation runs. And emotional bandwidth, because adaptation is cognitive work even when people agree with the direction.

Stack initiatives without governing absorption and you get shallow adoption across all of them. What then shows up as resistance is usually exhaustion wearing a different label.

Most PMOs track projects, not people. Budget, milestones, RAG status, but not the cumulative change load landing on the same managers and frontline teams. That is the blind spot, and it is where execution quietly breaks down.

Change portfolio management is what solves this, and most organisations do not have it. It goes well beyond a heatmap. It asks what the cumulative load on people actually is, where changes are colliding rather than simply stacking, and whether the last round of change embedded before the next one launched. That is how good strategies die: not from one failed initiative, but from a portfolio of competing demands nobody is governing as a whole.

The executive move is straightforward. If the change load is red, sequence rather than stack. Make it a governance rule: no new initiative is approved unless you can show where it lands, who it hits, and what stops or shifts to make room.

Strategy execution rarely fails because the capability does not exist anywhere in the organisation. It fails because of how leaders make decisions about that capability under pressure.

The project budget gets stretched across more initiatives than it can carry. When something has to give, the project is not stopped. The execution capability around it is cut. Delivery orchestration is pared back. Change enablement is handed to the business. Business ownership is assigned on paper, and that person is pulled straight back into operations.

Each decision looks reasonable at the initiative level. Across the portfolio, the damage adds up. Technical capability gaps get the airtime and the specialist gaps get the budget, while the capabilities that actually determine whether any of it lands are treated as important but never critical. Until execution starts to drift.

In my experience five execution capabilities are non-negotiable, whatever the initiative is delivering: delivery orchestration, executive sponsorship, business ownership, change enablement, and domain expertise. Two of them, delivery orchestration and change enablement, can be sourced internally or externally. The other three cannot be outsourced. They have to be built and protected internally.

The distinction that matters most is between a capability being named and a capability being present. Protected means someone with the right skill, genuine capacity and the authority to be effective. Stretched means the skill exists but is shared across too many priorities, so quality erodes and responsiveness slows. Substituted means the role is filled but the capability is not, and it is the most common and least visible form of execution risk. Absent means nobody is assigned and the organisation is relying on the assumption that the business will absorb it.

Read the pattern across the portfolio, not initiative by initiative. One capability weak on one initiative is a resourcing decision. The same capability weak across most initiatives is a systemic gap. Several capabilities weak on one initiative means it was funded without a feasible execution plan. Several capabilities weak across the portfolio means strategy has outpaced execution capacity.

One leader in my research put it plainly: you can wish and you can dream, but if you do not have the capability to deliver on that ambition, you are just spinning your wheels.

The first four elements are only governable if leaders can see them. Execution infrastructure is the data, systems, standards and reporting that make feasibility visible across the portfolio rather than inside individual project plans.

This is the element that gets skipped, because it looks like a tooling conversation. It is not. Every feasibility question in this lever depends on it. Can your funding model respond to what execution is teaching you? Only if the data connects investment to evidence. Can you see cumulative people demand? Only if resource data aggregates beyond individual project plans. Can you govern the cumulative absorption of change? Only if change impact data is visible at portfolio level. Can you tell whether capability is protected or stretched? Only if capability coverage is tracked across initiatives rather than project by project.

Without that infrastructure, leaders are making portfolio decisions without portfolio-grade information. That is not a technology gap. It is an execution design choice, and it is usually an unexamined one.

Five dimensions determine whether the infrastructure is doing its job: portfolio visibility, data integration, methodology consistency, reporting standards, and whether the information reaching leaders is decision-grade. Each of them sits somewhere on a path from fragmented, through partial and connected, to genuinely governing.

The organisations that do this well do not simply have better tools. They have leaders willing to ask harder questions earlier, and infrastructure honest enough to answer them.

Start with the dimension scoring lowest and ask one question: what would it take to move one column to the right within the next quarter?