Standard Work: The More Detailed, the Less Compliance? — A Case Study of an Electronics Company's Transition from "Office-Authored" to "On-Site Defined" Standards
1. Introduction: Why a "Perfect" Standard Work is Not Followed
Many companies have faced the same dilemma when implementing Standard Operating Procedures (SOPs): process engineers put in a great deal of effort to create visually rich work instructions—actions are broken down to "pick up, align, press," cycle times are precise to the second, and are accompanied by photos and error-proofing reminders. The templates are standardized, posted on walls, and training is provided to all employees. However, once on the shop floor, employees continue to do things their own way. Audit compliance rates remain below 40%, and the reasons given by operators are varied: "It's too slow to follow this," "This sequence doesn't work," "The people who wrote the standards have never done this job."
What is the real issue? The problem lies in a step that is often overlooked: standards are "written" rather than "walked." The company analyzed in this article took three months to completely overhaul the standard work creation process, finally breaking the deadlock of "written but not recognized."
2. Case Background: The "Two-Skin" Dilemma of an Electronics Company
A certain electronics company primarily produces PCBA components for home appliance controllers, with an annual output value of about 600 million yuan and over 900 employees. It has three assembly lines operating in two shifts. In 2025, the company introduced lean management, and the first step was to implement standard work. The Process Department assigned four engineers to work in isolation for two weeks, referencing equipment manuals and old process documents to "compile" 120 standard work tickets. Each ticket was three to four pages long, with action-level descriptions, standardized templates, wall postings, and company-wide training, all done with great fanfare.
However, after one month of implementation, the data was a harsh reality check: the on-site audit compliance rate was only 38%; the customer PPM (Parts Per Million) rate increased instead of decreasing; and more troubling, employees followed the SOPs in front of auditors but reverted to their own methods once the auditors left. The Quality Manager discussed the issue with the team leaders, who revealed the truth: "Following your cycle time, my line would produce 12 fewer units per hour. Who will bear the loss in output?" The process engineers felt wronged: "We have clearly specified the actions, cycle times, and key points. Why aren't they being followed?"
3. Problem Analysis: Three "Mismatches" Turning Standards into Waste Paper
The implementation team invited a consulting group to conduct a week-long on-site analysis, identifying three "mismatches" between the standards and the shop floor, each of which could render the SOPs ineffective.
Cycle Time Mismatch: The cycle times in the SOPs were copied from the "theoretical cycle times" on the equipment nameplates. However, the actual cycle time was 8 seconds slower due to the material rack being three meters behind the operator, requiring two extra steps to retrieve each part. Following the SOP cycle times would inevitably lead to unmet production targets—not because employees are unwilling to comply, but because the standards themselves are impractical. Using unexecutable standards to evaluate employees results in employees voting with their feet.
Sequence Mismatch: Engineers wrote the "textbook sequence": install A first, then B, and finally screw in the fasteners. However, experienced employees actually pre-assemble all B-class small parts before uniformly screwing in the fasteners, reducing the need to change fixtures. The shop floor had already evolved a more efficient method, while the standards remained in an ideal state. Employees immediately recognize that "the people who wrote the standards have never done this job," and the standards lose credibility—once trust is lost, no matter how detailed the standards are, no one will follow them.
Key Points Mismatch: The critical skills that truly determine quality—such as the anti-reversal feel for surface mount capacitors, the "click" sound indicating the correct position of wire harness clips, and the need to add half a turn when the screw torque is at the lower limit—are all in the minds of the experienced workers, not on paper. The standards omit the most valuable knowledge, leaving only the "common sense actions" that anyone can perform.
The three "mismatches" point to the same root cause: standards are not derived from the shop floor. Writing standard work from an office is like someone who has never swum writing a swimming tutorial—no matter how beautifully it is written, it won't save a drowning person.
4. Transformation Process: A Five-Step Method from "Office-Authored" to "On-Site Defined" Standards
The company spent three months completely revamping the SOPs for four critical production lines. The implementation team set a strict rule: standard work must be written at the workstation, not in the office. The entire creation process was divided into five steps.
Work Observation: Teams of three—process engineers, team leaders, and experienced employees—spent three consecutive days at each workstation, observing without interruption or guidance, and only recording "how it is actually done": action sequences, handling distances, waiting times, and abnormal interruptions. The first day was to help employees get used to being observed, while the second and third days provided more accurate data. After three days, each process had a "real work map," which, when compared to the paper SOPs, clearly showed the differences—these differences themselves were the best improvement lists.
Action Breakdown: The work was broken down into main tasks, auxiliary tasks, and human-machine waiting periods, and each action was registered in an action breakdown table: the purpose, key points, and required time for each action. The breakdown granularity was controlled at the "step" level rather than the "action" level—too coarse and the key points are lost, too fine and no one will read it. Experienced employees explained "why they do it this way" during the breakdown process, and those "feelings" and "tricks" were captured and written into the key points column. This step made the engineers realize for the first time that the knowledge density on the shop floor far exceeds that in the process documents.
On-Site Timing: Each cycle was observed 20 times continuously, and extreme values caused by material shortages or machine stoppages were excluded before calculating the average, while also recording the range of variation. The timing results surprised everyone: a workstation with a theoretical cycle time of 42 seconds actually took 50 seconds, and the bottleneck was not in the equipment but in the material rack position and tool placement. Moving the material rack forward by two meters and changing the tools to a hanging system brought the cycle time back to 43 seconds—no equipment investment was needed to "buy" back 7 seconds.
Workload Chart Layout: The actual times for each workstation were plotted on a workload chart, making the bottleneck workstations immediately apparent. Two actions from the bottleneck workstation were reassigned to adjacent workstations with spare capacity, improving the line balance rate from 71% to 89%. This step made employees feel for the first time that "standard work is helping us reduce the burden, not just imposing restrictions"—attitude change is often more important than the method itself.
Employee Co-Creation and Pilot Run: The initial draft of the new SOPs was first reviewed by all employees on the shift, and any feedback was addressed on the spot. Then, one line was selected for a one-week pilot run, during which 47 feedback items were collected, and two revisions were made before full-scale implementation. The final version was condensed to a single page: cycle time, work sequence, standard WIP (Work in Progress), three key points, and a diagram, posted directly in front of the workstation, making it easy to glance at and follow, no longer needing to flip through the three to four-page "manual."
5. Results and Reflections
Three months after the transformation, the data showed: the on-site audit compliance rate increased from 38% to 96%; the assembly line defect rate decreased from 8200 ppm to 1500 ppm; the time for new employees to work independently was reduced from 14 days to 5 days; and during the customer second-party audit that year, 20 workstations were randomly checked, and the action consistency rate met all standards.
Upon reflection, the true gains from this transformation were not just the over 100 new SOPs, but three cognitive shifts. First, standards are "walked" out, not "written" out—the best standards come from the shop floor, and the role of engineers is to be "recorders and optimizers," not "inventors." Second, employees are the best teachers—experienced employees possess a wealth of tacit knowledge, and excluding them from the creation process means losing half the value of the standards. Third, creation is just the beginning—the company simultaneously established monthly work observation and quarterly standard review mechanisms, allowing standards to evolve with improvements, otherwise, in six months, today's hard-won standards would again become waste paper.
6. Conclusion
Standard work is the foundation of a continual improvement system, but whether this foundation can be solid depends on how the first shovel of earth is dug. Instead of spending two weeks in the office "compiling" a hundred documents that no one reads, it is better to spend three months on the shop floor "walking" out ten truly followed standards. The level of detail is never the key; proximity to the shop floor is. When an SOP can make an experienced worker nod and say, "This is exactly the job I've done for decades, and it's even clearer than what I can explain," it truly deserves the title of "standard."
Summary: The level of detail in standard work is not as important as its proximity to the shop floor—let standards emerge from the workstations, and employees will truly take them seriously.
Knowledge ID: 5.3.2
Version: v20260831
Author: Quality Excellence Think Tank The Quality Excellence Think Tank is dedicated to providing systematic professional knowledge, methodologies, and practical tools for quality management practitioners, helping companies continuously enhance their quality capabilities.