This case study is drawn from direct observation of this organisation by a project manager working within it. Conversations were had with field technicians, existing staff, and management over an extended period. Concerns were raised internally. They were not acted upon. Details have been generalised to protect confidentiality. It is presented as a cautionary tale — an example of what happens when operational systems are absent and nobody stops to name the problem. The diagnostic framing reflects The FIELD Method™ framework applied retrospectively.
Every stage broke. Because no stage had ever been designed.
A Southern Ontario company operating in agricultural technology and farm automation had a people problem — or so it appeared. They were hiring journeymen electricians at $37.50 per hour for full-time 40-hour weeks. The shortest tenure of any journeyman hired was three months. The longest was four months. Five journeymen cycled through in the period under observation.
From management's vantage point, the story was straightforward: they were hiring people who weren't working out. Some were let go before they could leave. Others left before they were let go. Either way, the outcome was the same — a revolving door of qualified tradespeople who couldn't seem to perform to the standard the company needed.
What management couldn't see — because they had no system that would have made it visible — was that they were the ones creating the outcome they kept trying to hire their way out of.
The perspective in this case study comes from a project manager working inside the organisation — someone with direct access to the field teams, the new hires, and management. Conversations happened across all three groups. The alarm was raised internally. It wasn't acted on. What was observed over the following months was a pattern that was simultaneously predictable and entirely preventable.
The turnover wasn't a hiring problem. The company wasn't selecting the wrong people. Journeymen electricians are qualified, skilled tradespeople with years of experience. The problem was what happened — and what didn't happen — after they were hired.
Every new journeyman went through the same onboarding experience. For approximately three months, they were paired with an existing employee and accompanied them on jobs. This was called training. In practice, it was three months of being used as a helper. Handing tools. Picking up materials. Cleaning up at the end of the day.
The specific systems, equipment, and agricultural automation technology the company worked on — the things a technician actually needed to know to do the job independently — were never taught. The existing employees weren't running structured training sessions. They weren't explaining what they were doing or why. They were doing their jobs and each new journeyman was there alongside them, watching from the outside.
Management designed a three-month onboarding period and assumed it was producing competent technicians. Nobody had defined what the onboarding period was supposed to teach, how it was supposed to teach it, or what standard a technician needed to meet before deploying independently. The existing employees didn't know they were supposed to be training anyone. They thought they were just getting some help on their jobs.
As the three-month mark approached, management began evaluating the new hires for independent deployment. What they saw were technicians who appeared to be lagging behind — uncertain about the systems, unfamiliar with the equipment, not ready to run their own jobs. Management interpreted this as underperformance. Some journeymen were let go. Others, sensing the trajectory, left first.
What management was actually seeing was the entirely predictable output of an onboarding process that had never transferred any knowledge. They had spent three months paying a journeyman $37.50 an hour to carry tools — and then evaluated them on knowledge they had never been given.
On the service delivery side, a separate but related problem existed. The company's field service operation had no standardised service standards. Customer expectations were shaped entirely by whichever technician happened to service their account regularly. One tech's approach became one customer's baseline. Another tech's approach became another customer's baseline. There was no cross-pollination, no documented standard of what good service looked like, and no way for a new technician — even a fully trained one — to know what was expected of them on any given customer account.
Service standard variance across the same company:
Without a defined standard, service quality became a function of individual personality and habit. A new technician had no way to know what customers expected because expectations had never been documented — they had simply accumulated, informally, over years of whoever happened to show up.
The turnover felt like a hiring problem. The financial reality was something different. When you lay out what five journeymen cycles actually cost — in wages alone, before recruitment, before lost productivity, before customer trust erosion — the number is not a hiring budget line. It's an operational failure with a price tag.
| Journeyman | Avg. Stay | Hours Paid | Rate | Wages Paid | Productive Output |
|---|---|---|---|---|---|
| Journeyman 1 | ~13 weeks | 520 hrs | $37.50 | $19,500 | Helper / labourer |
| Journeyman 2 | ~14 weeks | 560 hrs | $37.50 | $21,000 | Helper / labourer |
| Journeyman 3 | ~13 weeks | 520 hrs | $37.50 | $19,500 | Helper / labourer |
| Journeyman 4 | ~16 weeks | 640 hrs | $37.50 | $24,000 | Helper / labourer |
| Journeyman 5 | ~14 weeks | 560 hrs | $37.50 | $21,000 | Helper / labourer |
| Total | ~70 weeks | 2,800 hrs | $37.50 | $105,000 | Zero independent technicians produced |
These figures cover wages only. They do not include the time existing employees spent with new hires on the job — time that was neither productive field work nor structured training. They do not include recruitment costs, job posting fees, or the management time spent evaluating, terminating, and rehiring. They do not include the cost of customer accounts that received inconsistent service during transition periods.
$105,000 in wages. Zero independent technicians produced. The same cycle starting again.
This wasn't a complex operational problem. It didn't require expensive software, consultants, or a restructure. It required four things that the business had never built and never prioritised — because the absence of each one was invisible until you looked for it.
None of these things are difficult to build. A structured onboarding program for a field service technician role typically takes 20–30 hours to design properly. The technical documentation exists in the heads of experienced technicians — it needs to be extracted, not invented. The competency sign-off is a checklist, not a performance review.
The business didn't build them because nobody had ever stopped long enough to ask why good people kept leaving. Management was so focused on the next hire that they never examined what was happening to the current one.
This case study is a cautionary tale precisely because the FIELD Method™ was never applied here. What follows is what the engagement would have looked like — and what it would have found.
This is where the cautionary tale becomes a business case. The four systems that would have broken this cycle permanently — a structured onboarding program, a technical standards library, a competency sign-off process, and a service delivery standard — are exactly the kind of work The FIELD Method™ is built to deliver.
Here is what the engagement would have looked like, what it would have cost, and what that number looks like against the $105,000 the business spent cycling through five journeymen who never had a fair chance to succeed.
That is the difference between what the business spent cycling through five journeymen and what it would have cost to fix the system that was producing the cycle. A FIELD Scale engagement would have paid for itself before the second journeyman finished their first week. The system gets built once. The cycle ends.
This is not a unique situation. Across trades and field service businesses, the most expensive operational failures are the ones that repeat quietly — never dramatic enough to force a reckoning, always just manageable enough to keep the cycle going. The FIELD Method™ is built to find these patterns, name them precisely, and install the system that breaks them.
The question is never whether a proper system is worth building. It's whether the business will wait until the cost of not building it becomes impossible to ignore.
"They weren't hiring the wrong people. They were building the wrong outcome — and calling it a hiring problem."
Every one of those five journeymen was a qualified tradesperson who arrived ready to work and left without a fair chance to succeed. The onboarding process didn't fail them — there was no onboarding process. There was a ride-along that nobody had ever examined, an evaluation against standards nobody had ever written down, and a management team that genuinely believed the problem was somewhere in the talent pool. It wasn't.
The most expensive operational failures aren't the dramatic ones. They're the quiet, repeating ones that get reclassified as normal. $105,000 in wages. Zero independent technicians. The same conversation happening again at the next hire. That is what it costs when a business mistakes a systems failure for a people failure — and keeps hiring instead of fixing.