7 Operational Myths Still Killing
Toronto Businesses in 2026
The problems costing you millions aren't mysteries. They're myths, stories your organization tells itself about why things are the way they are. Here are the seven we keep finding.
Walk into any Toronto warehouse, clinic, back office, or manufacturing floor and you will find the same thing. A broken system that has been running long enough that everyone stopped questioning it. The people inside it have tried to fix it. Nothing stuck. Eventually they stopped calling it broken. They started calling it just how things work around here. That is the moment a problem becomes a myth.
No you don't. You have a system that makes your existing people invisible.
The most common version of this myth lives in warehouses, assembly operations, and anywhere components need to be tracked, but it thrives just as well in clinics and back offices. The backlog grows. The answer is always more staff. More staff get hired. The backlog keeps growing, because the new people inherit the same broken search. Your team spends enormous amounts of the day looking: for parts, for files, for information, for the thing that was definitely here yesterday. Search time doesn't appear on any report. It looks and feels like productive work, but it produces nothing. It is the tax a system charges when nothing has an address.
One facility hired three temps at $30 an hour, 40 hours a week, for six months ($86,000) to manually search for parts a coded staging area located in seconds. When the searching stopped, daily output went from one kit to twelve. Headcount didn't change. Visibility did.
Source: Myths case study, aboveBefore you post another job listing, ask: how much of my current team's day is spent searching for things instead of doing things? If you can't answer that question, you do not have a staffing problem. You have a visibility problem.
The software didn't fail. Nobody looked at both systems at the same time.
Software implementations fail at a staggering rate, some studies put it above 70% for large projects. But most of those failures aren't technology failures. They're diagnosis failures. The wrong problem was solved, or the right problem was solved the wrong way, because nobody understood the existing system well enough before building the new one.
A national professional association paid $50,000 for a new membership platform. The migration corrupted more than 10,000 member records: duplicates, missing reports, incomplete payment histories. The original vendor quoted $10,000 more to maybe fix it. The actual fix took a weekend and cost $1,800, because the problem was never the code. It was that two databases storing the same facts in different shapes had been treated as if they were the same system, and nobody had looked at both structurally at the same time before pressing migrate.
Before your next implementation, ask: does anyone in this room understand both the system we have and the system we're building at the same time? If the answer is no, you are not ready to migrate.
Expertise is knowing how to do your part. It is not the same as seeing the whole thing.
Your team is experienced. They know their jobs. But expertise is vertical. It runs deep inside a domain. The accountant knows the numbers. The floor lead knows the floor. The developer knows the code. Operational failures are horizontal. They live in the handoffs, the assumptions, and the spaces between departments, exactly where no one's job description points.
Look back at the case studies above. An enterprise vendor who knew databases. A warehouse team who knew kits. A platform vendor who knew their software. Association staff who knew their members. Every expert did their part competently. The six-month backlog and the 10,000 corrupted records both lived in the one place no expert owned: the connections between the parts. In both cases, the person who caught it wasn't more expert than the people in the room. They were simply the only one whose entire job was to look at the whole.
On your next complex project, ask: who in this room is responsible for looking at how all the pieces add up, not just their own piece? If everyone points at everyone else, you have your answer.
Sometimes. But people problems and systems problems wear the same clothes.
People perform inside systems. A good person in a broken system will produce broken results. Before you decide you have a people problem, you need to be sure the system isn't making people look like the problem.
43% of workers regularly copy and paste data between systems by hand, turning a technology problem into a labour cost nobody budgeted for, while making the people doing it look slow when the system is what's slow.
Source: IDC Document Disconnect surveyThat said, sometimes it really is a people problem. Sometimes the bottleneck is a manager whose self-interest has quietly become the org chart. A dynamic nobody will name. We name it. Because organizations that fix their systems but leave the human dysfunction in place just build a faster, more efficient broken organization.
Before managing a person out, ask: would a different person in this role produce different results with the same tools, the same information, and the same constraints? If the answer is probably not, you have a systems problem wearing a people costume.
Things will not slow down. Every month you wait is a month you're paying for the broken version.
Operational inefficiency isn't free in the meantime. It's actively expensive every day, in overtime, in errors, in customer experience, in staff turnover, in the management time spent dealing with consequences instead of creating value.
1 in 5 small businesses cannot survive a single system failure costing as little as $10,000, yet 6 in 10 have never calculated what an hour of their own downtime costs. Waiting is a bet placed with numbers you have not run.
Source: ITIC 2024The math is almost always the same. An $1,800 diagnostic identifies a problem quietly costing $15,000 a month. The fix takes three weeks and costs $8,000. The payback period is measured in days, not quarters, and the meter on the broken version was running the whole time you were deciding.
What is this broken system actually costing per month in staff time, errors, workarounds, and management attention? If you can't calculate that number, that's the first thing to fix.
The skills to fix it are usually already in the building. What's missing is someone to see what they're for.
Organizations consistently underestimate the capability sitting inside them. The person who built the workaround understands the problem better than anyone. The manager dealing with the consequences for three years has a mental model of the system nobody else has. The frontline worker doing the job manually knows exactly where the friction is. What's missing isn't knowledge. It's the structural ability to take that distributed knowledge and turn it into a coherent picture of what's broken and how to fix it.
Before hiring a specialist, ask: who in this organization understands this problem most deeply? Have they been asked to design the fix? Have they been given the authority to implement it? If not, start there. You may already have everything you need.
The most expensive problems are the ones that look like normal.
This is the myth underneath all the other myths. Operational dysfunction doesn't arrive dramatically. It arrives gradually, and then it becomes the baseline. New staff are onboarded into it. Managers inherit it. The people who remember what it was like before eventually leave, and everyone who remains assumes the current state is just how things work.
Over two decades, Ontario manufacturing productivity grew at a third of the US pace. There was no single crisis, no dramatic failure to point at. Just accumulated, normalized inefficiency that nobody flagged, because by then it was simply how things worked.
Source: Ontario Advanced Manufacturing Council 2024Someone has to be willing to walk in and say: this isn't normal. This is broken. Here is exactly why.
When did you last have someone with no investment in how things currently work take a serious look at your operation? Not a consultant who'll tell you what you want to hear. Someone who will tell you what's actually there. If you can't remember, that's your answer.
So what do you do with a myth?
You name it. Out loud. In a room full of people who've been living inside it. That's the hardest part. Not the fix, the diagnosis. The moment someone says this isn't working and here's exactly why is the moment the myth stops being invisible. Once it is visible it is fixable. It is almost always simpler to fix than anyone expected.
We have cleared a six-month backlog in five days at a company running a million dollar Oracle system. We have recovered a $50,000 database migration for $1,800, with 10,000 professionals verifying their own records before a single row went live. Not because we're smarter than the people in the room, but because we walked in without any investment in why things are the way they are.
That's what it takes to see a myth clearly. Someone who did not help build it.
Does one of these sound like your operation? Book a 15-minute clarity call and we'll tell you in one conversation whether this is fixable and what it would cost.
Book a free clarity call