Capacity planning starts with a question that a busy team may find difficult to answer. Is there more work than the team can handle, or is work waiting for something else? Imagine an owner sees a growing list of unfinished requests and starts drafting a job advertisement. Before committing to another role, it helps to understand what is actually holding those requests up.
This is an illustrative situation, not a DBG360 client story. Hiring may be the right choice. The purpose of this review is to make that choice specific enough to explain, rather than treating a longer task list as proof that another person will solve it.
Begin capacity planning with one type of work
Choose a repeated activity with a clear starting point and a usable definition of done. Examples include preparing a standard quotation, completing an order check or answering a routine service request. Do not combine unrelated work simply because it sits in the same application.
Ask the team what must happen before a request is ready to work on. Missing customer information, an unavailable approval or an unresolved technical issue can leave a task waiting even when someone has time to handle it. Record those conditions rather than counting every waiting item as an equal demand on staff.
Separate skills from the amount of work
The NIST Baldrige Criteria Commentary distinguishes workforce capability, meaning the skills and abilities needed, from workforce capacity, meaning sufficient staffing. That distinction is useful for capacity planning because extra people and different skills address different questions.
Ask who can complete the selected work, which decisions they can make and what support they need. A queue of technical exceptions may require specialist knowledge. Moving more general work to that specialist could make the exception queue harder to clear. Check the actual work before deciding that everyone should be interchangeable.
The review below is our operating recommendation. It is not a NIST staffing formula, a legal staffing standard or a guarantee that a particular team size is sufficient.
Build a small capacity planning record
For a period that reflects how your business operates, keep a simple record of the selected work:
- Requests arriving, separated by relevant type or complexity.
- Requests completed to the agreed standard.
- Work still waiting and how long it has waited.
- Items blocked by missing information, approval or another dependency.
- Skills and actual coverage available for that work.
Keep counts consistent. Decide whether a reopened request is the same item or new work, and record that choice. Do not compare a week of simple enquiries with a week of complex investigations as though each request required the same effort.
Use the capacity planning record to find questions worth checking with staff. A growing queue can justify investigation, but the count alone does not identify its cause. Look at the oldest relevant items and the steps they are waiting for.
Check timing before assuming the whole week is overloaded
Work may arrive unevenly. For example, a team could have enough suitable coverage across a week but too little during the hours when customers need an answer. This is a hypothetical possibility, not a claim about your team or an instruction to change working hours without agreement.
For capacity planning, compare the arrival pattern with the actual skills and coverage available at those times. Include training, supervision, planned leave and other assigned responsibilities. Do not treat every paid hour as time available for the selected queue.
Check any proposed coverage change against employment requirements, existing agreements and staff needs. More activity is not a reason to assume unlimited overtime or remove necessary breaks.
Choose the action that matches the constraint
A capacity planning review may point to different actions. If requests wait for an approval, clarify the decision and its backup. If one task needs a skill the team lacks, assess training, specialist support or a role with that skill. If comparable work consistently exceeds the coverage available, assess additional capacity.
Before hiring, describe the work the new person would do and what would let them start doing it. Include access, training, supervision and the time existing staff will spend supporting them. A role description should explain the operating gap, not repeat that the department is busy.
Technology may help when repeated copying or routing creates unnecessary work. Assess implementation and maintenance costs against the actual problem. Automating a blocked approval does not decide who has authority to approve it.
Recheck capacity planning after the change
Give the capacity planning review an owner for the next comparable period. Check work completed, items still waiting, age of the queue and quality. A higher completion count is not enough if staff have simply moved errors or unfinished work to another team.
For a business in the United States or Georgia, use its actual contracts, local working arrangements, languages and service commitments. Verify employment and other legal requirements separately with qualified advisers. This worksheet does not assume the same rules or staffing costs apply in both countries.
Start capacity planning with one queue that is creating pressure. Ask the team to show what arrives, what finishes and what waits for a decision or skill. Use that evidence to choose the next change, then check whether it addressed the gap you identified.
DBG360 can help map the workload, clarify responsibilities and assess the process, staffing and systems choices through operational optimization. If you are unsure whether growth needs another role or a different way of working, book a discovery call to discuss the work behind the hiring decision.
