What happens when being "nice" means never setting standards, never addressing poor performance, and never holding teams accountable? In this episode, Jason explores the uncomfortable consequences of avoiding accountability and questions whether protecting people from difficult conversations can ultimately hurt them more. He discusses operating systems, training, field walks, psychological safety, and the responsibility leaders have to create an environment where people can succeed while still maintaining high standards. What you'll learn in this episode: Why an operating system, training, and field walks work together to drive consistent performance. How avoiding accountability can create drift, complacency, and poor project performance. Why leaders must consider the impact of weak standards on workers and trade partners. How high standards and psychological safety can coexist within a healthy company culture. Why consistently performing may be kinder than avoiding difficult conversations and eventually laying people off. Which is truly kinder: avoiding accountability, or holding high standards while helping people succeed? 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 everybody, welcome out to podcast number 1698. In this podcast I'm going to talk about behaviors and consequences when it comes to how you operate within a company. And 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 out in Budapest, Hungary doing an assessment with a really, really cool company and I'm excited to be back this week on
Friday. I'm learning so much over here in Europe and I'm excited to take this stuff back. And what are some other things that are new updated items? Yeah, the project going with Buckeye is proceeding along really nicely. I'm going to start making videos on our progress there. One of the coolest things that I'm interested in and excited about is the 3D logistics model that we're going to be building out of foam and other supplies.
We've already got folks mobilized to the office and I can't wait to start that project up. We're already doing some vetting for some positions and getting everything going, so I'm super excited. Anyway, let's talk about the podcast for today. This is an interesting observation and it was, I'm not entirely sure that I'm 100% accurate about this, but it is a question. Here, I'll frame it as a question. Well, the question will come later, but the observation for me is that there are companies
that will say that they're not into, and it is their business and that's fine, that they're not into holding people accountable. They're not into protecting their culture and they are not going to be, what's the word? I don't want to use forceful, I don't want to use strict. They're not going to be consistent with asking project teams, project delivery teams on their projects
to perform in a certain way. When anytime they get anywhere near the point of having even a little bit of conflict, they shy away from it. They say, no, that's not our culture. We want to be soft and nice and fluffy all the time to the point that there's drift. We have constantly seen in the format of operating system training field walks that if you're missing any one of those three, that you really have a lack of performance. What I mean by that is you have
to have an operating system that your company uses, then you have to, or get to rather, it's probably a better word, get to scale training and then do monthly field walks for the purpose of working shoulder to shoulder, helping people out, providing support, and then also saying, hey, this is what we expect and we are going to expect to see progress. We call them on yellow brick road documents. It's follow the yellow brick road. It's like, here are the instructions from one
field walk to another field walk. You have to do that if you want progress. I know there's companies that are like, I'm fine to adopt the system. Elevate will even adopt yours. We'll buy all the books. I'm fine to do boot camps. Last year, three companies had us go out to their location for super PM boot camps at a considerable expense, I might say, and train their people, which was remarkable and very effective. Then sometimes they will say, yes, let's go
ahead and do the field walks and within months take it all the way. They scale it and they have the results. Then some companies are like, no, no, no, no, no. The job site teams wouldn't like us checking in. We don't like that much transparency. I know they're not following the system, but you have to let the superintendent run it his own way. I don't want to have that difficult conversation. I'm kind of like, hey, that's fine.
That's fine. That's your company culture. I don't think it's fine if it affects ... Okay, so here's two things. Here are the two things where I have a problem with that. It's fine for you to say you're going to be nice. It's fine for you to say you're not going to hold people accountable. Then on the other end, here's what I'm seeing. It's a problem if it affects workers and foremen in the field, meaning it disrespects a trade partner or somebody gets hurt or somebody's disrespected or workers have to live in chaotic, stupid conditions and environments.
The other thing that I've seen recently with the economy is that those same companies who are too, quote unquote, nice to hold their people accountable and actually perform and to actually hold standards will then go lay people off. I'm not saying that I'm innocent of thinking about laying people off. As companies get big, candidly, I'll just say that I've thought about it. I know it's a possible reality in the future for some companies, maybe even for us,
but I don't like that being the default, of course. Let me frame it like this. As a company, we're helping everybody succeed. We're training them. We're investing in them. We're holding them accountable and ourselves accountable and we're performing. Then a market turns and we have to downsize the company. That's one thing. Being irresponsible, losing track of finances, not holding teams accountable, not holding ourselves accountable, not performing,
losing work and losing margins because of complacency, because we're, quote unquote, nice just so we can turn around and immediately terminate people or lay people off sounds a little gross to me. I'm not perfect. I don't have the perfect stance on this. Candidly, I've probably got a million miles to grow in this regard, but the other day when watching this happen, I was like, wow, did that really pan out to be weak and wimpy with standards only to lose performance,
only to then have to lay people off? Here's my question. Here's how I turn this into an okay podcast into a good podcast, which is nicer having a job, providing jobs in a company for good people on a consistent basis where we have high standards and actually saying something or being super, super sweet until we dump somebody on their butt and they don't have a job. I personally think it would be nicer, kinder to hold high standards and to actually do
those field walks and to actually perform and have jobs for the people around them. That's my personal stance. My question to you because I am not any kind of authority whatsoever on this. I may not even know what I'm talking about, but here's my question to you. Which one is nicer? Obviously, I'm going to leave that to you because you know how to gauge that. When you think in your company, should I hold project delivery teams accountable or not, and
should I say something, and should I have high standards? I would just encourage us to say, can I do this in a psychologically safe way, which I haven't done perfectly. In fact, maybe I haven't even done that well at all, but if it could be done in a psychologically safe manner while still holding teams accountable and driving progress, is that kinder than just dumping somebody on their butt once we stop performing or we're not making money? I'll leave it to you. I hope you've enjoyed this podcast. On we go.
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...
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...
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,...
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...
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...