Your Level 10 Meeting Runs Long Because the IDS Segment Is Not Actually IDS

The weekly leadership meeting has a fixed shape and length. Ninety minutes, same day, same time, same agenda, ending on time whether or not the work is finished. The opening segments are meant to take about thirty minutes between them, leaving sixty for issues and five to close.

When a team tells me their meeting runs to two hours, or that it "needs" to, the cause is almost never that the company has too many problems. It is that the meeting is doing something other than what the agenda says, and the issues segment absorbs the consequence. Here is what eats the clock, in the order it tends to happen.

The first thirty minutes are not supposed to contain any discussion

This is the part teams find hardest to believe. Every segment before the issues list is a read-out, not a conversation. Anything worth discussing goes on the issues list for later, in priority order.

The segue. A brief personal and professional good news round. It overruns when it becomes a check-in on how everyone's week is going. Keep it short and keep it to good news specifically, which is not corporate positivity, it is a deliberate reset from whatever people were doing five minutes ago.

The scorecard. Five minutes, on track or off track, nothing else. The failure mode is universal: a number is off, the owner explains why, two people ask follow-ups, and eleven minutes are gone. The correct response to an off-track number is one word, "issue," and the owner's name goes on the list. No explanation in this segment, ever. Reading every number aloud is also slower than it needs to be; put them on screen and call only the ones off track.

The Rock review. Same discipline. On track means the owner still expects to finish by the end of the quarter, not "I worked on it." An off-track Rock becomes an issue.

Headlines. One sentence each on customers and employees. Storytelling creeps in here. If a headline needs context, it is an issue.

The to-do list. From last week's solves. Done or not done. A not-done to-do carries to this week, or becomes an issue if it is not-done twice. No status narration.

If those five segments take twenty-five to thirty minutes, the meeting works. If they take fifty, no agenda change will save you: the issues segment has already been halved.

Then the issues segment, which is usually not IDS

The issues track has three distinct steps, and teams skip the first and the third.

Identify. The owner states the issue in one sentence. Then the group agrees that is the issue, or changes it.

This step gets skipped constantly and it is the expensive one. A list full of topics rather than issues guarantees a long meeting. "Marketing" is a topic. "We cannot tell which leads came from the trade show, so we are about to renew a booth on no evidence" is an issue. Topics produce fifteen minutes of unstructured conversation. Issues produce decisions.

The first-stated issue is also frequently a symptom. "The new hire is not ramping" is often really "we have no onboarding process and the last three hires ramped by luck." Asking twice whether the stated issue is the real one is the highest-value thirty seconds in the meeting.

Discuss. Once. Everyone with something new to add says it once. Repeating your point louder is not discussion, and the facilitator's job is to say so. The usual leak is people arguing about the solution before the group has agreed what the problem is, which ends with nobody changing their mind.

Solve. This is the step that gets dropped most often, and dropping it is why the same issue comes back every week.

A solve is a to-do: one person, one action, one date, written down while everyone watches. "We should look into that" is not a solve. If the group cannot produce a to-do, the issue is not solved and it stays on the list, which is an honest outcome. Moving on while feeling like something happened is not.

Only three issues get solved in a week, and that is correct

Teams with a twenty-item issues list try to work through all twenty and solve none.

Prioritize three. Solve those three properly. Leave the rest. Next week, prioritize again from whatever is there, which will not be the same three, because half of last week's list has resolved itself or turned out to be a symptom of something you already fixed.

Voting is simple: everyone picks their top three, simultaneously, so nobody anchors on the CEO's choice. That is easier to do cleanly in a remote meeting, because votes go into a shared board or into chat on a count of three.

Two rules keep the list usable. Anything sitting there for weeks without ever being voted up is not an issue, and should be deleted. And anything that keeps getting voted up and never solved is usually a structural problem in an operational disguise.

Issues at the wrong altitude

A leadership meeting solving departmental issues will always run long. An issue solvable entirely inside one function belongs in that function's own weekly meeting. The leadership meeting is for issues that cross functions, exceed a single leader's authority, or affect the company's direction.

The quickest test: if the owner could solve it alone with the authority their seat already has, they should. Its presence on the leadership list usually means they are seeking cover for a decision they are entitled to make, which is a decision-rights problem and a signal about the accountability chart rather than the meeting.

The two things that are not meeting problems at all

The meeting has eleven people in it. A leadership team is generally three to seven. At ten or more the meeting becomes a broadcast, quiet members stop contributing, and the issues segment cannot function because too many participants have no stake in most items. Eleven people usually means your structure has a layer missing and the meeting is showing you that.

Nobody in the room can actually decide anything. If every solve requires the owner's approval and the owner is absent, or present and overrules the group afterward, the meeting is theater and shortening it will not help. That is a question about authority, and it belongs on the quarterly agenda rather than the weekly one.

Small mechanics that buy back real time

• Rotate a timekeeper who calls the time out loud at each segment boundary, and not the person running the meeting.
• Put the agenda and a visible countdown on screen. On a video call that does more work than it does in a room.
• Start on time regardless of who is missing, end on time regardless of what is unfinished. Ending on time is the promise that makes people show up.
• Capture solves live, on screen, so the wording is agreed rather than reconstructed later.
• Rate the meeting out of ten at the close, and anyone scoring under eight says why in one sentence. That question surfaces the pattern faster than any analysis.

It gets worse before it gets better

A team that starts enforcing this will feel like the meeting got harder for about a month. People will feel cut off in the scorecard segment. The issues list will grow rather than shrink, because things once absorbed in twenty-minute tangents are now being written down. That growth is the system working. The list peaks and then falls, usually within a quarter, and the meeting that was running two hours starts finishing early.

These patterns hold across industries, though the shapes differ. A trades business tends to fill the leadership meeting with dispatch and scheduling issues that belong to the operations seat, while construction leadership teams fill it with project-level detail that belongs in a project meeting. Both are altitude problems, and both look like meeting problems until you look at the accountability chart.

If your weekly meeting keeps overrunning and none of the above explains it, tell us what your last three agendas looked like and where the time went.