When an IT team shrinks and the device fleet doesn’t, something has to give. The only real choice is whether you decide what gives, or let it happen one missed ticket at a time.
If you’ve been told to keep the same service with fewer people after layoffs or a hiring freeze, device work is one of the first places the gap shows. Frontline devices break on their own schedule, and every broken one is a worker who can’t do their job.
This post covers how to sort device work into what to stop, automate, hand off, and keep, and how to show leadership the trade-offs in terms they can decide on.
Device work doesn’t shrink with the team
Device work is driven by the size of the fleet and the number of sites, not by the size of the IT team. The same number of devices still need setting up, fixing, replacing, and retiring.
Geography makes it worse. A team that used to send someone to a store or depot now has to choose which sites get help, and remote sites across Canada are the first to wait.
Fewer people means the same queue moves slower. Replacement devices take longer to ship, new hires wait longer for their handhelds, and projects stall because the remaining team is covering the gap.
Hiring your way back isn’t easy either. A Robert Half survey of 1,500 Canadian hiring managers, published in February 2026, found that only 5% of technology managers say they have the skills and headcount to complete high-priority projects. Most IT teams were already stretched before the cut.
Sort device work into stop, automate, hand off, and keep
Start by listing every recurring device task, then put each one in one of four buckets. The exercise makes the trade-offs visible and gives you something concrete to take to leadership.
| Bucket | What belongs here | Examples |
|---|---|---|
| Stop | Work that adds little value or exists only out of habit | Custom one-off device builds, manual reports nobody reads, supporting device models outside the standard |
| Automate | Repetitive configuration and monitoring | Zero-touch enrolment, app and OS update policies, compliance alerts |
| Hand off | Physical, repeatable work that doesn’t need your team’s judgment | Staging, repairs and replacements, spare devices, returns, secure retirement |
| Keep | Decisions that need internal knowledge and authority | Security policy, device standards, vendor decisions, priorities |
The keep bucket should be small. If it’s long, look again at what’s really judgment and what’s just familiar.
What to stop doing, and how to say so
Stopping work is harder than it sounds, because every task has someone who relies on it. Pick the ones with the least impact and announce them, rather than letting them quietly lapse.
Common candidates are custom device builds for individual requests, support for device models outside your standard, and manual reports that duplicate what your management platform already shows. Tell the people affected what’s changing, why, and what they should do instead.
Protect the frontline first. When you decide what slows down, keep replacement devices and new hire setups at the front of the queue, because those are the requests that stop people from working.
What to automate first
Automate the tasks that happen most often and take the most hands-on time per device. For most fleets, that’s setup and re-enrolment.
Zero-touch enrolment lets new and reset devices configure themselves on first power-on, which removes most of the manual setup per device. Update policies keep apps and operating systems current without someone pushing them by hand. Alerts flag devices that fall out of compliance, so problems surface before a user calls.
Just know that automation helps with configuration, not with the physical work. It won’t repair a cracked screen, ship a replacement, or process a box of returns.
What’s easiest to hand off
Handing off doesn’t have to mean everything at once. Most teams start with the single task that takes the most hours each month, then add more once the first handoff is working.
The physical work is the easiest to hand off and usually the most time-consuming. Staging devices, sending repairs out and back, keeping spares charged and stocked, processing returns, and wiping retired devices all follow repeatable steps.
That work also has a real cost when you keep it in-house, which the guide to the cost of managing mobile devices in-house breaks down. When the team shrinks, those hours come straight out of everything else.
How to explain the trade-offs to leadership
Leadership approved the headcount reduction, but they may not have approved what it does to device service. Make the trade-off explicit so they can decide on it.
- Show the workload. Device tasks per month and the hours they took before the cut.
- State the service you can still hold. Which device requests you can still meet on time with the current team, and which you can’t.
- Name the impact. Longer waits for replacement devices, slower new hire setups, and delayed projects, in operational terms.
- Offer the options. Accept slower service, automate, hand off specific work, or restore headcount, each with its cost.
Put it in writing and ask for a decision by a date. A trade-off leadership has chosen is easier to defend later than a slowdown nobody agreed to.
If you’ve already measured how device work affects projects, the post on IT teams spending more time fixing devices than on projects covers how to present those hours.
Where outside help fits
Handing off device work isn’t the same as giving up control. Your team keeps the standards and decisions, and someone else does the hands-on execution.
Through lifecycle management, our in-house Canadian team handles repairs, spare pool management, asset tracking, and help desk support. We think of it as a force multiplier for a smaller IT team, not a replacement for it. The comparison of in-house versus outsourced managed mobility walks through the cost and control trade-offs.
Just know that it fits best for fleets of hundreds or thousands of frontline devices across several sites. For a small fleet at one office, automation and a tighter standard may close the gap on their own.
Questions we hear after IT headcount cuts
How do I manage the same device fleet with a smaller IT team?
Sort every recurring device task into stop, automate, hand off, or keep. Stop low-value work, automate setup and updates, hand off the physical work such as staging, repairs, and spares, and keep policy and decisions in-house. Then agree the service levels you can realistically hold with leadership.
Which device tasks are easiest to hand off?
Physical, repeatable tasks are the easiest to hand off. These include staging and setup, repair logistics, spare device management, processing returns, and secure retirement of old devices. They follow standard steps, take a lot of hands-on time, and don’t depend on internal knowledge to do well.
Will outsourcing device work mean losing control of our fleet?
Not if the split is clear. Most organizations keep device standards, security policy, and vendor decisions in-house, and hand off the execution. Agree on reporting, service levels, and who approves changes up front, so your team sees what’s happening and makes the decisions.
Where to start
List every recurring device task your team handled last month, with rough hours, and sort them into the four buckets. Bring that list to leadership with the service levels you can still hold, because a clear trade-off gets a decision. A general warning that the team is stretched usually doesn’t.
References
- Robert Half Canada, Only five per cent of organizations have the skills and headcount needed for priority projects in 2026 (February 2026). Survey of 1,500 Canadian hiring managers.