Why your weekly leadership meeting feels like a waste, and the 90-minute fix.

By Ray Myers · Professional EOS Implementer^® · Dallas–Fort Worth

The meeting you already dread

A 40-person services firm in Plano called me because their weekly leadership meeting had turned into what the CEO called “a two-hour update on things nobody could do anything about.” Seven leaders in a room. Everyone reporting on their week. Almost no decisions made. The real work, the hard conversations and the actual problem-solving, happened in hallway huddles after the meeting ended.

Sound familiar? If your weekly leadership meeting feels like a tax you pay to be a leader, you don’t have a meeting problem. You have an agenda problem.

Why status updates ruin leadership meetings

Most weekly leadership meetings default to a round-the-room status update. On paper it feels efficient. In practice it’s three things at once, none of them well:

1. A performance review with an audience. Nobody wants to admit their number is off in front of peers, so bad news gets softened or buried.
2. A trivia game. Everyone learns about issues they can’t help solve, and by the time the third person is talking, the first person has stopped listening.
3. A place decisions go to die. The real issues get flagged, then punted to “let’s take that offline.” Offline never comes.

The Level 10 Meeting^®, part of the Entrepreneurial Operating System^®, is designed to solve all three problems by giving each of them its own dedicated slot, and by ending on time whether you finish or not.

The Level 10 agenda

Ninety minutes. Same day, same time, every week. Same seven-part agenda in the same order. That last part matters more than people expect.

• Segue (5 minutes). Each person shares one personal best and one business best from the past week. Sounds soft. Isn’t. It shifts the room from “grinding through work” to “we’re a team,” which is the only mode where the rest of the meeting works.
• Scorecard review (5 minutes). Five to fifteen numbers. Anything off-track becomes an issue on the list. That’s it: no explanation, no story, no defense.
• Rock review (5 minutes). One at a time: “On track” or “Off track.” Off-track Rocks become issues. Again: no story.
• Customer & employee headlines (5 minutes). Wins and warnings from the front lines this week. Anything that needs solving goes on the issues list.
• To-do review (5 minutes). Last week’s commitments. Done or not done. The healthy target is 90 percent done. Not-done to-dos become issues.
• IDS (60 minutes). Identify, Discuss, Solve. This is the meeting. Everything above was triage. Now the team actually solves the top three issues on the list, in priority order, until they’re done or the clock runs out.
• Conclude (5 minutes). Recap to-dos and who owns them. Any communications to cascade to the rest of the company. Rate the meeting 1 to 10. The goal is an average of 8 or better. Below 8, we talk about why, briefly.

Total: 90 minutes. Same order. Every week. Forever.

Why the order matters

Notice what happens in the first 25 minutes: every part of the business surfaces its issues onto one list. Numbers off? Issue. Rock behind? Issue. Angry customer? Issue. To-do skipped? Issue. By the time you get to IDS, you have a real, ranked list of the things standing between your team and the quarter you said you wanted.

The old status-update meeting “solves” issues the moment they’re raised, which sounds efficient but means the loudest person’s issue gets solved first, and the biggest one might never get discussed at all. The Level 10 flips this: everything gets logged, then the team picks the biggest one.

What changed for the Plano firm

The 40-person services firm made three specific changes:

• They stopped the round-robin status update. It became five minutes of Scorecard, five of Rocks, five of to-dos, and only off-track items surfaced to the issues list.
• They protected the IDS block. Sixty minutes, no exceptions. If IDS ran out of time, whatever was still on the list moved to next week. Nothing rolled into an off-the-books hallway meeting later.
• They ended on time. This one felt like a rule at first and became a culture within six weeks. When people know the meeting will end at 90 minutes no matter what, they show up ready and they cut the storytelling.

A quarter later, their meeting rating averaged 8.4. More importantly, the CEO stopped seeing people in his doorway after the meeting to have “the real conversation.” The real conversation was now happening in the room.

What it doesn’t solve

Honest pushback, because I owe you that.

A great agenda doesn’t fix a broken team. If two of your leaders can’t have a hard conversation without one of them shutting down, no meeting structure will save you. That’s a People Analyzer^® conversation or a coaching conversation, not an agenda conversation.

The Level 10 also doesn’t work without the tools that feed it. If you don’t have a working Scorecard, you have nothing to review in the second five minutes. If you don’t have Rocks, you have nothing to check in on. If you don’t have an Accountability Chart^®, half your IDS conversations will be about who should have decided this in the first place. The agenda is the container. The rest of EOS is what goes in it.

And it takes about six weeks to click. The first two meetings feel awkward and rushed. The next two feel mechanical. Somewhere around week five or six, teams stop noticing the structure and start noticing they’re actually solving things.

Try this next week

Even without a full EOS^® implementation, you can steal the shape of a Level 10 for next week’s meeting:

1. Print the seven-part agenda. Time-box it.
2. Keep a running issues list on a whiteboard or shared doc.
3. Reserve the last hour for IDS on the top three issues.
4. End on time. Rate the meeting 1–10 out loud.

If your rating averages below 8 for three weeks, something below the meeting layer is broken. That’s the conversation worth having, and the one a 90 Minute Meeting is designed for.