Compare the options
Find the cause of the capacity gap.
Repeatable handling
Test a small automation
A rule such as copying an approved status into another system is a candidate for automation. Check whether the rule holds in real records, what permissions it needs and how exceptions will reach someone.
Low volume, frequent changes or costly errors can make a manual process the better choice even when the task is repetitive.
Coverage and expertise
Check what the role must provide
A team may need someone available during a particular shift, able to resolve an account problem or authorised to approve an exception. Saving time elsewhere does not necessarily provide that coverage or authority.
If the service is already failing, a staffing response may be needed while the workflow is improved. Do not budget as though an unbuilt automation has already removed the workload.
Mixed work
Compare a combined approach
A new colleague could own customer decisions while a small workflow handles reminders and status updates. Include the time they will spend checking failures, maintaining rules and answering unusual cases.
The useful comparison is the service delivered and work left behind under each option, including a smaller build, a different role or redistribution within the team.
Unnecessary work
Remove a step before staffing it
An internal report nobody uses or an approval nobody needs may not require another person or another tool. Check who relies on the output before removing it.
Simplifying a process is an option to test, not a reason to assume the current team has enough capacity. Measure what remains after the change.
