They Tried for 20 Years. Here’s How We Helped Them Finally Standardize.

We recently wrapped up work with a large, family-owned manufacturing company that operates four plants across the U.S.

They had spent more than two decades trying to standardize processes across locations.

Twenty years. Multiple initiatives. Plenty of internal champions. No lasting change.

And it wasn’t because they didn’t care. Or because they didn’t have smart, capable people. It was because they were too close to it—and too consumed with the day-to-day to lead the change themselves.

When they came to us, they were clear on two things:

1. They didn’t want to hire someone internally to take this on. They’d tried that route before. What started as process improvement always got pulled into operational firefighting or team politics.
2. They wanted outside expertise—someone who could cut through the noise, ask the right questions, and actually move things forward without getting caught in the internal gravity of “how we’ve always done it.”

Here’s what we found when we came in:

Each plant had its own way of doing things. Some methods were solid. Others were outdated. And none of it was documented in a way that could scale across locations.

If someone from Plant A went to support Plant D? It was like walking into a different company. That lack of standardization was costing them—time, efficiency, and ultimately, profitability.

Here’s what we did instead of another top-down mandate:

• We visited each plant. Talked to people on the floor.
• We captured what was actually happening—not what was supposed to be happening.
• We mapped current-state processes across teams and compared where things aligned—and where they didn’t.
• Then we facilitated collaborative redesign sessions where the people doing the work got to shape the new standardized processes.

This wasn’t a one-size-fits-all approach. It was a build-the-best-version-of-what-works-and-share-it approach. And because it came from within—with the support of a neutral facilitator—it didn’t trigger resistance. It generated buy-in.

We then built the infrastructure around it:

• Standardized workflows
• Clear roles and responsibilities
• Visual SOPs and training materials
• A rollout plan that respected capacity, timelines, and plant culture

What happened next?

Processes that had stalled for decades were finally adopted across all four plants. Not because we forced them—but because we made the change doable, grounded, and genuinely better than what came before.

And here’s the thing: They could have kept trying to fix it internally. But they recognized the difference between operational ownership and change leadership. And they made the call to bring in someone who could walk beside them—not get pulled under.

If you’re staring down a problem that’s “too big to solve right now,” we’d challenge that thinking. You might not need more internal effort. You might just need the right outside partner.

Let’s talk about what that could look like: info@launchpointco.com | www.launchpointco.com