By Jennifer Dubose

Project Management Without the Chaos: Building Systems That Actually Deliver, #3

One thing we’ve learned in manufacturing is that projects rarely fail because of bad intentions. They fail because of poor communication, lack of planning, unclear ownership, or because everybody gets stuck fighting fires instead of managing the bigger picture.

In this episode of Manufacturing Blueprint, we break down what project management actually looks like inside a manufacturing business and why it’s one of the most important skills a shop can develop if it wants to grow without chaos.

We talk through everything from machine installs and ERP implementations to lean projects, quality initiatives, and process improvements, but more importantly, we focus on the systems behind successful execution. This isn’t about building complicated spreadsheets or creating layers of bureaucracy. It’s about creating clarity. What are we trying to accomplish? Who owns it? What could go wrong? And how do we keep small problems from turning into expensive delays?

Throughout the conversation, we share real examples from our own experiences, including projects that went sideways because key details were missed upfront. We discuss tools like APQP, risk mapping, RACI frameworks, Scrum-style task management, and project management software, but we also explain how simple systems and strong communication can often outperform overly complicated processes.

At the end of the day, great project management is really about turning ideas into measurable results. It’s about building repeatable systems that help your team execute consistently, reduce surprises, and keep your business moving forward instead of constantly reacting to problems.

Segments

  • (0:00) Why manufacturers need mitigation plans before problems happen
  • (1:24) Aligning projects with long-term business vision and strategic goals
  • (2:56) Defining scope, objectives, metrics, and measurable outcomes
  • (4:22) Building timelines, identifying resources, and establishing communication
  • (5:23) The difference between having a project and actually managing one
  • (7:02) Using APQP to improve product launches and avoid repeat mistakes
  • (9:33) Lessons learned from a CNC machine installation gone wrong
  • (11:05) Risk mapping, probability analysis, and mitigation planning
  • (13:25) Why we created Hire MFG Leaders (and why you should use it)
  • (13:56) Project management software vs. simple visual systems
  • (19:26) Using Scrum, T-cards, and daily sprints to manage projects incrementally
  • (21:11) Implementing a new ERP system while balancing shifting deadlines
  • (22:51) How ProShop ERP can help you achieve on-time delivery
  • (23:49) Understanding RACI: Responsible, Accountable, Consulted, and Informed
  • (28:30) Improving company-wide communication and reducing silos
  • (30:44) Why you need to listen to the Lights Out podcast
  • (31:19) Common project management failures including scope creep and poor accountability
  • (32:31) The role of leadership in keeping projects on track
  • (34:41) Real manufacturing examples where project management drives results
  • (37:40) Why documenting lessons learned creates long-term organizational value

Read the Full Episode Transcript

[0:00] But you’re mapping out all your risks and then you can rank them. What’s the probability of a problem with this, and you can prioritize them. That allows you then to put a mitigation plan in place.

[0:11] So if any one of these things does go wrong, if anything happens, here’s how we’re going to respond. If that machine ends up being two months late into production, well, what’s your mitigation plan to protect your customer? Are you just going to two months late delivering product or have you got a backup plan? And you need to put mitigating actions in. So that whenever these events arise, that you can respond quickly and that you’ve got a plan in place.

[0:35] Uh, just not being caught short. But I go, yeah, we would say don’t get caught with your pants down. Well, I didn’t want to say that, but yeah, it’s okay.

[0:47] We’re just amongst friends here. It’s fine. Welcome to the Manufacturing Blueprint.

[0:55] This is the show where manufacturing leaders, shop owners, and operators come to sharpen their thinking, strengthen their teams, and improve the way work gets done. From leadership and culture to systems, strategy, and execution, we break down the blueprint used to build high-performing manufacturing organizations, no fluff, just straight talk and real conversations, real lessons, and real results. Here’s your host, Jason David.

[1:24] Okay. So we’ve kind of covered the upper level portion of project management. So Paul, talk to me a little bit about maybe a little bit more on the basic side of project management, what it is for you in the manufacturing context.

[1:38] Uh, maybe even give some examples of common types of projects or… So we talked in some of our other episodes about, right, where we’re going as a business and direction and the vision where we’re going, so we have always kind of got this vision direction that we’re going on our, our project management, no matter what level that is, whether it’s just simple daily task boards or, or larger project management, it needs to move with the correct vision that you want to take your business. You need to understand first what your projects are going to be and what they’re trying to deliver to you. It needs to, to align with the strategic goals that you’re trying to deliver for your business.

[2:17] Um, and we’ll take that as part of our five-year goals, three-year goals. What do we need to deliver to take the business that notch forward? And then what we’re doing is breaking those big plans, those big projects down into smaller daily bite-sized chunks that we can manage on a daily basis, uh, through daily task boards to ensure that whenever we deliver those series of small tasks that they’re working together to deliver the big project management plan, which is substantially changing our business and taking us to a better place in one year, two years, three years down the line. Right, right, right.

[2:55] Yeah. Yeah. I think that kind of, for me, that breaks down into like four key elements.

[2:59] You’ve got your scope, which is understanding that vision. And I think that’s a really key part that we, we probably miss a lot of times that the vision aspect of it is so important and unfortunately not everybody has the ability to have that future vision, right? So there’s going to be some organizations and some individuals inside of your organization that can just see it. They can see what it’s supposed to be.

[3:24] And there are others that just can’t see past right here, just because that’s just the way they’re wired. And that’s critical. It’s critical, right? If you don’t have a division where you’re going, how’s your project ever going to be successful? If you never know what it’s going to look like in the end.

[3:37] And you need to be able to see that so that you can clearly define your scope, as you said, and then what’s the objectives, what is the point of this project, because you’re not just doing work, we’re not just spending money. We’re not just moving, reorganizing the shop floor just because we can, right? There has to be an end goal and you need to be able to quantify that, running your metrics. What are we expecting the outcomes to be? How does that impact its efficiency, profitability? You need to mark, benchmark where you are at the start so that whenever you deliver your project, you can measure it and you can say, well, here was our work.

[4:10] Here’s what it cost us, but actually here’s our results. So it’s really important to establish that project charter before you get going. Yeah.

[4:21] So you got your scope, uh, and then at that point you start building the timeline, right? So, uh, obviously it’s going to be a lot more challenging if you’re doing a project over one, three, five years. I mean, that’s going to be a little bit different, uh, scenario, but, uh, really this process can go for something that’s going to take you even a day. Um, maybe obviously you’re not going to have as many details, but if you’ve got something that might last a day, a week, or three months, you can still use these same, these same processes, but you got your scope, make sure you’ve got your vision, your scope, your timeline, and then identify the resources that are going to be needed, uh, to be involved.

[5:01] Uh, that can be individuals, that can be equipment, that can be, um, some of the finances, those types of things, and then making sure that we communicate. And, and I think it’s really important that we identify how we’re going to communicate to each other and how often we’re going to communicate to each other, because making sure the teams are informed are, are very important. I think we might can talk about that a little bit more in depth, but that kind of leads me, I think, to now the next step is, all right, so we’ve, we’ve got our scope, we kind of understand what our timeline is going to be, our resources.

[5:33] The next part is what tools or what systems can we use that will help organize all of this? Cause it’s, it’s called project management for a reason. So if you think about it, there’s two pieces to it. There’s the project part of it, and there’s the management part of it.

[5:49] And it’s really blending these two things together. We have an idea, we have a vision, we know where we want to go now. What does that roadmap look like? What are the tools that we can use to help identify that map? All right.

[6:02] So I’m going to show my age. Um, I don’t know if you’re quite old enough, but I remember back when I was a kid or when I was younger, like we would travel somewhere, you ever have like an app, uh, an atlas where you literally open up a map, right, and you would map out, this was before the internet, before smartphones, and you had to map out how you were going to get somewhere on a trip, right? Is that before your time? I thought you navigated with the stars. Well, I’m not quite that old.

[6:32] Okay. So, but I remember like, you know, like as, as you think about it, like you look at a map and you know, you want to go from point A to point B, that’s all we’re doing is we’re, you know, we’re drawing that route. We want to go to, go to this road and turn right, go for 12 miles, go to this road, turn left, um, and that’s what we used to do on the maps, uh, and you had to write it all down or else you’d get lost.

[6:55] But that’s exactly what we’re doing here. We’re just taking and creating a roadmap. So what are the tools or what are some of the things, systems that you guys use that help create this roadmap? With our, with our new products, we do an APQP.

[7:12] I don’t know if you’re familiar with that or not. There’s maybe not every business we’d run it, but APQP it’s advanced product quality planning. And if we’re specifically taking a new product into service, that’s what we’re doing.

[7:28] We’re trying to make sure that we go, as we go through the phases and whether that’s from the initial planning and design, from our concept initiation phases through the approvals, um, into product design and development, our third phase where you’re starting prototypes, it’s going into early stages of production, then you move into your pilot phase where you’re looking at product and process validation. So that whenever the product hits production, that you have all the problems worked out. So APQP is one of the things that we would use in a lot of big industries.

[8:05] We’d use that. That’s a fairly wide known concept. Sure.

[8:09] And we do that. And I guess the point of that is that as you do the cycles of new product introduction, you take a lot of learnings and you need to have a structured approach to say, well, the things that we learned from this, how do we record those and how do we build those in so that we don’t make mistakes in the future? And it’s about catching those at the right time in the project. So if you’re designing a new product, for example, a lot of those mistakes you may not see until you actually reach production.

[8:41] But if you had identified them far earlier in the design phase, then you could have avoided them. So it’s not easy sometimes to identify those mistakes early. That’s why it’s so important that you do reflections.

[8:53] And as you do your delivery and actually assemble on this, it’s a bit going back to your process, your program management phase and saying, how do we capture this as a check or here’s what we did wrong the last time? So whenever we come back to our design stage, we say, well, this went wrong before, or we’ve already used this mechanism or we’ve already used this process on this machine and here’s the problem that we found and how are we going to avoid it next time? The point of that is to make our process the next time more efficient. So we get less setbacks with less costs, less cost due to scrap and makes that become easier to manage. Yeah.

[9:28] That’s a little bit of an APQP if you’re not familiar with that. And I think, you know, yeah, no, I, I, and I’ve got an example from, from, from my history where this was really before we were doing much in the way of any project management and it, and it came with the delivery of a, we purchased a new piece of CNC equipment. And we didn’t have a plan in place.

[9:48] We didn’t have, we didn’t have anything kind of prepared. We just knew we needed to get it. And we knew we had to have somebody to take it off the, we needed riggers to take it off the truck.

[10:00] So we kind of had the, the, the plan of the machines coming and the riggers are going to be here. And then it’s, we started doing a little digging and we found out, oh wait, we’ve got to have a pad because this machine is so big, it needs its own individual pad. So a week before delivery, we’re scrambling around trying to get the, the concrete cut out, get a pad poured, but there’s cure time that comes with that.

[10:23] And then we found out, oh wait, well, this machine isn’t a 220, it’s on 440. And so, uh, the, the wiring that we had the electrician do is now incorrect, or we need to purchase a transformer and that’s going to take three weeks to get in. And then we also had an issue with that is we had tooling that wasn’t, uh, exactly like we were expecting it to be.

[10:49] Some of the, some of the tooling with the machine. So all total, we ended up losing about three months worth of time when, you know, at the end of the day, we’re having to make payments and we haven’t even made a, we’re not even machining parts yet. So that was very difficult.

[11:04] But, but what that did is it, it really helped us identify, okay, we’ve got to stop, we’ve got to create a checklist and a template. So that way, the next time that we purchase a piece of equipment, we know, all right, does it need a pad? What is specifically, very specific? What is the electrical requirements? What are the tooling requirements? What are the rigging requirements? And we can go through this checklist and we can have all of these things taken care of upfront. So, like you said, it is kind of building, like taking, taking an assessment of what happened wrong, what happened right? And making sure that we make those adjustments.

[11:43] So the next time around, we don’t, we don’t repeat those same errors. That’s right. And if you’ve got, if you’ve got the scope of your work, if you know what you’re trying to deliver in your project, it allows you to do a risk mapping.

[11:57] I don’t know if you do that as a business, but if you do risk mapping, what is your, you’re going through and as your team, when you get together with your project team, you’re looking for what’s the potential risks. Right. You’re saying I’m introducing a machine.

[12:11] What’s the potential risk? What could go wrong in this? It could be late, it could be the way of the machine. It’s how we move it. I don’t know, but you’re mapping out all your risks and then you can rank them.

[12:21] What’s the probability? What’s the probability we could have a problem with this? Then you can prioritize them. That allows you then to put a mitigation plan in place. So if any one of these things does go wrong, if anything happens, here’s how we’re going to respond.

[12:35] If that machine ends up being two months late into production, well, what’s your mitigation plan to protect your customer? Are you just going to two months late delivering product or have you got a backup plan? And you need to put mitigating actions in so that whenever these events arise, that you can respond quickly and that you’ve got a plan in place. Uh, just not being caught short. I like that term.

[12:59] Yeah. Uh, we would say don’t get caught with your pants down. Well, I didn’t want to say that, but yeah.

[13:05] It’s okay. We’re just amongst friends here. It’s fine.

[13:09] But that’s what it’s about, right? It’s a, how can you make your project predictable and reliable? How can you reduce the risk to protect your business and to protect your customers, which protects your reputation and your revenue? Hey, it’s Paul from Making Chips. If you’ve been burned by recruiters who don’t understand manufacturing, you are not alone. That’s exactly why we created Hire MFG Leaders.

[13:37] We’re not just recruiters. We’re current and former shop owners, and we know what it takes to lead in this industry. Whether you’re hiring your next operations leader, sales manager, or production supervisor, we’ll help you find someone who actually fits.

[13:50] Learn more at makingchips.com slash hire. Well, and I think what that does is that helps us get into some of the systems that are probably helpful, right? So I’m not, I’m not sure about you guys, but I know from our standpoint, you know, we used to work on, um, you know, just work out of Excel and maybe create a Gantt chart, um, or some type of timeline of those, those types of things, but now with project management softwares, I mean, that’s really makes, makes life so much easier. Uh, we use a project management software.

[14:25] And with that, we’ve got the ability to create projects, create individual tasks, assign tasks, um, give deadlines, uh, create milestones. We can, you know, set schedules, those types of things. So, um, I think as those projects get larger, having some type of system, it can be done out of Excel or, or, or Word or just by hand, but having a software that helps manage all that together, helps the individuals collaborate with each other, you know, share files, those types of things and make notes, uh, that helps that collaboration, having a project management software is, is, is very helpful from that sort of thing.

[15:05] So, but I think visual management, um, you know, if you’re, if you’re doing certain things, having some type of visual management on your floor is important, that’s kind of helping again, that collaboration of things. Um, but ultimately I think it’s important that we, we keep things very simple because at the end of the day, we want to make sure that we’re maintaining this project because we make things too complicated, that project management part of it will just fall away. And then you’re back to the old days, or, you know, no, you’re not managing it.

[15:39] You’re not, you’re not monitoring it. Um, so I think it’s, it’s keeping it simple is very, very important. You have to be agile enough and be able to react and respond as quickly as you need to.

[15:50] And yeah, it could be a lot of medium, smaller businesses that don’t have project management software. And I wouldn’t let that has to not put them off. Right.

[15:59] Because just keeping a track KTM, simple KTM Gantt charts that you can draw up in Excel work fine, especially if you’ve got, you know, a small team, four, five, 16 members that can all work out of it together, print it out, get it stuck up on the wall, draw all over, write everything on it. The important thing is it’s having the right stakeholders, the right people involved to put together a robust plan. The worst thing that you can do is trying to work on your own.

[16:29] And sometimes I seen that with project management software that it’s on one person’s computer and sometimes it can get really complicated and there’s licenses involved, so there’s costs. Yeah. Right.

[16:43] And then it becomes one person’s project because a lot of people don’t know how to work the project software. And yeah, that can become hard. Sometimes with projects, it’s really good just to get the guys on the shop floor involved in those projects.

[16:58] So sometimes if it’s not even on a computer, it’s actually far better for them to get involved in where they can just come up and they can write on the plan, they can say where they’re on track, off track and yeah, make it become part of everyday life. Yeah. Well, and I think, I think there’s a, there’s a piece of it too, where I feel like, so we use a project management software and I use it for so many things just daily that just help me keep checklists, help me keep on task because I get, you know, you end up getting pulled in different directions and you forget things.

[17:31] Um, but one of the things that we use it for is like our 5S projects or our Kaizen projects, and we might only have two or three people that can view those while there’s six or seven people that are involved in that project itself, but we’re just kind of using it behind the scenes a little bit for keeping us on track, but that’s what’s driving us to go out and communicate with the team. That’s what’s driving to go out and post and have those conversations. Um, so it doesn’t, you know, we don’t have to have everybody involved in the actual software part of it.

[18:05] Um, but we can use that, uh, there. Um, another thing we use it for is like, um, we, we use it for candidate tracking. So as we have candidates that are coming in, you know, we can track like all of our communication with them.

[18:17] Uh, the way we’ve got it organized is like basically in boards that just kind of go across the screen. And it’s, um, you know, did we, once we’ve made our first contact, we have the resume there and then we make notes based off of our interview, what, what we want to do, what do we want, you know, do we have an interest in hiring them or if we make an offer, those types of things. And what’s, what’s, what I’ve really found is really cool about it too, is.

[18:41] If we do, if we’re very diligent in making notes, we might have somebody that it doesn’t work out at the moment, but for whatever reason, but if we make diligent notes and we know, okay, well, we like this person and we would hire them if we had the opportunity, maybe we, we flag it so we can contact them again in six months and we’ve actually had, uh, scenarios where we’ve been able to contact somebody that was maybe from a year previous and because we had notes, we know exactly what the situation was, we knew all the details and we were able to go back and, and, and work that out. So keeping really good notes inside of those, uh, that software system is important as well. it’s good.

[19:21] It seems like it’s, it’s practical and part of everyday life for you. It really is. It really is.

[19:26] Yeah. We take a lot of our projects and again, we use project management software as well, but we would take a lot of those smaller lines, right? So you, you map your big project and you broke them down into the incremental steps and that for us, we take that out of the shop floor and that to our daily task board. And we love, I love, maybe not.

[19:47] We love, I love T cards. I love T cards, right? T cards. Yeah.

[19:52] Tell us a little bit more about your T cards. What we do is we would use a strategy, um, like scrum, right? We call it scrum. The point of that is everyone come together, like at the task board and everybody talks about what’s their actions they’ve got to do in the day.

[20:08] And all these tasks should be working towards a significant step on your, on your KTM, on your project management. How do you progress it? And we then do sprints. So the sprint is the action.

[20:21] So today my action is this, and this is what I’m going to do. And I’m going to close that one today. Then the next day, what’s your next action on your next card? It’s this.

[20:30] And that’s your next sprint. And, and if you’ve got five or six people in your team, and even if they’re only doing these little small things, it’s about making sure that we deliver a chunk. Because sometimes we look at our project management and some of the elements of work really, really, really big.

[20:46] And you say, well, that’s going to take us two to three weeks to deliver. But that’s actually really hard to manage because if you’re three or four days in, how do we know that we’re on track, right? It’s about breaking those down into smaller little elements of work. And every day then putting that onto the task board, delegating that out to the team and say, how do we deliver these small chunks of work to make sure that we’re incrementally working towards the next milestone on our project? You know, one of the things I just had this conversation this past week, we’re, we’re in the middle of implementing a new ERP system.

[21:18] Um, I will, I’ll give a little shout out to a pro shop. So we are, uh, putting that as our, uh, new ERP system in our business. And that’s obviously been a challenge just from the standpoint, not, not because of pro shop, but anytime you change your ERP system, I mean, there’s a lot of work to it, right? And a week and a half is our, our live date.

[21:38] And we were just having the conversation yesterday and you know, it’s a little bit of concern about, look, we might not meet this date. And I kind of take the stance of like, I’m okay with that. I’m okay.

[21:49] Um, if we have to adjust our schedule sometimes, um, because it’s not impacting our customer, but if we have to impact our schedule, that’s okay is as long as we are making our steady progress. And that’s why we’re tracking it. So we can make sure that we’re, um, you know, that we’re staying on task.

[22:08] And if we’re going to miss something, then we can make adjustments and we can make a decision. Okay. From a business standpoint, do we need to drop everything we’re doing and put six people on it and get it back on schedule? Or are we okay for it to be a, to, to drift three days out, right? Because it’s, it’s important, but it’s not so critical that we need to just like stop everything and, you know, run around and change things.

[22:32] Well, in this situation, it really in the, in the grand scheme of things, if I’m three days late on that, because of certain things that happened that we weren’t expecting, I’m okay with that. And we can make those adjustments and then shift our schedules as we need to. Hey everybody.

[22:52] What do you think of when I say OTD? Well, in making chips, we’ve got lots of acronyms to deal with, but OTD is on-time delivery. On-time delivery is part of Hill’s mission. Deliver quality parts on time, every time.

[23:05] When I was shopping for an ERP system, I was looking for something that would ensure that we do that on a regular basis. Delivering jobs on time was something we struggled with. And I know that most shops struggle with.

[23:17] I think I saw recently that 70% of shops struggle with delivering parts on time. So the best decision I made in that, enter ProShop. Did you know that many of ProShop’s customers quickly experienced 95% or better on-time delivery rates with their customers? And now ProShop has a guide to help all shops, whether you’re using ProShop or not.

[23:37] Visit ProShopERP.com slash 95. Again, that’s ProShopERP slash 95 to get your copy today. So we’ve talked about some of the basics.

[23:50] We’ve talked about the tools and systems that we’re going to use. What about some of the roles and responsibilities? We want to think about like, who’s the owner of the project? What’s a project manager versus a team leader, maybe a sponsor. So I know you guys use… We would normally use a RACI, if that’s how you want to pronounce it.

[24:11] People may say that differently, but we talk about RACI. So who’s responsible, who’s accountable, consulted and informed. And that’s to make sure that you’re getting a right team, a diverse team from the right departments, the relevant stakeholders, and everyone’s involved at the right level.

[24:29] So I guess, first of all, talking about responsible, who’s responsible for the, who’s responsible for the project, right? And generally that’s going to be business owner, who’s the boss, right? So who’s the major stakeholder that this project’s going to implement? Who’s it going to impact? Do they know what’s involved? What the risks are, what the costs are, what the actions, the timeline. Then you’re talking about your accountable. So who’s accountable for delivering it? That’s normally a program manager or some kind of business unit manager, operations manager, engineering manager, whatever level that is, but who’s accountable, who’s going to be, who’s this to start with to make sure that this delivers on time.

[25:09] And these can be multiple people. It doesn’t necessarily just have to be one, right? This can be cross-functional. Thinking about consulted then.

[25:16] So who needs to be consulted? Do we need to, and this project, do we need to bring in the quality department, things that they need to be consulted on various steps to make sure that we’re compliant with our certification or engineering need to be consulted, is there any more finance needs to be consulted because of costs. And it’s about making sure that those people are brought in at the right time. And then who needs to be informed.

[25:40] And again, maybe that’s finance because there’s costs associated. Maybe that’s engineering quality. Maybe that’s the shop floor technicians, right? Who’s the guy’s going to be using this machine.

[25:50] Who’s the people expected to use this new process on us. It’s about being able to run these projects and not let it just be a shock to anyone at any one milestone so that everyone is informed from the start and every, all the stakeholders are identified early so that when the project reaches the end, that person who’s expected to do this task or to take ownership or responsibility of the outcome knows the process has been part of the development has seen the risks, knows costs associated with it, knows what it’s supposed to be delivering and that they’re ready to execute and carry it forward so that we sustain the project. So it’s making sure that you get the right team involved at all the levels.

[26:32] And we would apply that RASI for every stage in the project management cycle. So if you draw your Gantt chart and you have each element, each line going down, each line in your KTM or maybe select your major milestones in each major milestone, reconsider that who’s responsible, who’s accountable, who needs to be consulted in this, who needs to be informed of the changes, the outcomes. And then every time you pass those milestones, you’re making sure have we consulted, have we informed, are we on track and it’s making sure it really helps with the communication and making sure then that there’s no surprises.

[27:09] And also that we don’t drop the ball because there’s something we haven’t considered like, Oh, there’s a new machine, but you know what? We didn’t talk with quality. We forgot to plan the calibration and now we’re going to be delayed for X number of weeks. Oh, we forgot to check with finance.

[27:24] Now we have a bill for this amount of money and we hadn’t budgeted for it. Yeah, no, it’s about bringing all those people right in. And if you do that up front, right at the start of the project, by the time you reach the end, there should be less surprises, less shocks, better execution.

[27:39] Well, and I think a lot of, and a lot of smaller organizations, like you mentioned, those, those people who are responsible, accounted, consulted, informed, they might even be the same, they might be all the same person, you know, uh, And normally, normally we make like a little matrix for it, right? Responsible, accountability, consulted, informed, and here’s the team members. And then every time you come to a new phase in your project, you might just like X, well, this person’s accountable, consulted and informed and, and this person that should be informed and actually, no, we don’t need this person for this one, so forget about that. And so on.

[28:16] So it’s just, you can make a quick way, but it’s just a conscious decision to say, have we got the right people informed and engaged at the right level? And it’s just good to stop at every milestone and make sure that you’ve covered it. Yeah. And I think, I think that’s, that’s important too, from the standpoint of, um, a lot of times I feel like in our business, our communication to, um, across the business has been lacking at times, like to the floor, to all employees, and so I think them getting a good understanding of the direction the company’s going, understanding some of those projects that are going on, you know, we might, we might want to inform the entire organization at certain points, because this is kind of a big thing, maybe it’s a project and it’s a big thing for the organization.

[29:04] And somebody that’s involved in shipping doesn’t have anything to do with what’s the project itself, but it’s good for them to hear, Hey, this is something that the company’s doing. This is a direction that we’re moving. This is something that’s going to improve our overall business, maybe our capabilities, those types of things.

[29:23] So then keeping them informed in that, um, while yeah, so somebody that’s in shipping and packaging, they’re not involved with a machine install, but Hey, it helps keep that communication and will help that, um, run that business a little more efficiently, keep people with some, some buy-in. Yeah, absolutely. And, and the, and it’s hard when you’re running a business because the people that work in those individual areas, whether it’s inbound freight or whether it’s in shipping or anywhere in between, they all come with a little bit of expertise, and if you sit down to write out a big project on your own, you won’t know everything you need to consider, whether it’s transit lead times or free at terms, or you may not, there’s so much, so engage in the right people.

[30:08] It’s just critical. It also stops people just working on silos because everybody’s there in a business and everybody’s trying to make little improvements and everybody’s trying to improve their own processes. And sometimes there’s overlaps, right? And then there’s two people and they’re trying to do the same thing, but they’re not really going the same direction.

[30:24] It’s just trying to keep everybody on the same page and be a good, create a good process for communication and then setting up the regular cadence for that as well, how often do all those stakeholders get together to review that plan? Are they on track? Are they not? Running a shop today is nothing like it used to be. Automation, robotics, and lights out machining are changing the game. On Lights Out, we break down how manufacturers are scaling their shops with automation and technology to boost profits and efficiency.

[30:59] If you want to work smarter, not harder and take your shop to the next level, you need to be listening to Lights Out. Subscribe now, wherever you get your podcasts. We’ve touched on the basics.

[31:12] We’ve talked about different tools that are involved. We’ve covered roles. We’ve also want to, we also want to cover some of the common challenges.

[31:21] Uh, while we’ve kind of talked through them as we’ve gone through the whole process, um, you mentioned earlier scope creep, right? That’s something that’s really important and, and making sure that we know how we can keep our projects contained, right. And making sure that we’re, we’re not getting distracted. We’re not getting pulled away from different, different things.

[31:41] We make sure that we keep those, those on, on track. Um, we’ve got poor communication, right? We’ve covered that and how important it is to make sure that we set up our regular check-ins and that way we’ve, we’ve got that ability to communicate to each other, make adjustments, make changes as needed. Accountability, right? Again, all of these things tie to each other.

[32:01] Like that’s your, your responsible, accountable, consulted, informed, while that’s important. We’ve got to make sure that somebody’s accountable and that, that there’s also somebody checking in on that, right? Why, knowing why deadlines slipped and knowing if, how we need to enforce them. Right.

[32:17] We kind of covered that. You’ve got to deal with a firefighting culture. You’re right.

[32:22] You’re right. I think critical thing is the strong leadership, right? And you need to manage those things you talked about, scope creep. And it’s really careful.

[32:31] Whenever you have that project defined at the start, it’s up to the leadership. It’s up to those people that are responsible for delivering this to display strong leadership. You can’t delegate leadership.

[32:42] You can’t just, you can’t just delegate that to the team. It needs to be there, but you need to be able to hold teams accountable as well. If you have a big project and if you think of all your dependencies, right? You’ve got lead times and you might need to bring people in at certain phases.

[33:00] Like you mentioned earlier about putting in a pad and you need to cure time and maybe you need to organize guys to come calibrate machinery and equipment. And lots of times there’s lead times that all overlap. So whenever you put this whole plan together and you strategize and you plan that all out, it’s critically important that you hit those deadlines.

[33:19] So yeah, you also need to be a leader as much as you want to be flexible, right? And be able to prioritize your plan, move things around and be agile, which you will have to be, there’s still also a time where you need to be strong leadership and you need to be able to say, we have to hit this deadline and we need to be able to figure out how, if we fall behind, how do we recover that? Be able to provide that guidance to your cross-functional team. You need to be able to influence them with a certain amount of authority, but at the same time, you still need to inspire them to achieve the goals and the commitments that they set out to do. It’s about fostering that positive culture.

[34:00] I’m trying to create that collaborative problem solving work environment so that it’s good for morale because sometimes whenever we see these big projects, they’re hard, right? The reasons why we haven’t done some of these projects before is because they’re hard to do. And whenever you go down to do change, there’s challenges with it. None of it’s easy.

[34:22] So you need to be able to find some way to help with that morale whenever the project gets hard and you get setbacks, you need to be able to pick up the team and provide leadership and get them through that. Yeah. So it is a test of leadership as well, especially with big projects.

[34:36] Projects with high risk. Yeah, yeah. That’s very difficult.

[34:40] Yeah. It’s a big challenge. And I really kind of maybe want to talk about what are, what are some of the areas like thinking about the manufacturing world? What are some of the areas where project management really comes into play? And I think, you know, obviously we’ve touched on like a new machine install.

[34:54] That’s fine. You’ve got process optimizations. Like if you’ve, if you’ve got processes on your floor, you know, one of our previous episodes, we talked about the logistical side of our parks, right? That really, for us, it was a project and we, we walked through it and we, we used our project management team to, to go through that, you know, to help you reduce your cycle times or your tool life or, you know, whatever it is on that key part.

[35:18] But you’ve got, maybe you’re looking at OEE improvement, or if you’ve got like some type of lean project that’s going on, your 5S, Kaizans, or maybe a work cell realignment. Those are all projects. And you got, even if you look at like maybe the quality side, if you, if you’re looking at ISO certification, or if you’re looking at AS certification, those are going to things that are going to help you prepare for that audit.

[35:42] Even maybe a non-conformance reduction project, or how do you handle your first article inspection? Maybe you need to look at a program for that, working through your supplier quality improvement. Maybe you’ve got, maybe you need to create a new process for PPAPs or, or your FAIR. So there’s a lot of things from a quality aspect.

[36:03] Engineering, I know we use it for new products. So anytime we’re going to have a new product that’s coming through, it goes through risk mitigation, those types of things. We use it for our quoting as well.

[36:14] Maybe you deal with prototypes and you’ve got to kind of walk something through that prototype aspect or your process validation. I know, I’ve got a friend who they really use it for their tool development. So they, they’re really heavy on the tool side and that’s, that’s what they do.

[36:29] So other projects, maybe you’ve got like scrap reduction, setup time reduction, maybe downtime tracking. So these are all ideas that just kind of in that manufacturing world that you can, you know, use these for. And don’t, I don’t want to forget like employee aspects of it too.

[36:45] So you’ve got, whether you’ve got employee training programs or cross training, you’ve got improvement projects and maybe a safety improvement or onboarding, performance reviews, and also leadership development. So these are all really projects that I think that you could take the, these things that we’ve talked about, take these roles, take these tools and be able to put these into your business and help make your business function better. So it’s not just this one project that we want to do this one thing with our business, but we want to utilize this across our entire business.

[37:22] So you might have six, eight or 10 projects running all at the same time. And that’s why it’s so important to make sure you’re, you’re managing those projects. You can be, you can be running five or six projects at a time, but utilizing the tools, utilizing a software to help keep them all organized.

[37:40] It’s good to leave behind a footprint. And sometimes whenever there’s projects going on, the tendency is just go and do it. And whereas sometimes that’s really tempting.

[37:50] The benefits of actually leaving behind a footprint or leaving behind a process that actually records what you’ve done and how you’ve done, it’s far more valuable because you may not be in that position the next time your team that delivered that project may not be there the next time. And even if it goes well, how do you know that the next guy that you bring in and you task for running a similar project, how does he know what to do? How do you capture all those lessons learned? Lessons learned. And then whenever you need to reapply it, then you can bring it out and say, here, look, here’s the last time we introduced a new part.

[38:25] Here’s the last time we moved the machine. And even creating all those work instructions, right? We talked before about work instructions. How do we create them? When do we create them? And even through these projects, it’s about leaving behind that footprint so that the next time we can go back and say, here’s what we did.

[38:43] What can we learn from this one? How can we do it better? And how can we avoid the mistakes we made the last time? That’s it. Yeah. Starting with a clear plan, break the big projects down into small trackable milestones, celebrate your small wins, document the lessons learned and, you know, just make sure that you’re managing those tasks as you go.

[39:02] So, all right, Paul, I think maybe that’s a point where we start to wrap things up. You know, just make sure that we know that that project management is about clarity, accountability, communication. Those are some of the things we talked about earlier because projects fail in silence, right? That’s one thing that helps us stay more successful is to not stay silent.

[39:22] So, make sure that we are managing that and those expectations with our, um, with the employees. So, project management for me is how manufacturers can turn ideas and investments into real measurable results without letting chaos, delays, and waste take over. That’s it for this shift on the manufacturing blueprint.

[39:43] You’ve got the blueprint. Now go build it. And don’t forget, subscribe, share, and join us on the next episode.

This transcript was auto-generated and may contain errors.

Resources mentioned on this episode

Connect With Manufacturing Blueprint

Subscribe

For the latest episode straight to your inbox, business-building tips and other exclusive content, Subscribe to #MetalworkingNation today.