Who Owns the Number? The Case for a Demand-Side Capacity Owner
Photo: Masato Kanda, CC BY 4.0, via Wikimedia Commons
Capacity planning is typically treated as an infrastructure responsibility. The infrastructure team monitors utilization, models growth, and provisions resources. When the forecast is wrong, the infrastructure team is asked to explain why. But the signals that determine demand rarely originate in the infrastructure team. They originate in product roadmaps, sales pipelines, marketing campaigns, pricing changes, and business-unit plans. The people who own those signals often have no formal accountability for the forecast that depends on them.
This is the asymmetry at the heart of capacity planning. The team accountable for the outcome does not control the inputs. The teams that control the inputs are not accountable for the outcome. The result is a forecast that is technically rigorous and commercially uninformed.
The Asymmetry at the Heart of Capacity Planning
Infrastructure teams are good at measuring what has already happened. They can show utilization trends, peak loads, and growth rates. They can model the cost of additional capacity. What they cannot do is know that a product launch will double sign-ups in a region, that a sales promotion will drive a spike in transaction volume, or that a pricing change will shift workload patterns.
Those signals sit with the demand side of the business. Product managers know the roadmap. Sales leaders know the pipeline. Finance knows the budget. Business-unit leaders know the operating plan. Without a formal mechanism to bring those signals into the forecast, the infrastructure team is left to extrapolate from history — a method that works until it does not.
Who Actually Sees Demand First
The demand-side view is distributed, but it is not mysterious. Product teams see feature launches and adoption plans. Sales teams see pipeline and seasonality. Marketing teams see campaign calendars. Finance teams see budget cycles and pricing decisions. Each group holds a piece of the demand picture.
The problem is that no one is responsible for assembling those pieces into a capacity forecast. The infrastructure team can ask for input, but asking is not the same as owning. When the input is late, incomplete, or optimistic, the infrastructure team has little recourse.
A Named Owner, Not a Committee
A committee is not enough. Capacity planning needs a named demand-side owner — a single leader who is accountable for collecting demand signals, reconciling them with the infrastructure forecast, and representing the business perspective in capacity decisions.
That owner does not need to be a technologist. The role is about demand, not infrastructure. The owner should sit close to the business planning process, have access to product and sales forecasts, and have the authority to challenge optimistic assumptions. The infrastructure team retains responsibility for supply-side modeling, cost analysis, and provisioning. The demand-side owner retains responsibility for the assumptions that drive the model.
This separation is important. It prevents the infrastructure team from being blamed for inputs it does not control. It also prevents the business from treating capacity as a technical detail that can be ignored until something breaks.
A Shared Forecast Cadence
The second requirement is a shared forecast cadence. Capacity forecasts should be reviewed on a regular schedule that matches the business planning cycle. A quarterly review is common, but fast-growing businesses may need a monthly cadence for critical systems.
The cadence should include three elements. First, a demand review: what has changed in the product, sales, and marketing plans? Second, a supply review: what is the current capacity position and what changes are planned? Third, a decision review: what actions are required, and who owns them?
The cadence should be documented and tied to existing planning processes, not run as a separate exercise. If the business already has a quarterly operating review, capacity should be part of it. If it has a monthly sales forecast, capacity should consume it.
Scenario Planning as a Discipline
Scenario planning is the third requirement. A single-point forecast is fragile. A scenario-based forecast is resilient. The demand-side owner should work with the infrastructure team to model at least three scenarios: a base case, a high-growth case, and a stress case.
The scenarios should be tied to specific business events, not abstract percentages. A high-growth case might assume a successful product launch in a new region. A stress case might assume a promotional spike combined with a delayed infrastructure delivery. The goal is not to predict the future; it is to understand the cost and risk of being wrong in either direction.
This is where scenario planning earns its keep. Overprovisioning is expensive, but surprise saturation is worse. A scenario-based approach allows the enterprise to make explicit trade-offs between cost and resilience rather than discovering them during an incident.
The Cost of Leaving the Seat Empty
The cost of leaving the demand-side seat empty is paid in two ways. The first is idle capacity: infrastructure provisioned for demand that never arrived, carrying depreciation, power, and support costs. The second is saturation: demand that arrived faster than the forecast, forcing emergency procurement, performance degradation, or both.
Neither cost is inevitable. Both are symptoms of a planning process that separates accountability from information. Naming a demand-side capacity owner will not make forecasting perfect. It will make the forecast honest. And an honest forecast is the minimum requirement for spending infrastructure dollars wisely.