Capacity Planning

Capacity planning is essentially figuring out what a team can get done without everyone burning out by Tuesday!

It serves as a reality check between what is on the roadmap and the actual hours available to do the work. If this balance is off, the result is usually over-promising to stakeholders and then scrambling to deliver half-baked results.

When assessing availability, honesty is the most important factor. A forty-hour work week is a myth. Once the time for "quick" syncs, admin pings, and general life admin is subtracted, the remaining time for deep work is significantly lower. This "true" capacity is the only realistic figure to use for planning. It is also necessary to look beyond just the total number of people.

It doesn't matter if five people are free if none of them have the specific technical or design skills needed for the next phase of a project. A bottleneck at the specialist level can stall an entire initiative, even if the rest of the team is sitting idle.

The process is straightforward: look at what is on the plate, estimate the effort required, and see if the maths adds up. If the figures do not align, a call must be made to either move the deadlines or drop certain tasks.

There are always factors that will disrupt a plan. Scope creep is the most obvious, where a project slowly expands until it is twice the size originally agreed upon. There is also a natural human tendency to be too optimistic about how fast work happens. Most high-performing teams actually aim for about seventy or eighty per cent utilisation.

Trying to book people at one hundred per cent leaves zero room for the inevitable fires that need putting out or the creative breathing room that leads to good work. It is a constant cycle of tweaking and adjusting as the work changes, rather than a plan that is set and forgotten.

To move from theory to action, capacity planning requires a mix of reliable data and the right toolkit. The goal is to replace "gut feeling" with a repeatable system.

How it is done: The Strategy

Industry standards generally follow three main strategies depending on the organisation’s appetite for risk. A Lead Strategy involves adding resources in anticipation of demand, which is proactive but carries the risk of under-utilisation. Conversely, a Lag Strategy waits for demand to actually peak before adding resources, which saves money but often results in stretched teams and missed deadlines. Most modern environments use a Match Strategy, making small, incremental adjustments as the workload fluctuates.

The process itself relies on a simple feedback loop. This involves centralising all work intake into a single backlog, breaking projects down into measurable units (like story points or estimated hours), and then comparing that against a team’s true availability. A buffer for "business as usual" tasks and unexpected fires is essential, usually leaving about twenty per cent of the schedule unbooked.

The Toolkit

While spreadsheets are a common starting point, they often become a liability as teams grow because they lack real-time updates. Professional capacity planning typically moves into dedicated software that integrates with existing workflows.

Ultimately, the best tool is whichever one the team actually keeps updated. Without accurate time-tracking or status updates, even the most expensive software will produce a flawed plan.

Resource-Specific Tools Platforms like Float, Resource Guru, and Runn are designed specifically for scheduling and heat-mapping. They make it easy to see exactly who is over-allocated at a glance.
Integrated Management For teams already using Jira, Monday.com, or Asana, the built-in workload views allow managers to balance tasks without switching between different apps. Linear has also become a favourite for its speed and minimalist approach to tracking technical tasks.
Strategic Planning Higher-level tools such as Productboard or Saviom help align these day-to-day tasks with the broader roadmap, ensuring that the team isn't just "busy," but is busy with the right priorities.