Terence Monaghan argues that meetings should form a management system, not a weekly reporting circuit that sends every decision back to the CEO. He lays out seven meetings, three common mistakes, and seven actions for building a business that runs at the right level.
Each week, I share practical ways to improve profit, control, time and enjoyment in your business, without making every decision depend on you.
This week: seven meetings that create a proper management rhythm, three mistakes that make meetings ineffective, and seven actions to take immediately.
I see the same diary in growing businesses all the time.
Monday morning: sales meeting.
Monday afternoon: operations meeting.
Tuesday: project review.
Wednesday: finance meeting.
Thursday: management catch-up.
Friday: another catch-up to discuss everything that did not get resolved in the first catch-up.
At first glance, it looks disciplined.
There is only one issue.
The same problems are still sitting on the table the following week.
The sales forecast is still unclear. The late project is still late. The customer complaint is still open. The cash concern is still “being watched”. The manager who needed a decision last Tuesday still needs it this Tuesday.
And somehow, every conversation still needs the CEO.
The problem is not that the business has too few meetings.
It is that the meetings do not form a management system.
They are a collection of conversations. Different agendas. Different numbers. Different expectations. Plenty of updates. Very few decisions.
Over time, the company develops a simple operating rhythm:
When in doubt, invite the boss.
The CEO thinks there is a leadership team.
What they actually have is a weekly reporting circuit.
And every road still leads to the same desk.
The turning point comes when you stop asking:
“What meetings should I attend?”
And start asking:
“What meetings should run properly without me?”
That question changes the calendar.
More importantly, it changes the business.
A meeting attended once is a conversation. A meeting repeated every week is a management process. A meeting that still cannot work without the CEO is a dependency.
Meetings feel like control.
People arrive. Numbers are shown. Problems are discussed. Actions are mentioned. Minutes are circulated. The diary looks busy and the management team feels active.
Often, very little has changed.
Information has moved around the room. Authority has not moved. Ownership has not moved. Capability has not moved. The decision has simply moved upwards.
The meeting ends. Everyone returns to work. The CEO leaves with six more actions than they had when they walked in.
That is not delegation.
It is centralisation with a calendar invitation.
A good meeting should do at least one of four things: expose a problem early, make a decision, coordinate action across teams or build management capability.
If it does none of those things, it is probably just a habit.
The purpose of a management rhythm is not to fill the diary.
It is to make sure the right conversations happen at the right level, often enough to keep the business moving, and without turning the CEO into the answer to every question.
This meeting manages today.
Keep it short. Ten or fifteen minutes. Run it as close to the work as possible.
The local manager should lead it. Not the CEO. Not somebody from head office who happens to like meetings.
Ask:
That is enough.
No slides. No speeches. No detailed review of last quarter. No attempt to solve every problem in the room.
If an issue needs a deeper conversation, assign the right people and take it outside the huddle.
The objective is visibility and immediate action.
A business that waits until Friday to discuss a problem that appeared on Tuesday is already too slow.
Every function should be capable of managing itself.
Sales should run sales. Operations should run operations. Finance should run finance. HR should run people. Supply chain should run supply chain.
The functional manager should know what was committed to, what was completed, what missed, what the numbers are saying and what the team is doing about any gap.
The meeting should answer four questions.
| Question | What it tests |
|---|---|
| What did we commit to? | Whether expectations were clear. |
| What actually happened? | Whether performance is visible. |
| What is off plan? | Whether the manager understands the gap. |
| What are we doing about it? | Whether the function can act without passing every issue upwards. |
Anything that genuinely needs to go higher should be clear.
Not a vague problem. Not a long story. Not, “What do you think we should do?”
Bring the facts. Explain the options. Make a recommendation.
A manager who simply arrives with a list of problems for the CEO is not really managing.
They are reporting.
This is the central meeting in the weekly rhythm.
Same day. Same structure. Same core numbers. Every week.
Do not go around the table asking everyone for an update. That usually produces plenty of talking and not enough management.
Focus on where the business is off plan.
Sales. Margin. Cash. Customers. People. Operations. Projects. Risk.
Whatever matters in your business.
The questions are:
The leadership meeting should not repeat the functional meetings. If sales can solve a sales issue, it should be solved in sales. If operations can solve an operational issue, it should be solved in operations.
Bring something to the leadership team because it affects the whole business, requires support from another function or needs a decision that sits above the manager’s authority.
And if an action leaves the room, give it one owner and one date.
Not “Operations”. Not “Finance”. Not “the leadership team”.
One person.
Otherwise, it is not an action. It is a polite intention.
This meeting keeps the business ahead of cash.
It should be simple, factual and disciplined.
Review current cash, the 13-week cashflow, debtors, expected receipts, supplier commitments, payroll, tax, capital expenditure and any tight weeks ahead.
Do not turn it into a broad finance presentation.
The meeting has one job:
“Do we know what cash is coming in, what is going out and where pressure could appear before the next review?”
In a healthy business, this meeting will often feel fairly boring.
Good.
That is exactly what you want.
Cash surprises are rarely improved by being surprising.
The wrong time to start paying attention to cash is when you suddenly do not have enough of it.
The weekly leadership meeting runs the business.
The one-to-one builds the manager.
Do not turn it into another status update. The CEO already has other places to get the numbers.
Use the time to understand how the manager is thinking.
Ask:
And every so often, ask one more question:
“What am I doing that is making your job harder?”
That can be uncomfortable.
Which is probably why it is worth asking.
A good one-to-one should leave the manager clearer, stronger and more capable of making the next decision without you.
If every one-to-one ends with the CEO taking over the manager’s problems, the meeting is developing the wrong person.
Weekly meetings keep things moving.
The monthly review creates enough distance to see the pattern.
Are sales improving or simply fluctuating? Is margin genuinely stronger? Is working capital under control? Are customer problems reducing? Are major projects moving? Are management actions changing performance?
Review revenue, margin, EBITDA, cash, working capital, budget versus actual, customer performance, operational performance, people, major projects and risk.
But do not let the meeting become a reporting marathon.
Reading numbers aloud is not management.
The real questions are:
Three priorities are useful.
Twenty-three priorities are a list of everything the business is worried about.
If everything becomes a priority, nothing is a priority.
This is where the leadership team steps out of the week-to-week noise.
The purpose is not to admire a large presentation.
It is to test whether the business is still heading in the right direction.
Ask:
I would rather leave this meeting with one useful page than a seventy-page deck.
Three priorities. Clear owners. Measures. Milestones.
Something people can actually execute.
Strategy is not what the leadership team discussed for a day.
It is what the business does differently on Monday.
Businesses are very good at accumulating meetings.
A new problem appears. A weekly call is created. The immediate issue eventually disappears. The meeting remains.
Six months later, eight people are still attending and nobody is quite sure why.
Recurring meetings are management processes. Each one should have a clear purpose, owner, inputs and decisions.
If the purpose no longer exists, neither should the meeting.
If something can be read beforehand, read it beforehand.
Use the meeting to question, debate, decide and act.
A forty-slide presentation followed by four minutes of discussion is not a management meeting.
It is a document-reading service.
Send the information in advance. Make it clear what people should notice and what decisions are required. Then use the room for the work that actually needs the room.
If last week’s actions never come back, the meeting has no memory.
Problem discussed. Action assigned. Minutes sent. Everyone feels organised.
The following week, a new agenda begins and the old action quietly disappears.
That is how the same issues return wearing a different date.
Begin each meeting with the previous actions. Confirm what was completed, what missed and what happens next.
Accountability should not reset when the meeting ends.
Start with the calendar. Include daily, weekly, monthly and quarterly meetings. If the same people are discussing the same subjects in several places, make that visible.
Use one sentence.
If you cannot explain the purpose clearly, the meeting probably does not have one.
One person owns the agenda, the information, the quality of the conversation and the follow-up.
Not “management”. Not “the team”.
One name.
Do not invite people because they might have an opinion.
Invite them because they own information, contribute to a decision or are responsible for the action that follows.
Send standard numbers and updates in advance. Agree the few measures that everyone will use. Stop rebuilding a new presentation every week.
Use the meeting for exceptions, decisions and action.
Record it before the meeting moves on.
At the next meeting, start there.
An action without an owner and a date is simply a sentence everybody agreed with.
This is the most important test.
If the CEO disappeared for two weeks, which meetings would continue properly? Which decisions would still be made? Which managers would take ownership?
Every meeting that collapses without the CEO is showing you where capability, authority or confidence is missing.
That is not just a calendar problem.
It is a management-development plan.
Every growing business needs meetings.
Customers change. Priorities move. Problems appear. Teams need to coordinate. Decisions have to be made.
The goal is not to build a company with no meetings.
The goal is to build a company in which meetings create management rather than dependency.
A company where:
The real danger is not having a busy diary.
The real danger is using a busy diary to hide the fact that every important issue still travels upwards.
So this week, do not ask:
“How many meetings do we have?”
Ask:
“Is the business being managed at the right level?”
That is how conversations become decisions.
That is how managers become capable.
And that is how you build a business that can grow without every problem, approval and decision eventually landing back on you.
Terence Monaghan | terence.ie
Put This Into Practice
The CEO Scorecard gives you a clear view of the constraints affecting profit, cash, the team and your time.
Continue Reading
Back to all articles