No history yet

Implementing Deming's Principles

Transcript

Beau

Okay, so we've been through Deming's life, the System of Profound Knowledge, the 14 Points… and it all makes so much sense on paper. It's this beautiful, logical framework. But then I think about trying to actually… you know, *do* it. In a real company. And it just feels… huge. Overwhelming.

Jo

That's the classic reaction. Because it is huge. And I think the first mistake people make is treating it like installing a new piece of software. You know, you follow the manual, check off the 14 points, and poof, you have a Deming-ified company.

Beau

Which is exactly what I would try to do. Create a project plan with a Gantt chart.

Jo

Exactly. But Deming's work isn't about project management, it's about cultural change. It's less like building a machine and more like… gardening. You can't just command a seed to grow. You have to create the right conditions—good soil, water, sunlight—and then tend to it.

Beau

Okay, gardening. I like that. But a garden has weeds. What's the biggest weed when you're trying to plant these ideas?

Jo

Resistance. Almost always. And not necessarily from the people on the factory floor or answering the phones. It's usually from management.

Beau

Because they're being asked to give up control? To stop managing by numbers, which is one of the 14 points we talked about.

Jo

Precisely. Their entire career might be built on hitting quarterly targets and managing individual performance metrics. Deming comes along and says, 'Stop that. Drive out fear. Focus on the system, not the person.' That's a direct threat to their worldview and, frankly, their job security as they see it.

Beau

So how do you get past that? You can't just walk into your CEO's office and say, 'Hey, that MBO system you love? It's ruining the company.'

Jo

You don't. You start small. You find one part of the system that is clearly not working and that people are frustrated with. Something with a tangible output. Say, the process for onboarding a new client. Everyone agrees it's slow and error-prone.

Beau

Okay, I can picture that. A classic bottleneck.

Jo

Right. So you get a cross-functional team together—someone from sales who sold the deal, someone from finance who does the billing, someone from operations who delivers the service. You don't call it a 'Deming Transformation Initiative.' You call it the 'Make Onboarding Suck Less Project.'

Beau

I'm on board with that project name. So you're smuggling the philosophy in under the radar.

Jo

You're demonstrating its value. You use the tools. You map the process. You use a control chart to understand the variation in how long it takes. You identify the special causes of delay versus the common causes. You're teaching them about variation and systems without ever giving a lecture on the System of Profound Knowledge.

Beau

And when you make progress, you have data. Not just feelings, but actual proof. 'Our average onboarding time went from 15 days down to 4, and errors dropped by 90%.'

Jo

Exactly. Now you have a story. Management understands that language. You've just measured the impact in a way they can't ignore. And even more importantly, the people on that team now get it. They've experienced the power of breaking down barriers and improving a process constantly. They become your advocates.

Beau

So it's a beachhead strategy. You win one small, decisive battle, and then you expand from there.

Jo

A perfect way to put it. You know, there was a hospital system, ThedaCare, that did this brilliantly. They had a huge problem with patient wait times and treatment delays. They didn't try to fix the whole hospital at once. They started with one specific value stream, say, from cardiac event to treatment.

Jo

They got nurses, doctors, admin staff, and even janitors in a room to map out every single step. They discovered massive delays were caused by simple things, like waiting for a specific piece of equipment to be cleaned. They applied these principles—improving the process constantly, breaking down departmental barriers—and achieved dramatic results in that one area.

Beau

And I bet once that happened, the oncology department next door started saying, 'Hey, how can we do that?'

Jo

That's how the culture spreads. Success is contagious. It’s not a memo from the top; it's a pull from the teams who want to do better work and are sick of the broken system.

Beau

So the measurement part is critical. It's not just about improving things; it's about proving you've improved them. But how do you measure something like... 'driving out fear'?

Jo

That's a fantastic question. You can't put a number on fear directly. But you can measure its effects. Are people reporting more near-misses and small errors? That sounds bad, but it's actually great. It means they're not afraid to point out problems.

Beau

Ah, so you're measuring leading indicators, not lagging ones. You're measuring the health of the soil, not just the size of the vegetables.

Jo

Bringing it back to the garden, I love it. Yes. Another one is tracking the number of improvement suggestions implemented. Is that number going up? Do people feel empowered? It's about finding proxies for the culture you're trying to build.

Beau

So, the takeaway here isn't to go in with a megaphone announcing the Deming revolution. It's to find a squeaky wheel, apply the principles quietly, get a data-driven win, and let that success do the talking for you.

Jo

That's the heart of it. The transformation happens one process, one team at a time. It’s a slow, steady, and constant improvement. Just like Deming said.