How to Run Better Leadership Meetings

Introduction

The weekly leadership meeting is where strong execution really matters. As the COO, it's your responsibility to make sure it not only runs smoothly but also helps move the company forward. When the meeting works, the week almost runs itself. When it fails, you spend the next four days chasing the things it should have caught, or worse, the wrong priorities get tackled.

This article covers how to run a great leadership meeting: the agenda, the pacing, what needs to be in place before anyone sits down, the habits that keep quality high week after week, and the pitfalls to avoid.

But before we dive in, do any of these stereotypes sound familiar?

Which meeting host do you recognize?

Every leadership meeting has a host, and most hosts fall into a recognizable pattern. See if you spot yourself, or the person whose meeting you sit in every Monday.

The Narrator. Reads updates aloud that everyone could have read in advance. The meeting is a live performance of a written document. People listen with one eye on their inbox and wait for their turn to narrate.

The Firefighter. Whatever burned that morning becomes the agenda. The planned topics wait another week, again. The team learns that preparing is pointless because the fire always wins.

The Diplomat. Keeps the room comfortable. Every number is "fine," every priority is "coming along," and disagreements get smoothed over before they surface. The meeting is pleasant, and the surprises arrive at quarter-end.

The Prosecutor. Turns every update into a cross-examination. People arrive braced to defend their area instead of being ready to solve problems. Issues get hidden because raising one means going on trial.

The Wanderer. Has an agenda somewhere, but follows the conversation wherever it goes. One interesting tangent leads to another. At minute ninety, three topics got half-discussed, and none got decided.

Each of these is a capable person doing their best inside a meeting with no structure. The fix in every case is more or less the same: better inputs, more visibility and accountability, a real agenda, and a few pacing rules. That is what the rest of this article is about.

What a good meeting is

Eliyahu Goldratt's The Goal offers a useful test. In the book, every activity gets judged by whether it moves the company toward its goal. Busyness does not count. Effort does not count. Only throughput counts.

Apply that test to your leadership meeting.

A good meeting surfaces the biggest issues in the operation, solves them, and assigns ownership. People leave with decisions made and to-dos owned.

A bad meeting consumes ninety minutes of your leadership team's time and leaves the operation exactly where it was. In Goldratt's terms, work that happened without producing throughput.

Patrick Lencioni adds a second lens in Death by Meeting. Meetings fail when they lack real conflict about real issues, and when one weekly session tries to hold updates, tactics, and strategy all at once.

A good meeting has structure, and inside that structure it has honest disagreement.

Hold those two ideas together and you'll see that a good leadership meeting confronts the most important issues, argues about them openly, decides, and assigns owners. Everything else is a status update that could have been an email.

What you need before the meeting

Many meeting problems come from bad preparation. The Narrator narrates because the data lives in his head. The Firefighter firefights because issues have nowhere to go during the week. Fix the inputs, and half the meeting fixes itself.

Recurring metrics

Your meeting needs a scorecard and KPIs: five to fifteen numbers that tell you the operation is healthy, each with one owner and a weekly target. Revenue, pipeline, churn, on-time delivery, support response time... Whatever fits your business priority this quarter.

It replaces opinion with fact. Without it, the meeting opens with "how is everything going" and everyone says "good." With it, the meeting opens with three numbers off track and you know issues need to be created and see where the conversation needs to go.

The numbers must be current before the meeting starts. If people fill in the scorecard live, you lose precious minutes and the review loses its teeth. Use a tool like MonsterOps to remind people that KPIs are not updated before the meeting starts.

Rock status

Rocks are your quarterly priorities. Whether you are running EOS, Scaling Up, 4DX, or your own playbook. Each Rock has one owner and a binary status: on track or off track.

"It's coming along" tells you nothing. On track means it will ship by the deadline. Off track means on the current path it will miss. Forcing the choice forces honesty, and it protects your team from the Diplomat pattern. MonsterOps also supports At-Risk, that you want to use when there are risks outside of your control, like a new legislation that may come into affect, or a vendor that may not deliver on time. This gives you an opportunity to create an issue and discuss backup plans if needed.

You may want rock owners to recommit on the spot instead of simply saying the status has not changed. In MonsterOps, you can use deck view to hide the previous status, forcing each owner to rethink the status of their rock.

A running issues list

Issues appear on their own schedule. Tuesday at 4pm, in a customer call, in a Slack thread. If the meeting is the only place to raise them, people either forget them or derail the agenda with them. That is how Firefighter meetings are born.

Keep one shared list where anyone can drop an issue the moment they spot it. In MonsterOps, an issue raised on Tuesday lands on the next meeting's agenda by itself. The meeting then works from a list built across the whole week, tackling the most important issues first (avoiding the "squeaky wheel gets the oil" effect).

Issues are resolved when plan of action is determined. That is, to-dos are reated and assigned with deadlines.

Last week's to-dos

Every meeting produces action items, and the next meeting must check them. When to-dos are scattered across notebooks and chat threads, the check becomes quickly impossible and accountability vanishes. Keep them in one place, separated from daily operations, to operate the business, with an owner and a due date each. Then the review takes ninety seconds and isn't lost in a sea of tasks unrelated to moving the company forward.

The agenda

Here is an example of a weekly agenda that works. It borrows from the Level 10 Meeting in Traction and holds up under pretty much any framework. It takes about ninety minutes and happens on the same day, at the same time, every week.

1. Check-in (5 minutes): One piece of good news each, either personal or professional. This gets every voice in the room within the first five minutes, and people who have spoken once speak again when it matters.

   Alternatively, you could use a hand update to surface more information:

2. Scorecard review (5 minutes): Read the numbers. On track or off track. Anything off track drops to the issues list without discussion. The review identifies problems; the issues segment solves them. Speed is essential if you want to keep the momentum going. That's why you can do this in two clicks in MonsterOps.
3. Rock review (5 minutes): Each owner states their status. Off track goes to the issues list, again without discussion. Separating reporting from solving is key. Speed is also essential here.
4. News (5 minutes): Customer, product and employee news in one sentence each. A big win, a key hire, a notable complaint, a new release... Anything that needs more than a sentence or two should really be an issue.
5. To-do review (5 minutes): Read last week's to-dos. Done or on the list for discussion. You want ninety percent completion week over week. A to-do that keeps rolling over is an issue in itself.
6. Solve issues (60 minutes): This is where the meeting really starts. You now have a list built up throughout the week, plus everything that has just dropped from the scorecard, rocks, news, and to-dos. Pick the most important issues and start with those.

   Identify the real issue first, because the stated issue may often be a symptom. Discuss it once, with everyone saying their piece a single time. Then solve it, which means a decision is reached, and a to-do with an owner and a date is created to tackle it.

   Keep in mind that three issues solved well beat ten touched briefly. Whatever stays unsolved stays on the list. Nothing is lost, so nothing needs to be rushed.

7. Conclude (5 minutes): Recap the to-dos created and agree on what gets communicated to the rest of the company. In MonsterOps, everything is automatically summarized, and you can score each meeting so your meetings keep improving over time. Note that MonsterOps also captures attendance for future reference.

Other agenda formats that work

The ninety-minute agenda works well for most places. It covers reporting, accountability, and problem-solving in one weekly block, and it is where I would start. But it is not a one-size-fits-all. Here are three variations that hold up, plus one companion.

The 30-minute condensed version. For leadership teams of three or four, or for operations where the issues list runs short. Drop the check-in. Kpis, rocks, and to-dos in ten minutes of binary reporting. Eighteen minutes on the top one or two issues. Two minutes to conclude and score. The discipline stays identical; only the time per section changes. If the issues list keeps outgrowing the eighteen minutes, move back to the full agenda rather than letting this get out of hand.

The scoreboard-and-commitments format. The style 4DX teams run. Twenty to thirty minutes in three parts: review the scoreboard, report on last week's commitments, make one or two new commitments each for the coming week. It works when the team is driving toward one or two clear goals and the rest of the operating rhythm is healthy. In MonsterOps, you can use the objective section to make sure everything is aligned. This format usually struggles as a company's only meeting, because it has no room for issues outside the goal.

The OKR check-in. Weekly and short. Each key result owner reports the metric plus a confidence score from 1 to 10 that the target lands by quarter end. Anything below a 7 becomes an issue. Solve the top ones in the same session, and pair the weekly check-in with a monthly session that digs into the low-confidence areas properly. Well-suited to teams focused on execution.

The daily huddle. Five to ten minutes, standing, same time every day: what I finished, what I am on today, where I am stuck. The huddle absorbs logistics and quick unblocking, which keeps the weekly meeting clean for real issues. Best suited for teams that need to move fast (e.g., startups or founder mode 🙂). Lencioni argues that different decisions need different meetings, and mixing them all into one is how the weekly session turns into a stew.

Whichever format you pick, four things stay constant. Reporting should be binary and fast. Issues live on a running list. Every discussion ends in a to-do with one owner. And the meeting gets scored ideally. You can change the format as much as you like, but keep the contents. In MonsterOps, the agenda is yours to shape, so any of these formats runs with the same scorecard, rocks, and issues attached.

Running the meeting

An agenda on paper keeps nothing on track. A person does. That's part of the facilitator's job, in practice.

One facilitator

One person runs the meeting, week after week. The best pick is whoever can hold the clock and push for decisions without needing to win the arguments themselves.

Keep the role stable. A facilitator gets good through repetition, and a rotating one never does.

The clock

Each segment has a time box, and when the box ends, the segment ends. This feels abrupt for the first three weeks. Then the team adapts, reporting gets crisp, and the sixty minutes for issues stops getting eaten from both sides. It is easier to hold the boxes when each segment has a visible timer, which is where software like MonsterOps helps: the clock runs on screen, so the facilitator can just enforce a timer that is visible to everyone.

The facilitator's most useful sentence: "That's an issue. Drop it on the list." Someone starts explaining a bad number during the metrics review? Issue, list. Two people start debating mid-report? Issue, list. In MonsterOps, that drop is one click, you don't want to lose momentum capturing an issue. The list is where the topic gets its full turn, in the hour that exists for that purpose.

Tangents get called by rule

Tangents survive because interrupting a colleague feels rude. Make the interruption structural. Agree as a team, in advance, that anyone can call "tangent" at any time, and the response is to note the topic and return to the agenda. When it is a shared rule, calling it is a service. When it depends on someone's nerve, the Wanderer wins.

Pull the disagreement out

A meeting that stays on pace but avoids conflict is a faster version of a bad meeting. Lencioni's point is that engagement comes from real disagreement about things that matter. If two people are visibly holding back during an issue, the facilitator names it: "You two see this differently. Say it now." The issues segment is the safe, structured place for that conversation. Use it, and the Diplomat pattern is broken.

Every issue lands somewhere

Each discussion ends in one of three ways: a decision with an owner and a date, a to-do to gather missing information by a set date, or a deliberate choice to park the issue. "Let's keep an eye on it" belongs to none of the three. People need to be heard. Once they have been, they commit to the decision, including the ones who argued the other way.

Practices that compound

The agenda gets you a solid meeting. These habits raise the average, week over week.

Score every meeting. At the close, each person rates the meeting from 1 to 10, out loud. I like every score to come with a why. Scoring creates a feedback loop on the meeting itself and makes quality a shared job instead of the facilitator's burden. Track the trend, automatically done with MonsterOps. A team averaging 8.5 is running a different operation than a team averaging 6. Pro-tip: MonsterOps randomizes the order for scoring, but the leader should always score last.

Prepare, or reschedule. metrics current, rock statuses done, issues on the list, to-dos updated. If the inputs are missing, the meeting will spend time gathering them, which is the most expensive way to gather anything. When the data lives in one system, preparation is a fifteen-minute job. When it lives across spreadsheets, decks, and chat, it gets messy fast, and the mess arrives in the room with you. Favor one system like MonsterOps to track more easily and have clear notifications when something is missing.

Same day, same time. The meeting is an anchor for the whole week. When it moves, everything becomes a mess; people are not available or need to shift other meetings. Protect the slot; no one should miss the most important call of the week.

Start on time, end on time. Starting late taxes the punctual to subsidize the late. Ending on time forces people to communicate efficiently because there is still work to be done after the meeting.

Track to-do completion. Ninety percent done, week over week, is the bar. Below that, you have an accountability gap hiding in plain sight. The number only exists when to-dos live in one place with owners and dates. MonsterOps tracks the due date as well as the completion rate for you, which turns "things slip around here" into an actual figure you can manage.

Cascade the decisions. The leadership meeting decides things that the rest of the company needs to hear. End each meeting by agreeing on the cascading messages: what gets shared, by whom, to which teams. A decision that stays in the room changes nothing on the floor.

Review the meeting quarterly. Once a quarter, make the meeting itself the topic for fifteen minutes. Which segments earn their time? Does the scorecard still measure the right things? Are the same issues recurring? A recurring issue means the meeting keeps treating a symptom. Goldratt would say you are managing around the constraint instead of finding it.

Pitfalls to avoid

Even with the right agenda and inputs, a few habits will quietly undo the meeting. Watch for these.

Too many people in the room. The leadership meeting is for the people who own the numbers and the rocks. Beyond seven or eight attendees, reporting takes too long and honest disagreement gets harder. If someone is needed for one issue, invite them for that segment and let them leave after.

Scorecard bloat. A scorecard with thirty metrics measures everything and tells you nothing. Cap it at 10 to 15 that are important for this quarter or the year. If a number has been green for six months and nobody would act on it either way, retire it and free the slot for something you would act on. If you need visibility into operating numbers, you can snooze metrics in MonsterOps. They will only become visible again when they go out of range and need review, giving you the opportunity to create an issue if necessary. Peace of mind.

Punishing off track. The first time an owner gets grilled for declaring off track, the whole team learns to declare on track. Treat an honest off-track as the system working. The issue goes on the list, it gets solved, and the owner who raised it early did the company a favor.

Skipping the meeting when things get busy. Busy weeks are the weeks the meeting exists for. Cancel it twice in a quarter, and the team reads the message: this is optional. The commitments inside it become optional too. People should not get dentist appointments during this time…

The meeting after the meeting. If decisions get relitigated in the hallway or in a private chat afterward, the real meeting is happening without the team. The fix is inside the room: pull the disagreement out during the issue, get to a genuine commitment, and treat reopening a decided issue as a new issue for the list.

To-dos that live in the recap email. An email is where action items go to be forgotten. Nobody reopens Tuesday's recap on Friday. To-dos need to live where people work, with an owner and a date, and get read back at the start of the next meeting. MonsterOps sends daily reminders and even escalates to the leader when to-dos assigned to direct reports are not completed on time.

Score inflation. When every meeting is a 9, the score has stopped measuring anything. If the average has not moved in months while rocks keep slipping, the team is rating politeness. Reset the bar: an 8 means issues got solved and to-dos got owned, and anything less earns a lower number and one sentence on why. Be clear on what you want the team to rate.

Where this leaves you

The scorecard tells you where the operation stands without you collecting it. Rock statuses accurately reflect reality. Issues surface during the week and get solved in a structured hour. To-dos carry owners and dates, and ninety percent of them get done week over week. Everyone knows who is doing what and where it stands. Everyone is aligned on the priorities.

Alignment and accountability is hard to achive but running a good leadership meeting helps with that. The clarity you used to provide personally becomes built into the way the company runs.

You can do this with discipline and spreadsheets, and some teams do. But it's much harder than it needs to be. Or you can run it in one place. MonsterOps holds your metrics, company objectives, rocks, core values, issues, to-dos, past meeting notes, and the meeting itself, all connected with AI, so you get access to everything with just a prompt.

MonsterOps has a strong API to enter some metrics automatically, or create some issues, but it also supports MCP, which allow you to query the whole data of your organization from Claude.

Teams running frameworks like EOS, Scaling Up, 4DX, or their own playbook find it easy to use, and thanks to its flat pricing model with unlimited seats, you can bring your whole company onto it.

Either way, remember that a good meeting moves the company toward the goal. Run yours so it passes that test every week, and the hours you get back can finally go toward the work that grows the business instead of just reporting on operations.