GA 287 | The Wheel of Sustainability with Adam Lawrence
26 Nov 2025 · 34 min
This podcast episode (Gemba Academy Podcast, episode 287) features Adam Lawrence describing his "Wheel of Sustainability," a model for sustaining process improvements. The Wheel has eight spokes (notification; training & review; visible evidence; tools; clear benefit; layered audits; accountability/leadership accountability; recognition) with leadership commitment as the hub. Adam illustrates the model with a weld-shop 5S/kaizen story showing how the spokes and leadership support prevent backsliding and encourage ownership. The episode closes with practical advice: tie improvements to clear purpose, ensure leadership commitment, and implement the spokes to fight organizational entropy.
Chapters
When you help people make something better, there's got to be purpose to it. If you can tie everything you're doing to that purpose, they're more likely to keep it alive.
If you've been practicing continuous improvement for any period of time, you can probably remember a time where you made something better and then you came back three months later and it had slid back to the original state, or perhaps it even was a little bit worse than it was before you made it better. Obviously, these situations are less than ideal. So being able to sustain the improvements that we make, or in a perfect world, we want to keep making them just a little bit better over time so we never have to worry about any backsliding. Well, obviously that's where we want to be with our continuous improvement journey. And that's why I'm so excited for today's show, because my guest today, Adam Lawrence, is going to talk about a model that he has created for his clients that helps them really sustain and continue to improve the process that they're focused on. And throughout this show, Adam walks us through an eight step model. And we're going to include a download of this model in our show notes. And I highly recommend that you download that model, study it, listen to the podcast, and then see how what? See how the model might work for you. Maybe you have to modify it a little bit to fit your business, but I think the principles Adam's going to share are really relevant to just about anyone who's practicing any form of continuous improvement. So show notes for this particular episode can be found over@gembapodcast.com just look for episode 287. Again, we're going to have some downloads, so be sure to visit the show notes page today. Gembapodcast.com look for episode 287 and as always, you can check out Gemba Academy's Lean Learning library over@gembacademy.com with a fully functional three day trial. All you got to do is go to the main website, gemba academy.com, scroll to the bottom and you'll see a link for a three day tr. Hit that button and yeah, you'll have access to thousands of videos and lots of learning resources. Okay, enough for me. Let's get to the show. Adam, welcome to the show. How's it going?
It's going great, Ron. Well, thanks for giving me the opportunity to be part of the conversation.
Oh, yeah, my pleasure, my pleasure. Look really looking forward to it. So, Adam, I know you've listened to the podcast in the Past. And you know how we kind of like to get things going with a quote. So do you have one?
Yeah, sure do. So I was inspired many years ago by picking up a book from Shigeo Shingo in 1991, and he was kind of my entrance way into Lean. Had been doing continuous improvement for a number of years before then. But my favorite quote is, the most dangerous kind of waste is the waste we do not recognize. And the reason why that's so impactful to me that you get so bound up in the way you do things every day that sometimes you have to be able to step back and say, wait a minute. Why am I doing it this way? Why would I put myself in that situation? And as Lean practitioners, we have that opportunity to help people see that waste that they're not recognizing on their own and then help them problem solve their way beyond that. That's great.
That's great. All right, well, let's go ahead and have you just tell us a little bit about yourself, Adam. Tell us about your background, Tell us how you first got introduced to all this continuous improvement stuff, and then tell us what you're up to these days.
Okay, well, great. Thanks, Ron. So I'm a graduate of Virginia Tech, graduated in the 80s with a degree in industrial engineering. Had the opportunity to join a company in North Carolina, and spent my early years as an engineer just helping people solve problems and make things better. So I was doing continuous improvement, probably without really knowing it, moved to Chicago. I was a supervisor in a sealing grid factory. And one evening, we were having some extreme difficulty setting up one of our punch presses. And I noticed on the shelf in the supervisor office there was this book by a guy named Shigeo Shingo called A Revolution in Manufacturing the Sped System.
Yep, I got this.
Yeah. And I said to the other supervisor, can I borrow this?
Yeah.
And he said, dude, you can have this book. I'm like, really? This looks like this could help us. So I started reading it, and all of a sudden it was like the light turned on for me. There were so many fabulous ideas in the book that I could apply directly. And so all of a sudden, I was able to help the people in my factory. And just for the next, oh, I don't know, 25 years or so, you know, I'd been applying those principles, reading voraciously, going to some conferences, you know, getting training where I could kind of creating my own approach. And I worked for essentially the same company in multiple locations for about 30 years. Early last year, they gave me the opportunity to go out on my own. Some people might call that downsizing, but that's okay. So I loved the idea that I was able to help people all over the world. And I thought, wouldn't it be great if I could come up with a way to help more people and kind of do it the way I like to do it? So opened my own practice May of last year. Was very, very fortunate to get early customers who. Who had known me in the past. And so the word of mouth has spread, and I'm just able to help people solve some pretty complicated problems. And the real work that I try to do is to engage, empower them, and then teach them how to actually sustain all the great solutions that they've created during these sessions and these visits. And so that's where I really put my energy.
Great. And we'll definitely link to your website. What's the name of your consulting business?
Process Improvement Partners.
Okay, good, good, Good. And it's PI-partners.com, i think, is the website, Right?
That's right. Good, yeah.
And we'll link to that in the show notes and we'll mention it again at the end. So. Okay. Yeah. So you just mentioned sustainability. So I think it's kind of the topic that I want to hone in on here a little bit today in this episode, and we're free to explore other areas as well. Adam, but why are you so focused on this topic of sustainability? Why is it so important to you?
Well, people spend so much effort trying to solve problems. And what I noticed over the years, including my efforts, were we solve the problem, and then it comes back. Solve the problem, then it comes back. So you put all this tremendous effort into getting people aligned around the thing they're trying to solve. They put all their energy and creativity into it. They solve it. But why is it not sustaining? So I started to really reflect and think through, what are we not doing? What's not right about our approach that isn't allowing things to sustain. So I started to realize some of the mistakes I had personally made and some of the things that I saw, and I started to build this construct around the components and the system for sustaining. For the last number of years, I've been using it, and I'm going to just say quite successfully with teams to help them sustain and actually take their solutions to an even better place.
Well, yeah, this topic is so important, you know, because, you know, back to your engineering days, the second law of thermodynamics is entropy.
Right?
And entropy is always pulling, Right. It's always trying to bring disorder into any type of system, whether it's your, you know, 5s event that you just did or your, you know, from a science perspective, the barbecue grill, you're done cooking and it's going to cool off. That's entropy. Right. The energy is going to escape. Right. Whether you like it or not.
Not.
And yeah. So if we don't have some systems in place or we don't have an approach in place, any, any, any gain, any type of improvement is going to backslide and sadly sometimes get even worse than it was before. You made it better, right?
Absolutely, absolutely.
All right, so let's talk a little bit about the model. What are you, what did you discover? And maybe I'm also curious on how you developed the model because I'm sure you, you, you probably learned some lessons along the way. So let's, let's dig into that a little bit.
Okay, well, thanks. So, yes, absolutely. Lessons learned and mistakes made along the way kept exposing components of the model that were missing for me. So eventually I started out, it kind of looked like a molecule, like a nucleus with circles around it. And eventually I built a thing I called the Wheel of sustainability and originally had six spokes and a hub and it now has eight spokes and a hub. And what I realized was not only was it helpful, but it was memorable to the team and I could explain it and we could then test against it in any problem solving situation. So what I would say and the joke I make with my teams is that some of these posts came in because I realized I was missing them. And then, and once I realized it said, oh, need that spoke, need that spoke. And what that really is is, is this. So there are, right now, I'm sure there could be more eight spokes and one hub on the wheel. And so I teach my teams each spoke and how we can actually turn it into something real. And then we test our work against each spoke and at least give it a shot, you know, give it a shot on each spoke. At least try to put it in place so that you can say, hey, I've got a chance to sustain all this good work. So if you'll allow me, I'll take you around the spokes.
Yeah. In fact, I've got the. You shared a diagram over email with me the Wheel of Sustainability. And we'll include this in the show. Notes for folks to download, you know, once they get done listening, as a takeaway.
Okay, great. Okay, well, we'll start at 12 o'. Clock. We'll start with the more traditional things. So the first spoke is notification. So we've made a change, we've solved a problem. We need to tell people, we need to show them. We need them to understand that this is the new way, the better way, the thing that's going to make things safer, more productive, whatever we're working on. So notification, it gives people a chance to say, hey, okay, tell me more about that. So then the next spoke is again, pretty traditional, but training and review. So tell, show and do whatever method you use to engage people so that they can understand, try it, ask good questions, help them feel comfortable with the new approach, and kind of reinforce what it is that we're trying to do. So pretty simple stuff. And we do that traditionally anyway, or we think we do. We can always do better. The third spoke at 3 o' clock is the visible evidence. So the point then is, can I see from a distance away that the new change is being done correctly? Can I understand where I need to come back and help if someone's not doing it the proper way? Because if we're not doing it well or right, it's typically more of a leadership process than a personal process. We have an issue in our process. So can I, within 10 seconds at 12ft away, understand, are we following the standard work? Are we making? Are we doing the steps in the new way, or are we doing something in our own way? So that's visible evidence. The next spoke is, have I supplied all the proper tools so that I can do this work well? So in a very simple 5s example, have I put the tools on the toolboard, well positioned, well located, diagrams well labeled, outlined, every simple way that we can help that person doing the job know that they have exactly what they need, where they need it, they don't have to chase it down in a virtual world. Have I given them the software? You know, is the computer set up properly? Is it ergonomic? Have we done all those things to make it as safe and simple as possible to do the work the way it's supposed to be done? The next spoke is clear benefit. So this is the. What's in it for me? Can you truly show to that person, can they derive the benefit from the new way of doing so? We know that human nature would say we don't love change, right? You're going to tell me to do something different? Yeah. Move my cheese. Yeah. Why would you do that to me? So the point is, for my kaizen teams. Hey, guys, you have been working on this in the kaizen room for three days. Let's test it on somebody that wasn't in the room with us. Let's see what they think. Let's see if they believe it helps them because frankly, if it doesn't, they're probably not going to do it. So that's a really strong test. Let's find out. Did this help this person feel like they can do the job in a safer, simpler and more productive manner, or is it just something different that they're going to fight against? 2 in the morning. We're not there to evaluate that. They're following the standard work. If it's not a benefit to them personally, probably not going to do it. So that's a test that sometimes my teams try to shy away from. So I'll bring them out to Gemba as we always do, and say, come on, let's go find a couple of crew members and see what they think. So make it as safe a process as possible because it's a great way to get buy in from the greater organization anyway. Let's get their feedback, let's get their input, let's make sure we're giving them something that's going to make their lives better. Okay, the next spokes spoke, number six is the Laird audit. So, okay, even with the best of intentions, we're not showing the leadership to our teams to say this is the better way, this is the safer way. So let's go out on Gemba, let's go audit. Let's audit at the operator, the supervisor and the leader level. And let's make sure that everybody understands we're here to support them, to do the right thing. We also want to reinforce how important the right thing is. And we want to learn from each other as we're auditing because maybe there's something even better out there. But we won't know if we just assume everybody's following that new procedure or the new standard work. The next one's accountability. This is more leadership accountability to me. This is not the operator mechanic accountability. This is to say I'm walking out to Gemba. Somebody has chosen for whatever reason not to follow the standard work or the. There's an abnormality that is happening that's forcing us off standard settings. I am accountable to go there and help. I'm there. I need to go there, show my leadership, show my support, and see if there's anything I can do to get us back to standard. What help do you need? So it's the leadership accountability versus the operator accountability. Interesting. Okay, got it. My final spoke on my wheel is recognition. And I always joke with my teams, this is not prizes for anybody. This is understanding, cause and effect. Because we did this, we were more productive, we were safer. It's the storytelling. I used to have a disorganized area, but we did some 5s. And now instead of taking an hour to find the equipment I need to do the job, it's immediate and it's made my life better. So it's those sharing of stories and the re emphasis of those stories so that everybody understands, hey, this stuff can help us. This stuff can work. So that's the recognition I'm talking about. So finally, in the center is the leadership commitment. So, you know, I have a rule when I go help teams if, if our leadership isn't committed to letting us make the change, we shouldn't do this. I'm not going to waste your time. I'm not going to waste their time. So they need to understand when they've told a team we're going to solve a problem and we want to keep it solved, then they have to have the commitment to support all of those spokes, all of those aspects, so that the team can win every single time. So I have those strong conversations with the leadership teams before we even run the Kaizen event. And then I have this discussion with the team to show them, hey, you wouldn't be in this room, you wouldn't be out on Gemba off your normal job doing this if leadership wasn't so committed to your success.
Yeah, no, I like it. So let me run around the wheel here as a review, make sure I got it. All right. So the first 12 o' clock spoke was notification, basically communicating that we've made an improvement. Training and review was the next one. Visible evidence is the next one. All tools are available, making sure everybody has what they need. Six o'.
Clock.
At the bottom of the wheel, we have clear benefits. Then we had layered audits. Then we had leadership accountability. It says accountability, but we really were focused on leadership here. And then recognition with leadership commitment being. Being right in the middle of all these spokes. So it's really interesting model Adam. So I guess my first question related to this is, you know, some of them I, you know, you could see are, you know, they're related in a way, you know, like, like notification and clear benefits. It's interesting. One's 12 o', clock, one's 6 o', clock, but, you know, and it's right down through the middle of leadership commitment. I don't know if that's on purpose. But, but, but it's, it's, you know, these things, you know, probably play well together, I would assume. Is that, is that right? I mean, is there an order or. I guess talk to me about that.
Well, okay, so that's a great, great question. So I'd like to think I'm as clever as you might make me out to be, but I'm probably not quite that clever. So I really started out as traditional being the first ones because I thought one way to ease people into this new way of thinking. It's not really new, it's just a different way to look at it. I would suspect is, okay, look, we know we got to talk to people. We made a change. You're going to do that anyway. Let's be very aware. We need to do it, but let's think about how we should do it then training and review. Of course we're going to do that. But let's think about what's the most value adding way to do it. So I kind of worked my way from traditional to maybe not as obvious. I'd like to think all these spokes are fairly obvious. But what I can tell you is I see people that I don't expect to take notes on anything, writing notes on these document because this is one of the few things that I actually hand out. I like to work from, you know, engaging people in the discussion during the Kaizen event. Maybe a little PowerPoint. They probably would say too many PowerPoints, as everybody does. Yeah, you know, flip chart demonstration. But this is one thing that I realized that, you know, the way people retain information, it's good to have something to take away. And if you write notes, it means you're trying to reinforce that concept. And so I do see people keeping it. Not everybody, of course. And then again I try to reinforce it. By now let's test our change against these eight and if we're missing some. All right, let's design how we're going to do it. So I have some examples of that, of course.
Okay, good, good, good. All right. Really good model. Interesting model. So I guess talk a little bit about how you train and teach and engage gauge teams around this model.
Okay, great. Well, thanks. So I get brought in to help teams solve multiple problems. I mean, I appreciate those opportunities. So one of the key principles for me is that our results, we need to win and these results need to live on. I'm very purposeful around. Anything we do is done for purpose. I have a story of a well shop that we organized using 5s, but to make our welders safer, more productive, and able to respond very well to the needs of the factory. When welders are needed, typically it means that the line is down, money is being lost, people need help quickly. And, you know, the welders, bunch of mechanics, they aren't your typical Kaizen team members. As a full team, they get a little skeptical. Let's just say they get skeptical at the beginning. So the point is, hey, guys, we're going to do all this great work. We got to make it live on. We have to do everything in our power because we're going to make everybody's lives better. We don't want to have it go back the other way. So, like I said, I had a bunch of skeptical folks. So what I did was we got to the point of, all right, how are we going to make sure? Their concern was everything's going to go back to the way it was. Tools are going to leave, locks are going to be taken off. Things that we need aren't going to be where we need them. How are we going to make sure? Well, the point was, okay, so where are we missing? Well, we had all the welders, so notifying and training was fine. They got it. They developed their new system that was fantastic. We did the visible evidence. We did the tool boards. We had footprinting. We had good signage, large visuals. Somebody like myself who's not a welder for sure, don't even play one on television. You know, I could walk in that shop immediately, see that everything was as it should be. You know, we. We got rid of 90% of the clutter. It was amazing, maybe more. But what was left was everything they needed in the proper condition, right where they needed. So tools were there, the benefits, you know, they were able to identify. But then we got to the audits, and if you're like me and you've dealt with mechanics, not to put them into a silo, but, okay, maybe in the traditional manufacturing, they're not really fans of the, let's call it paperwork idea. Okay, so I'm going to tell you a story of how we got them to the audit they needed. So, okay, guys, what are we going to do? How are you going to hold people accountable to do what needs to be done every day in this shop? You know, how's leadership going to make sure it's as it should be? Don't you want something that you can document? Well, Adam, we don't want paperwork. I get it. I hear you. I understand it but how are you going to show the accountability? We can do it on a board, but we got to do something that shows that people are doing the right thing. We want them to always do the right thing. I had to get onto the PowerPoints. They had no interest in any of it. This was like day three of an event. We had already sorted and done everything else that we wanted to do, and now it was, how are we going to sustain? So I'm showing them examples of how to do that. Well, you could just tell they were having none of it. Okay, guys, we got to do something. What do you want to do? None of it. Well, no, that doesn't really work. You want this to live on, Right? Right. Okay, great. So I realized I had to create a significant emotional event. Now, this is a little risky, as you might know, but they need to own their solution. So I got to a point where I'm actually showing them a checklist and I'm reading every single line on a checklist. By the sixth line, the leader of the team, let's call him Jimmy, who was definitely team efforts were not his thing. Fabulous welder. Tremendous. Jimmy gets up, beat, red face. Adam, we're going out to the smoke shack, and we're going to figure out what we want to do. And you can't come with us, but we're going to tell you what we want to do. And I said, okay. So they walked, they stormed off. There were six of them. They stormed off. And I said, okay, that's what I needed to do because this other stuff wasn't working. And they were gone for about 20 minutes. And it felt like about two and a half hours.
Yeah.
Yeah. I'm sitting in the room by myself, you know, going, okay, you did the right thing. I gee, I hope they come back. Twenty minutes later, they come back. They look like the cat that ate the canary. They're just really proud of themselves. And Jimmy says, adam, all right, get on the computer. You type the checklist. We got the checklist for you. You type it the way we tell you. I'm like, okay. So I'm like, you know, they have no idea what I'm doing. I'm in. I'm loving it, but I'm going, okay. At least they came back. So they give me 11 point checklist. I had given them 12. They gave me 11. Then it was in their words, fabulous. So I typed it in. I could. Those are great ideas. Okay, now that we have this, what do you want to have happen with your checklist? Okay, we need People that use the area, they have to use this checklist daily. And then what we want to do is have a weekly verification by leadership. They need to be responsible and accountable. Great, that's perfect. We want a picture of our team leader, our area owner. That was Jimmy, who was not smiling in the picture, but that's okay. And you know, my recommendation, it's great, let's make it visible. So we put it right outside the area. Okay. Their checklist. Well, how about that? And they were really into the accountability. We want leadership to be accountable. Fantastic. So great. So they put this thing up and at the report out, they start describing what they need from leadership and how critical it is for leadership to support this and how don't let us miss a day on our checklist. And you guys have to do this weekly. And leadership is just eating it up. Fabulous. And I don't know, some folks don't like to do report outs. They don't like to present in front of groups. I always let my group practice and mechanics typically don't like to do it. These guys were talking from the heart. It was unbelievable. One of them actually said, I've worked in this factory nine years, I've never done anything as impactful as what we did this week. He actually said that in front of a bunch of people. He probably got ribbed later for actually being talking from the heart. But the upshot from all this is about four months later, for some reason, I was brought back in to help another group of mechanics in a different area organize their area. So I took them out to Gemba and I took them to the weld shop. And it just turns out as we came in, because I just want to show them some examples of what. What it could be. Jimmy happened to be welding as we walked in. Can't make this stuff up. And so he stops and I'm just giving a little demonstration of the toolboard to let's say seven or eight people because this is the first time they've ever seen was very new in this factory. And Jimmy, right in the middle of my little spiel says, all right, I gotta stop you right here. He goes, I know this stuff sounds silly and I know this stuff sounds stupid, but this stuff works. By the way, he didn't use the word stuff, but we're just going to do that for your.
Okay.
So that was the moment that I knew and that was the reaction and impact that I want to create for the teams every single time. Because once they own it and they get this model to sustain It. Things just get better. Yeah. You know, because you are fighting the entropy. It's exactly what you said, Ron. I mean, it is that law of entropy. Things will. And I've. In the past, that's what was happening. And I was realizing that some of these spokes, I wasn't helping teams implement each of those spokes. Now there may be more, and maybe some of them are duplicates, I don't know. But all I know is, as Jimmy would say, this stuff works, so why mess with.
Yeah. So, you know, the story you told of Jimmy and the team, obviously there's a, you know, you got these tough, tough and rough mechanic guys, you know, who don't like to, you know, share their feelings or anything like that. But getting up and making comments like that gentleman did in nine years and never done anything like this, I mean, done correctly. Continuous improvement can be deeply, deeply personal and deeply emotional. That's been, in my experience and really as part of the. It's not one of the spokes, but it's kind of an underlying spoke, if you will, is like we make an emotional connection between, you know, the success of the, of the event is the success of people and, and, and. And all of us. It's like humanity. Right. That's why this respect for people is so hard to put our finger on. Like, what does that really mean? But it, it is, it's. It is. It's what you just did. Right. With those folks and, and helping them come up with their own solutions and owning it. And then, yeah, the, the, the. The person who's got their arms crossed at the beginning of the event, those are my favorite. Because if you do your job right, they'll be your biggest cheerleader like Jimmy was when he went back in there four months later.
Right, right. Well, I said, you know, I tell people all the time, how can you not love helping people in this way where you can create now, you don't always get that kind of connection, but when you do, wow. I mean, it just makes, it makes the days and weeks following that just. I mean, I still think of those moments and I still get goosebumps.
Yeah. Yeah. So I assume when you went back in four months later, Jimmy and the team were still following the checklist, maybe even improved it. Is that right?
Oh, Ron, one thing I do is I check to see, hey, I wonder if they filled out last week and the week before and they're still there. Yeah. And the space actually to this day is better than we left it because they learned and they exposed more things and they go, ooh, I want more of that over here. Or this would make the work even better. And if we footprint this over here, we'll never lose it. It'll always be where I need it. Yeah. So that is something that I look for and treasure, because then you go, you really made a difference for these people. And that's all you're doing, is you're just helping people.
Yeah. So maybe let's wrap it all up into a bow. Short of people bringing you in, which everybody call up Adam and make them too busy, and so he has to say no to people's business. But that would be great, you know, as far as, you know, teaching your model. But if there was, like just one or two, maybe three practical tips that you want to leave our listeners with as far as how they can maybe make their. Their gain sustain, what would they be? I mean, short of the eight spokes, Just summarize some. Some tactical, practical things they could do.
Well, I think the big thing for me is when you help people make something better, there's got to be purpose to it. If you can tie everything you're doing to that purpose, they're more likely to keep it alive. Okay. So people don't reject the eight spokes. Eight sounds like a lot, and I totally get it. But the reality is, if you can tie it in those welders, they weren't going to do a 5s to do a 5s. What they were going to do was be safer and more responsive to the needs of their facility, and they weren't going to be frustrated. So when I was teaching them about the spokes, it was all about tying that to ensuring that they would never be frustrated again. So I think that's the first tip. Be very purposeful around whatever help you're giving to create continuous improvement. So I shy away from calling something a 5s, kaizen or a smed or this or that. People love to say, I'd like to do a SMED over here. I get it. But what's the problem we're really trying to solve? Let's be very purposeful and intentional about that, and then we'll apply the right tools to help us get there. So I like to be. Let's be modifying to help the team win. And you have to be able to zig and zag, because sometimes they have different needs than you suspect in the beginning anyway. Yeah. So that. That would be my biggest tip here. I said don't. And don't forget how big a commitment it is from leadership to this day, over a year later, leadership. Somebody from the leadership team Gembas over to that weld shop and most of these guys never did anyway, and they're doing the audit and they're engaging with the people and they're helping. So never discount how important that hub of leadership commitment is. Don't commit to the Kaizen if you aren't committed to all that's going to happen the moment the kaizen's over.
Yeah. Fantastic. Oh, that's really fun. Excellent model, Adam. Thank you for sharing that. Again, we're going to put. We'll link up that PowerPoint slide showing the diagram in the show notes. So this will be episode 287. So all you got to do, folks, is go to GembaPodcast.com look for episode 287 with Adam Lawrence, and we'll have a link to that download there. Adam, thank you so much for coming on and taking time out of your day to visit with us. We already mentioned your website once, PI-partners.com Is there any other ways that folks can connect with you? LinkedIn? Does your son got you on Snapchat or anything like that?
Yeah, I'm not quite that advanced. Yes. So I do have a LinkedIn page.
Okay.
So just look me up at Adam Lawrence.
Okay.
It has all my contact details. I also do have a company LinkedIn page, but I would say, you know, just have a conversation with me. Love to talk to folks. There's always something to learn. Love to share stories as you can tell and just anybody at all that's interested. I always have time to talk to other interested people.
Beautiful. All right, thanks again, Adam. Keep up the great work and yeah, hopefully we can connect face to face someday.
Great. Thank you, Ron. Thanks for the opportunity.
All right, bye bye. Thanks for listening to the Gemba Academy podcast. Now we invite you to take a no strings attached, fully functional Test drive of Gembaacademy.com gain immediate access to more than a thousand Lean and Six Sigma learning resources, all free of charge at Gembaacademy.com.
