When Capacity Changes, Which Initiative Should Move First?

When delivery capacity shrinks, leaders need explicit criteria for deciding which commitments take precedence.
We had two release pipelines, the paths through which product changes reached customers. One was committed to a compliance effort for several weeks. That squeezed the remaining release capacity to one release per product during the affected period.
The products still had delivery targets. They now had fewer opportunities to reach them.
I pulled together an emergency release window meeting to review the conflicts and delivery targets. The most important discussion was how we would decide which commitments took precedence.
What should determine priority when everything cannot fit?
Potential revenue was part of the discussion. So were contracted engagements.
In this case, contracted engagements took precedence.
An opportunity to generate revenue and an obligation already made to a customer carry different consequences if delivery moves. We needed to consider those consequences and agree on the criteria for resolving conflicts.
That decision reflected the circumstances we were managing. In another situation, a regulatory deadline, operational exposure, or time sensitive opportunity could warrant a different choice.
An illustrative starting order might be:
Regulatory obligations with fixed deadlines.
Contracted customer commitments.
Opportunities whose value depends on a specific delivery window.
Potential revenue without a firm timing obligation.
That ordering requires judgment. Leaders still need to examine the consequences, available alternatives, and dependencies before deciding. Its purpose is to give the discussion a shared starting point.
Find the constraint that limits delivery
Teams can have capacity to develop work while the organization has limited capacity to release it.
That was the issue here. With one pipeline occupied by compliance work, the remaining release opportunities became the constraint.
Looking only at team capacity would have missed the decision we needed to make: which delivery targets could fit into the available release windows, and which would need to change?
Portfolio decisions need to account for the full path to delivery. Development progress alone does not establish that a commitment can be met.
Make the decisions visible
The meeting resulted in a business unit wide email communicating its outcomes. That gave the broader organization visibility into the decisions and their implications for delivery.
A priority decision affects people beyond those in the room. Product leaders, delivery teams, and stakeholders need a shared understanding of what takes precedence and what that means for their plans.
If the release sequence changes but expectations remain untouched, the conflict continues elsewhere in the organization.
Keep priorities current
The emergency meeting became a recurring priorities meeting held every six weeks, which I led to review and validate changes in priority.
The immediate result was broader communication of the decisions. The lasting change was a recurring forum for reviewing priorities as circumstances evolved.
For leaders establishing a similar cadence, urgent changes also need a route to an earlier decision. A threatened regulatory deadline, contracted delivery date, or release dependency should trigger review by the accountable decision owner before the next scheduled meeting.
The regular meeting provides a checkpoint. The escalation path allows decisions to happen when circumstances require them.
Three questions to guide the discussion
When capacity changes, start with:
What is the actual constraint? Identify the release window, capability, decision, or dependency limiting delivery.
What happens if each commitment moves? Make the business consequences explicit.
What criteria determine precedence? Establish a shared basis for resolving conflicts.
Then communicate the decisions and establish when they should be reviewed.
When the portfolio can no longer deliver everything as planned, leadership needs to decide which commitments to protect and how the remaining expectations must change.
That is where priorities become an executable delivery plan.
Competing commitments and constrained delivery capacity? Explore NBD’s Executive Delivery Alignment Sprint to establish shared priorities and resolve delivery tradeoffs.
About the Author
Duane L. Nicholson is the founder and Chief Transformation Officer of NBD Consulting Services, helping leaders connect strategy, product, technology, and delivery.


Comments