Recent thoughts on the overtime work of QC team leaders: Why has the monthly salary system become a "stumbling block" for on-site management?
1. Starting point of the problem: "Being present" is the core value of the QC team leader
In the past week, I've been constantly pondering a "contradiction" in the quality department - the QC team leader, who is supposed to be an "on-site supervisor", is always "absent" when the production line is working overtime.
The work of a QC team leader has never been about "sitting in the office writing reports". When the production line changes models, they need to confirm the first-piece inspection standards; when new employees measure the wrong dimensions, they need to provide immediate guidance; when batch defects occur, they need to trace the source at the first moment... In these matters, "being present" is more important than "ability". However, the company sets a "monthly salary system" for QC team leaders, with the logic being "fulfill duties within eight hours, and overtime is voluntary". But on-site problems never care about "clocking out on time". Last Wednesday during the night shift when rushing orders, a new employee misinterpreted the "appearance defect judgment standards". Since the team leader couldn't be found, the production line had to be stopped for 40 minutes, ultimately resulting in 200 products needing rework. Last Friday, when the production line temporarily changed materials, the QC's on-site inspections were interrupted, and a batch of uninspected defective products almost made it out.
I suddenly realized that the "flexibility" of the monthly salary system has instead become the enemy of "on-site responsibility". Team leaders would think, "I've done what I'm supposed to do within eight hours. Overtime is extra and unnecessary." However, what the on-site situation actually needs is precisely this "extra presence".
2. The Logical Flaw of the Monthly Salary System: The Disconnect between Remuneration and Responsibility
More importantly, the monthly salary system eliminates the "incentive for overtime work". Previously, I had a chat with five team leaders: "Would you be willing to work overtime if there were overtime pay?" 80% of them said "yes" – it's not that they are lazy, but they think "it's unnecessary to work for free". For example, Team Leader Wang dealt with production line anomalies on three late shifts last month without getting a single cent. He said, "I also want to help on-site, but I always feel that 'I'm at a loss for doing extra work'."
The essence of the monthly salary system is to "bundle the payment for duties", but the duties of the QC team leader are "dynamic" - they need to step in when the on-site work is busy and can take compensatory leave when it's idle. However, the company's monthly salary system turns the "dynamic responsibilities" into "static eight hours" - it's like asking a firefighter to work on a "desk job salary" while requiring him to be "on call at any time", which is neither reasonable nor sustainable.
3. Mandatory penalties are a dead end: they can address the body but not the mind
At first, I also had the idea of "mandatory overtime" - stipulating that "when the production line works overtime, the QC team leader must be on duty. Those who fail to do so will have 200 yuan deducted from their performance bonus." But after careful consideration, this method has three potential risks:
Be in the wrong: The company clearly promised that "the monthly salary system means eight - hour work", but suddenly went back on its word. The team leader would think that "the company doesn't keep its word."
Inefficiency: Even if the team leader comes, they are "physically present but mentally absent" - with the mindset of "just killing time to avoid pay cuts" and will never handle problems with dedication.
Opposition: Coercion will turn "management issues" into "labor - management conflicts". The team leader will regard "overtime work" as "the company targeting me", and instead resist on - site work.
In a nutshell, solving problems by "blocking" will only create more problems.
4. Breaking the deadlock: Use "data + incentives" to turn "unwilling to do" into "willing to do"
After figuring out the root cause, I did three "specific things":
① Count the "real needs": Provide a basis for the plan
I went through the production logs and QC duty schedules for nearly three months and calculated two key data points:
- The production line needs to work night shifts to rush orders for an average of 15 days per month. Correspondingly, the QC team leader needs to spend an additional 12 - 15 hours on - site.
- In the current monthly salary, the value of "extra working hours" accounts for approximately 15% of the total salary. That is to say, the team leader used to work overtime for free before.
② Reconstruct the salary logic: Ensure that efforts are rewarded
Split the monthly salary of the QC team leader into two parts:
Fixed basic salary: Corresponding to "basic duties within eight hours" (such as formulating inspection plans and training new employees).
Overtime subsidy: Calculated on an hourly basis, and the standard is 1.2 times that of ordinary employees (which not only reflects the management value of the team leader but also conforms to cost control).
In this way, "overtime work" is no longer an "obligation" but a "rewarded duty":
- When the production line works overtime, if the team leader goes, they can get overtime pay.
- If you don't go, you won't get this part of the money. Replace "coercion" with "incentive", and people's behavior will naturally change.
③ Substitution system: Make responsibilities clearer
I added a rule called "On-site Collaboration Rules" to the plan.
When the production line starts working overtime, the QC team leader needs to arrive at the post synchronously and be responsible for three tasks: first - piece inspection confirmation, abnormal situation handling, and guiding new employees. Those who fail to arrive at the post will have their "on - site management performance" (accounting for 20% of the total performance) deducted for the current month.
This is not "forced overtime" but "clarifying the boundaries of responsibilities". You are the team leader, so you have to take on the on - site problems, and there is compensation for this "taking on".
5. Communication with the human resources department: Replace "persuasion" with "data"
When I talked to the HR manager this afternoon, I didn't preach any big principles. Instead, I directly laid out three tables:
- "Correspondence Table of Production Line Overtime Periods and QC Requirements" (Explanation of "Why Team Leaders Need to Work Overtime");
- Analysis of the Monthly Salary Composition of QC Team Leaders (The original salary did not cover "extra working hours");
- "Team Leader's Research Results" (80% of people are willing to work overtime for overtime pay).
The personnel manager only took five minutes to make a decision: "We can conduct a trial run in the assembly workshop and the injection molding workshop first, and then make adjustments based on the data after three months." He said, "This is not a salary increase. It's about turning 'ambiguous costs' into 'clear incentives' – it can solve on-site problems without increasing the company's burden."
6. The essence of management: "Dredging" is always more effective than "Blocking"
This incident made me understand more clearly that management is not about "controlling others" but about "straightening out the logic".
The problem with the monthly salary system lies in the misalignment between "responsibility" and "reward" – you pay a person who has to "stay on-site" an "eight-hour wage" but require him to "be on standby at all times", which is inherently unreasonable. Changing to a base salary plus overtime pay is essentially a form of "relieving the pressure":
- Use "motivation" to turn "unwilling to do" into "willing to do".
- Use "data" to turn "vague requirements" into "clear responsibilities";
- Use "systems" to transform "opposition" into "synergy".
7. Resistance to change: Think three steps ahead
Of course, I haven't ignored the resistance either. Old employees will definitely complain, "We could earn this much without overtime before, but now we have to work overtime to get it." The solution is actually very simple:
① Transparency: Explain the logic clearly
When having a group meeting, I will make a PPT on "working hours statistics" and "salary breakdown" and clearly tell everyone:
② Provide a transition period: Allow old employees to adapt
Veteran employees can enjoy a "one-month buffer period": In the first month, they will be paid according to the original salary, and the transition will be gradually carried out starting from the second month. Newly appointed team leaders will directly follow the new system - use "time" to ease the resistance.
③ Speak with results: Let everyone see the benefits
During the trial operation period, I will count two data every week:
- On - site abnormal handling duration (Target: Shorten from 40 minutes to 15 minutes);
- Team leader overtime rate (Target: Increase from 30% to 80%).
When the results come out, there's no need for me to explain. Everyone will naturally approve. There has never been a shortage of supporters for the solutions to problems.
Finally: The core of management is "making people willing to do"
After going around in a circle, I found that what I should really think about is not "how to make the team leader work overtime" but "how to make the team leader willing to work overtime".
The trap of the monthly salary system lies in "taking people's efforts for granted"; while good management has always been about "transforming taken-for-granted efforts into responsible actions with rewards".
Just like this plan, there is no "compulsion" and no "punishment". It simply clarifies the "ambiguous rules" and reveals the "hidden rewards". People are all driven by self - interest. If you make them feel that "it is beneficial to themselves to do this thing", they will naturally do it.
This is the power of "looseness".