There’s a particular kind of leadership meeting that looks productive from the outside.
Everyone turns up. There’s an agenda. People take turns explaining what they’ve been working on, what’s happening in their department & what they plan to do next.
Someone raises a problem. Two people spend fifteen minutes discussing it while the other five sit there wondering why they needed to attend.
Then someone says, “Let’s take this offline.”
Ninety minutes later, everyone heads back to work.
Plenty of talking. Not much actually solved.
That’s not a leadership meeting. That’s status theatre.
And if your leadership team is spending more time reporting on work than solving the issues stopping the business from moving forward, something needs to change.
The Problem With the Update Parade
I’ve spent the better part of eight years working as an Integrator with leadership teams running on EOS®. One thing I’ve come to appreciate is just how much time businesses can lose when meetings don’t have a clear purpose.
The problem usually isn’t that people have nothing useful to say. It’s that the meeting gives everyone an opportunity to say everything.
Someone starts with a quick update. That leads to a question. The question turns into a discussion. Before you know it, fifteen minutes have disappeared & you’ve somehow ended up debating something that only concerns two people.
Meanwhile, the bigger issues are still waiting.
The staffing problem nobody wants to address. The process that keeps breaking. The quarterly priority that’s quietly falling behind.
Those are the conversations that actually need the leadership team’s attention.
But they often get squeezed into whatever time is left after everyone has finished reporting.
The Boring Trick That Makes Level 10 Meetings Work
One of my favourite things about the EOS Level 10 Meeting® is that the structure is deliberately boring.
Same day. Same time. Same agenda.
Every week.
It starts on time, finishes on time & follows a consistent 90-minute format.
The first 25 minutes cover the essentials: a quick personal & business check-in, the Scorecard, quarterly Rocks, customer & employee headlines, & the previous week’s To-Dos.
Then comes the important part.
Sixty minutes dedicated to identifying, discussing & solving issues.
Not reporting. Not delivering presentations. Actually solving the problems that are getting in the way.
It’s a pretty significant shift when you think about it.
Instead of spending most of the meeting explaining what’s happened, the team spends most of its time deciding what needs to happen next.
Numbers Don’t Need a Story
Here’s where teams can make a simple meeting unnecessarily complicated.
Someone reports that a number on the Scorecard is off track.
Immediately, the explanations begin.
“We were going well until Thursday, but then this happened, & we think next week will be better because…”
Five minutes later, you’re still discussing one number.
The Level 10 approach is much simpler.
Is the number on track or off track?
If it’s on track, move on.
If it’s off track, add it to the Issues List.
The same principle applies to quarterly Rocks & weekly commitments. Establish whether things are on track, capture anything that needs attention & keep moving.
You’re not ignoring problems.
You’re making sure they get dealt with at the right time, with enough attention to solve them properly.
Stop Discussing Issues. Start Solving Them.
The real value of a Level 10 Meeting comes from the Issues Solving Track, often referred to as IDS.
Identify. Discuss. Solve.
The team prioritises its most important issues & starts with the biggest one.
First, identify what’s actually wrong. Not just the symptom someone has noticed, but the underlying problem.
Then discuss it openly, making sure the relevant perspectives are heard.
Finally, solve it. Agree on what needs to happen, who’s responsible & what action will move things forward.
Sounds straightforward enough.
But it’s surprisingly easy to spend an entire meeting discussing problems without reaching a decision.
That’s why the structure matters.
It stops the team from bouncing between issues, chasing distractions or repeatedly reopening conversations that should already have been resolved.
The aim isn’t to talk about every issue on the list.
It’s to solve the most important ones.
Why the Rigidity Is Actually the Best Part
I’ll admit, the first few Level 10 Meetings can feel a bit rigid.
People are used to giving detailed updates. They’re used to jumping into discussions whenever something comes up. And suddenly, someone is telling them to stop explaining & put the issue on a list.
It can feel unnatural.
But give the team a few weeks to get comfortable with the process & something interesting starts happening.
People stop worrying about the format.
They know when to report, when to raise an issue & when it’s time to solve something.
The meeting starts running itself rather than depending on one person to constantly bring everyone back on track.
And that’s the point.
The structure isn’t there to make meetings more complicated.
It’s there to take unnecessary complexity away.
What Do You Actually Want Back From Your Meetings?
Think about what your current leadership meetings are costing you.
Not just the hours spent sitting around the table, but the conversations that happen afterwards.
The meeting after the meeting.
The issues that need another meeting because nobody made a decision.
The founder who still ends up sorting everything out because ownership was never clear.
A good leadership meeting should reduce those problems, not create more of them.
With the right structure, your team can make decisions, solve issues & hold each other accountable without everything coming back to you.
You get fewer repeated conversations, clearer ownership & more time to focus on running the business.
And perhaps most importantly, your leadership team starts operating like a team rather than a collection of people delivering individual reports.
An hour of solving beats three hours of updating.
That’s the trade.
And it’s one worth making.