Safety glasses are sitting in lockers

Grinding throws sparks, dust, and micro‑abrasives that cause eye injuries even when the operator “feels fine.” Particulates can lead to scratched cornea or long term eye injury.

Operators mostly understand the risk and expectation. However, compliance is low or zero because wearing safety glasses is not practical in current conditions. Fogging, discomfort, and lack of visibility are common reasons. These are valid and can be dealt with. Here are some tips to improve worker safety and comfort. Here is an easy way to prove you care about your employees and their health.

Show a 10‑second demo: shine a flashlight through airborne dust. It reveals the invisible plume.

OSHA actively enforces eye protection in grinding departments. In a recent case, OSHA cited Yesac Corp. for allowing employees to grind without safety glasses, issuing a serious citation under 29 CFR 1910.133(a)(1) with a final penalty of $3,376.20. Across all industries, OSHA issued 220 citations totaling $603,672 for eye‑protection violations in the past year, and national PPE data shows eye‑protection citations average $3,425 each. Grinding without safety glasses is one of the most consistently fined PPE failures in U.S. manufacturing.

Risk --> to --> Fix

Getting abrasive particles in your eye can scratch the cornea.
Fines average $3,000-$4,000 for failure to equip safety glasses.

Make PPE comfortable, fog‑free, and easy to clean.
If PPE is miserable, compliance dies. If PPE is easy, compliance rises.

Set the expectation

Post a one‑page sheet:

• “Put glasses on before touching the grinder.”

• “Clean lenses before each job and whenever needed.”

• “There are always fresh replacements available.”

Make it easier to do the right thing

Provide good glasses, a cleaning station, and a fan/hood layout that doesn’t fog lenses.

Record keeping & reinforcement

Use a positive record‑of‑enforcement log (below).
Reward consistency.
No write‑ups needed.

🔧 ENGINEERING CONTROLS: FAN + HOOD + DUST COLLECTOR 

Correct Geometry

This is what most factories get wrong, and the part that makes PPE tolerable.

Operator & Grinder Position

• Operator stands centered in the workstation

• Facing 12 o’clock

• Back toward 6 o’clock

• Grinder and workpiece at 12 o’clock, within natural reach

GOOD GEOMETRY (Use This)

• Pedestal fan at 4 o’clock

  • Height: 36–42 inches

  • Angle: 5–10° upward

  • Purpose: push clean air across workspace toward (but not directly at) hood

• One hood only — at ~ 1:30

  • Distance: 8–12 inches from wheel

  • Height: 2–4 inches above wheel centerline

  • Angle: 15–20° downward toward wheel

  • Purpose: capture the dust/spark plume at the natural upward arc

  • Leads to central dust collector

BAD GEOMETRY (Avoid These Airflow mistakes)

• Hood at 10 o’clock (opposes fan, creates turbulence)

• Hood at 12 o’clock (blocks operator)

• Hood at 3 o’clock (too close to fan, counterflow)

• Fan blowing directly at the grinder

• Two “hoods” competing for suction

This airflow section is what prevents fogging, reduces PPE friction, and makes compliance sustainable.

👓 Recommended Anti‑Fog Safety Glasses (Highly Reviewed)

All options below are ANSI Z87‑rated and well‑reviewed for grinding, anti‑fog performance, and comfort.

Buy a few pairs of each and let individuals pick a favorite

• Pyramex I‑Force dual‑pane anti‑fog, removable foam, great for hot grinding bays.

• Honeywell Uvex Genesis XC reviews great anti‑fog. Unsealed

• Tirade Sealed Safety Eyewear Ratcheting temple – 15 Degree for a customized fit

🧼 Safety Glasses Cleaning Station (Tissues + Anti‑Fog Solution)

Place one station at the grinder entrance and one near the time clock. [^5] [^6] [^7] [^8] Best Value:

• Pyramex LCS20 — 16 oz solution + 1200 tissues.

• NSI C-Clear™ Non-Silicone Anti-Fog Small Disposable Reusable Safety Glasses Lens Cleaning Station

 📋 Positive Record‑of‑Enforcement Log (No Write‑Ups, No Drama)

How to enforce compliance and avoid fines and injury without penalty or threats to position.

How it works

Supervisors approach a clipboard with three checkboxes and do a single spot check each day.

[ ] PPE worn correctly

[ ] Quick reminder

[ ] PPE unavailable / needs replacement

(I recommend - include Part Number / Ordering info to streamline restock)

No names or write‑ups. Just a record of interaction.

Why it works

It creates:

• A record of enforcement

• A record of coaching

• A record of system failures

Without creating a writeup system or threatening positions or penalties.

How to display it

Mount a clipboard at the grinding bay entrance with:

• The daily log sheet

• A pen attached with a retractable cord

• A “PPE Check‑In” sign above it

Workers see supervisors checking the board, that’s reinforcement of the requirement. 

🖊️ Attached Writing Implement Setup

This seems like a pointless addition but one main reason why logs don’t get used is because the paper is far from a pen, and once it slips the mind, it’s gone forever. So the habit doesn’t stick past probably 3 days.

Use a retractable badge reel or coiled tether screwed into the clipboard.

• Pen never disappears

• Supervisors don’t have to hunt for one

• Log gets filled consistently

🧩 What the Plant Manager Can Do Next

1. Buy the glasses + cleaning stations

Use the links above.
Stock 2–3 models so workers can choose what fits.

2. Install the cleaning stations + clipboard

Put them where workers naturally pass.

3. Position the fans and dust collection hoods

This is the most important step. Without preventing the known issues of sweating and fogging, proper usage remains uncomfortable; always a battle to maintain compliance.

4. Train supervisor on the 30‑second log

No names.
No punishments.
Just checkboxes.

When dealing with purchased parts from outside suppliers where you do not control the upstream process, Go/No-Go gauges are highly effective defensive containment strategy—provided they are used to enable Poka-Yoke (mistake-proofing) at the line level.

Here is how to think about Go/No-Go gauges, why they don't violate lean principles if deployed correctly, and how to use them effectively when supplier control is out of your hands.

1. Reframing the "Inspecting Quality In" Dilemma

The phrase "inspecting quality into a product" refers to taking a batch of finished assemblies, measuring them at the end, sorting the bad ones into a scrap bin, and hoping the good ones ship. That creates waste (Muda) because labor and material were already expended on bad units.

Using a Go/No-Go gauge at Incoming Receiving or at an In-Line Station works differently:

• It is Containment, Not Process Control: You aren't pretending the gauge fixes the supplier's process. You are building a firewall so vendor defects don't consume high-cost internal labor down the line.

• It Prevents Defect Propagation (Poka-Yoke): If a gauge is integrated into the assembly nest (e.g., a part physically cannot fit into the fixture unless its key dimensions are within tolerance), the gauge acts as a mistake-proofing device. It stops an operator from attempting to assemble a bad part.

2. When Go/No-Go Gauges Are Highly Effective

• Purchased Parts with Unknown/Variable Capability: When you don't own the CNC machines or injection molds, a gauge gives immediate binary feedback (Pass/Fail) without needing skilled technicians to read calipers or micrometers on every single incoming batch.

• High-Speed Line Integration: Reading a dial indicator takes 10–15 seconds; dropping a shaft into a ring gauge takes 1 second.

• Preventing Downstream Tool/Fixture Damage: Catching an oversized component before forcing it into a delicate assembly fixture saves downtime and tool wear.

3. The Major Risks & Pitfalls of Go/No-Go Gauges

While effective for containment, Go/No-Go gauges come with distinct technical limitations you must manage:

• Zero Trend Information (No SPC): A No-Go gauge tells you a part is out of tolerance, but it doesn't tell you how far out. It doesn't tell you if the supplier’s tool is wearing out over time or if the process is drifting toward the high spec limit. You get an attribute (Good/Bad), not variable data.

• Gauge Wear and Calibration: Go gauges wear down over time because they constantly make physical contact with passing parts. An uncalibrated Go gauge will eventually start letting bad parts pass.

• Operator Force Variance: If an operator forces a No-Go pin into a hole, they can force a bad part to "pass" or ruin the gauge.

4. Strategic Framework: How to Deploy Gauges Correctly

To turn Go/No-Go gauges into an effective quality shield without falling into the "inspecting quality in" trap, follow this 4-step framework:

Step 1: Push Inspection Upstream via Fixturing (In-Line Poka-Yoke)

Don't make operators pick up a hand gauge, check the part, lay the gauge down, and then install the part. Make the assembly fixture itself the gauge.

• Design the loading nest so an out-of-spec component physically will not seat.

• If the part doesn't drop in effortlessly, it's rejected instantly before any assembly labor is spent.

Step 2: Establish "Source Inspection" Clauses with Vendors

Use your Go/No-Go gauges to hold suppliers accountable:

• Require suppliers to purchase or manufacture the exact same Go/No-Go gauge set you use.

• Put in the purchase agreement that parts must pass that specific gauge at their facility prior to shipment.

• Shift the inspection labor cost back to the vendor.

Step 3: Use Guardbanding for Critical Purchased Tolerances

Because Go/No-Go gauges don't give exact measurements, vendor parts right at the spec boundary can cause friction during assembly.

• Make your receiving Go/No-Go gauge slightly tighter (guardbanded) than the engineering drawing limit.

• This guarantees that any part passing receiving will assemble smoothly without tight-fit rejections on the line.

Step 4: Pair Attribute Gauges with Periodic Variable Audits

While line operators use Go/No-Go attribute gauges for speed, Quality Assurance should sample 5 to 10 parts per lot with optical comparators, CMM, or micrometers.

• Use exact data to track supplier Statistical Process Control (SPC) trends over time.

• If CMM data shows the vendor drifting toward the upper spec limit, alert the vendor before your line operators start catching hard rejections on the No-Go gauge.

Summary

Using Go/No-Go gauges to weed out bad purchased parts isn't a violation of Lean philosophy—it's necessary containment.

The ideal progression is:

• Short Term: Use Go/No-Go gauges at receiving or line entry to stop the bleeding.

• Medium Term: Integrate the gauge directly into the assembly station's fixture (Poka-Yoke).

• Long Term: Send the gauge specification to the vendor so they reject bad parts at their factory floor, not yours.

I walk into a light assembly facility. Somebody in the back corner, headphones in, has a bench full of finished units that came off the line looking correct and don't function correctly. He's been fixing these for years. Ask anybody in the building who handles the hard stuff and they point at him without looking up.

This is not rare. It's electrical and electro-mechanical assembly, mostly. Component tolerances stack up wrong, or a dimension is off by a hair, and the unit passes visual inspection and fails the thing it was actually built to do. So one person spends eight hours a day troubleshooting and reworking units that everybody else already signed off on.

That job becomes easy for him. Repeatable. He gets so familiar with the failure patterns that he settles into something close to a zen state, doing not the same thing every time, but one of the same hundred things, over and over, all day. He's not struggling. He's cruising. And that's exactly the problem, because nobody can document what cruising looks like, and nobody can train a new hire to do it.

I call this the best person bottleneck. It's the person with the most expertise and the most tenure on a product, who has absorbed so much responsibility over the years that almost everything they touch has quietly become expert-level artisan craft. Nobody assigned it to them that way. It just accumulated.

Sitting with him

I'll sit with one of these guys for up to four hours, once or twice a week. Watching, asking, interviewing. And for the first hour or two it feels like a dead end. Every unit has a different defect. Every fix sounds like a special case. It feels non-transferrable, because from where he's sitting, it is; he's never had a reason to sort his hundred fixes into categories. He just does the next one.

That feeling is a trap. Sit there another day or two and you start noticing the same errors resurfacing, dressed up slightly differently each time. The thing that looked one of a kind the first time you saw it turns out to be the fourth time you've seen it this week.

Once you can pull out what's actually recurring, and pin down what the troubleshooting was, why it had to happen, and precisely what he did to fix it, you can start to describe the ideal state of the unit. Sometimes that ideal state isn't written down anywhere. It's not on the drawing. It only exists in his hands. If you can move that ideal state upstream, into the process before the unit ever gets to his bench, he has fewer things left to fix, and a junior associate can be trained to handle the handful that remain.

Where the ideal state is hiding

Building quality into the process ahead of time isn't easy, because a lot of what needs fixing is something the engineers never thought to specify. It doesn't become real until fabrication shops and suppliers start sending parts that meet the drawing, or almost meet it, and somebody downstream has to decide when "almost" does, in fact, count. 

Nobody sits down and fine-tooth combs fifty-five tolerances and dimensions on a single bracket. Nobody has time for that, and honestly, most of those fifty-five don't matter.

But once you've watched enough rework, you start to know things like this: if the leg on this particular bend comes in short, that's always a problem. So maybe incoming inspection on that part stops trying to check everything and just measures the leg length. You can trust the rest of the pattern, because it's a CNC laser-cut part and the cutting was never where the variance showed up. The bending was.

That's the whole game. Not inspecting more. Knowing what to look for and exactly where to look for it, because somebody already paid for that knowledge one rework at a time, and it's sitting in his hands, waiting for somebody to write it down.

The Fosbury Flop: Why Breakthrough Improvement, "Kaikaku," Beats Kaizen When Time Matters

Everybody has heard of Kaizen, because it makes and keeps a neat little promise. Unfortunately, it often keeps teams wading in the shallow end of the pool. Breakthrough improvements are really the better story, don't you think?

Let's jump in. 

In 1968, an awkward university student named Dick Fosbury changed high jumping forever by doing something that looked completely wrong.

While everyone else perfected the Western Roll and Straddle techniques, methodical incremental improvements to the traditional form, Fosbury literally went backwards. His "Fosbury Flop" approach had him launching over the bar backwards and headfirst, landing on his back.

Coaches called it dangerous. Traditionalists called it a gimmick. Oh.. okay...? 

Let's go see who made it on the podium. What's your guess, the traditionalists or Dick Fosbury?

By all physiological metrics the LEAST athletic participant in the event, Fosbury easily won gold at the 1968 Olympics. He made every other technique obsolete overnight. Within a decade, nearly every elite high jumper had adopted his "backwards" method.

The Manufacturing Improvement "Kaizen" Timeline

Traditionalist manufacturing improvement follows predictable phases. 

First twelve weeks: considering whether to bring in outside expertise or double down with internal resources. Many readers are within these first 12 weeks at this moment! Welcome. 

Weeks 13-20: We found the expert. 30+ years in the industry. A real fixture of our region. 

Consultant: Opens briefcase. What's inside? The Western Roll. Value Stream Mapping. Meticulous assessment and planning. Daily meetings. Seminars, glossary sheets, count footsteps, 30-cycle time studies. Statistical distribution data analysis. Ooh... this one's a gamma, so we're gonna have to really dig. 

Weeks 21-28: Meetings. Rearranging workstations. Pilot implementations and refinements. Consultant exits after 16 weeks on site. 

Outcome: Party with cake. We have reduced weekly walking distance by 700 feet per employee (in the pilot cell). We now project 6% labor savings per part. 

Current Calculated Parts and Labor: Parts = $120, Labor = $32.00

Improved Calculated Parts and Labor: Parts = $120, Labor = $30.08

Those are certainly outcomes. They didn't make anything worse. The consultant was precise. His guidance was confident and well-practiced. Your team knows your processes better than anyone. Your engineering staff has deep technical knowledge. Your operators understand the practical constraints and know their tasks extremely well. Everything is INSANELY precise and provable. Unfortunately this might have been a waste of 28 weeks. 

"Kaikaku," or The Factory Fosbury Flop

Kaikaku means breakthrough improvement. 

I hadn't heard this word until this week (well I still haven't heard it, I've only seen it in writing). 

Anyways, by this "Japanese principle," instead of incrementally optimizing existing processes, you fundamentally reimagine them. Instead of gradual assessment phases leading to gradual implementation phases, you systematically identify constraints and engineer solutions.

Breakthrough Timeline:

First twelve weeks: considering whether to bring in outside expertise or double down with internal resources. Many readers are within these first 12 weeks at this moment! Welcome. (Worth mentioning, I could save you 3 months of losses if you decide sooner - and ROI is guaranteed.) 

• Week 13: We brought in the MR Guy. Constraint identification and throughput analysis

• Weeks 14-16: Systematic redesign and rapid prototyping

• Week 17: Implementation with embedded monitoring systems

Target performance achieved and sustainable - and we're looking at more than 6%, folks. 

Less time, better results. 

Why This Feels Counterintuitive

The traditional approach makes sense. And it is familiar. It is familiar because it is done every day by tons of teams globally. Thorough analysis reduces implementation risk. Gradual rollouts allow for course corrections. Extended timelines accommodate learning curves and organizational change management.

These are legitimate considerations from experienced manufacturing professionals.

But for two reasons, choose breakthrough improvements. 

For the time on site, let's just compare two approaches for similar results. 

Similar results? Never. But let's say these two methods both arrive at the same 6% savings. I would never walk away from anything with 6% but I can pretend if we really need to keep it apples to apples. 

Improvement per week.

Did you know you can just make up metrics to compare things?

Traditionalist

6% / 16 weeks = 0.375% improvement per project week

Breakthrough

6% / 5 weeks = 1.20% improvement per project week

This shows that accomplishing a result in 5 weeks is better than the same result in 16 weeks by about 3.2x. 

...Now consider the disruption. 

Traditionalist

Meetings

32 x $1,000 meetings (two per week, all participant salary and opportunity cost of halted throughput)

Implementation

Two Work Days to move all the desks around and plug everything back in. 

Breakthrough

Meetings? 

No. I will work and speak with operators sparingly. Maybe 5-10 minutes?

I will work and speak with managers and directors as requested, engineers as needed

I will present Options and Recommendations once I have play-tested any hypotheses or assumptions

Implementation

I will look for opportunities to grow throughput by 2x, 5x, or 10x in every way possible including streamlining, reassignment, strategic support, fixturing, work holding, error-proofing, material presentation, design for assembly and design for manufacturability, BOM simplification, job design, and work precedence improvements. 

Everywhere I've served, I have found hundreds of thousands of dollars in savings and throughput improvements. I love throughput. Not every option or recommendation is selected for implementation. But you can depend on significant throughput and quality improvements in every project. 

If your factory would be better off if you could just make more each day of what you sell, toss the tradition and perhaps start with a free baseline assessment.

If you're already making enough product each day for all customers, meeting monthly shipment targets, and rarely struggling with shortages or stoppages, your system is already in pretty good shape, and you might instead benefit from sales and marketing improvements. Those are things I am not qualified to touch. I mean just look at this website. I spent more time debugging one html hyperlink issue than it took to solve an $85,000/month quality problem. And I have no clue why some key elements don't show up on Google. ...I'll stick to productivity & throughput. 

Practical Kaikaku Framework

Week 1: Constraint Reality Mapping, material flow observation. Systems, Processes, Methods, - inputs and outputs. Track actual parts through actual processes. Identify where work stops, not where procedures say it should flow. Note backlogs and queues. Find imbalance and busy work. Many bottlenecks hide behind "that's just how we've always done it" explanations.

Week 2-4: Systematic Process Redesign Challenge fundamental assumptions. "Why do we batch this operation?" "What if we eliminated this inspection step?" "Could we mistake-proof this instead of error-detecting it?" Design solutions that make defects impossible, not just catch bad parts before loading them onto the truck.

Week 5: Implementation Instill changes, deploy automatic feedback mechanisms. Create visual management that makes highlights deviations. Build monitoring into the process, not on top of it.

The Uncomfortable Truth About Continuous Improvement

Most manufacturing operations have capable, dedicated teams working on legitimate improvement initiatives. Kaizen events deliver measurable gains. Value stream mapping identifies optimization opportunities. Statistical process control maintains quality standards.

The challenge isn't competence. The challenge is velocity. Those first 12 weeks are not the time to be meticulous when you're missing $10,000 per day in revenue. 

When you're systematically optimizing a fundamentally constrained process, improvements simply plateau. 

When massive breakthrough thinking eliminates constraints entirely, performance curves jump to new levels.

When Backwards Thinking Becomes Forward Thinking

Dick Fosbury's technique looked wrong until Olympic medals proved otherwise. His innovation wasn't about "higher jumping." He just noticed his hips were always hitting the bar, so he invented a whole new jump that maximized the vertical displacement of his hips.

Manufacturing breakthrough thinking works similarly. Instead of asking "How do we make this process better?" ask "What if this process didn't exist?"

Sometimes, (well at least One Time), the most productive question isn't "How can we get more experts involved and keep track of the (always missing) tape measure to help identify and sort each pallet of these components when they arrive?" but rather "Why can't the fab shop dump all of these 96 parts into 8 labeled bins rather than in one big sloppy pile?" 

At a previous employer we faced an incoming Bureau of Workers' Compensation (BWC) visit the same day a huge delivery of steel arrived. The fire extinguisher was now 100% obstructed, and the pallets were double- and triple-stacked, wall-to-wall, down the aisle. The supervisor, Nate, looked at the few inches between each pallet and started listing who he'd pull from production to use forklifts and pallet jacks to scoot all the pallets outward by a few inches each. Hopefully this would add up to create just enough walkway toward the center to reach the extinguisher. He planned to go all-hands on deck for the next 30 minutes so we wouldn't be out of compliance when the auditors arrived. 

I surveyed the crowded floor and all the sheet metal, then glanced up at the extinguisher hanging in its bracket. There was a little sign pointing down to it from above. Four (4) screws held them in place.

"Actually, Nate, what if I go reprint the area map and you could just ask maintenance to put the extinguisher over there. And can you let the rest of the guys know we're moving it?"  

So I pointed 'Over there' to another wall, cleaner, with better lighting, and a location that would never be inadvertently blocked by materials. Today's steel is not the problem. The planning was the problem. This was a mistake from 20 years ago.

 I remember this only because of the way he stood there with his arms crossed, one hand covering his chin and mouth. He squinted, tilted his head, and half‑nodded, like half “who are you,” half “I think there's something really wrong with this guy."

"Yeah, no problem, easy," he motioned away from his chin to the blocked pathway, "Man, but who thinks like that?" 

When the old guard teaches teams to “straddle” constraints, backwards thinking asks if those constraints even exist. 

Flip a problem on its head. Practice object impermanence. You might uncover something innovative hiding behind twenty years of “that’s just how we do it.”

Both continuous improvement and breakthrough methodology can move the needle. But only one gets you to target performance in 12 weeks instead of 52.

But right now you need to decide: keep perfecting your “Western Roll,” or change the game entirely.

Ready to see what backwards thinking could reveal in your operation? Let’s pinpoint the constraints you’ve been working around instead of eliminating.

Understanding Variation: Managing Chaos

March 31, 2025

by Mitch Robinson

This quote is from Understanding Variation: The Key to Managing Chaos, by Donald Wheeler, and perhaps it has just changed your life. Check out the book if you're interested in a bit of profound knowledge. 

“Every data set contains noise. 

  Some data sets also contain signals. 

  Before you can detect the signals within your data, 

  you must filter out the noise.” 

           -Wheeler

If your company is comparing sales or defects or shipments "month over month" or "versus this time last year" they are wasting everyone's time and attention. Learn about the nature of variance in statistics and save a string of pointless meetings!

Get yourself a copy of this "cult classic" for $5. 

link: Understanding Variation - The Key to Managing Chaos 

"We live in the Information Age, and much of that information comes to us in the form of numbers. 

...But before numerical information can be useful it must be analyzed, interpreted, and assimilated. 

...Unfortunately, teaching the techniques for making sense of data has been neglected at all levels of our educational system. 

...As a result, throughout culture there is little appreciation of how to effectively use the volumes of data generated by both business and government. This book can remedy that situation. 

...Readers report that this book as changed both the way they look a data and the very form of their monthly reports. It has turned arguments about the numbers into a common understanding of what needs to be done about them. These techniques and benefits have been thoroughly proven in a wide variety of settings. Read this book and use the techniques to gain the benefits for your company." 

If nothing else check out the mind-bending examples of how well-meaning managers inadvertently manipulated their actions to satisfy metrics, usually to show progress or improvement, much to the inadvertent detriment of their businesses. 

I'll take the OVER if we're betting: 

"This still happens in 95% of companies and almost everybody is blind to the underlying facts."

What I could accomplish? Check out recent projects 🔗

Startup Support, Kaizen Workshops, and Contract Engineering opportunities

Or sign up for your free 4 hour factory analysis - for the curious & cautious.