Every founder who’s brought in new equipment already knows how this part goes. It works beautifully in the demo. It gets wheeled in with everyone standing around for the first run. Three weeks later, half the team’s quietly back to doing it the old way, and the new machine’s running at a fraction of what it was bought to do.
That’s not a technology problem. It’s a sequencing problem, and it’s showing up right now across a wave of new funding landing in Ontario manufacturing.
Different equipment, same gap
Picture a small food producer that’s just secured funding to automate part of its production line. Or picture a metal fabricator bringing in new machinery to keep up with growing orders. Or picture a packaged goods manufacturer modernising its operations while pushing into new markets at the same time. Different products, different equipment, same moment: new tooling is about to change how a group of people do their job, and the plan for getting there usually starts with the machine, not with them.
Recent workplace research backs up how often that default goes wrong. 85% of employees say they can’t actually apply the training they’re given to their daily work. More than half say they’re too buried in the version of the job the tool was meant to replace to find time learning it. And close to four in five say the real learning happens somewhere else entirely, a side conversation, a message thread, not the system itself. None of that is really a training problem. It’s what happens when a tool arrives before anyone’s asked the people using it what they actually need from it.
What I’d actually do
If I were walking onto that floor the week new equipment arrived, I wouldn’t open with the manual. I’d start with the people already doing the job it’s about to change.
First, before the equipment lands, sit down with the three or four people who currently do the work by hand and ask them where the process actually breaks today, not where leadership assumes it breaks. That’s where the new equipment either fixes something real or inherits the same mess, just faster.
Second, hand the rollout to a small group of the people who’ll use it daily before anyone else touches it. Let them run it, break it, and tell you what’s missing. A process shaped by the people using it spreads on its own. A process handed down finished rarely does.
Third, check back properly at thirty days, not with a satisfaction survey, but by watching who’s actually using the new process and who’s quietly reverted to the old one. That gap tells you more than any dashboard about whether the rollout actually worked.
None of this slows the equipment down. It’s what makes the investment behind it actually pay off, instead of sitting half used on a floor nobody was asked about first.
If you’re bringing in new equipment or automation and want the people running it involved before it lands, not after, let’s talk it through: https://calendar.app.google/nJyTsHMsJJ5TnCzBA