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.1726 - Level 10 Meetings: Identify, Discuss, Solve

Nov 18, 20268 minAudio
ShareXLinkedInFacebookWhatsAppEmail

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 Operating System and explains why each part of the agenda is designed to feed the next. Jason walks through the full sequence from the segue and scorecard to rock review, customer and employee headlines, to-dos, IDS, and the conclusion showing how the meeting continually identifies issues, turns them into action, and keeps leadership teams aligned and accountable. What you'll learn in this episode: Why Level 10 Meetings are designed around alignment, accountability, and focus. How scorecards, rocks, headlines, and to-dos help surface issues. Why problems should move into IDS instead of being discussed randomly throughout the meeting. How Identify, Discuss, Solve turns issues into decisions, owners, and deadlines. Why a consistent meeting system helps teams gain traction between meetings. Are your meetings simply reporting information or consistently identifying and solving what is keeping the team off track? 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 1726. In this one, I'm gonna talk about the purpose and flow behind level 10 meeting agendas. If you're interested in that, please stay with us. Welcome everybody, I hope you're doing well and staying safe out there. I'm excited about this one because people hear a lot, probably about level 10 meetings. And it's hard to know, just like with

anything, it's hard to know what is it if you're not around it all the time and haven't had the time to dig into it enough to where it's muscle memory. So level 10 meeting agendas come from Gina Wickman in the book, Traction, from the Entrepreneurial Operating System. And it's a business system that quite a few folks use and I really have enjoyed being around it and being exposed to it.

And I can tell you that over the last couple of years hearing people say level 10 meetings, I haven't immediately known what they were talking about, meaning that it's not on the top of my mind. And so I've gotten a lot more used to it and I wanted to cover it right here, not only to help me, but to say if any of you all have been in the same boat, I wanna make sure that I'm helping everybody out as much as I possibly can. So level 10 means that we need to have, from one to 10, a level 10

meeting, like really, really top-notch. We can't have crappy meetings, right? This is a weekly leadership team meeting within whatever sphere that you're in. And the purpose is to keep the leadership team aligned, accountable, and focused. So this could be at whatever level of leadership you're in, so it doesn't just have to be one group. The key concept is that each agenda item feeds the next, it works in a flow. And I remember first seeing this with Patrick Lencioni, where he talked about the meeting agenda

in Death by Meeting, how each item needs to flow to the others and help human beings do what they need to do. So this was an expansion on it. In fact, Gino Wickman expanded on the work of Jim Collins, Patrick Lencioni, Peter Drucker, and a number of others. And so that's why this stuff seems so familiar, because it is, it's a combination. Gino Wickman, and maybe we should say that we did what he did, because he came before us, but what we did with Lean

Construction, pulling it all together into a system, is what Gino Wickman did with all of these business systems. So the concept here is that, again, that they all flow together. Now this could be a shorter meeting, it could be up to 90 minutes. You're not just reporting information, you're identifying what's off track. It all comes back to IDS, IDS, identify, discuss, solve. Identify, discuss, solve. Identify, discuss, solve. If you want to get traction, you got

to clear the way. It's the same thing in construction. So you determine what needs attention, and then you solve the problems, and you assign actions, and that's how you drive forward. So the agenda is typically segue, scorecard, rock review, customer employee headlines, to-do list, IDS, and then conclude. So let's go through these one by one. Segue, it's five minutes, and this is where you connect the team and transition into the meeting. Each person briefly states good news, personally or professionally. This kind of sets the mood, sets the

tone for the meeting, and really, I think, diffuses any nervousness, and gets everybody in the habit of being positive in a meeting that possibly could be hard, meaning business meetings are sometimes hard. So it starts with the human aspect, right? First who, then what? Then the scorecard, and this is where I first learned it from Patrick Lencioni, and it's really great. This is where you review weekly performance measures. You identify numbers that are off target, move

exceptions to the issues list rather than discussing them immediately, and the reason this is so important is because you want to form your agenda or what you discuss in the meeting based off of data, so you hit the scorecard first. Then you go into number three, the rock review. Now when we talk about rock, we're talking about goals. The analogy comes from the water, sand, aggregate, rock analogy fitting into a vase, no, it's

a vase, or a big transparent container. If you put the sand in first, then the gravel, then the rocks, everything spills out. If you put the rocks in first, then the gravel, which filters around it, then the sand, which filters around it, then you can actually even add water, and it fills into the container perfectly without any overflow. So the concept is do the big things first. Rocks are goals, and those goals should be set at a certain interval, and these are

the things that will help you to get traction in your company. So check whether each quarterly priority is on track or off track. Off track rocks become issues. Now you'll notice here that any numbers that are bad become an issue. Any rocks that are not on track become an issue, okay? And then that's left to the IDS. So anything that you're looking at throughout this agenda, if it's a problem, it becomes an issue. So we're basically mining for issues by reviewing the scorecard and the rocks.

Number four, customer-employee headlines. Share important news, including PTO, staffing changes, customer concerns, and developments requiring leadership awareness. Remember, problems become issues. Then you go into your to-do list. This is where you review commitments from the previous meeting, mark each one done or not done. Unfinished items may become issues again when they indicate an obstacle or a recurring problem. So basically, your scorecard, rock review, customer-employee headlines, and to-do list, you're either making

traction or you're identifying issues. Now, number six, IDS. Identify, discuss, and solve problems or issues. So you prioritize the issues list, identify root causes, discuss solutions, make decisions, and assign owners and deadlines. Then those assignments become to-do list items that you actually accomplish between the next meeting. Then you conclude. Five minutes, recap new to-dos, decide what needs to be communicated, and rate the meeting from one to 10, and it needs to head towards a 10.

So I'm in love with this meeting. It is very effective, and the entire thrust is to identify problems and solve them and keep everybody on track between meetings. And if you've never heard of a level 10, I hope you do and get a chance to experience it. And here's the other thing that I'll say. Even a level 10 done poorly is better than one not done at all. We've got to make sure that we're jamming

as best we can into a meeting system that will allow us to gain traction, as Gina Wickman says, and that comes from solving issues. 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.1725 - Preparing to Go to Bid

    Nov 16, 202611 minAudio

    Going to bid is not just about sending drawings to trade partners and waiting for numbers to come back. In this episode, Jason breaks down the planning, estimating, scoping, and documentation that need to happen before...

    Credit the people on this episode