Walk through an offsite construction factory, and you will hear complaints. Somebody is waiting for material. Someone else has drawings that don’t match what's on the production line. A supervisor wonders who approved a change, while the person doing the work wonders why nobody told the supervisor.
If you have spent enough time around factories, you know that complaining is practically an unofficial department. It doesn’t have a budget, although it can certainly help explain where some of the money went.
My first reaction when somebody starts bitchin’ is to wonder whether they want to solve something or simply find an audience. But making that judgment too quickly is dangerous. The loudest person might be pointing to a problem management should have addressed three weeks ago.
Here is the approach I believe makes sense: “Bitchin’ doesn’t fix a factory. But neither does ignoring the person who spotted the problem. Tell me what’s wrong, bring an idea if you have one, and let’s figure out what we can do about it.”
That puts responsibility on both sides. Employees need to explain what they are seeing. Management needs to do something useful with the information.
First, Find Out What the Complaint Actually Means
“This place is a mess” might accurately describe somebody’s afternoon, but it gives a production manager little to work with. Neither does “Engineering never gets anything right” or “Purchasing needs to get its act together.”
The first step is to turn the complaint into a specific problem. Which drawing is wrong? What material is missing? Which module is affected? Where did the work stop, and what happened immediately before it stopped?
Imagine a crew repeatedly discovers that the window openings shown on its drawings don't match the windows delivered to the factory. The complaint might start as, “Here we go again. Nobody around here knows what they’re doing.”
A manager can argue with that statement for twenty minutes. Or the manager can walk over, compare the drawing with the delivered window, check the approved specification, and establish exactly where the mismatch occurred.
One approach creates an argument. The other creates something the company can investigate.
That distinction matters because a loud complaint can contain a legitimate problem, just as a calm explanation can contain a mistaken assumption. Volume is not evidence. Go look.
You Don’t Need to Know the Answer to Spot the Problem
I understand why owners say, “Don’t bring me problems. Bring me solutions.” They are tired of being the destination for every frustration in the building, and they want employees to think before passing something upstairs.
But taken too literally, that rule can shut down the information a factory needs most.
The employee framing a wall may know that the same opening has required rework on several modules. That employee may have no access to purchasing records, customer approvals, or the engineering revision history. Expecting a complete solution before allowing the concern to be raised is asking someone to fix a system they cannot see.
Ask for an idea. Encourage participation. But do not make having the answer the price of reporting the problem.
The better question is, “What are you seeing, and what would help us understand it?” Sometimes the most valuable contribution is simply identifying the point where the process stops working.
Protect Today’s Production Before Fixing Tomorrow’s Process
Once you confirm a problem, you usually have two jobs: contain the immediate damage and prevent it from happening again. Factories get into trouble when they do the first and declare the second completed.
In the window example, the immediate response might include identifying every affected module, separating questionable material, and getting approval before building more walls. If safety or structural compliance could be affected, stop the work until qualified people resolve the issue.
That is containment. It keeps the problem from spreading.
Having a skilled carpenter modify the opening may get one module moving, but it does not explain why the wrong information reached the station. If the drawing release process remains unchanged, tomorrow’s crew may face precisely the same problem.
Offsite factories often have employees who can rescue almost anything. Those people are valuable, but their ability to recover should not become management’s excuse for leaving a broken process in place. A factory cannot build its operating plan around somebody performing a small miracle before lunch.
Follow the Problem Across Department Lines
The place where a problem becomes visible is not necessarily where it began. A production mistake may have started with a late customer decision. A material shortage may trace back to an incorrect bill of materials. An installation problem may involve a substitution that never made it into the drawings.
This is why “tell production to be more careful” is so often an incomplete answer.
Bring together the people who handle the affected steps and reconstruct what happened. What information was approved? Who received it? Which version was used? Was an earlier version still available at the workstation? Did the schedule allow an unresolved decision to enter production?
Keep the discussion focused on the sequence of events. If everybody spends the meeting defending their department, the process will escape without a scratch.
The goal is to identify the condition that allowed the mistake and the missing check that let it reach the next person. Accountability still matters, but a public scolding is not a revision-control system.
Give the Fix an Owner and a Deadline
“We need better communication” may be the most comfortable conclusion ever reached in a factory meeting. Everybody can agree with it, and nobody has to change anything before heading back to work.
A workable correction is much more specific. It identifies who will do what, by when, and how the factory will know it worked.
For the window problem, that might mean assigning one person responsibility for coordinating approved window specifications with purchasing and drawing releases. It might include a check before the affected job enters production and a way to withdraw superseded drawings.
The exact answer depends on the cause. Adding another approval signature will do little if the real problem is that employees cannot tell which drawing is current.
Keep the correction practical enough to survive a busy Tuesday. A process that requires six people to stop everything for a routine decision will soon develop an unofficial shortcut.
Then check the result. Review the next affected jobs. Did the dimensions match? Did rework decline? Did the crew receive the correct information before starting? Closing an item on a meeting agenda is not the same as closing the problem on the floor.
What Happens When Management Keeps Ignoring It?
At first, the consequences can look manageable. A little extra labor. A delayed station. A supervisor pulled away from another task. Nothing that appears large enough to justify interrupting the production meeting.
But repeated problems add up in costs across the factory. Rework uses labor that should be advancing another module. Replacement materials cost money and take time to purchase. Delays can disrupt later stations, delivery arrangements, and site schedules.
The schedule may still look respectable because employees absorb the damage through overtime, improvisation, and unfinished work pushed downstream. That doesn't make the problem cheap. It makes the expense harder to see.
Quality can also become inconsistent as different crews develop different workarounds. One person follows the drawing. Another follows yesterday’s verbal instruction. A third uses the method that worked on the previous house. Now the factory has several answers to a question that should have had one approved answer.
Eventually, the consequences may reach the builder or customer through defects, delays, callbacks, and explanations nobody enjoys making.
The Most Expensive Consequence May Be Silence
Another cost doesn't show up neatly in a job report. Employees learn whether speaking up accomplishes anything.
If someone reports the same problem repeatedly and gets only irritation or silence, they may stop reporting it. Management may mistake the quieter floor for an improving operation, when all that has improved is the employees’ ability to keep their opinions to themselves.
That is a dangerous trade.
The people closest to the work often see trouble while it is still small. When they stop sharing what they see, management loses an opportunity to intervene before a recurring annoyance becomes a serious production, quality, or safety issue.
Close the loop with the person who raised the concern. Explain what you found, what will change, or why you can't use a proposed solution. Even when the answer takes time, a clear update is better than allowing the complaint to disappear into the office.
Gary’s Observation
I am not suggesting every complaint deserves a committee, a consultant, and a new software subscription. Some complaints need a straightforward explanation. Some need a firm conversation about personal responsibility. Others need the owner to put down the coffee and walk out to the production line.
The important thing is knowing which one you are hearing. You will not find that out by automatically dismissing the complainer, and you will not fix it by letting the same complaint become part of the factory’s daily soundtrack.
A well-run factory gives people a way to raise problems, expects them to participate where they can, and makes someone responsible for following through. It also checks whether the correction actually worked.
Bitchin’ by itself won’t fix your factory. But when someone keeps pointing to the same problem, I want to know whether I am listening to a difficult employee—or an expensive mistake management has learned to tolerate.
No comments:
Post a Comment