Most mid-sized employers have bought something in the last two years that was supposed to make work faster: an ERP upgrade, a scheduling tool, an automation line, an AI assistant for the finance team. Plenty of those purchases are still waiting for the payoff.
The usual cause is not the software. It is that nobody planned for the people side of the change, including who to hire, who to keep and who needs to be doing something different by month three.
The tool is the easy part
A vendor will configure a platform in weeks. Getting a plant floor, a sales team or an accounts payable group to work differently takes longer, and it tends to fail in predictable places:
- The supervisor who was never told why the process is changing, so quietly keeps the old one.
- The one analyst who understands the data, and who is now the single point of failure.
- The project that ran on a contractor, who left before anyone internal learned the system.
- Training scheduled for the week of go-live, when everyone is already stretched.
None of these are technology problems. All of them are staffing and leadership problems that could have been seen in advance.
Decide what roles the change actually needs
Before posting anything, write down what the new system changes in each team. Be specific about tasks, not titles.
- Operations and manufacturing: Automation usually reduces manual handling and raises the value of maintenance, quality and process-improvement skills. You may need fewer entry-level hands on one task and more skilled trades or technicians. Hire those people before the equipment arrives, not after the first breakdown.
- Finance: Automating close or reporting work shifts the team toward review, analysis and controls. A controller often needs a stronger senior analyst, not another processor.
- Sales: A new CRM or AI-assisted pipeline tool only helps if reps enter clean data. Someone has to own sales operations, or the reporting will not be trusted.
- AI and data: The gap is rarely a lone data scientist. It is usually someone who can clean data, connect systems and explain results to a manager who is not technical.
Use contract talent for the build, permanent hires for the run
Project-based specialists are a good fit for migrations, integrations and one-time builds. The risk is handing them the knowledge and then losing it.
Set two rules at the start. First, every contractor works alongside a named internal person who will own the system afterward. Second, documentation is a deliverable with a date, not a favour at the end. If the work will be needed for years, plan a permanent hire and treat the contractor as a bridge to that person.
Give managers the job of leading the change
Front-line managers decide whether a new process sticks. They need three things from senior leaders before rollout:
- A plain explanation of what is changing and why.
- A clear view of what happens to their team's roles and workload.
- Time in the schedule to train people, not just permission.
If you cannot tell a supervisor whether their team will grow, shrink or change shape, expect rumours to fill the gap. In a tight labour market, your best people are also the ones with options, and uncertainty is a common reason they start taking calls from other employers.
Watch for early warning signs
In the first 90 days after a rollout, check a few simple things:
- Are people still keeping side spreadsheets or paper logs?
- Has overtime gone up rather than down?
- Have any of your strongest people resigned or asked about moving roles?
- Are managers able to describe the benefit in their own words?
If the answer to the first three is yes, or the last is no, the change is not landing. Fix that before spending on the next tool.
Plan the workforce alongside the budget
When the capital request goes to the owner or the board, the workforce plan should go with it. That means the roles to add, the skills to build, the people at risk of leaving and the cost of a gap in each. Technology spending without that plan is a bet that the existing team will absorb the change on top of their day jobs. Sometimes they can. Often they cannot.
We saw this on the production side with a food manufacturer in the GTA. Over 20 hires in 18 months across production, skilled trades and office roles worked because the hiring was sequenced with the growth in the plant, not scrambled after it.
What to do next
Pick the one system or process change you have underway or planned. List the roles it touches, the skills missing and the person who will own it in a year. Then decide which gaps are permanent hires and which are short-term contract work.
A Traverse recruiter can help you scope those roles and find the people for them, in Canada or the US.