All Articles

Article

Leadership Team Meetings That Actually Get Things Done

Sep 16, 20268 min read
Leadership Team Meetings That Actually Get Things Done

If your leadership team meetings feel like a status update nobody needed, you are not imagining it. The weekly leadership meeting is the most repeated event in most businesses, and it is the one most often left on autopilot. Fix it and you fix the rhythm of the whole company. Leave it alone and every other problem takes longer to solve than it should.

I am Reyan Fernando, a Professional EOS Implementer® based in Geelong. I work with leadership teams across Victoria, Sydney and Sri Lanka, and when a team tells me they are stuck, the weekly meeting is the first place I look.

Why most leadership team meetings drain the week

Sitting in a lot of these rooms, the same four patterns come up again and again.

They are reporting sessions, not decision sessions. Each person walks the room through what happened in their area. Everyone nods. Nothing is decided, and the one genuinely contentious topic gets three minutes at the end because time ran out.

The agenda changes every week. If the structure is improvised, the meeting becomes whatever the most senior or most vocal person wants to talk about that morning. People stop preparing, because there is nothing predictable to prepare for.

Issues get discussed but never closed. The same three topics reappear month after month. The team has talked about the broken handover between sales and delivery so many times that raising it now feels rude.

They run long. A meeting scheduled for an hour that reliably takes two teaches everyone that start and finish times are negotiable. That lesson spreads to deadlines, then to commitments, then to the numbers.

None of this is a people problem. It is a structure problem, and structure is fixable in a week.

What effective leadership team meetings actually look like

Inside the Entrepreneurial Operating System®, the weekly leadership meeting is called the Level 10 Meeting™. It runs for 90 minutes, at the same time on the same day every week, with the same agenda. That sameness is the point: when the shape of the meeting never changes, the team stops spending energy on how the meeting will go and spends it on the business instead.

Open with people, briefly

Five minutes where each person shares one good thing personally and one at work. It sounds soft. It isn’t. It gets everyone off email and talking to each other as humans before you start arguing about margin.

Look at the numbers before the opinions

A Scorecard is a short weekly list of measurables, each with an owner and a target. You read it in five minutes, asking one question of each line: on track or off track? Not why. Anything off track becomes an issue for later. Reviewing numbers first grounds the conversation in what is actually happening rather than who feels most strongly.

Check the 90-day priorities

Rocks are the handful of priorities the team committed to this quarter, each owned by one person. Same question, same five minutes. A Rock off track for three weeks running is not a status update, it is an issue, and it goes on the list.

Headlines and to-dos, at speed

Short customer and staff headlines: a sentence each, no discussion. Then last week’s to-do list, which should be seven-day commitments that people either did or didn’t do. A team carrying the same to-dos for a month has either taken on too much or has an accountability problem worth naming out loud.

Spend the bulk of the meeting solving issues

This is what makes the 90 minutes worth it. Roughly 60 of them go to the issues list, worked through using IDS: identify, discuss, solve.

Identify means getting to the actual problem rather than the symptom someone walked in with. “Our quotes are slow” is a symptom; the real issue might be that nobody owns quoting. Most teams skip this step and then wonder why the same topic keeps coming back.

Discuss means everyone says their piece once. Part of the leader’s job is to notice when a point is being made for the third time and move the room along.

Solve means a decision with a named owner and a date, captured as a to-do. If it cannot be solved this week, the team decides what the next concrete step is and who takes it. The issue comes off the list either way.

The discipline is to solve the most important issue completely rather than touch all twelve lightly. Three issues closed for good beats a dozen revisited.

End on time, and rate it

Recap the to-dos, confirm what needs to be communicated to the rest of the business, and finish on the minute. Then each person rates the meeting out of ten, and anything under eight comes with a reason. That is how the meeting improves instead of slowly rotting.

The part teams skip: actually closing issues

If you change one thing this month, change this. Keep a visible issues list. Anything that surfaces during the week goes on it instead of triggering an ad hoc meeting. Then work top down and finish what you start.

Two things happen when a team does this consistently. Corridor conversations shrink, because people trust the list gets dealt with. And the issues get harder, because the easy ones are gone. That is a good sign.

It is also the antidote to the permanent firefighting so many owners describe. I wrote more about that pattern in why most businesses feel like they’re constantly firefighting.

Running the meeting when your team is split across locations

A good chunk of my work is with leadership teams in Sri Lanka, and with Australian businesses that have people in Colombo, Melbourne and Sydney all in the same meeting. A distributed leadership team does not need a different agenda. It does need three habits held more tightly than a team sharing one office.

One shared screen, always. Scorecard, Rocks and issues list visible to everyone, every week. When half the team can see the numbers on a boardroom wall and half cannot, the remote half becomes an audience.

Cameras on, and airtime deliberately shared. In any team where the founder is the loudest voice in the room, the quieter people hold back, and a video link makes that worse. Asking each person directly for their view is not a nicety; it is how you find out what is really going on.

Protect the time slot. Cross-border teams are tempted to move the meeting around travel, public holidays in two countries, and client calls. Pick a slot that works in both time zones and defend it. The meeting you reschedule twice is the meeting people stop preparing for.

One client I work with has teams across Sydney, Brisbane and Melbourne, and bringing everyone together through a consistent rhythm of meetings has helped create far greater alignment and connection across the business.

Rather than operating as separate regional teams, they have developed a much stronger sense of being one team. The regular cadence creates discipline and accountability, but over time it also builds something just as important: trust. People understand what’s happening across the business, what their colleagues are working towards and how their work connects to the bigger picture.

If you are running a business in Sri Lanka and want the detail on how the full system works locally, start with my EOS Implementer Sri Lanka page, or read the overview of what EOS is.

How to tell if it is working

Give it a full quarter before you judge it. The first three or four meetings will feel clunky, because you are learning a new rhythm while also clearing a backlog of issues that have been sitting around for years.

By week twelve, ask your team four questions:

  • Are we finishing on time, most weeks?
  • Are issues leaving the list and staying gone?
  • Do our to-dos get done inside seven days?
  • Has the number of unplanned meetings between us gone down?

Four yeses means the rhythm is holding. Anything less usually points at one of three things: the issues list is not being worked top down, the meeting is still being used for reporting, or someone is not being held to their commitments. All three are solvable, and all three are conversations worth having openly.

Where to start this week

You do not need an entire operating system to improve your leadership team meetings. Start small: a fixed 90-minute slot, a written agenda that does not change, a visible issues list, and a hard finish time. Run it for a quarter without negotiating with yourself about it.

Fixing the meeting tends to expose the next problem, which is exactly what it is meant to do. Once you can see clearly, you start choosing what to work on rather than reacting to whatever arrived that morning.

If you would like a second set of eyes on how your leadership team is running, get in touch. I offer a 90-minute session where we walk through how your business is running today and where the friction actually sits. No pitch, no obligation.


Reyan Fernando is a Professional EOS Implementer based in Geelong, Victoria, working with leadership teams in Geelong, Melbourne, Sydney and Sri Lanka. He spent more than 20 years in IT, founding and scaling an IT business that later merged with an MSP.

Share

More Articles