How to run a leadership meeting that solves problems

A leadership team meeting is the recurring rhythm where the people running a business align on the plan and solve the problems blocking it — not a status update, not a calendar habit that survived because no one cancelled it.

Most aren't that. Executives now spend an average of nearly 23 hours a week in meetings, up from under 10 in the 1960s, and much of it is people reading out numbers everyone could have read alone (HBR, Stop the Meeting Madness). The cost isn't the hour. It's that the actual problems never get solved, because the meeting was spent describing them.

Here's the reframe, and the rhythm that fixes it.

A meeting is a thing you manage

A leadership meeting has one job: produce decisions and aligned action. Everything else is theatre.

In Resolute, Meetings is the fourth of the twelve questions — seven of leadership, five of management — and it sits firmly on the management side. You lead people; manage things. A meeting is a thing you manage: a mechanism for taking the plan that already exists and keeping it on track. It is not where you set the vision or rethink the strategy — that's the leadership side, and cramming it into the weekly is how both jobs get done badly. (The Leadership Curve framework lays out which questions are which.)

Get that distinction wrong and every meeting becomes a soup: a bit of status, a bit of strategy, a bit of firefighting, no decisions. Name the meeting's job and the agenda writes itself.

Why most leadership meetings fail

They report instead of decide. Someone walks the team through a deck that restates the dashboard, everyone nods, and the one genuinely hard call gets deferred to "let's take that offline." The status was the content. The decision was the casualty.

Amazon removed the failure mode at the root: no slide decks. Teams write a narratively structured six-page memo, the room reads it in silence for the first twenty minutes, then discusses — because, as Bezos put it, prose forces clarity that bullet points let you fake (Amazon, 2017 letter to shareholders). You don't have to adopt the memo. You do have to kill the read-aloud. Andy Grove made the same point decades earlier in High Output Management: the meeting is the medium through which managerial work actually happens, so a meeting that produces nothing is managerial work not done.

The rhythm: two cadences, not seven

Resist the urge to invent a meeting for every problem. Two cadences carry most businesses.

The weekly tactical. Sixty to ninety minutes, same time, same agenda, every week. Its job is the present: run the plan, surface what's off, solve the top issues. The sameness is the point — when the shape never changes, prep becomes muscle memory and the team stops relearning the meeting. (EOS calls its version the "Level 10 Meeting"; the structure below is the Resolute take.)

The quarterly. Half a day, away from the desks. Its job is the future: step back to the leadership questions — is the strategy still right, where is growth focused, what are the few things that matter next quarter. This is where you're allowed to reopen the plan. The weekly is for running it.

How to run the weekly

Work it in this order, because the order enforces the discipline:

1. Data first. Open on the few numbers that tell you whether you're winning — the scorecard. This is the Data question (management five) doing its job: report the number, move on. No commentary on green.
2. Goals check. Run the quarter's priorities — on track or off. One word each. Off-track goals become issues.
3. Issues, prioritised. Build the list, then solve the top one to three — fully — before touching the rest. A meeting that "covers" fifteen issues solves none. The ones you don't reach roll to next week. That's fine; they were lower priority by your own ranking.
4. Decisions and owners. Every solved issue ends with a decision, a single owner, and a date. No owner, no decision — just a conversation you'll repeat next week.

The move that separates a working meeting from a status meeting is one rule: report the number; debate only the exception. If it's on plan, it gets a sentence. The room's time goes to what's off.

In practice a ninety-minute weekly breaks down roughly like this: five minutes to land (good news, a quick personal and professional win — it changes the room's temperature), five on the scorecard, five on goals, then a full hour on issues, and the last ten minutes confirming the decisions, owners, and dates out loud so no one leaves with a different version in their head. The proportions are the lesson: more than two-thirds of the meeting is spent solving, not updating. If your ratio is inverted — fifty minutes of reporting, ten of problem-solving — you have found the disease.

The quarterly: where you're allowed to reopen the plan

The weekly keeps you on the road; the quarterly checks you're still on the right road. Once every ninety days the leadership team steps away from the desks for half a day and runs the leadership questions, not the management ones: is the strategy still right, has the market moved, where is growth actually focused, and what are the one, two, or three priorities for the next ninety days. Those priorities — the Focus question — become the goals the next twelve weeklies run against. Keep the two cadences clean and they reinforce each other: the quarterly sets the destination, the weekly drives toward it, and neither has to do the other's job badly.

What a great meeting will not do

Be honest about scope, because the meeting gets blamed for failures that belong upstream.

A meeting cannot fix an unclear plan, undefined roles, or numbers no one trusts. If the same issue resurfaces every week and never resolves, that's not a meeting problem — it's a Plan, Roles, or Data problem wearing a meeting's clothes (the other four management questions). More meeting discipline won't save you. Sharper answers to the upstream questions will. The cadence executes clarity. It can't manufacture it.

So the test isn't "was the meeting good?" It's blunter: could you cancel this meeting and lose nothing? If the answer is yes, you've been running a reporting ritual, and the inbox would do the job cheaper.

If you're not sure where your operating rhythm actually stands, that's worth measuring. The free Resolute business diagnostic reads your business across the twelve questions — Meetings included — names the stage of the Leadership Curve you're on, and the one thing to build next. The working canvases live in the Resolute Library; the canon goes deep on all five questions of management.