Operational capacity
Also known as Run capacity, Operations capacity
Definition
Operational capacity is the portion of a team's available capability used for support, incidents, maintenance, reliability, releases, and other work required to operate a service. It is part of real capacity even when it is not feature delivery.
Running the service consumes capacity
Operational work includes incident response, maintenance, access changes, deployment support, reliability improvements, and customer-impacting fixes. If a plan counts only new features, operational demand appears as surprise interruption and the forecast becomes systematically optimistic.
A concrete example
An illustrative team has ten planned delivery slots but routinely spends two on production support. Treating all ten as feature capacity creates a queue each month. Reserving operational capacity makes the tradeoff explicit and gives reliability work a place in the plan.
Measure the work you can see
Classify operational items, inspect arrival and aging, and compare them with incidents and recovery outcomes. A rising operational queue may indicate system debt, insufficient automation, or a temporary event. The remedy depends on the cause.
Limitations
Operational work is not always recorded as a clean item. Activity measures can undercount investigation and collaboration. Avoid comparing teams until their definitions and recording practices are aligned.
How this relates to Weave
Weave can help teams see engineering activity and delivery patterns that may indicate operational load. It cannot capture every support interaction or on-call responsibility, so capacity planning should join its evidence with incident and service records.
Explore Engineering intelligence