Episode Details

What if you could tackle a persistent problem without guesswork? In Part 10 of the Path to Improvement series, John Dues and Andrew Stotz discuss how John's team uses Plan-Do-Study-Act (PDSA) cycles to calm a chaotic process with precision. Discover how to shift from blame to solutions by leveraging data and Deming thinking. You'll also find out where the team stands on their path to reducing chronic absenteeism in their schools. Listen now! #EducationLeadership #ContinuousImprovement #SystemsThinking #DemingInEducation

TRANSCRIPT

0:00:02.2 Andrew Stotz: My name is Andrew Stotz, and I'll be your host as we dive deeper into the teachings of Dr. W. Edwards Deming. Today I'm continuing my discussion with John Dues, who is part of the new generation of educators striving to apply Dr. Deming's principles to unleash student joy in learning. The topic for today is mapping the process, part two. John, take it away.

0:00:23.5 John Dues: Hey, Andrew. It's good to be back. Yeah, we've now been talking about our efforts to improve chronic absenteeism for several episodes. And we've talked about two Plan-Do-Study-Act or PDSA cycles focused on where we were working with specific students and their families regarding obstacles to getting to school. And then we shifted gears, and we started running this PDSA cycle three that we talked about last time. And just as a refresher for listeners, the objective of PDSA three is to create a process map, basically. And the goal for the process map is to standardize our attendance intervention system. And I think one of the things that comes to mind when you sort of work on process maps or on important processes is this quote from Dr. Deming. He said, If you can't describe what you're doing as a process, you don't know what you're doing, which is pretty convicting when you really think about it. I think a lot of people initially will say, No, no, no, I know exactly what our process is. And then you say, Well, write it down, map it. And then it becomes much more apparent that most people most of the time have a very rough version in their head that they can't translate into an actual written process.

0:01:44.8 Andrew Stotz: And I'm curious why that is, because on the one hand, when I've done mapping a process, you end up with, Okay, but then there's this exception, and then there's this. And oh, yeah, but don't forget that. So there's like all these intricacies. That's one reason. And then there's another reason is why is that someone's tunnel vision on I know the process because I know the three parts of the process that I'm working with. Why do you think it's hard for people to understand the whole process?

0:02:11.9 John Dues: Well, I think that first reason is probably the biggest reason where there's when they actually start mapping it, there's all these things that they initially left out. And I think as soon as an organization gets to a certain number of employees and has a certain amount of complexity, or you have to add a person that's now going to do part of what you previously did because your role changed or something shifted, needs change, or whatever in the environment. And you have to bring them in. You realize pretty quickly that you can't rely on that stuff that lived in your head anymore. So I think it's a combination of all those things for why this becomes so important. And the other reason I mean, the reason you want to do this is so that there's a starting place, a standard place where people are working from so that whatever it is that the focus is that it can be improved. It's hard to do that when there's no set process to start with.

0:03:08.5 John Dues: Let me. I'll share my screen and just kind of as a refresher, take a look at