A portfolio can contain sound individual proposals and still make promises the organization cannot keep together. Assessing each business case separately leaves a consequential question unanswered: which existing commitments will lose access to the people, decisions or systems that the next initiative needs?
The difficulty emerges in delivery. The same specialist appears in several plans. Different sponsors need decisions from the same executive. Teams begin work before dependencies are ready, then revisit it when an answer changes. The portfolio becomes an argument over access to scarce capacity.
At OutcomesLab, we call this Dilution Drag: commitments begin to weaken one another as they compete for shared resources and attention. Project count alone is a poor guide. The useful question is which commitments interact, where they meet a constraint and what happens to the work already there.
The proposal is only half the decision
A conventional business case asks whether an initiative is attractive. It may estimate benefits, costs and risks carefully. Yet the people and decisions required to deliver it can also be promised elsewhere. An affordable proposal can therefore be operationally unfunded.
Consider an illustrative portfolio in which several teams require the same data specialist to prepare tests. Each plan allows a small share of that person’s time. Together, the shares exceed the time available. Hiring another generalist does not necessarily resolve the constraint. Until the specialist can complete an input, other team members either wait, make assumptions or switch to different work.
Counting projects would miss the constraint in this example. Two independent initiatives may coexist comfortably, while two dependent initiatives compete intensely for one decision maker or specialist. Leaders need to test the demands on shared capacity before deciding how many priorities the organization can sustain.
Richard Rumelt argues that a list of aspirations is insufficient as strategy: a diagnosis and guiding policy must lead to coordinated action. Applied to a portfolio, coordination means asking whether the approved actions can coexist. A set of initiatives does not become executable merely because each has an executive sponsor.
How another commitment changes existing work
An additional priority can create several kinds of pressure. Distinguishing them matters because their remedies differ.
Shared capacity becomes contested. A person’s time, a testing environment or a review function may already be committed. The new request takes a place in the same workload. The cost is not confined to the new initiative: another commitment may lose access to the resource when its plan expected it.
Unresolved choices move into delivery. Sponsors may agree on broad objectives while disagreeing about which outcome takes precedence. When two deadlines collide, teams must seek a decision or negotiate a compromise. A portfolio choice that leaders avoided returns as a delivery dispute, often when changing direction is more expensive.
Work is started before it can be completed. Teams may begin an activity to demonstrate progress, even though a prerequisite remains unsettled. A later answer can invalidate the assumption, creating rework. The issue is not simply that people are busy; it is that the sequence of commitments does not allow them to finish reliably.
Attention is consumed by renegotiation. Progress meetings become negotiations over borrowed staff, competing dates and exceptions. That time may be necessary under the circumstances, but it is part of the cost of the portfolio. Reporting more frequently will not resolve the underlying competition unless someone can change the commitments.
These pressures can reinforce one another. A delayed decision changes a team's schedule; that change conflicts with another team's booking of a specialist; the conflict requires another executive decision. A seemingly small initiative can therefore create coordination work well beyond its own team. Look for those connections in the actual flow of work before deciding what to cut.
Use a Priority Load Test
Before approving another material commitment, map what it needs against the existing portfolio. The proposed OutcomesLab Priority Load Test makes that comparison explicit. It is a practical discussion about promises made to scarce resources, rather than a score intended to declare the portfolio healthy or overloaded.
Start with a specific outcome and the period in which it is needed. Identify the people, decisions, systems and approvals that could prevent completion. Do not stop at the project’s nominal budget or team. Include a specialist borrowed from another function and an executive whose timely decision is assumed.
For each constraint, ask what is already committed and when that demand will arrive. An average allocation across the year can hide several initiatives needing the same resource in the same two weeks. Ask the resource owner and the people doing the work to check the timing together.
Next, identify the displacement. Which existing outcome would receive less support if this proposal began? Would a deadline move, a scope shrink or a quality risk increase? If the answer is “nothing,” test whether capacity is actually available or merely absent from the planning document.
Finally, record the choice. Approve with a funded capacity change, defer until a dependency clears, reduce scope or stop something else. Give the decision an owner and communicate it to affected teams. An instruction to “find a way” transfers the trade-off into delivery without resolving it.
Greg McKeown, in Essentialism: The Disciplined Pursuit of Less, emphasizes deliberate selection of the work that deserves time and effort. The organizational application is concrete: declining or deferring a worthwhile proposal can protect a more consequential commitment. Its value does not disappear; its place in the sequence changes.
Watch the work, not just the priority list
A shorter list is useful only if demand on the constraints changes. Merging six projects under one program name does not release a specialist. Removing a slide does not cancel a request. Confirm what has actually stopped and whether the freed capacity reaches the intended work.
Use a few observable signals. How long does work wait for the shared resource? How often are agreed dates renegotiated? How much work returns because a prerequisite changed? Can teams identify who decides when commitments conflict? A worsening signal is a reason to investigate, not proof of dilution: poor quality, unexpected demand or a missing skill may be the real cause.
Review completed outcomes alongside work in progress. An initiative that produces many updates but cannot reach a usable result may be under-resourced, badly sequenced or based on an unsound premise. Those explanations require different decisions. Avoid turning every delay into a request for more capacity.
Roger L. Martin argues that strategic capabilities require systems that build and maintain them, part of the management discipline in Playing to Win: How Strategy Really Works. In a portfolio, that calls for a recurring allocation process with authority to revise commitments. The choices made in a planning workshop must survive the next attractive request.
When more priorities are reasonable
The strongest objection to subtraction is that an organization has several legitimate responsibilities. Independent teams may have genuinely separate capacity. A regulated activity cannot simply be postponed to improve a commercial project’s schedule. Resilience may require alternatives, and exploration may require several small experiments rather than a single large commitment.
The test should accommodate these differences. Protect essential obligations explicitly. Distinguish bounded experiments from commitments to scale. Identify genuinely independent resources rather than assuming all initiatives compete equally. Reducing the portfolio indiscriminately can destroy options or leave useful capacity idle.
Rita Gunther McGrath describes discovery-driven planning as a way to examine assumptions at checkpoints before deepening commitment. That provides a useful alternative to approving a full program or rejecting an uncertain opportunity outright. A limited experiment can earn the next allocation through evidence. It still needs explicit capacity and an end point; “pilot” should not become a permanent exemption from portfolio discipline.
Make the next approval a real choice
The next approval should identify the commitment it changes, not simply add another claim to the portfolio. Make that change visible to the people whose schedules and decisions depend on it.
At review, check whether the affected work can finish more reliably and whether the displaced work incurred an acceptable cost. That comparison tests the allocation decision rather than merely celebrating a shorter list.
The Focus Multiplier examines what concentrated effort can build over repeated cycles. Dilution Drag comes one decision earlier: can the organization honor the commitments it already has? A new priority earns its place when leaders can show where its capacity will come from and accept the trade-off that follows.