In this episode, Jason discusses how construction teams can rethink variances and use them as opportunities to improve systems instead of assigning blame. He explains why understanding the root cause behind missed commitments is valuable but only when teams create an environment where people can openly identify problems. Jason explores why traditional variance categories can feel negative and cause people to avoid acknowledging issues. What you'll learn in this episode: Why variances should be used to improve systems instead of blaming individuals. The limitations of relying only on lagging indicators like Percent Plan Complete. How changing variance categories can create a more neutral problem-solving environment. Why proactive roadblock removal can become a leading indicator for project performance. Are your teams using variances to find someone to blame, or to identify and remove the problems that prevent flow? 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 1684. In this podcast, I'm gonna talk about variances. If you're interested in that, please stay with us. Welcome everyone, I hope you're doing well and staying safe out there. I've got a really cool podcast for you over here and the podcast is gonna talk about variances and I really do appreciate the work of The Last Planner System in starting the concept of doing a root cause if
we don't hit our commitments and understanding why there was a variance. There are times when, and I said this to a team just the other day, there are times when people ask me about percent plant complete. It's one of my least favorite KPIs because it's a lagging indicator. The other thing is you lock yourself within a week in your weekly work plan with a lock line and that's not great. Like if there's something I need to substantially change the day before, I'm going to do
it. So I don't think that we should be penalized for that. PPC penalizes you from stopping the train of trades and using workable backlogs. So it's not super effective. It also attracts every activity and not just the ones on the path of critical flow. So it's not really a number that indicates whether or not your project has flow and I've never actually seen a project team dig into the root cause of why commitments weren't
met well enough to actually identify a variance and then a corrective measure properly. But I will say that using these variances and turning them into something that we can foresee and prevent is very valuable and it can turn into a leading indicator in the form of the roadblock removal average. So very cool stuff here. The thing that got me thinking about and wanting to talk about variances is that they're
not set up for human beings to actually want to acknowledge. Like for instance, they're very negative. Number one, bad planning. Number two, prerequisite work not done. That would be tattling on somebody else. Design issue, blaming the designer. Failed inspection, that means the trade did not perform well out ahead. Labor not available, that's kind of neutral. Materials not available, kind of neutral. Equipment not available, that one's fine. Contract COs, okay, submittals, whether those are fine.
But the first four that hit you are not aligned with United States culture. In the sense that they're quite negative. They're asking somebody to admit that they didn't do something right or that somebody else didn't do something right. They're not neutral in the sense that we're looking for, we're looking for something that is a condition, that is a system or a process problem.
So it's very hard for United States to actually use these because it moves against their identity. We got a couple of things. We do believe in being kind even though United Statesians are pretty rough and rowdy. The other thing is that from a religious standpoint, religious folks don't identify as being unkind. So there is a better way to do this and I feel like there's two things that will help us. Number one is switching these variances from a
lagging indicator and looking at them past tense or sorry, after the fact to do a root cause analysis, actually look for them before they impact work and switch them to where they're neutral types of roadblocks. So whether changes to the plan, planning incomplete, work area not ready, permissions needed, layout not currently ready, failed inspection. That one could be a little bit modified.
Something in the way, defects, missing information, missing resources, defects by way of materials, equipment issues, labor shortage, site conditions. These are more neutral and they aren't triggering the brain that you're being negative or blaming somebody else. So I've never really liked the LCI list. I do appreciate LCI. I've never really liked the LCI list. I'm encouraging the softwares and lean experts to
switch from the old list to the roadblock list and to switch them in time. And that is the podcast for today. I hope you enjoyed it.
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...