Organizational capacity planning and workflow
A team can be fully occupied while the organization’s most important work remains waiting.
Before adding staff or raising utilization targets, examine where work accumulates, which constraint determines completion and how demand varies. Arcus helps leaders compare capacity, scheduling, work-design and service choices with their costs and implementation requirements.
The decision before the program
01 / Where does work actually wait—and why?
02 / Does the constraint lie in people, approvals, information or another resource?
03 / What capacity is required to meet the service commitment under realistic conditions?
Start with the service commitment, not a utilization target
An illustrative review team appears to have enough annual hours for the cases it receives. Yet cases wait because arrivals peak around deadlines, specialist review is available only on certain days and incomplete submissions return for correction. The annual arithmetic does not explain how the service will meet its turnaround commitment.
Arcus’s central thesis is that capacity planning must connect demand, flow and service expectations at the point where work is constrained. Average staffing and activity measures are useful, but insufficient when timing, case mix and dependencies determine whether work can be completed.
The executive choice is not simply whether to hire. Leaders may need additional capacity, a different schedule, clearer intake requirements, fewer simultaneous commitments or an explicit change to the service offer. The appropriate response depends on the mechanism creating the delay.
Four explanations for the same backlog
Test these alternatives before attributing a queue to low productivity.
01 / Demand persistently exceeds usable capacity
Compare arrivals and completed work over a relevant period, accounting for case mix and quality. A persistent gap supports a capacity or service-scope decision; a temporary backlog does not automatically justify a permanent staffing increase.
02 / Capacity exists at the wrong time or place
Compare demand by period and task with availability of the required skill, approval or equipment. Aggregate hours can conceal a scheduling mismatch or a scarce specialist shared across teams.
03 / Work recirculates
Incomplete intake, unclear acceptance criteria and repeated approvals can create avoidable demand. Measure first-pass completion and reasons for return. Faster processing of the same rework may be less useful than removing its cause.
04 / Commitments exceed the operating model
The organization may promise rapid response, high customization and low cost simultaneously without funding the capability required. Leaders must choose a feasible commitment rather than ask staff to reconcile the contradiction informally.
What operations evidence contributes
MIT Sloan’s operations-management teaching on queueing and capacity illustrates how congestion can rise nonlinearly with utilization under stated stochastic assumptions. It also shows the trade-off between capacity and delay costs. These are analytical relationships and teaching examples, not empirical results from an Arcus engagement or a universal target for staffing utilization.
The distinction matters: spare capacity can have operational value when it absorbs variation or enables recovery. Its value depends on the service commitment, consequences of waiting and flexibility of resources. The analysis does not imply that every organization should maintain the same buffer.
Arcus’s interpretation is to examine the pattern of demand, the location of constraints and the consequence of delay before selecting a utilization target. A team’s apparent efficiency can improve while the overall service deteriorates if unfinished work is transferred downstream or quality checking is deferred.
The Arcus demand-to-flow diagnostic
This original management diagnostic structures the evidence needed for a practical recommendation. It is not a substitute for validating a detailed model.
01 / Define the unit and promise
Specify what counts as a completed case, request or deliverable, and the timeliness and quality expected. Distinguish urgent work from work that can be scheduled or deferred.
02 / Trace arrivals, waits and returns
Follow representative work through intake, processing, approvals and completion. Record elapsed time separately from hands-on time. Identify peaks, incomplete inputs and recirculation.
03 / Identify the effective constraint
Test which scarce resource, decision or dependency limits completion. Examine usable time and task eligibility rather than assuming that all staff hours are interchangeable.
04 / Compare and test responses
Model a bounded set of options, document assumptions and identify quality safeguards. Pilot a suitable change and review whether the queue, completion time and workload actually improve.
A simple example that changes the staffing question
Suppose a service receives 100 requests each week and can sustainably complete 100 of the same mix. An existing backlog of 400 requests will not clear merely because ongoing arrivals and completions are balanced. Clearing it in ten weeks would require 40 additional completions per week during that period, assuming unchanged arrivals, case mix, rework and availability. This is illustrative arithmetic, not a staffing recommendation.
The analysis should distinguish temporary recovery capacity from the capacity needed to sustain the service afterward. Overtime or temporary support may address a backlog but be unsuitable as a permanent operating model. A permanent hire may be justified by sustained demand, but the immediate queue could still require a separate recovery plan.
Before converting the additional output into positions, examine task times, required skills, scheduling and the constraint. If a single approval stage limits completion, adding upstream staff can increase work waiting at that stage. A flow review helps locate where capacity would change the result.
Compare practical capacity alternatives
These options can be combined, but each should address an identified constraint.
Add permanent or temporary capacity
Appropriate when the relevant resource is insufficient. Compare recruitment lead time, training, supervision and sustainable cost. Temporary help requires a handover plan; permanent capacity should be tested against sustained demand.
Reschedule or pool compatible work
Can align availability with demand and share fluctuations across suitable resources. It requires compatible skills, clear priorities and management authority. Pooling unlike work can increase coordination and switching costs.
Improve intake and reduce rework
Can release capacity where incomplete requests or repeated corrections are material. It requires evidence about failure points and effects on users. Rejecting difficult cases is not the same as improving first-pass completion.
Change the service commitment
Can make demand manageable through scope, prioritization or timing choices. It requires an authorized decision and appropriate communication. The cost may appear as unmet need or additional burden elsewhere, rather than in the service budget.
Examine the cost of the constraint and the cost of the response
Include management and specialist time, training, tools, temporary cover and implementation effort in the comparison. Assess delay costs and quality risks in terms appropriate to the service. Some consequences cannot credibly be reduced to a dollar value; identify them explicitly rather than excluding them from the recommendation.
Consider whether a proposed efficiency transfers work to clients, another department or a later period. Automation may reduce processing effort while creating exception handling, review and support demands. Cross-training can improve flexibility but consumes scarce expert time during implementation.
Test plausible changes in demand, case complexity and resource availability. Document which assumptions would change the decision. A single point estimate without these dependencies can make an uncertain recommendation appear more precise than the evidence supports.
What an Arcus engagement can deliver
The scope can focus on a service, shared function or cross-department workflow.
01 / Establish the decision
Deliver a service-demand definition, agreed outcomes and evidence plan. Confirm the decisions the client can make about resources, priorities and service commitments.
02 / Diagnose demand and flow
Develop a workflow and constraint map, capacity baseline and assessment of data limitations. Use operating records and representative cases to distinguish workload from delay and rework.
03 / Compare options
Prepare a capacity-options paper, scenario model, recovery-versus-sustainment analysis and implementation requirements. Identify costs, dependencies and quality safeguards.
04 / Support a practical test
Define pilot responsibilities, measures and a review decision. Assess whether throughput, waiting, quality and the burden on connected teams move in the intended direction.
Make the operating decision reviewable
Leaders should examine where the backlog sits, its age and case mix, what demand is arriving, and which resource actually governs completion. Agree a small set of measures that can reveal displaced work or declining quality as well as improved speed.
A pilot should end with a decision to continue, adapt, expand or stop. An improvement during an unusually quiet period is not enough to establish sustainable capacity. Conversely, an increase in completed work can be valuable even before the backlog visibly falls, provided arrivals and quality are also examined.
Related staffing studies and workforce planning address workforce composition and deployment. Capacity planning adds a service-flow question: how do those resources translate into timely completion? Explore relevant expertise through the central consultant directory.
Discuss the work that is waiting
Tell Arcus which service is under pressure, where work accumulates, the commitment you need to meet and what has already been tried. We can discuss a focused capacity diagnostic, workflow review or options-and-implementation engagement.