When Good Initiatives Compete for the Same Capacity

Executive Summary

The previous article examined implementation pressure — the organization's total capacity to absorb change across everything underway at once. This article looks at a narrower, related question: not the aggregate strain, but which specific initiatives are quietly drawing on the same specific scarce resource.

Most strategic planning processes are built to answer a single question well: is this initiative worth doing? Business cases are built, returns are modeled, risks are assessed, and a decision is made. What these processes are far less built to answer is a second, quieter question: what else, already underway or already approved, is this initiative about to compete with — not for budget, necessarily, but for the executive attention, specialist expertise, governance capacity, and organizational credibility that determine whether it actually gets done well? This article is about that second question, the resources it concerns, and why the competition between good initiatives is so often invisible until it has already degraded the outcome of more than one of them.

A pricing change, a product overhaul, and the patience neither business case counted

A B2B software company undertakes two initiatives at once: a significant redesign of its onboarding and customer success experience, aimed at reducing churn among mid-market customers, and a shift to usage-based pricing, requiring renegotiated contracts with its twenty largest enterprise accounts. Both decisions are sound on their own terms. The onboarding redesign responds to real, well-documented churn data. The pricing shift addresses a genuine mismatch between how customers actually use the product and how they are billed for it.

Both initiatives, reviewed separately, had their resourcing needs modeled carefully: product and design capacity for the onboarding work, legal and commercial capacity for the pricing negotiations. Neither business case flagged a conflict, because on paper, they don't compete for the same people or the same budget line.

What they compete for is something neither business case had a line item for: the patience and goodwill of the same handful of large customers whose engagement both initiatives depend on. The account teams need those customers' willingness to sit through detailed pricing renegotiations, at exactly the moment the product team also needs their willingness to trial and give feedback on a substantially changed onboarding flow. Neither ask, on its own, is unreasonable. Both, arriving in the same quarter, ask the same relationship for more attention and tolerance than it may have to give.

Neither initiative is under-resourced in the conventional sense. Both have adequate budget and adequate specialist staff. What is scarce, and was never modeled as scarce, is the finite willingness of a small number of customers to engage deeply with the company twice in the same period. A few months in, renewal conversations with two of the twenty accounts have grown noticeably harder — not because either initiative failed on its own terms, but because the same customers were asked to absorb two significant asks at once, and their patience, reasonably, ran short.

The resources that don't appear on a resourcing plan

The acquisition-and-modernization example illustrates something worth naming precisely: the resources initiatives compete for are considerably broader than the ones organizations typically model. Budget and specialist headcount are the two resources almost every business case accounts for, because they are the two that are easiest to quantify. But a much longer list of genuinely scarce organizational resources rarely makes it into any planning document at all:

**Executive attention** — not simply the hours a senior leader has available, but the sustained, high-quality focus a genuinely difficult judgment call requires, which is a considerably scarcer thing than calendar availability.

**Specialist expertise that exists in only a handful of people** — the individuals who understand a legacy system, a regulatory nuance, or a customer relationship well enough that no amount of additional headcount substitutes for their specific judgment.

**Governance capacity** — the bandwidth of steering committees, investment boards, and approval bodies to give each decision the scrutiny it deserves, rather than rubber-stamping it because the agenda is already full.

**Organizational credibility** — the finite goodwill a change programme can draw on before an organization's tolerance for further disruption runs out, regardless of how well-justified each individual disruption is.

**Political support** — the sponsorship and backing of influential stakeholders, which is not infinitely available to every initiative that could use it, particularly when several initiatives need the same sponsor's visible commitment at the same time.

**Decision-making bandwidth** — the organization's capacity to make good decisions quickly, which degrades when too many consequential choices are competing for attention in the same window, independent of how capable any individual decision-maker is.

**Customer attention** — relevant especially where multiple initiatives each require some engagement from the same customers or partners, whose patience and willingness to participate is not unlimited.

**Operational stability** — the baseline of predictable, well-functioning operations that gives an organization room to absorb change, which is itself consumed as multiple initiatives simultaneously ask parts of the business to operate differently than they did before.

None of these appear on a conventional resourcing plan, because none of them are easily quantified in the way budget and headcount are. That doesn't make them less real. It makes the competition for them considerably harder to see coming.

How this differs from implementation pressure

It's worth being precise about how this relates to implementation pressure, discussed in the previous article, because the two are closely related and easy to conflate.

Implementation pressure is about the organization's *total* capacity to absorb change across everything underway — a single, cumulative measure of overall strain. Resource competition is a more specific question: not how much pressure the organization is under in aggregate, but which *particular* initiatives are drawing on the *same specific* resource, and whether that overlap was ever deliberately examined. An organization can have ample overall implementation capacity and still have two initiatives quietly competing for the one specialist who understands a particular legacy system, or the one executive whose sponsorship both genuinely need. The aggregate pressure might look entirely manageable while a specific, narrow bottleneck between two particular initiatives goes unnoticed.

This distinction matters practically. Reducing overall implementation pressure — by phasing initiatives, adding capacity, or slowing the overall pace of change — does not automatically resolve resource competition, because the competition may be for something that doesn't scale with overall capacity at all. You cannot create a second CFO with the specific institutional knowledge the acquisition and the modernization effort both need, no matter how much you reduce the organization's total change burden elsewhere.

Four places this shows up beyond the obvious

The acquisition-and-modernization scenario is one version of this pattern. It recurs in several other executive contexts, each drawing on a different one of the resources listed above.

Two **transformation programmes relying on the same executive sponsors** often collide not because their objectives conflict, but because both were designed assuming the sponsoring executive's full, engaged attention at the moments each programme's most difficult decisions arise — moments that, when both programmes are underway simultaneously, frequently land in the same quarter, drawing on a form of engagement that cannot simply be split in half without both programmes receiving a diminished version of what their design assumed.

**AI initiatives and cybersecurity investments** increasingly compete for the same underlying specialist expertise — the relatively small population of technical professionals who understand both the organization's data architecture and the security implications of exposing it to new AI capabilities. An organization can fund both initiatives generously and still find both constrained, because the constraint was never funding; it was the number of people qualified to do either piece of work well, a number that doesn't expand simply because both initiatives have healthy budgets.

**Multiple regulatory programmes drawing on the same governance functions** create a particular strain on a resource easy to overlook: the legal, compliance, and audit functions responsible for providing sign-off across every regulatory initiative the organization runs. Each individual programme's governance requirement looks modest in isolation. Several running concurrently can quietly overwhelm the governance function's capacity to give any single one the scrutiny it deserves, a strain that shows up not as an obvious bottleneck but as gradually declining rigor across all of them.

**Strategic initiatives competing for limited investment funding over several years** reveal a longer-horizon version of the same pattern. An organization may approve several multi-year initiatives independently, each fitting comfortably within the current year's budget. The competition only becomes visible several years later, when all of them reach their most capital-intensive phase simultaneously, competing for a pool of investment capacity that was never modeled as shared, because at the time each was approved, the others' future funding needs weren't yet part of the conversation.

Naming this deliberately, rather than discovering it in hindsight

The common thread across all of these examples is not that any individual initiative was poorly conceived. It is that the strategic planning process which approved each initiative separately never asked the specific question this article has been building toward: given everything else the organization has already committed to, what scarce, often unquantified resource does this new initiative draw on, and is that resource already being drawn on by something else?

This is precisely the kind of question the perspective this series has been describing is built to surface. Sequencing, examined earlier in this series, asks what order decisions should be made in. Strategic dependencies ask what a commitment quietly requires of the organization afterward. Implementation pressure asks whether the organization's total capacity for change is being exceeded. Resource competition completes this picture by asking a more specific question still: across everything currently underway or under consideration, which particular initiatives are quietly drawing on the same particular scarce thing — attention, expertise, credibility, sponsorship — regardless of how sound each initiative looks when evaluated entirely on its own.

Together, these four mechanisms describe a single underlying idea from four different angles: that a strategic decision's consequences extend well beyond its own stated objectives, into the shared, finite resources — some obvious, many not — that other equally sound decisions are also quietly relying on.

Making the competition visible before it accumulates

In practice, surfacing resource competition deliberately means asking, at the point any significant initiative is being approved, a question that rarely appears explicitly in a business case template: beyond budget and headcount, what does this initiative need from the organization that other initiatives, already underway or already committed, are also relying on? For a small number of initiatives, this is a question a leadership team can work through directly, provided someone is explicitly tasked with holding the full picture across initiatives rather than assuming any one sponsor will naturally see it.

As the number of concurrent strategic initiatives grows, and as the resources in question become less tangible than budget or headcount — executive attention, specialist judgment, governance capacity, organizational credibility — this becomes considerably harder to track through discussion alone, because these are precisely the resources least likely to appear on any existing plan.

Cascade Engine, the implementation of Decision Space Analytics discussed throughout this series, is useful here in a specific way: given a set of strategic initiatives an organization is running or considering, it helps a leadership team compare how alternative combinations and timings draw on the same underlying resources — including the less tangible ones this article has focused on — making visible, before commitments accumulate, which initiatives are quietly relying on the same scarce thing. The purpose is not to produce a definitive allocation of which relationship absorbs the next difficult conversation; that judgment belongs to the leadership team. The purpose is to make the competition specific and visible enough to be part of the conversation when initiatives are approved, rather than something discovered only once two programmes are already underway and both quietly underperforming for reasons neither one's own status report can explain.

---

Key Takeaways

- Most strategic planning evaluates whether an initiative is worth doing. Far fewer processes ask what scarce, often unquantified resource it will draw on that other current initiatives are also relying on.

- Resource competition extends well beyond budget and headcount to include executive attention, specialist expertise, governance capacity, organizational credibility, political support, decision-making bandwidth, customer attention, and operational stability — none of which typically appear on a conventional resourcing plan.

- This is distinct from implementation pressure: implementation pressure measures total organizational strain in aggregate, while resource competition asks which specific initiatives are drawing on the same specific scarce resource, a narrower question that can go unnoticed even when overall capacity looks adequate.

- The pattern recurs across a wide range of executive situations — shared executive sponsors, overlapping specialist expertise between AI and cybersecurity initiatives, shared governance functions across regulatory programmes, and shared long-horizon investment capacity across multi-year initiatives.

- None of the initiatives involved need to be poorly conceived for this competition to emerge; the gap is that no part of the standard planning process asks what an initiative draws on beyond its own explicitly modeled resourcing needs.

- Cascade Engine helps make this competition visible and comparable across alternative combinations and timings, before commitments accumulate to the point where the competition can only be discovered in hindsight.

---