Capacity planning

Define demand in useful units

List the work expected during the planning period and describe what completion requires. A “campaign” can range from a small email update to a multichannel launch, so counting campaigns alone may hide substantial differences in effort.

Estimate activities and dependencies at an appropriate level. Include research, production, review, revisions, setup, QA, and reporting where they are material. Use observed history from comparable work rather than relying only on optimistic first estimates.

Separate committed work, likely demand, and uncertain requests. This helps stakeholders understand which assumptions drive the plan. Record required dates and the consequences of delay, but do not treat every requested deadline as equally fixed. A useful demand model makes tradeoffs visible instead of placing all requests into one backlog labeled urgent and assuming the team will somehow absorb them.

Estimate effective capacity and bottlenecks

Calculate available time after known commitments such as leave, recurring operations, and essential meetings. Then consider skill and dependency constraints. Ten available design hours cannot automatically replace ten hours of legal review or analytics engineering.

Identify bottlenecks that limit the complete workflow. A large production team can still deliver slowly if every asset waits for one overloaded approver. Increasing work upstream may enlarge the queue without increasing finished output.

Use ranges when effort is uncertain and retain some capacity for genuine variability. The appropriate reserve depends on the work and service commitments; there is no universal percentage that suits every team. Avoid converting a rough planning estimate into a promise of exact personal productivity. The model should support delivery decisions and expose constraints, not judge individuals through a simplistic utilization score.

Worked example: planning a content sprint

Imagine a fictional team with two writers, each scheduled for 40 hours in a week. Together they have 80 nominal hours. After 20 hours of agreed operational work, meetings, and leave, 60 hours remain for the planned production scope.

Six articles are estimated at eight writing hours each, requiring 48 hours. However, each also needs two hours from one editor, requiring twelve editing hours. If that editor has only eight hours available, the plan has an editing bottleneck even though writer capacity appears sufficient.

The team can reduce the committed article count, adjust timing, simplify the approved scope, or obtain appropriate review capacity. It should not label six drafts as six completed articles. The example shows why capacity planning follows work through completion and accounts for specialized constraints rather than considering only the most visible production stage.

Prioritize and change scope deliberately

When demand exceeds capacity, make an explicit choice. Compare business value, deadlines, dependencies, risk, and effort. A smaller complete deliverable can be more useful than several unfinished initiatives, but the change must preserve the outcome stakeholders need.

Discuss scope reductions concretely. Removing an optional asset differs from skipping required validation. Identify what the revised deliverable includes and what effect the change has on the customer or business objective. Avoid silently lowering quality to make the original schedule appear achievable.

Limit simultaneous work when too many open tasks create switching and waiting. Coordinate handoffs so downstream specialists receive work in a manageable sequence. If additional resources are proposed, include onboarding and coordination time rather than assuming they create immediate full capacity. The plan should reflect how the work actually moves through the team, not only how resources look on an organization chart.

Review actual delivery and update the model

Compare planned effort and completion with observed results. Investigate recurring differences: underestimated review, unclear briefs, rework, unexpected support demand, or dependencies outside the team. The objective is to improve the planning assumptions, not to punish every variance.

Track finished outcomes and cycle time alongside workload. A team can be highly occupied while little work reaches completion. Look for queues and blocked tasks that indicate a process problem rather than a simple shortage of hours.

Update capacity when staffing, skills, tools, or demand changes. Keep a visible record of assumptions and decisions so stakeholders understand why commitments move. A useful plan is a maintained decision aid. It should help the organization choose sustainable delivery priorities and respond to new evidence without pretending that uncertainty can be eliminated through more detailed scheduling.

Related terms

• Campaign management: coordinating marketing delivery. Capacity planning helps make its timelines and resource commitments realistic.
• Marketing operations: the processes and systems supporting execution. Capacity is one part of that operating model.
• Campaign QA: verifying readiness and correctness. Its effort must be included rather than treated as free final work.
• Content calendar: planning content timing and activity. It should reflect the resources needed to finish the work.
• Campaign: coordinated marketing activity around an objective. Its complete workload needs to be reflected in capacity estimates.
• Workflow automation: using software to support repeatable processes. It can change capacity but still requires maintenance and exception handling.