HPA

Label Dash

Our Blog

Why Your Weekly Management Meeting Produces No Decisions

Back

15 September 2026

Your management meeting happens at the same time every week. Everyone attends. Each department gives an update. Problems are discussed. Notes are taken. Then the same problems return the following

Your management meeting happens at the same time every week.

Everyone attends. Each department gives an update. Problems are discussed. Notes are taken.

Then the same problems return the following week.

The meeting is happening, but leadership is not.

Ineffective management meetings often look perfectly respectable from the outside. They have an agenda, a set of reports and a room full of senior people.

What they lack is a reliable way to turn information into decisions.

The purpose of a weekly management meeting should not be to tell the owner what happened. It should enable the management team to identify exceptions, make decisions and take responsibility for what happens next.

If the meeting regularly produces discussion without action, the problem is not simply the agenda.

It is the standard of accountability in the room.

Signs your management meetings are ineffective

An ineffective management meeting is not always chaotic or badly organised.

In fact, some of the least productive meetings are calm, polite and well documented.

The warning signs include:

  • Each manager gives a lengthy departmental update.
  • Most information could have been shared beforehand.
  • Problems are raised without recommendations.
  • The owner answers most of the difficult questions.
  • Decisions are delayed because more information is requested.
  • Actions are assigned to several people.
  • Deadlines remain vague.
  • Previous commitments are not reviewed.
  • The same issues appear on several consecutive agendas.
  • Managers leave with less work than the owner.
  • Nobody can explain what changed because the meeting took place.

The meeting may feel busy, but it is not moving the business forward.

The meeting has become a reporting ritual

Many management meetings follow the same pattern.

Sales talks about the pipeline. Operations describes current delivery pressures. Finance reviews the numbers. People discusses recruitment.

The owner listens, asks questions and provides direction.

This structure keeps the founder informed, but it does not necessarily develop the management team.

Each person reports upwards rather than leading across the business.

A useful update answers, “What happened?”

Leadership must go further:

  • What does it mean?
  • What is likely to happen next?
  • What action have you taken?
  • What decision is required?
  • What do you recommend?

Managers should arrive ready to interpret information, not simply present it.

Why updates should happen before the meeting

Routine information should be circulated before the weekly management meeting.

This might include:

  • Performance against target
  • Forecasts
  • Completed actions
  • Current operational activity
  • Departmental updates
  • Known risks
  • Changes since the previous meeting

The information should be concise and consistent.

Managers should not need a presentation to explain whether their area is on track.

Sending updates in advance creates an important expectation: everyone arrives informed.

The meeting can then focus on matters that require collective judgement, challenge or a decision.

This does not mean every detail needs to be read beforehand. It means leaders are responsible for understanding the important information before using the company’s most expensive collective hour.

Focus on exceptions

A management meeting does not need to discuss every result.

It needs to examine the results that require attention.

An exception is something that is:

  • Behind target
  • Forecast to move behind target
  • Materially ahead of expectation
  • Creating a cross-functional problem
  • Introducing significant risk
  • Preventing an agreed action
  • Requiring a decision outside one manager’s authority

If a number is on track and no decision is required, acknowledge it and move on.

If a number is off track, the accountable manager should explain:

  1. What changed
  2. Why it changed
  3. What they have already done
  4. What they expect to happen next
  5. What decision or support they require

This keeps the meeting focused on performance rather than narration.

Stop accepting problems without recommendations

A manager who brings a problem without a recommendation is transferring responsibility to the room.

In founder-led businesses, this usually means transferring it to the owner.

The pattern is familiar: “We have a problem with delivery. What do you think we should do?”

The owner supplies the answer. The manager leaves with an instruction rather than developing their judgement.

This may solve the immediate problem, but it keeps the owner central to future decisions.

Require every agenda item to include:

  • A clear description of the issue
  • The commercial or operational impact
  • The underlying cause
  • The available options
  • The manager’s recommendation
  • The decision required

The recommendation does not have to be perfect.

It gives the team something specific to test, challenge and improve.

More importantly, it establishes that the person raising the issue remains responsible for helping resolve it.

Name the decision before starting the discussion

Management teams often spend considerable time discussing an issue without agreeing what they need to decide.

Different people answer different questions. The conversation expands. More information is introduced. No conclusion is reached.

Before discussing an agenda item, state the decision required.

For example:

  • Approve or reject the proposed pricing exception
  • Choose between recruiting and subcontracting
  • Decide whether to delay the project
  • Agree which customer segment to prioritise
  • Select the person accountable for the recovery plan
  • Decide whether to stop an underperforming service

A clearly stated decision gives the conversation a boundary.

It helps the chair determine which information is relevant and when the team has reached a conclusion.

If no decision is required, consider whether the item belongs in the meeting.

Do not confuse more information with better judgement

“We need more information” can be a legitimate conclusion.

It can also be a way to avoid making a difficult decision.

When someone asks for more information, clarify:

  • What exact information is missing?
  • How could it change the decision?
  • Who will obtain it?
  • By when?
  • Who will make the final decision?
  • What happens if the information remains unavailable?

A leadership team will rarely have perfect information.

Its job is to make sound decisions using the evidence available, understand the risk and adjust when circumstances change.

Repeatedly postponing decisions has a cost. Projects slow down, managers wait, employees receive mixed messages and problems become more expensive.

Decision speed is part of management performance.

Give every action one owner

“Sales and operations will sort it out” is not clear accountability.

Neither is “we all need to improve communication”.

An action assigned to several people often becomes an action owned by nobody.

Every commitment should have one named owner.

That person may need support from other departments, but they remain responsible for ensuring the action is completed and reported.

A clear action includes:

  • One owner
  • A defined outcome
  • A deadline
  • Any agreed support
  • The point at which progress will be reviewed

For example:

Weak action: Sales and operations to improve project handovers.

Clear action: The operations director will introduce the agreed project-handover checklist for every new contract by Friday.

The second version makes success visible.

The team can tell whether the action was completed without debating what everyone thought had been agreed.

Use deadlines that mean something

“Soon”, “next week” and “as quickly as possible” are not deadlines.

A deadline should include a specific date.

For larger actions, it should also include milestones. This prevents the team discovering on the final day that no meaningful progress has been made.

Ask:

  • What will be completed?
  • By what date?
  • What is the first visible milestone?
  • What could prevent delivery?
  • When will the team review progress?

Managers should not agree to deadlines simply to end the conversation.

They should test whether the commitment is realistic and then treat it as a leadership obligation.

Review previous commitments first

One of the fastest ways to improve a weekly management meeting is to begin by reviewing the actions agreed previously.

For each commitment, record whether it is:

  • Complete
  • On track
  • At risk
  • Overdue
  • No longer required

Do not accept “almost finished” as a permanent category.

When an action is overdue, ask:

  • What prevented completion?
  • When did you first know it would be late?
  • Why was the risk not raised earlier?
  • What is the revised commitment?
  • What needs to change to prevent repetition?

The purpose is not to embarrass people.

It is to establish that commitments made in the meeting matter after everyone leaves the room.

When overdue actions are repeatedly accepted without challenge, the team learns that deadlines are optional.

The owner must stop being the default decision-maker

The owner’s behaviour shapes the meeting.

If the founder answers every question, resolves every disagreement and assigns every action, managers will learn to wait.

This can happen even when the owner wants more initiative.

Owners often intervene because they know the business well and can reach an answer quickly. But solving every problem personally protects short-term speed at the cost of long-term capability.

Before offering an answer, the owner should ask:

  • What do you recommend?
  • What alternatives have you considered?
  • What are the commercial consequences?
  • Is this decision within your authority?
  • What will you do next?
  • What support do you need from the team?

The owner should still challenge assumptions, protect standards and make decisions reserved for their role.

But routine operational judgement must move into the management team if the business is going to scale.

Managers must lead the whole business

Management meetings become defensive when each person protects their own department.

Sales demands more delivery capacity. Operations blames poor sales handovers. Finance rejects investment without considering operational consequences.

Everyone may be correct from their own functional perspective.

Leadership requires them to make decisions for the whole company.

Managers should be expected to:

  • Understand the main commercial priorities
  • Consider the effect of decisions across departments
  • Challenge colleagues constructively
  • Support an agreed decision after the debate
  • Own their contribution to shared problems
  • Avoid protecting departmental performance at the company’s expense

A senior title gives someone responsibility for a function.

Their ability to weigh trade-offs for the entire business determines whether they are acting as a leader.

A better weekly management meeting structure

A productive weekly management meeting can follow a simple structure.

1. Review previous actions

Confirm what was completed, what is at risk and what is overdue.

Do not spend time retelling the history of every action. Focus on commitments that require attention.

2. Review performance exceptions

Look at results and forecasts that are outside the agreed range.

The accountable manager should provide the cause, response and recommendation.

3. Review significant risks

Discuss risks that could materially affect cash, customers, delivery, people or strategic priorities.

Assign an owner and response to each significant risk.

4. Make priority decisions

Select the two or three issues that most require collective judgement.

State the required decision before beginning each discussion.

5. Confirm actions

Read back each decision and commitment.

Ensure every action has one owner and a specific deadline.

6. Confirm what changed

End by asking:

  • What did we decide?
  • What action will happen next?
  • What risk did we reduce?
  • What will be different by the next meeting?

This final check prevents discussion being mistaken for progress.

What should stay out of the meeting?

Protecting the agenda requires discipline.

The following items will not normally need leadership-team time:

  • Routine updates that can be read
  • Detailed departmental troubleshooting
  • Matters one manager can decide independently
  • Issues without sufficient preparation
  • Problems with no material effect on business priorities
  • Topics included only because they are interesting
  • Repeated debates about decisions already made

Some of these conversations still need to happen.

They simply need to happen elsewhere, with the right people.

A leadership meeting becomes more valuable when attendance is not used as a reason to discuss everything.

How to measure whether meetings are improving

Do not measure meeting quality only through attendance, length or whether the agenda was completed.

Track what happens because of the meeting.

Useful measures include:

  • Percentage of actions completed by the deadline
  • Number of decisions made
  • Number of issues carried forward
  • Number of overdue commitments
  • Number of actions assigned to the owner
  • Percentage of agenda time spent on updates
  • Accuracy of management forecasts
  • Number of decisions escalated above agreed authority

Over time, effective management meetings should produce:

  • Fewer repeated issues
  • Faster decisions
  • Clearer ownership
  • More reliable commitments
  • Better forecasts
  • Less routine escalation to the founder

The meeting is improving when the management team becomes more capable outside the meeting.

A four-week management meeting reset

You do not need a complicated meeting system to create change.

Start with four disciplines.

Week one: Move updates outside the meeting

Circulate routine information in advance. Use the meeting only for exceptions, risks and decisions.

Week two: Require recommendations

Do not accept a problem on the agenda without an explanation of its impact, available options and the manager’s recommendation.

Week three: Strengthen action ownership

Give every action one owner, one outcome and one deadline.

Week four: Review the evidence

Measure completed actions, repeated issues, decisions made and tasks transferred to the owner.

After four weeks, ask one question:

Is the team taking more responsibility than it did before?

If not, the problem is deeper than meeting structure. The business needs to address leadership expectations, capability and decision authority.

The real test of a management meeting

A successful meeting does not need to feel energetic or impressive.

It needs to produce movement.

The right issues were discussed. Decisions were made. Actions were assigned. Deadlines were understood. Managers left owning more responsibility rather than passing it to the founder.

The test is not whether everyone had an opportunity to speak.

It is whether the business is clearer about what happens next.

Replace departmental updates with exceptions.

Replace open-ended discussion with decisions.

Replace shared actions with named owners.

Replace good intentions with deadlines.

That is how a weekly management meeting begins to create accountability rather than simply record activity.

Your management meeting should not send every problem back to you

HPA helps founders build leadership teams that own measurable results, make decisions and deliver against clear commitments.

If your weekly meeting produces plenty of discussion but leaves the owner with most of the actions, the agenda is not the only problem. The leadership standard underneath it needs attention.