Before You Hire Your Next Employee, Read This
A $60K hire costs $85K to $120K in year one, takes 6 months to become productive, and has a 46% chance of failing within 18 months. There's a better sequence.
A manager at a motor freight company was asked a simple question: how much of your delivery trouble is caused by your drivers?
His answer was instant. All of it.
The man asking was W. Edwards Deming. Same Deming who rebuilt Japanese manufacturing after the war, whose quality framework became the backbone of Toyota, Motorola, and every modern operations system worth studying. His response to that manager was just as quick: that answer is a guarantee the problem will never be solved.
Deming spent decades measuring the split between system failures and individual failures across hundreds of organisations. His conclusion, published in 1986 and never seriously challenged since: 94% of workplace troubles belong to the system. 6% belong to the individual.
That number should change how you think about every performance conversation you've ever had.
Your team isn't slow. They're buried in work that isn't work.
A 2025 survey of 2,000 knowledge workers found that 51% of the average workday goes to low value tasks. Not client work. Not the creative thinking you hired them for. Formatting emails, copying data between systems, writing status updates, chasing approvals that sit in someone's inbox for three days.
The numbers stack up fast:
| What's happening | The cost |
|---|---|
| App/website toggles per day | 1,200 (costing ~4 hours/week) |
| Time to refocus after an interruption | 23 minutes, 15 seconds |
| Average screen attention span | 47 seconds (down from 2.5 minutes in 2004) |
| Productive time lost to context switching | Up to 40% |
Read that middle row again. Every time someone gets pulled out of focused work, it takes 23 minutes to get back. Not five. Not ten. Twenty three. Your open plan office with Slack pinging every 90 seconds isn't a collaboration tool. It's an interruption machine.
And here's the part that makes it a process problem, not a people problem: nobody chose to toggle between 1,200 screens. The workflow demands it. Four tools to update a single client record. Three apps to check before answering a question. Two spreadsheets that should be one database. Your team didn't design this. They inherited it.
The average employee spends 5.6 hours every week on administrative tasks that AI could handle right now. Not in some future state. Not with custom software that doesn't exist yet. With tools that are already on the market.
That's nearly a full working day, every single week, spent on avoidable admin.
Across the US alone, the bill comes to $818 billion per year. Per employee, roughly $17,000 annually in wasted labour. For a team of 20, that's $340,000 a year paying real people to do work that doesn't need a person.
The highest earners get hit hardest. People making six figures lose 76 minutes per day to admin that a properly configured automation could handle in seconds. Your most expensive talent is spending their most expensive hours on your least valuable tasks.
48% of workers have considered leaving their job specifically because of admin overload. You're not just wasting their time. You're pushing them toward the door.
Everyone talks about burnout. Almost nobody talks about boreout.
Boreout syndrome (yes, it has a clinical name) describes the state of being simultaneously exhausted and understimulated. You're tired, but not from hard work. You're tired from doing the same mindless task for the 400th time while knowing you're capable of more.
Research published in Motivation and Emotion found that more than half the workforce experiences job boredom daily. Not occasionally. Daily. And boredom doesn't just make people check out. It's positively correlated with counterproductive work behaviour. More errors. More corners cut. Less care.
85% of workers say repetitive tasks are a top contributor to burnout. One in three has considered quitting because their technology is outdated or frustrating. Not because the work itself is bad. Because the tools and processes wrapped around the work make it miserable.
And when they do leave? The replacement costs are brutal:
The most painful part: 42% of employees who voluntarily left say their manager could have prevented it. Not with more money. With better conditions.
Your best people leave first. They always do. High performers have options, and when you trap them in repetitive processes that waste their skills, they don't complain to HR. They update their LinkedIn.
There's a reason this pattern persists. It's a well documented cognitive bias called the fundamental attribution error.
When something goes wrong, humans instinctively blame the person involved rather than the circumstances around them. Your sales rep missed a follow up? Lazy. Your ops manager dropped a deadline? Disorganised. Your new hire made an error on a client deliverable? Bad recruitment decision.
A paper in Professional Safety put it bluntly: blaming individuals for system failures is a cognitive default, not an evidence based conclusion. Even aviation crash investigators (people who literally have black box data and decades of protocol) report that their first instinct is still to blame the pilot.
If trained investigators with hard data fall into this trap, what chance does a founder running on four hours of sleep have?
Deming's 94/6 split isn't a suggestion to be nicer to your team. It's a diagnostic framework. If 94% of the problem is structural, then 94% of your improvement effort should be aimed at the structure. Coaching, performance reviews, and motivational talks are aimed at the 6%.
A data processing employee taught himself Python on weekends. He wrote scripts that automated 70% of his daily tasks. Output went up. Errors went down. His manager's response? Slow down and do it manually.
He started job hunting that week.
A sysadmin at a 200 person company built a complete onboarding and offboarding automation. Nobody asked him to do it. He built it because he was sick of watching the same manual process break every time someone joined or left the company. Leadership's response? They refused to invest in rolling it out.
Then there's the story (widely shared, 646 upvotes on Hacker News) of someone who automated their entire role over a year ago and simply never told anyone. They show up. The work gets done. Nobody asks questions.
These aren't outliers. They're symptoms. Your most capable people can already see the waste. Some of them are building fixes on their own time, with their own skills, without being asked. The question is whether your organisation rewards that or punishes it.
This isn't a motivation problem. You can't pep talk your way out of 1,200 daily app switches.
The processes your team follows were probably designed (if that's even the right word) when the company was smaller, the tools were different, and the client load was a fraction of what it is now. They've been patched and extended and worked around so many times that nobody remembers why half the steps exist. But everyone's afraid to touch them because last time someone "improved" a process, it broke three other things.
So nothing changes. And the cost compounds quietly.
One company that tackled this directly (measuring and removing specific friction points from daily workflows) reduced attrition by 35% and saved $4 million annually. Not by hiring better people. Not by running another engagement survey. By fixing the processes that made good people want to leave.
Separately, 92% of companies that implemented automation reported improved employee satisfaction. Not just improved efficiency, though that came too. People were genuinely happier because they stopped spending their days on tasks that insulted their intelligence.
You don't need to automate everything at once. Start with the highest frequency, lowest complexity tasks: the ones your team does dozens of times a week that follow the same steps every time. That's where the fastest wins are, and where the morale impact is biggest.
The pattern for teams that break out of this:
The $17,000 per employee isn't a fixed cost. It's a design choice your organisation is making by default, every year, because nobody has stepped back far enough to see it.
Your team isn't the problem. They never were. And unlike hiring or restructuring, process redesign and automation can start producing results in weeks. If you want to see exactly where your team's time is going, book a free audit. We'll map it with you.
Everything we've learned building 300+ automations for small businesses, in one practical guide. Written for business owners, not engineers.
Completely free.