Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Elevate Construction

Elevate Construction artwork

Ep.1657 - Why Lean Fails Without the Right Team

Aug 6, 202619 minAudio

In this episode, Jason explains why the team component is essential to the Integrated Production Control System. Without the right leadership, team behaviors, and a shared performance goal, even the best Lean systems will struggle to work. What you'll learn in this episode: Why every successful project team needs a multiplier leader. How trust, healthy conflict, shared standards, and accountability create a cohesive team. Why a strenuous performance goal creates urgency and exposes problems within the team. How strong leadership and team alignment support every other part of Lean and production control. Does your project have the leadership, team behaviors, and shared goal needed to make Lean actually work? If you like the Elevate Construction podcast, please subscribe for free and you'll never miss an episode. And if you really like the Elevate Construction podcast, I'd appreciate you telling a friend (Maybe even two 馃槉). Also, here are links to our YouTube Channels: 路 Jason Schroeder YouTube Channel: https://www.youtube.com/channel/UC4xpRYvrW5Op5Ckxs4vDGDg 路 LeanTakt YouTube Channel: https://www.youtube.com/c/leanTakt 路 LeanSuper YouTube Channel: https://www.youtube.com/channel/UCzQDevqQP19L4LePuqma3Fg/featured 路 LeanSurvey YouTube Channel: https://www.youtube.com/channel/UC-Ztn3okFhyB_3p5nmMKnsw

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show. Tap a time to play from there.

Hey there, welcome everybody out to podcast number 1657. In this podcast, I'm gonna talk about what happens if you are missing the team component in the integrated production control system. If you're interested in that, please stay with us. Welcome everybody, I hope you're doing well and staying safe out there. I am super excited, a couple of, oh, oh gosh, I gotta do something here real quick. A couple of things that I need to make sure everybody knows is that somebody posted

a regional sales manager posting on Indeed. And this is causing lots of problems because people are reaching back and thinking it's me and there's an email where they want you to click on a link and it is clearly a scam. And in case you're like, Jason, why don't you stop it and report it? Well, they're creating false email addresses so there isn't anything really that I know how to do that will help prevent it. So we posted it on our website and

we are trying to do everything that we can to make sure that people are kept safe. But please, and here's another thing that I gotta say is that, and by the way, this is not a criticism. This is not a criticism. I think that a good practice, well, so this is another reason I hate email because you can get an email from anybody with a link, click on it and get scammed. It's a lot harder to do that on text and on WhatsApp. But a good practice is never ever click

on anything, anything, anything, anything, anything ever from an email. There's just no reason for it. If a company, and by the way, this isn't a lecture. I'm trying to help you out. I hate that scammers do this to good, innocent people. There's no reason ever really to click on a link from an email. In fact, there have been legitimate companies that have sent things to me and they're like, hey, here's the link. And I'm like, no, I ain't clicking on that. They're like, why won't you click on that? I'm like, I don't click on any link, any email anywhere.

Scamming is just too prevalent. The bottom line is, they're really, like somebody the other day, so I was talking to a general superintendent with a company that I used to work for. And he was like, your auto-reply message and your voice messages are wild. And he kind of criticized me a bit, which is super fine, super fine. But like, life has changed. Like, there are no, and when I say there are no, I mean, there are no,

there are no legitimate phone calls anymore. Like, everything is a scam. Everything is spam. Everything is a sales call. Everything is like, everything is corrupt. All of our information is out there being sold by these big tech companies. It's really, really quite a nasty thing. So, I just think we all got to be careful and I'm super sorry about that. By the way, that wasn't intended to be a lecture. The other thing is, I'm saying it because I want to help.

The other thing is, we just moved into, as I probably told you in a previous podcast, into our building here at Elevate and Lean Logistics. And this is where we are. We're already manufacturing these simulations for the industry to make Lean easy to implement. I'm really, really super excited about it. And so, we're here. I'm in my office getting through a couple

of things and I'm really excited about that. We're going to be, we're already producing simulations. We are already on our way to packaging pull planning kits. We're already on our way to the point where we can make the pre-construction, pre -planning kits. We're going to have everything super decked out and then every product that somebody wants to buy, it'll be available. We'll have shirts and caps and all kinds of stuff here available pretty soon.

I'm super, super stoked. Anyway, those are some of the updates. And the goal is really to turn this into a pretty big shop. Like we want to manufacture bathroom pods. We want to manufacture the little mobile mini offices that people utilize when they first start a project. But we want to do it cheaper to where it's not like, so a lot of these bathrooms that people provide and the mobile minis, they're super nice, but they're so expensive.

Like I just, why can't we get a really good structure where you can forklift it and it's sturdy and it's all sealed in, but that it doesn't cost so much money. You know, it doesn't, there's certain materials that are just unnecessary with some of these things. Anyway, so that's where we are. I just wanted to give you some updates and I want to get on top of the topic today. And the topic today for me is all about building the team. There's a couple of books that I want to mention right now out of the gate. And you've heard me talk about this before.

I really want to talk about what happens if you don't have this component. But the books are The Motive, The Five Dysfunctions of a Team, and then a book called Silos, Politics, and Turf Wars. The book Silos, Politics, and Turf Wars, that book is about how to make sure that you're forming the team around a strenuous performance goal and that everybody is performing in that direction and pulling together. If you don't have a strenuous performance goal, then basically you don't pull together.

Anyway, so those are the three books. The three main things that you have to have with a project delivery team is first, you have to have a multiplier leader, which can be found in the book Multipliers by, I think it's Liz Wiseman. And you have to have the five behaviors of a team. Again, that one is in The Five Dysfunctions of a Team and you have to have a strenuous performance goal. Now, I have told companies to F off, like after a while of them saying, Jason, will you go fix other people's failed projects?

I'm like, hey, I'm not about fixing a bunch of projects. I'm about preventing the problems from happening in the first place. But unfortunately, before I told them to politely F off, I got, I guess you could say I got the opportunity to recover a bunch of them. And there's a concept from how big things get done where they say that projects don't go, sorry, projects don't go wrong, they start wrong. I do agree with that. So I don't have anything with that. But if I had to, well, I have

something with it, but I don't have any problems with what they're saying. But I would modify it just a little bit. I would say projects don't typically, I would say projects don't typically go wrong, they start wrong. Because if they do go wrong, it's because of one of these key things in the team. Every project that I've ever had to recover before, like I said, I said I'm not doing that anymore because in my opinion, great superintendents don't recover projects. Projects, or great superintendents prevent them from ever

going wrong in the first place. They prevent them, right? So I'm not criticizing you if you've ever had to do that. I'm just saying that from a, I don't want to give anybody the impression that like I think it's cool to go around fixing projects. I don't think that we should reward people for that. I don't think we should pay people more for that. I think that we should pay people from preventing it from happening in the first place. Anyway, every time I've had to go recover a project, one of those three things is missing. We don't have a multiplier leader, we don't have the team behaving properly as a team, or we don't have a strenuous performance goal.

And I think I need to tell this story again, because it's so pertinent, it's so applicable. And if you've heard it before, I apologize, but there was a high rise in downtown Salt Lake City, and we had seemingly everything, all of the best of things. I mean, it was just really a cool project. And, you know, the actual general superintendent for self-perform, we had a handpicked project team, the best trailers, we had a budget for everything.

It was self-perform, it was super, super cool. So everything was going seemingly in the right direction. But right out of the gate, we lost, and I wasn't directly on the project, but Jocko Willink would say that if I'm a field director in the company, it's my fault, so I'll say we. We lost, right out of the gate, three months. And I was helping them to plan the project. It was so funny, the project director, a famous project director, had a couple of activities on a six-page CPM schedule, and I'm

like, oh my gosh, this is ridiculous. This is not how you plan a project. We've got to have more detail in an overall strategic plan. So even with all of the planning that we did, right out of the gate, we've got a problem, to the tune of about three months. So I come in, I'm still big on Patrick Lencioni, but back in the day, I was fanatical. I was like, you know, we can solve everything with Patrick Lencioni's frameworks. And I still believe that, so I'm not being negative about it, but I was super on it, on Patrick, or on their work,

and super excited about their work. Anyway, so I went to the team. I actually went with another field director, and we started to, we didn't actually diagnose anything. We were talking to the team about like, hey, here are some patterns that we've got to be aware of from the table group, from Patrick Lencioni. Anyway, so we start going through it, and one of the assistant superintendents says, and this is such a cool story. He was like, hey, we're falling asleep on this map placement day.

We can move this up by about six weeks. Sounds like a long time. You would be surprised at the details, the circumstances that made this possible. But he was like, we need to move this milestone up. We're falling asleep on this, and according to the Lencioni model, we will galvanize, that's the strangest performance goal. We'll galvanize as a team, and the team started talking, and there was like a buzz in our room. It was really quite cool. And the team was like, yeah, we can definitely do this. We can get this going, and yeah, we

can really get on top of this, and let's move the map placement up. Anyway, so they decided to do it, super cool, and they started jamming together. They leaned in as a team, and they really started working well together, and they pulled it in, and I say pulled it in. There was a tie on the top of the mat that wouldn't allow them to pull it in entirely, so it's not like a perfect fairy tale story, but they hit it within about six days, and then they recovered

the rest of the time shortly after. It was really, I don't know what a Cinderella story is, but every time I hear it was a Cinderella story, I'm like, yeah, well, if this was any kind of story, this was a Cinderella story. This is like a really cool story. Anyway, it worked, it worked, it worked, and they started to come together, but one of the things that everybody realized really quickly, and I mean everybody, is that the PM was, oh, so let me make sure I'm doing one piece flow. So there wasn't a strenuous performance goal, okay? All right, now everybody starts to lean in,

and things are going well, and everybody starts to realize that the PM and the project executive are not a part of the team, and if you're like, Jason, everybody, you're being, no, I mean like everybody noticed this. It was so apparent. The project executive and the PM were sitting, which I hate, by the way, you know me. Anytime I get a chance to criticize this behavior, I'm gonna criticize it. Like, I believe in feedback for improvement, but no, I'm gonna criticize this behavior, is sitting in their ivory castle office and not participating

with the team. They always had closed doors, like I mean like always. You're like, Jason, always you're being dramatic. No, I mean always. Like they were always sitting in a damn office somewhere, talking to each other, which for me has become a sign of bad leadership, because literally I saw a general superintendent once do that at Hensel Phelps, and then get, I think he got terminated actually, and he should have been terminated, because there's absolute incompetence. When the project's going well, he would just sit with the project superintendent in the office,

and they would opine about different things. Anyway, so locking leaders, when I wouldn't even call them leaders, locking themselves into offices when things go bad, and shutting doors to me is an immediate sign that something is wrong. Anyway, they started doing that, and it became so apparent that this was going to have to be fixed, okay? So one of the, so actually it was really hard to make some of these calls. It wasn't easy at all by any means,

but we made the decision to relocate the project executive, and we actually terminated the senior project manager. The senior project manager, he was so cocky. He was so arrogant. He would not listen. He was just one of those smug, like if I could say the word douchebag, like I would say it, but since I'm on the air, I can't say the word douchebag, because I don't want to, but he was just a complete limey piece of crap. Like I just, I never blame people, but I'm just going to hold an exception. Like he was just a real, real wiener.

Like anyway, so we terminated him immediately, got in a project executive in there that was hungry and high performing. Oh my gosh, he did such a good job. I take no credit. He just really galvanized that team, and he understood the mission. He was like, hey, we really need to gather everybody. The project executive was transferred to a project, not to go pawn him off on somebody else, but because he actually excelled with this other client, interestingly enough, and really, really had

a nice career after that, but he wasn't a fit for that project and the intensity that the owner needed, and that project team started to jam. Like, oh my gosh, they did so well. They pulled back the time. They finished with a raving fan client. Like it was just such an awesome thing, and I was like, whoa. Like, you know, you hear, you hear about Patrick Lencioni's, let's, shit, sorry, I didn't mean to disgust anybody. You hear about Patrick Lencioni's work, and you're like, wow, that makes super good sense, but then you see it right in front of

your eyes. It's crazy. So the bottom line is a multiplayer leader builds the team, has hard conversations, manages, coaches, and mentors direct reports, and, sorry, hosts remarkable meetings and scales clarity. Like that's what a multiplayer leader was, and we didn't have that. We didn't have that on that project, and so we got that. We made the hard decision, and the project team like really started to turn around. Okay, so if you don't have a multiplayer leader, nothing else will work.

All of your best players will be asking for and needing leadership or at a minimum support, and they won't get it, and your team will fall apart, and you'll have internal politics and conflict, okay? Now, the second one, behaviors of a team. You're not going to have the behaviors of a team if you don't have a multiplayer leader. That's just the bottom line. So if you don't have the multiplayer leader, you won't have the behaviors of the team, and the behaviors of the team are that you have to have trust, healthy conflict, set

goals and standards together, and then if you set goals and standards together, then you're able to hold each other accountable and perform, and you're not able to hold each other accountable and perform if you don't set those standards together, if you don't have healthy conflict, and if you don't trust each other. So, you will not have a team that's operating together and working together as a cohesive group. That's basic, that's the bottom line. And the thing that shows all of them is the strenuous performance goal. So, even though I'm explaining these in one order, the order that I really want to

talk about is the strenuous performance goal. There has to be a need. It's like a magnet. When I draw it on the wall, I'm like, hey, these are going to magnetize you in your performance to be able to accomplish the rest. You have to start with a strenuous performance goal. There has to be a need. Because what happened on that project in the story that I'm telling you is that we had great people, but they were getting complacent. The need was hiding, or sorry, the lack of need, the lack of urgency, the lack of a strenuous performance goal, was hiding waste.

So, that's the pattern. And I've seen that pattern work over and over and over. And if you don't have a strenuous performance goal, you won't see how the team is performing. And if the team's not performing, you won't be accomplishing anything. And that's probably the root cause of not having a multiplier leader. So, you've got to make sure that you're diagnosing that properly and having those as a part of the system. If you don't have this part of the system, if you don't have the team part of the system, nothing else in the integrated production control system will work.

Nothing else with Lean will work. Because if you don't have a team with the capacity, you're not going to be doing any of the things that I'm talking about. So, this is the pattern. This is what I want to talk about. And I hope you've enjoyed this podcast. On we go.

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Ep.1730 - Go to the Pain

    Nov 20, 20268 minAudio

    Avoiding the hardest problem rarely makes it disappear; it usually gives it more time to grow. In this episode, Jason explains why one of the best ways to improve projects, leadership, and even your own peace of mind is...

    Credit the people on this episode

  2. Ep.1729 - Sandbaggers and Superhumans

    Nov 20, 20268 minAudio

    When estimating durations, people tend to drift toward one of two dangerous extremes: padding the schedule because they have been burned before, or promising unrealistic performance because they believe they can push...

    Credit the people on this episode

  3. Ep.1728 - How to Lead From Below

    Nov 20, 20267 minAudio

    You do not need authority over the entire project to start leading. In this episode, Jason shares a story from his own career to explain why the most effective way to lead from below is not to wait for permission,...

    Credit the people on this episode

  4. Ep.1727 - Why Three-Week Pulls Don't Work

    Nov 18, 20267 minAudio

    A three-week pull may look like Lean planning, but Jason argues that it can leave teams focused on what is directly in front of them instead of preparing the entire phase properly. In this episode, he explains why...

    Credit the people on this episode

  5. Ep.1726 - Level 10 Meetings: Identify, Discuss, Solve

    Nov 18, 20268 minAudio

    A great meeting should do more than share updates it should expose what is off track and help the team solve it. In this episode, Jason breaks down the purpose and flow of the Level 10 Meeting from the Entrepreneurial...

    Credit the people on this episode