Questions we answerCapacity and workload
How do I reduce workload without hiring?
Three levers in order: stop doing some of it, change how the rest flows, and automate what is genuinely repeatable. Most teams reach for the third and skip the first two.
Free · a few minutes · starts from “We're overloaded”
The short answer
In order of cost: stop doing work that is not earning its place, change how the remaining work flows so less of it is rework and chasing, then automate what is genuinely repeatable and written down. Most teams try to automate first because it feels like progress, and end up automating work that should not have existed. The uncomfortable lever is the first one — deciding what to stop — and it is also the fastest, because it needs no build, no budget and no notice period.
This question is usually asked when hiring has been ruled out for reasons outside the team's control, which makes it feel like a constrained version of the real question. It is not. It is frequently the better question.
The reason is that hiring resources the current shape of the work. If a meaningful share of that shape is avoidable, hiring makes it permanent.
Is it really this?
Worth checking before you spend anything. These are the signals that tend to tell the two apart.
Signs it is
- You can name work the team does that nobody would miss if it stopped.
- A good share of the week is chasing, re-formatting, re-entering or checking.
- Several people touch the same piece of work without any of them owning it.
Signs it's something else
- Everything the team does is visibly valuable and still exceeds the hours.
- The bottleneck is one scarce skill rather than general volume.
- The work is already lean and the commitments are simply too large.
What's usually behind it
- A budget or headcount freeze against a workload that has not frozen.
- Work that accumulated one commitment at a time, none of which was ever reviewed.
- Processes designed for a smaller team that now cost more in coordination than they save.
What people usually get wrong
- Automating first, and locking in a process nobody examined.
- Asking people to be more efficient rather than removing anything.
- Cutting the visible work and leaving the invisible coordination that caused it.
The options, and when each one fits
In no particular order. Which of these fits depends on your situation, not on the question you typed.
Stop or defer some work
Something is being done from habit rather than because it earns its place.
Change how the work flows
A real share of the effort is rework, waiting and chasing.
Automate the repeatable part
The steps are fixed, written down, and come round often.
Move some of it outside
A defined piece could be briefed to someone outside the team.
When doing nothing is the right call
Not everything has an answer this quarter. If the team is coping and the pressure is stable, a deliberate decision to leave it alone and review in three months is legitimate — as long as it is a decision rather than an omission.
What the diagnostic asks
- What kind of pressure it is, and how long it has been there.
- Whether the work is mostly repeatable or different every time.
- How much of the process is written down.
- How often the work comes round.
“I don't know” is always an answer. Nothing is assumed on your behalf.
The routes it weighs
Every diagnostic weighs all ten routes. These are the ones that tend to matter for this question — a description of the rules, not a promise about your answer.
Process improvement
Change how the work flows — remove steps, name an owner, fix the hand-offs.
Redistribute
Move ownership of the work to where it fits, and make that explicit.
AI Assist
Keep a person in charge and give them AI for drafting, summarising, checking or analysis.
AI Agent
Delegate a defined, repeatable workflow to software inside boundaries you set, with human oversight.
Outsource
Hand a defined, ongoing scope of work to an external provider.
Do nothing yet
Record the issue, set a revisit date, and decide what would change your mind.
What changes the answer
- Highly repeatable, documented work opens up automation as a real option.
- Work that varies every time is reduced by removing steps, not by tooling.
- Pressure concentrated on one person points at distribution rather than volume.
Get your own read
A handful of short questions, then the strongest route for your situation, what's also credible, what we still don't know and what would change our view. No account, no setup.
Related questions
- My team is overloaded. What should I do?Start by finding out whether the overload is volume, design or ownership. Each has a different fix, and only one of them is more people.
- Repetitive admin is eating the weekWork out how much of it should exist at all before automating any of it. Some repetitive admin is a process nobody has simplified, some is a good candidate for software, and a little of it genuinely needs a person.
- What should I automate first?The most frequent, most repeatable, best-understood, lowest-stakes thing you do. Not the most annoying one, and not the one with the best demo.
- Is this a busy period or a real capacity problem?A peak has a shape and an end; a capacity problem does not. Telling them apart before you commit to a salary is the single most valuable thing you can do here.
- My best people are doing low-value workExpensive people doing cheap work is a real and quantifiable loss. The fix is usually to move or remove the work, not to hire someone junior to absorb it.
- Too much depends on one person. What are my options?Reduce the fragility before it becomes a crisis: write the work down, develop a second person, move adjacent work off them, or decide it is acceptable for now with a date to look again.