Plan realistic capacity for a small service team

A small team can look available on a calendar while already carrying more work than it can deliver. Meetings, customer responses, revisions and internal responsibilities rarely appear as large project blocks. Capacity planning brings those commitments into the same conversation as new requests, so a promise is based on available work time rather than optimism.

Start with the people actually available

For the planning period, record each person’s agreed working time, leave, fixed appointments and essential ongoing responsibilities. Do not assume every remaining hour can be allocated to concentrated delivery. Ask the team where interruptions and routine support normally occur.

Keep the exercise about work, not personal surveillance. You need an understandable estimate of availability, not a record of every movement. Review uncertainty openly rather than treating a rough number as a performance target.

Match work to the skills it needs

Atlassian’s capacity-planning guidance compares workload with availability and individual skills. That distinction matters in a small team: unused hours in one role cannot automatically resolve a specialist bottleneck elsewhere. Identify the tasks that require a particular person and the work that others can reasonably share.

Use a fictional example: a three-person studio may have time for production but little review capacity because one colleague approves every final file. Adding another project would increase the queue even if the overall calendar appears partly empty.

Include the whole delivery path

Estimate preparation, execution, checking and likely revisions separately where that improves understanding. Note customer inputs and approvals that affect timing. Waiting for a reply is not the same as active work, but it can still move the final delivery date.

Avoid filling the plan to its apparent maximum. Keep an explicit allowance for the type of uncertainty your work actually contains. There is no universal percentage that makes every team’s plan realistic; compare your assumptions with experience and adjust.

Decide what changes when demand exceeds capacity

Choose deliberately among sequencing work, changing the scope, moving a date or obtaining suitable support. Ask which commitment would be displaced before accepting an urgent addition. Overtime should not be the invisible assumption that makes an otherwise impossible schedule appear balanced.

Review the plan regularly with the people doing the work. Compare estimates with completed results and record the main reasons for differences. A useful capacity plan helps the team make better commitments; it should become more accurate through discussion, not more intimidating through extra columns.

Sources: Atlassian: What is capacity planning?.