Learning Without Scars
ExplorePodcast overview and latest content
EpisodesBrowse the full episode archive
TopicsDiscover episodes by category
PostsBrowse published articles & write-ups

Podcast

  • Explore
  • Episodes
  • Topics
  • Posts

Recent Episodes

  • How Fractional HR Helps Founder-Led Firms Avoid Landmines And Build Better Teams
  • If Best Doesn’t Mean What You Think, What Does It Mean
  • Old Tools, New Minds
  • What If The Normal Distribution Is The Biggest Lie In Your Business
  • How Concentration, Clean Data, And Customer Choice Beat Giants

About

Learning Without Scars

Learning Without Scars

Powered byPodRewind
    Learning Without Scars
    S2 E34•August 15, 2022•55 min

    Process Mapping Explored with Sara Hanks

    Send us Fan Mail (https://www.buzzsprout.com/1721145/fan_mail/new) Sara Hanks and I follow up on her Blog from August 9th on Process Mapping. In order to be effective at Continuous Improvement (CI) process Mapping is a foundational requirement. With Continuous Improvement it is felt that an improvement operationally of ten percent is very possible. This Candid Conversation covers the history of Process Mapping from the days of Industrial Engineering to the Data Analytics world we live in today. I am more than pleased that we have someone of Sara’s background and experience to point us in the right direction. Visit us at LearningWithoutScars.org (https://www.LearningWithoutScars.org) for more training solutions for Equipment Dealerships - Construction, Mining, Agriculture, Cranes, Trucks and Trailers. We provide comprehensive online learning programs for employees starting with an individualized skills assessment to a personalized employee development program designed for their skill level.

    Transcript

    0:21

    Aloha, and welcome to another Candid Conversation. Today we're joined by Sarah Hanks, and we have a subject that's near and dear to my heart from my old industrial engineering days. Sarah wrote a blog that's going up tonight on process mapping. So Sarah, welcome. Good day. Glad to see you. And here we go.

    0:46

    Aloha. It's good to be here.

    0:49

    What in the heck? For the unclean, unwashed is process mapping.

    0:59

    Well, I think, you know, just simply it's everything that you do, whether it's in your day-to-day life or is part of a task at your job, you're trying to accomplish something, an output. And process mapping is really identifying all of the things that need to happen between when that process needs to start and you deliver that final output.

    1:28

    Yeah, and in my era, it was called industrial engineering. It still is. And we used to do process flow charts, which is a very similar thing, much more rudimentary than the tools that we have today. But process mapping is, I think it's absolutely critical. And the reason I say that is if you go back to the 80s and the Japanese arrival of the total quality management, continuous quality improvement, whatever, that was almost revolutionary. And yet it's been around for hundreds of years. And the Japanese term of Kaizen, continually improving something every day, even if it's one one hundredth of a percent, as a cultural truth. is totally different than America. We teach people how to do things and say, okay, get faster, fewer mistakes, congratulations. But we never really get down to, why do we do that? It's true, isn't it?

    2:36

    Yeah, it's definitely true. And I think, you know, I think... Even stuck in status quo, what I've seen is people don't even necessarily follow the same standard to begin with. And so status quo is defined as chaos and everybody's doing things a little bit differently. And imagine all of the waste buried in all of that. You know, for example, taking a project through our business process, right? And every person that you ask. you get a different answer on what is required.

    3:11

    So how do you initiate these things? How do you get a company, a business, a department, an individual's attention saying, hey, George, you really need to do this? How do you stimulate the interest?

    3:30

    Well, I think it starts with, well, at least in my practice, there's an understanding that a change is needed, right? I think, and I mean, I know we talked about like people being stuck in status quo, but anytime we've been doing one of these, there's usually a reason to want to do things differently.

    3:54

    Yeah, I call those triggers. Yeah,

    3:57

    trigger. Maybe you're late delivering product to the customer, right? Maybe there's a shortage and you have to figure out how to deal with it. Maybe there's absolutely triggers, perfect word. So there's an identified need. And where I like to start is getting people to understand, well, how are you doing it today? And that's generally what starts the conversation then around. process mapping, because I think if you don't know where you're starting, it's really hard to get cleanly to where you're going. Yeah. And also you solve problems that aren't problems necessarily, right? You might have a trigger, let's say you're late and you have a assumption that the reason why you're late delivering product to your customer is the equipment's down, the manufacturing equipment's down. But maybe that's not the root cause. Maybe the root cause is something completely different. So you end up wasting time and money fixing problems that aren't true.

    4:56

    And I don't know how you can scope a problem to solve or to understand the red X until you understand what your current state looks like. And that starts with process mapping.

    5:06

    So in essence, if I could wave a wand, if you could wave a wand, we would want to have every process of every business mapped with precision. In great detail. Absolutely. Who's supposed to do it? So if we went into an organization, instead of looking for a policy manual or a procedure manual, I want to see the process map store.

    5:32

    I think a process map is going to tell it a lot easier than a manual will.

    5:37

    I agree. A visual is always easier. So you get a company, somebody identifies a problem. And we're agreeing we're going to go forward and do this. Who should be involved?

    5:54

    Well, I think that a representative from every role, function, person who's in that process, who has a step that's responsible to execute a step of the process needs to be involved.

    6:09

    So can I call them owners?

    6:12

    Yeah, I would say process owners. Well, generally, I like to think of. An owner of a process is being like who owns the output, but there's handoffs along the way. So as long as it's clear on what the definition of owner means, it's at a step level, not at the overall level. Obviously, the overall owner, the person who is accountable to the output of a process should champion it.

    6:39

    Yeah.

    6:40

    But they need to solicit input from others, too.

    6:43

    So we start having different jargon. process owners of steps. We have process owners of the business process. And then we have champions who are going to be the folks that we're going to rely on to implement. Is that a fair?

    7:03

    Yeah, they're going to be the ones to hold the team accountable to implementing the change. Okay.

    7:09

    So we come in, we've identified there's a problem. We're going to identify that we're going to solve the problem by doing process mapping. We've identified the people that are going to be involved in the deal. And it could be a large crowd. It could be five. It could be. It could be 10 people. It could be 20 people, depending on how big the process is. Do you try and limit the size of the audience that you're dealing with?

    7:36

    By limit, well, there's two ways you can limit. It's hard to control a room of 20 people and getting inputs. It's really hard. I don't know if I've had like a hard cap, but I do try to limit either based on scope, right? You can say, oh, we're going to process map our business and that's pretty broad and you're going to involve a lot of people. But if you narrow down the scope to, you know, what is the start? What's the end? I don't know if you've heard of this, a SIPOC or a COPUS. If you have a defined, where do you want to start? What are your inputs? And then what are your outputs and your customer? If you define that small enough, you can control the size of the room that way. But then also, you probably don't need multiple representatives of the same function. You can bring in somebody to act on behalf of the team or provide input.

    8:31

    So one of the things that you bring up is we should have a glossary of terms, shouldn't we?

    8:37

    Oh, for sure. Acronym CITY. I am the worst jargon.

    8:43

    We were just talking with a school this morning about classes and curriculums, and we have a reading list at the front end. And one of the deans that I was talking with said, you know, I need a glossary of terms because there's so much jargon here. I said, OK, I'm going to put that as part of the reading list at the beginning, and I need to make it compulsory now. because we don't want to have them misunderstand what that term means. He said, that's excellent. So I said, do you mind if I make a compulsion? He said, no, no, it should be.

    9:17

    Well, and then also accessible, right? Like you could turn in, you know, I'm thinking about, oh, I don't remember that term. Maybe it's hard for me to memorize and retain. You know, you could use a chatbot as, you know, a way to quick query the.

    9:34

    Exactly. So now we have. You know, can I help you? Little bubbles floating all over the place. It's interesting. So we have a glossary of terminology so that we don't get lost in jargon. We limit the audience by how we define the scope of the project. Yeah. I try not to have more than a dozen.

    9:56

    I would have said 10, but yeah.

    9:59

    Yeah. Okay. And the reason a dozen is dirty dozen, I always have to have some kind of, you know. anchor on which I can hang things. But it, okay, so that crew, every process, in my view, needs to have a goal statement. What does this process do?

    10:21

    Yes. I don't think we've done, I don't think in my process mapping, I've been clear on making sure the goal is defined up front. I think that's excellent.

    10:34

    It's well, it's I think we mentioned I mentioned this when we started our chat today. I use the term guidelines instead of policies. And the guideline is campaigns, for instance. When we run a campaign, here's a description, two, three, four paragraphs of what we mean by the campaign. OK, who owns the campaign? The person responsible, your process owner. Then. Is there a financial implication? If not, if there is, what is it? Is there a efficiency? What's the metric? Who owns it? Who can make changes? What data is involved? What formulas? And when was it last reviewed? So that there's clarity. And it always confused me because like you said, you go into a process mapping, six people do the job and they don't do it differently. Chaos is a perfect word. And what we're trying to do with the process mapping is also identify the skills that are required for the tasks within the process. True?

    11:41

    Yeah, absolutely.

    11:42

    And I don't think you could do a very good job at that.

    11:45

    Well, no, it's just like your blog that was released this morning on getting to a job description, right? I mean, you have a process, you have a clearly defined goal of the process. Yeah, to your point, there's things that need to happen along the way. And what does it take to do it? And that's your skills. And then how do you design your jobs to be around the skills instead of around the tasks?

    12:10

    It's interesting, isn't it? Because I don't, even in your manufacturing days, the job wasn't around skills, was it?

    12:18

    Not unless you were specialized. Not unless you were specialized. If you were specialized, I would say it's skill-oriented.

    12:24

    And in the case of the specialization, though, the skills that you acquired were given to you by the person who trained you, correct?

    12:31

    Yeah, that's true.

    12:32

    And there were no native skills required to facilitate or accelerate the training.

    12:38

    No.

    12:39

    Right? Yeah. It's kind of upside down. Yeah. It's, you know, we have SAT tests and ACT tests and all manner of different IQ tests and EQ tests. personality profiles, all kinds of things. But we really don't get down to what are your latent skills. You have really good organizational skills. You have really good interpersonal skills. You have really good analytical skills. We don't know a lot about that, do we?

    13:11

    No, no. I haven't seen tests that get into that level too until I think maybe a year and a half ago, I found a skills assessment test that actually. was structured that way. And I've been around for a long time and, you know, that was the first I've ever seen it.

    13:30

    People say that about our assessments, especially in the education community, that, you know, we have a 96 question multiple choice assessment of the job function skills. And they say, wow, nobody's ever done this before. And of course they have, but we don't find it's not generically used. Yeah. Okay, so we got the owner, we got the problem, we got the process identifier we're going to play with, we got the team, we know who's going to be the champion. What do you do?

    14:00

    Well, before, I like to get, my preference is to get everybody in a room. I've tried this, the virtual way. It's okay, but there's nothing that can replace like the natural chemistry that happens when you get everybody in a room to talk. You can see body language. You can identify if someone's frustrated. It's just more effective to be together. So that's going to require scheduling time. And so that is a hurdle in itself at times because you've got to take people out of their jobs for a long enough period of time. I'd say four hours minimum. It could be eight hours or even two days depending on the scope. And so getting something on the calendar, getting everybody's leaders, if it's necessary to buy in and excuse their time, I think that's, that's gotta happen. And then between like the time you schedule and the time you have the event, I think it's important to do pre-work. And what I see is pre-work.

    15:07

    If you is, you need to have something to start off of instead of going in with a blank sheet of music, because if you. When facilitating a discussion like this, ask people their opinion and it's going to go all over the place. And it's really hard to like hurt cats. So I like to go in with rough draft. And my favorite tool to go in with a rough draft is, it's another acronym. It's called a RACI chart or a RASC-Y chart. I define it the GE way, which was, you know, R is who's responsible for doing a step. The S is who's supportive. A is approver, although in a lot of documentation, they say accountable, but that's confusing to me because if you're responsible, you're accountable. So why? I didn't understand the difference. And then I is inform and C is consult.

    16:07

    And if you have at least a rough draft of what are the process steps and who is responsible, and how they, or needs to contribute to this and how, to me that at least gets you a place to start and it makes the conversation a lot more structured and less wandering because you have a place you can return to.

    16:32

    One of the things I find intriguing about what you do is that I don't believe there's a lot of people that are doing this. And I believe that this is absolutely critical. It has been critical, but going forward, it's going to be even more critical. And we've talked about this. With COVID, we compressed people's thinking, hopefully. Working from home as an acronym, as causing all kinds of angst problems for people. Really, the only folks that can work from home. are in major corporations. You know, a mechanic has to go to the job. An accountant has to go to the job. Somebody making food has to go to the job. There's no question about those things. Right. The big corporation jobs that can be done from home, I would submit to you that those are the first jobs that are going to be replaced with robotics.

    17:37

    That's an interesting point.

    17:39

    You know, so process becomes even more critical down that end.

    17:45

    Absolutely.

    17:46

    You know, robots can do an awful lot of things and robots in the manufacturing circumstance can do an awful lot of things, but there's limits. Right. And unless we get serious about what that process is, we're going to make big mistakes. Make a mistake with a robot, it's going to be a very costly mistake.

    18:04

    Even if you're looking to implement some kind of robotic process automation to replace transactional work. If you don't have a clear understanding of the process and what happens when things don't go to plan and how often, you're going to spend a lot of time implementing and money implementing these bots, right? And they're not going to be effective. So you have to understand how does work get done at the nitty gritty detail level.

    18:34

    Guys, one of the things that I have a strong belief in is you slow everything down at the front to speed everything up at the back. You do your planning, you do your detail work. And if you've got it all done, everything is easy. If you don't have it done, like you say, implementation becomes an unbelievable mess.

    18:51

    I've experienced it.

    18:53

    Oh, so it's not fun. It's not fun. So what do you have any tools that you use to facilitate the process mapping? Like you do wall burning or. You know, anything along that line? Have you got any tricks that make it easier?

    19:15

    So I think I'm a big fan of post-it notes, paper, and I even have a kit that I've made that has like an icon that represents how things are done within a process step, right? If you're doing, if you're sending an email and that stuff, I have an email icon. If you have a, you know, something to help visualize like every step of the journey, what are you doing and how do you convey what that looks like in an easy way? I think colors, assuming that, you know, I'm not sure what the guidelines are on color blindness or anything like that, but I do use colors to denote different roles or functions in a process. That way you can. clearly see who's doing what. Icons that represent, oh gosh, there's a lot of waste in this step of the process, or we have a lot of rework, you know, a big red, you know, starburst we would use to help identify that. And then we digitize it usually. And there's tools out there that help digitize processes pretty easy.

    20:29

    In my day, we used to call them process flowcharts. We had five icons. you know, decisions, you know, filed.

    20:39

    Here's a process block.

    20:41

    So, you know, you can monetize that. You know that.

    20:45

    I have a printable.

    20:49

    It's a tool that facilitates the process. You know, culturally, the difference between Japan and ourselves, Kaizen and not. If I could wave a wand and satisfy a dream of mine, that we'd have the same process improvement culture here that they do in Japan. And that everybody in a company would be tasked with, asked to identify what I call sacred cows. Is there something you do that doesn't make any sense?

    21:24

    Yeah.

    21:25

    Or I flip it. I have a thing I call five things. Give me five things. that would make your life easier in your job. Give me five things that are a pain in the butt to do in your job. Give me five things that'll make your job more productive for the company. So we got three different areas, five steps each, and I do this in groups. And at the end of the day, two or three of the five things are common on all. And you know what my question is going to be. If it's good for you, good for the company, and it's a pain for you to do, why don't you fix it? We don't have that motivation in our organizations.

    22:12

    I wonder if it's, I mean, I've done a lot of, we used to call them transactional lean events at GE, right? And we'd get in a room and everybody would sit and we'd map through, we identify all this waste and brainstorm ideas for solutions. And then. A lot of times things didn't happen afterwards and it boiled down to like cost because there wanted to be an investment in technology because software fixes a lot of this stuff. But in the, you know,2005 to 2015, like software is expensive. I wonder how much like not being able to fix it because there wasn't options to do it cheaply. people lost a distaste or something else happened. And I feel like in what I've seen in the culture is just like being told no over and over again, people stop trying.

    23:12

    Yeah. You know, it's, and I think it's an upbringing thing too, you know, in our families do this, don't do that. And we're trying to protect the child. Then we get to school, do this, don't do that. We're trying to accelerate the learning. And I've often said it's the troublemaker I want to pay attention to. The individual is saying, well, why are you doing that? That's crazy. I want to hear what's in their head. And then, you know, it's too expensive to fix a problem. That's a horrible answer.

    23:50

    It's a horrible answer because there's always an easy way. You can always make an incremental improvement for free somehow.

    23:58

    Exactly. But the other side of that is that that goes back to is your employee an asset or expense? Yeah. They're assets. We want to have them do the things that can't be done by anybody else. Yeah. And we don't know what those things are just yet. And unless we do a process map, we have no idea what functions are out there. It's kind of remarkable, isn't it? Yeah, it is. So we've sold things. We start with a cart. A couple hundred years ago with produce from the farmer. We go out in the street and stand in the corner and sell my apples and corn or whatever the devil it might be. Now we've got a supermarket. The cost of food,50% of it is transportation. It's weird. You process map that sucker or any supply chain issue. or particularly now with supply chain issues, what are we doing?

    24:54

    I don't know.

    24:55

    We've been doing this stuff forever, haven't we? Yeah. Yeah.

    24:59

    And it's, I think, you know, one of the things people don't think about is that cue time or that the time things are not happening, right? Like an action is supposed to happen and it's not happening and really understanding why, what's. What's driving that? Is it lack of information? Is it lack of motivation? Is it, you know, I think identifying and exposing those things, you could probably reduce a lot of your lead time issues and supply chain issues. It's not going to help your transportation cost side of it, but certainly cycle time can be impacted if people took action when action needed to be taken, right? Or that they were handed the ball, the baton, right? to take the next action and they don't. And I think there's a lot of opportunity to not invest money necessarily, but just make sure that the right trigger to take the next step is obvious.

    26:04

    You know, I sometimes use parallels of airports and let's just think of Dallas, Fort Worth or Chicago or New York or LA, major airports, Paris, Tokyo. and you and I are going to start a competitor, and we're going to build an airport 50 miles from DFW, and we're going to compete with DFW. Where in the world do you start? That spider web is so complex. Yeah. Rental cars and hotels. The story that I can reserve a car, a specific car, before I get there. And they got these cars all over the darn place. And I'll be able to go to a specific location and find the car. And then you go across the street to the hotel and they can't find the room that you've reserved. And the room doesn't move.

    27:05

    No, there's that number. It doesn't change.

    27:08

    How the heck do we get there? And again, isn't that a process deal?

    27:12

    Absolutely.

    27:13

    You know, my wife got really cranky after 9-11. didn't want to go anywhere near France because of their resistance to our desire for help. And we finally went to Paris after a long number of years. And we get to the hotel and we're greeted. The guy comes out to the taxi and sees us. And I've been there before. He says, well, welcome back, Mr. Slee. Good to see you. You're in room 1402. And my wife looks at this guy and looks at me and says, what in the hell happened to the people in Paris? That never used to happen before. Again, it's the recognition of a problem. And then somebody spent the time to determine what the process was and what the changes need to be. And the champion was going to be named and it was going to be implemented. And that person would ride off into the sunset and go do it somewhere else. Yeah. Which is what we do with process mapping. So you've been in private practice how long now?

    28:22

    Private practice, how?

    28:27

    Working freelance with different companies?

    28:30

    Well, working freelance, that's been since COVID 2020.

    28:34

    Okay. Every single client I've ever had needs process mapping. And very rarely have I been successful at getting companies to map processes. How successful have you been?

    28:50

    Well, with our software, we do it 100% when we go to a customer because I think it does a few things. It gets everybody on the same page of how things are supposed to go. And I'm trying to sell software to digitize a lot of what's there. So it gets everybody aligned on the same page. It exposes the waste in the current state, which helps me identify where the software will provide value to eliminate the waste. You know, even I'm on a board of a nonprofit and they want to change their CRM. So I've facilitated process mapping even with them just to do those things, right? Like you think changing to a new CRM or new IT platform that should bring about value or whatever. But if you don't understand what your... current state looks like where the wastes are how do you know that you're going to get that return on investment too so

    29:53

    so you introduced your software for a second why don't you take a moment and explain to us exactly what that software does for you what you're using it for why you're using it and give people a better idea of what what it does okay so

    30:10

    our software platform is it's a mechanism for companies to interface with their suppliers in a way that's collaborative. It's clear on who is supposed to do what step and it informs you what, you know, when you're supposed to take that next step so you can actually speed things up. If you're a manufacturer and you're bringing a new product line to market behind the scenes, there's a lot that happens, especially with your suppliers. You need to make sure they know what to make, that they're making it out of the right material, that they are producing parts correctly. And with a new, when you're bringing a new product to market, nothing's perfect. So there's rework that happens in the design, which then has to trickle back down to the supply chain. And so our platform makes it easy to understand where things are at in the process, who owns it. triggering the next action and it helps that time to market speed up.

    31:19

    So you have a big data collection element that ties to the software, correct?

    31:26

    Not yet.

    31:27

    Okay. Yeah. That's the next step.

    31:30

    Yeah. It's an iterative development for sure. But my intent is to put the analytics into the platform, right? So like some suppliers are better than others. And people are making decisions on what to buy from whom. So if we had AI-assisted decisions, right, like I'm going to recommend that you do this route instead of this route, you might actually have better decisions and then less rework, less, you know, better on-time delivery.

    32:04

    And just so you and I don't get caught, AI is artificial intelligence. You're letting the computer make it. that come to conclusions, make recommendations for you?

    32:14

    Make recommendations. I don't want to take, I think humans still should have some say, right?

    32:23

    For a forward thinking person, you're behind the curve on that one. There's a new AI driven computer program that plays chess that for five years has yet to be beaten. And all they, the computer was taught were the moves of the chess pieces. Nothing else. No games. Nothing was loaded. Like Big Blue had every single game loaded. And that's how they beat Kasparov because they could process all of what he had in his head faster. This time doesn't matter. They're coming up with arcane approaches that are just, what are you doing there? Which is really, really radical. I don't think we're ready yet in the human. side of things. Chess is a nice exercise. It can prove the point. But to make a determination, we're going to go from Farmer Bob to Farmer Joe because the quality of his kernel on his corn is better based on analytics. I don't think we're there yet.

    33:34

    No, I don't think. And I don't, there's exceptions too. Like you may have a reason that you would. not go with the recommendation, right? So I think having that final say, it's still important for a multitude of reasons. One, the data isn't good enough to automate the decision. You know, there's going to be messy data that's going to make it inaccurate in some cases, I think. And also from a change management standpoint, like as soon as you start talking about taking that decision-making away,

    34:07

    you

    34:09

    won't have any support.

    34:10

    That's right. Yeah, you're going to take away the bread and butter. The other thing is typically we don't have enough data points. We don't have enough data. No. You know, it's

    34:20

    the old Poisson curve.

    34:22

    Yeah, it's the old Poisson curve that 90% of the activity is in the other leg of the graph. Yeah. So in manufacturing, process mapping is reasonably straightforward. And a lot of continuous improvement projects did the manufacturing base. Distribution is slightly different, maybe a little bit more complex because you've got disparate locations, disparate functions, and maybe even disparate corporations. People need to have the ability to see that something in manufacturing would work in distribution or something in manufacturing or distribution would work in selling. Like CRM is a good case in point. Somebody bought a car 10 years ago. It's got 150,000 miles. Maybe somebody should be in touch with them saying, hey, don't you think you want to change your car? Yeah. We don't do that today. Alex Kraft, who is part of Heave, and he writes, he's got a software package that puts buyers and sellers together. So a customer says, I want this.

    35:43

    And salesmen that subscribe to Alex's service or a part of it get an email saying, George over there is looking for something. Kind of simple.

    35:53

    It

    35:54

    really does. It really does. I'm excited about process mapping. And I like your illustration of post-it notes. So if I want to have somebody who's listened to this do a process map with post-it notes. And forgetting about the ADA type of circumstance, colors and shapes are dynamic tools that you can see. I'm going to get those post-it notes. I'm going to put them all around the room, right?

    36:26

    Yeah. And the nice thing.

    36:28

    Oh, sorry. Go ahead. That's pretty easy to do. Yeah. And you started to say the nice thing.

    36:35

    Well, I was going to say, so when I do process mapping and we're trying to drive a change. we go through an exercise called waste identification. And when you identify waste, it's really important to start with traditional brainstorming techniques where people do the brainstorming silently and the post-it notes are really useful to transfer that knowledge from a person's head onto the board in a way that's respectful of everybody's. You know, it's respectful because if you're the quiet introvert, you still have an equal voice. And once the wastes are all identified on the process map, you can see clusters. Yeah, you talked about that earlier, right, with the questions and you have the same issue across all three buckets, right? You see those clusters and then you can group the clusters of waste together to do proposals.

    37:41

    And that's what I call the aha moment. They look at this and say, why didn't we see that? Yeah. It happens a lot that way, doesn't it? Yeah. It's a remarkable truth. We've been doing these things for so long. And when we go back and revisit it with a clean blackboard, I call it fresh eyes. We get stunned. It's remarkable. Why do we do that? Because we've always done it. You know, my dad and I used to argue about shoveling snow. If I'm going to have to throw snow, I only want to throw it once.

    38:20

    Yes.

    38:21

    And dad had his way of doing things. And I finally said, look, I'm not going to do it that way. I'll do it all. You go into the house. He said, no, no, I'm going to do it my way. So I said, OK, see you. And he did it himself. And he was a lot older than me, obviously. And the only way I resolved that is I bought him a snowblower. It was so inefficient, but he was so stuck on it. He could never change it. He was comfortable doing it that way. He'd always done it that way. It was almost robotic. And we have that with a lot of people. That's why I say, oh, my, that's as plain as the nose on my face. Why didn't we see that? Yeah. We're almost blind to it, aren't we? Yeah, we are. And same thing's true in your home.

    39:07

    Absolutely. I probably have some cooking examples of inefficient ways of doing things, but it's the way I do it.

    39:16

    It's the old process that one of my clients shaved his face in a different room every day to condition himself before he went to work that he was going to look at things differently.

    39:31

    That's cool.

    39:33

    Well, yeah, and I looked at him and said, you're an idiot. You don't need to have a visualization like that. You know, go to work and think differently. I'm not going to interfere with how people make it happen, but I want them to make it happen. He was a very successful change agent, but it was very, change is very hard for people. Process mapping helps with that, I think.

    40:01

    I think it does. I think it does. I mean, that's part of the outcome of. Process mapping, in my mind, is getting people to, well, A, when they participate in something, they're already committed to it in some way, shape, or form, right? Whether they're a full supporter or going in resistant, after you've spent time, you want to see that change through to completion. I think it exposes where all the shortcomings are in the current process. You know, once you see something, it's really hard to unsee it.

    40:37

    Yeah, that's really true. The other thing you mentioned earlier is that not everybody's outspoken about things. And the people, we want to give a voice to everybody. So that silence is a really good neutralizer of influence. Everybody participates in that sense and everybody is empowered in that sense. Another important feature of process mapping.

    41:01

    Yeah. Yeah, I would agree. Everybody has an equal voice.

    41:06

    You know, I did a lot of computer systems work, and I can't imagine designing or passing off an analytic process to a programmer without having really clear process mapping system flowcharts. The Post-it notes is such an easy illustration. And maybe for everybody, look at if you've still got one, the telephone operator, the receptionist. How does that work? And then the process that we went to to have everybody have their own phone number. How does that work? Yeah. And the process we have now that if you don't answer your phone and X number of rings, it goes somewhere else. How does that work? Right. And just using that as a silly example, we. make iterative changes, which makes it easier for us, I think, rather than the big leap.

    42:11

    I would agree with that, for sure.

    42:13

    So process mapping takes, segments the solution.

    42:19

    Yeah, and it can, if you keep it up to date, right, as you go through these iterations, I mean, I think the more you revisit it, the more clear it is.

    42:32

    And the more powerful. that people want to continue because they're experiencing success.

    42:38

    Yeah, absolutely. Right. Incremental is. Yeah. Only the way to go.

    42:43

    So with the work that you did at GE in here and the last X number of years, what would you do after process mapping? What's the next step? Is it automating it?

    42:58

    I think it depends on the project. I've definitely automated as part of it. In other cases, And we create what's called a Kaizen newspaper, which is really just an action plan with owners and due dates. And then we schedule a series of follow-up meetings, you know, with the champion included so that you had that person that's really going to help drive the change home and follow it through.

    43:29

    So if it's not manufacturing, it's distribution. And I want you to come in and do a determination of what needs to be mapped. In other words, I don't know the problem. I'm going to give you the opportunity. Here's the door. Come on in. Here's our business. I want you to snoop around and identify places where you believe we can make improvements. Where do you start?

    44:01

    I would start with the top of mind problems. What's keeping somebody up at night?

    44:08

    So you interview people and find that. Yeah.

    44:12

    Or if there's metric, I mean, if there's already established metrics or, you know, quantifiable things, is it a revenue challenge? Is it a cost challenge? Is it, where is it a cost challenge? Is it inventory? You know, you have to start somewhere.

    44:31

    Let me, let me stay there for a second. Most of those things are going to come from financial statements.

    44:36

    Okay. Yeah.

    44:38

    How often have you seen management reporting as opposed to financial reporting? That's a different ballgame, isn't it? Yeah. It always bothers me that we drive everything that we do off financials. Why don't we drive it off productivity? Why don't we drive it off market share? Why don't we drive it off customer retention? And none of those are in financial statements.

    45:15

    No.

    45:16

    And yet they're critical to our health, aren't they?

    45:19

    Yeah, they are. Yeah. If you don't have retention, that's the problem.

    45:24

    Huge problem.

    45:25

    Yeah. And it's productivity too. You know, with GE's like digital transformation, they did a lot of the implementation internally and they would report productivity to the street. Well, there was very strict guidelines. on what could be considered productivity even because it had to tie to the financials. And so if you saved every person in the company 20 hours a day, or not 20 hours a day, I'm sorry,20 minutes a day, right? You would have a happier workforce who would be maybe a little more efficient because they get to go home a little earlier. And none of that counted because it couldn't tie to the financials.

    46:09

    It was really funny. One of the things that I've done over the years is, We work with standard times on repair, just like manufacturing, right? And I was manic about I'm going to give everybody eight hours of work today of standard time work. Standard time always has a buffer. Yeah. Okay, always. So what I would say to people was I'm going to give you a choice. If you beat the standard time, I give you eight hours of labor, you're finished after seven. Do you want to be able to go home after seven or do you want me to give you another hour of labor? And I'll pay you nine hours today for the eight hours of work you did. Or do you want to go home after seven hours? What do you think they chose?

    47:00

    Going home.

    47:02

    It was remarkable.

    47:05

    I'm sure there were some people that would choose the extra money, but I would say the majority would go home.

    47:11

    It's split on demographics, Sarah, as to be expected. The younger people that have a young family need the money. They would work the extra hours. The older guys wanted to spend more time with mama or older gals, more time with papa. It's remarkable. And until you open up that door, the owners, they looked at me, go home, you're nuts. Right? I want the older, more experienced, more talented guys leaving early. And the young guys seeing them leave early saying, gee, when I grow up, I want to be like that. What do I need to do to get that?

    47:50

    That will help with skill development.

    47:53

    It's remarkable. It's absolutely remarkable. And the same thing's true with process mapping, I believe. Interruptions, critical. Idle time, critical. Rework, critical. How do we limit the 20 minutes you're talking about? I love it. And when you say we can make a 10% improvement, think about that.

    48:16

    It's huge.

    48:18

    I don't know that there's anything bigger. No. You know, when we got that 10% looked after, then we'll find something else that's bigger, but that's fine. Yeah. What's the next step for the audience relative to process mapping? Your blog goes up tonight that explains it, explains RACI and some of the other terminology used today. This discussion, I think, will help people understand where they could start. Any advice you'd give at this point to say, okay, this is what you do next?

    48:58

    I think what comes to mind is facilitation and learning facilitation skills. I think in process mapping, having a person that's capable of controlling a room, recentering the conversation, putting items in a parking lot that you can't. And then as far as the, you know, how do you wrap things up? I think how are you measure success and then tracking and creating a plan and then tracking that to that plan to closure and then measuring the success based on that.

    49:45

    I'm going to change the term from facilitation to communication.

    49:49

    Okay.

    49:52

    Communication skills are something that are not that common. It's kind of remarkable. We communicate with each other, talking all the time. Our families, our children are co-workers, but we don't really necessarily communicate. It's all kind of floating around up there. And the other thing that, you know, the top of mind, what keeps you awake at light? I think that's a brilliant approach. That might be something that you could focus on on another blog. What is it that motivates? What is it that initiates? What is the stimulus to get us to do a process map without you having a problem that asks you to stick your hand up? I need some help over here. What are those things that are bothering you that, you know, are hiding the problem? What keeps you up at night? That's hiding a problem.

    50:43

    Yeah, absolutely.

    50:45

    As a younger person, I didn't study enough, you know. That's keeping me up at night because the exam's tomorrow. Darn, you know, it's a little late now, isn't it? Oh, yeah. But executives have the same dilemma. There's a whole bunch of things that are sitting up there. Welsh in his book, Straight from the Gut, identified that. Here's the red items and here's the orange items. It's like a stoplight.

    51:10

    I haven't read that one yet.

    51:12

    It's a good one. Peter Senge is even better. Okay. I think we've pretty well beat up process mapping, yeah?

    51:24

    I just have a couple last-minute advices.

    51:30

    Go for it. I don't limit anybody. Let's go.

    51:38

    I think in process mapping, something you probably won't read about in a book is really to pay attention to the participants and their body language. I think you can identify a lot through that. If somebody, you know, is sitting back and is just disengaged out of the conversation, you know, go a little bit deeper to try to unpack what, why they've disengaged so suddenly there might be either a, they're super married to the. wake things are currently or something along those lines. When it comes down to communication afterwards, you may need to consider how to communicate to that specific individual. Right. I think collecting records. Oh, my gosh. I've seen so much over-processing with I've created this report because somebody asked for it 100 years ago and we still do it and nobody uses any of the information. You know, I think. Picking and collecting that stuff along the way, asking questions, who's using it.

    52:51

    I think there are two things I would add.

    52:54

    Yeah, business systems. I tell everybody that's involved, I want to know the frequency that the reporters run and who gets it. Yeah. And, you know, Jennifer Albright does a lot with purchasing and suppliers and buying. I used to go into companies and say, okay, I want every company form. Have you got an inventory of the company forms? What? You know, and then, you know, we got these 300 forms. Some of them are six part forms. Some of them are chemical. Some of them are carbon. I mean, wait a second. You know, what's going on here? There's so many things and process mapping identifies a lot of that too. Yeah. This is such an important subject. And it's one that I have a really hard time getting traction on. Getting companies to acknowledge that they need to have a look at how they've done things forever because it isn't necessarily the right way. Prove me wrong. Do the process map so you can confirm that that's the right way to do something.

    54:04

    Every now and again, somebody takes up the challenge and says, I hate you, Ron. Right? You see that all the time. Yeah. I wish it could become part of our normal way of doing things that everything that we do, we challenge at some frequency, not all the time, but it's enough frequency that you stay current.

    54:23

    Right. Absolutely. Thank

    54:26

    you, Sarah. This has been great. I hope everybody who's listening has got something from this and I look forward to having you again, Sarah, and everybody else with us again for another candid conversation. Mahalo. Thank you for listening to our podcast. We appreciate your support. Should you have any thoughts or comments, please don't hesitate to contact us at www. learningwithoutscars. com. The time is now. Mahalo!

    Process Mapping Explored with Sara Hanks

    0:00
    0:00

    Related Episodes

    If Best Doesn’t Mean What You Think, What Does It Mean

    If Best Doesn’t Mean What You Think, What Does It Mean

    Feb 13, 202657 min
    Dealer Management SystemArtificial IntelligenceCRM
    What If The Normal Distribution Is The Biggest Lie In Your Business

    What If The Normal Distribution Is The Biggest Lie In Your Business

    Feb 2, 202668 min
    Normal DistributionPower LawCustomer Concentration
    From Conventional Dealership to AI-Driven Operations: A Conversation with Troy Ottmer

    From Conventional Dealership to AI-Driven Operations: A Conversation with Troy Ottmer

    Aug 20, 202553 min
    Troy OttmerArtificial IntelligenceDealership Operations
    The Fourth Industrial Revolution: Navigating Change

    The Fourth Industrial Revolution: Navigating Change

    Aug 11, 202566 min
    Fourth Industrial RevolutionPredictive Buyer IntelligenceEquipment Dealers