Why manufacturing employees leave and how to understand why
Operators, technicians and supervisors leave for reasons that sit in shifts, skills and supervision. How to ask, read the pattern by shift and act on it.
6 min readRead articleMachine vision companies fit cameras and software to production lines to inspect, read or guide. The work needs people who know both optics and the customer's product, and that mix is rare.

Not sure what you need? Tell us about your business in six short steps and we will come to the first meeting prepared.
Share your requirementsA machine vision company builds systems that look at parts on a line and judge them: checking presence, size, print, surface faults or reading codes. A job starts with an application study at the customer's plant, where lighting, camera angle and product variation are tested. Engineers then select cameras and lenses, build the inspection software, test it on samples and fit it on the line. After installation, the system must be tuned as the product, lighting or speed changes. Teams include application engineers, software and algorithm developers, hardware and lighting specialists and field support. Many customers lack anyone who can look after the system, so calls come to the supplier. People who combine optics, software and plant knowledge are scarce. See also HR for manufacturing.
These are the places the people side of this kind of business tends to give way. The rest of this page works through them.
HR here has to work for each of these groups, not only the office. The set-up below is written with all of them in mind.
The engineer who studied the customer's product knows which lighting works, and that detail is rarely written down.
Software teams build an algorithm in the office, and field engineers find at the line that lighting and product variation break it.
A system needs adjustment as products change, so support engineers are on constant calls without a rule on how much is paid or free.
Time on the customer's line is limited, and trials run at night or on weekends with the same few engineers.
Candidates who know optics, software and industry are few, and a long hiring delay holds back projects.
Operators who see false rejects switch the system off, and the supplier is blamed.
Start with the topics that matter most here: Recruitment and Talent Acquisition; Learning and Development; Organisation Design. Then work through the rest. Each topic is written for manufacturing, not in general.
Requisition to joining, the same way every time.
Training planned from need rather than from the calendar.
Structure, reporting lines and who is allowed to decide what.
How many people, in which roles, by when — and what they will cost.
A first day that is the same for the fifth joiner as the first.
Records, attendance, leave and the day-to-day HR that must simply work.
Salary structure, payroll inputs and a month that closes on time.
Goals, reviews and ratings that hold up in a conversation.
Named backups for the roles that cannot be vacant.
Communication, recognition and the conditions people actually work in.
Two routes — one for complaints, one for conduct — kept separate.
Policies a manager can apply, and obligations with owners and dates.
Induction, records, incident reporting and follow-through.
Who leaves, when, why — and which of them mattered.
Resignation to relieving letter, in a defined order.
Records that survive people, and approvals that do not queue.
A short monthly pack management actually reads.
An HR function that runs the same way every month.
The pieces a machine vision companies business puts in place, in an order that makes each easier. Open any card for the detail.
A standard sheet with product, lighting, camera set-up, samples used and tuning notes, kept by the application engineer and reviewed by another.
What this coversHideA standard sheet with product, lighting, camera set-up, samples used and tuning notes, kept by the application engineer and reviewed by another. See hr documentation process.
A rule that developers join at least one site trial for each major project, so field problems reach the code early.
What this coversHideA rule that developers join at least one site trial for each major project, so field problems reach the code early.
Written rules on what tuning is included, how fast a call is answered and who covers after hours, with a rota for support engineers.
What this coversHideWritten rules on what tuning is included, how fast a call is answered and who covers after hours, with a rota for support engineers. The attendance and shift process supports the rota.
Agree line access windows early and share the trial load across the team, with rest after night work.
What this coversHideAgree line access windows early and share the trial load across the team, with rest after night work.
A short session for line operators on what the system does and what to do when it rejects wrongly.
What this coversHideA short session for line operators on what the system does and what to do when it rejects wrongly. See communication skills training.
Before changing anything, find out what is true today. These checks take an afternoon and tell you which of the topics above to start with.
Share your requirementsConfirm with a qualified professional. What applies to you depends on your business, your state and your arrangements, and it changes. This page describes practice. It does not state a legal position.
The services below fit this kind of business best. Each starts by recording where you stand, and every later report compares against that. We do not promise outcomes.
Written application records and role records so knowledge does not sit with one engineer.
A hiring process for scarce engineers who combine optics, software and plant knowledge.
A support rota and rest rules for night and weekend trials and calls.
Helps engineers explain the system to customer operators in plain words.
Start with a free conversation, or see the paid HR Diagnostic.
Understand the business, its workforce, current processes and HR challenges.
Find the missing, weak, inconsistent or person-dependent processes.
Create the structure, processes, policies, SOPs, dashboards and systems needed.
Help HR and department managers actually adopt the new system.
Digitise repetitive and approval-based workflows where it is worth doing.
Track hiring, attendance, employee cost, performance, training and attrition.
Strengthen the people-management system continuously, not once.
From the GullyHR blog: one on HR in manufacturing, and one on each of the topics this page points to.

Operators, technicians and supervisors leave for reasons that sit in shifts, skills and supervision. How to ask, read the pattern by shift and act on it.
6 min readRead article
Candidates who accept and never arrive are usually lost in the silence between offer and joining. What actually causes it, and a contact plan that closes the gap.
8 min readRead article
A calendar of courses, a budget spent by March and no record of what any of it changed. What a learning and development process contains when it starts from need rather than from the catalogue.
7 min readRead article
A flat structure works until the founder becomes the only route to a decision. How to tell when you have passed that point, and how to redesign without a reorganisation.
8 min readRead articleMore on the GullyHR blog.
Use a standard record for each job, review it with a second engineer and have them join follow-up visits. Do it while the work is fresh.
Send them to at least one trial per major project and have field engineers review code changes. Both sides learn quickly.
Write the support scope, response times and what is chargeable. Share the call load on a rota.
Test what they can do on a real problem, hire for aptitude in one area and train the rest. Expect the process to take time.
Train line operators on what it does and why it rejects, fix false rejects fast and keep a channel for feedback.
We would ask which applications only one engineer understands, count site trials developers joined and review how support calls are shared. A good first piece of work is an application record and a support rota. Scope is agreed in writing afterwards.
All 7 business types in industrial automation and robotics · Find another business type
Identify payroll leaks, record gaps and hiring bottlenecks in a free first conversation, and leave knowing what to fix first.
Know what you need? Share your requirements in four short steps.
Want the full picture? See the paid HR Diagnostic.
Prefer a quick message? Chat on WhatsApp