A manager asks for another role. The workload is real, the team is tired and the service level is slipping. Approving a hire may be the right decision. It may also place one more person into a process that wastes everyone's time.
The useful question is: what work needs to be done, at what standard, and what capacity is available to do it?
Map demand before debating headcount
Look at volume, complexity and timing. Is demand steady or concentrated on particular days? Has the expected standard changed? Which work is mandatory, which creates value and which continues because nobody has stopped it?
Then look at the skills needed. A shortage of specialist judgment cannot always be solved by adding general hours. Equally, a specialist may be carrying routine administration because no one has redesigned the support around them.
Find the capacity already being lost
Repeated reporting, unclear hand-offs, rework and approvals can consume a meaningful share of a team's week without appearing in a labour report. Ask people to describe where they wait, repeat, chase or correct work. Test those accounts against actual workload and service measures.
Make the trade-offs visible
There may still be a strong case to invest in more people. If so, show the demand it will meet, the service or output expected, and when to review the decision. If capacity can be released by changing work, be equally clear about the transition and the people implications.
Resource decisions are better when they consider the operating model and the P&L together. A saving on paper has little value if it damages service, safety or the team's ability to deliver.
Try this: Before approving the next role, ask for one week of real examples of work delayed, duplicated or done by the wrong role. The answer may strengthen the case for hiring — or reveal a better design.
Explore how to release capacity by fixing rework before adding more hours.
Use the team workload mapping guide to test where time goes before adding a role.