Level 10 Meeting: the weekly EOS meeting, explained

Seven segments in a fixed order, always the same length: five minutes of personal and business good news, five reading the Scorecard, five on quarterly Rocks, five for headlines about customers and staff, five checking last week's to-dos, sixty solving issues, and five to close. Ninety minutes in total, same day and time every week.

The arithmetic is the whole argument. Twenty-five minutes of reporting, five minutes to close, and everything left over goes to problems. Most leadership meetings invert that ratio without meaning to, spending an hour on updates and the last ten minutes agreeing to discuss the real issue next week, which is how an issue survives a quarter.

The lengths are not suggestions. A segment that runs long is stealing from the hour, and the hour is the only part of the meeting that changes anything. Whoever runs the meeting is really running a clock, and the most valuable sentence they say all week is that something is an issue and goes on the list.

The timer below is our own version, not an official tool. It runs the seven fixed-length segments and shows the clock for the current one. If a segment runs long, the overrun turns red and keeps counting until you move on. Two buttons count issues raised and issues solved. At the end, you see minutes over by segment and issues raised against issues solved.

Put it on the shared screen and have the person running the meeting press the buttons. It builds the habit the format depends on: when the clock ends a segment, anything unfinished goes on the list. After three or four weeks, the summary will usually point to the same segment running long. That is the issue to raise.

Teams treat it as a status meeting, a department meeting or a stage for whoever brought slides. It is none of those. The reporting segments are there to spot what is off, not to explain it. In five minutes on the Scorecard you can say a row is red and add it to the list. There is no room to hear why it went red.

Teams that keep the old habit and bolt the agenda on top end up with a status meeting that has a timer running. The tell is easy to hear. If the loudest word in the first twenty-five minutes is why, the meeting has drifted. Why belongs in the hour, once the item is on the list and the whole team has agreed it is worth that hour.

Each stray item already has a better home. Updates go into the shared doc or the channel people already read. Department business goes to that department's own weekly at its own level. A presentation, a new pricing model or a hiring plan worth forty minutes, gets its own booked session with the material sent out first, and whatever it needs decided comes back to the list.

The leadership team, one person per function, which for most companies lands between five and seven. One of them runs it, usually the Integrator™, the person who holds the day to day together. Someone keeps the clock and writes the list, sometimes the same person. A guest joins for the one item they are needed for, then leaves when it closes.

Running the meeting means guarding the format, not chairing the discussion. The person on the clock says very little about the content and a lot about the time: that segment is over, that is an issue, put it on the list, we are eleven minutes into a five-minute item. Handing the role to whoever is most senior tends to produce the worst version of it, because the most senior person in the room usually has the most to say about everything in it.

Be strict about guests. Keeping an operations manager in the room for the full ninety minutes so they can speak for twelve of them costs the company an hour and teaches everyone that attendance is decorative. Bring them in for their item, let them answer, send them back to work. If the same guest turns out to be needed most weeks, that says something about the shape of the leadership team, and it belongs on the list too.

Because reporting expands to fill whatever time it is given. The four reporting segments are deliberately too short to discuss anything, which forces every problem they surface onto a list instead of into the room. For about three weeks that feels wrong. Then the team notices the change: issues are closing, and the same three have stopped coming back.

The reading is the part teams find hardest to keep quiet through. A row comes up red, the owner starts explaining, and eight minutes disappear into a conversation two of the six people in the room needed to hear. The habit to build is a single word: the owner says off track, the facilitator writes the row on the list, and the board moves on.

Segue looks like the soft segment and is the one to protect. Ninety seconds of unstructured chat before a meeting starts happens anyway, so putting it inside the agenda costs nothing and buys a room where people have already spoken before anyone has to disagree with someone.

Working the issues list, one item at a time, hardest first. The team picks the top three by importance, takes the first, and stays on it until somebody has decided something or has committed to do something by a stated day. Nine issues touched and none closed is a worse hour than two issues finished.

The three-step version this system uses is called IDS®: identify the real issue, discuss it once, then solve it. Identify is where most of the value sits, because the thing raised is usually a symptom. Late deliveries turn out to be a hiring problem, and the ten minutes spent finding that out saves the forty that would have gone on scheduling.

Discuss means everyone says their piece once. The facilitator's job is to stop the second lap, where the same three positions get restated in different words. Solve means one person leaves holding one thing with a deadline on it, and that commitment lands on the to-do list where it will be read out next week whether it was done or not.

The same seven segments one level down, run by whoever owns that department. It reads that team's own numbers and works that team's own list, and it usually finishes faster because there are fewer rows. Anything the department cannot close by itself moves up to the leadership list, and anything the leadership team settles comes back down as context.

The two levels avoid overlap by owning the issue, not the topic. An issue sits on one list at a time, held by the group that can actually close it. A shipping delay a warehouse team fixes by moving its cut-off time is theirs. The same delay caused by a supplier contract nobody in that room can renegotiate goes up.

Watch for the same item being chewed over at both levels in one week, once on Monday and again on Thursday, ending in two decisions that contradict each other. Whoever runs the departmental meeting escalates out loud in the conclude segment: this one goes up, and you will hear what came back next week.

With three things in the last five minutes. Read back the new to-dos so every action has a name attached out loud. Agree what needs saying to the rest of the company and who says it. Then everyone rates the meeting out of ten, and anything below eight comes with one sentence about what would have made it better.

The rating is the part people skip and the part that fixes the format. A team that scores itself honestly for a month will find its own problems faster than any advice from outside, because the low scores cluster: always the same segment overrunning, always the same person arriving with nothing ready.

The cascading message matters more than it sounds. Half the damage a leadership meeting does is done in the hours afterward, when six people give six versions of a decision to their teams. Thirty seconds agreeing on one sentence prevents a week of quiet correction.

Four ways, and all four are visible from the clock. The reporting segments overrun. The issues list is written during the meeting instead of over the week. The hour is spent on the easiest items because they close quickly. And the meeting is moved when somebody is busy, which teaches the team it is optional.

Moving the meeting is the one that kills the habit outright. A weekly rhythm survives a bad week; it does not survive being rescheduled twice. Run it with whoever is in the room, and let the missing person read the notes.

The easy-items problem is subtler. Closing six small issues feels productive. The expensive one stays at the top of the list for another month. Pick by importance and accept an hour that ends with a single decision.

Rough, then better. Week one runs long because nobody has read numbers aloud to this room before. Week two the board is half empty. Week three the first hard issue arrives and the hour finally does its job. Week four the to-do list catches somebody out in public, and that is the week the format starts working.

Video works when three rules hold. Cameras on for the whole ninety minutes, one shared document everybody can see, and the list edited live so the room watches items land on it. The segue is the segment that dies first on a call, so protect it. A facilitator willing to interrupt matters more than mute discipline.

The shared document does the work a whiteboard does in a room. Put the numbers, the quarterly priorities, the to-dos and the issues list in one file, screen shared or open on a second monitor, and edit it while people talk. An issue that appears on screen as somebody names it gets argued about far less than one recalled from memory forty minutes later.

Segue on video collapses into three people saying good week, nothing much, because nobody can read the room and nobody wants to go first. Ask each person by name in a fixed order and let the pauses sit. It costs the same five minutes it costs in an office and it buys the same thing: a team that has heard each other's voices before the first disagreement.

Yes, and plenty of teams do. The agenda needs two things to work: a weekly list of numbers to read and a written issues list that survives between meetings. Neither requires the rest of the toolkit. What you lose without the wider system is the connection between the issues and a quarterly plan that decides which of them matter.

Printing the agenda and putting it on the wall is the cheapest version of adopting it. Seven lines, seven durations, and a facilitator willing to say that something belongs on the list. The rest of the tools this framework carries are worth reading about before you decide how much of it you want.

In EOS® the meeting is called the Level 10 Meeting, and it sits with the Scorecard and the quarterly priorities as one of the parts teams adopt first. The name matters less than the structure. If you take the ninety-minute shape and nothing else, you will still have a better meeting next Tuesday than you had last Tuesday.