Article Contents:
Business review meetings are common in most organisations.
Weekly, monthly, sales, operations, and functional reviews are conducted regularly. Yet, I have seen many organisations where people spend considerable time in these meetings without seeing a corresponding improvement in execution.
The problem is not necessarily the number of meetings.
It is what happens inside those meetings and, more importantly, what happens after them.
In some organisations, review meetings become a forum for sharing information. In others, they become lengthy problem-solving discussions. Sometimes, the business head dominates the discussion,n and the rest of the team mostly listens.
The meeting gets over. Everyone goes back to work. But after a few weeks, the same issues come up again.
This is something I have observed repeatedly while working with SMEs.
A business review meeting should not become another activity in the management calendar. It should help the organisation understand where performance is slipping, decide what needs to be done and ensure that agreed actions actually happen.
When this does not happen, even well-structured review meetings can consume management time without improving execution.
Why do business review meetings become ineffective?
One common problem I have noticed is that review meetings easily lose their purpose.
A meeting may start with a clear agenda. But when one issue comes up, the discussion moves deeper and deeper into that particular problem. Other important areas do not get adequate attention.
At one of the organisations I worked with, I participated in a KPI review meeting. When we started discussing one of the KPIs, the conversation gradually shifted into a detailed discussion of engineering and design.
The topic itself was important.
But was the KPI review meeting the right forum to solve that engineering problem in detail?
Probably not.
The relevant people could have taken that issue separately and come back with the required action. Instead, valuable review time was consumed by one operational issue.
I have seen this happen in different forms in many organisations.
A sales review gets stuck on one customer issue. An operations review turns into a detailed technical discussion. A management review becomes a conversation about the most urgent problem that day.
Gradually, the review loses its larger purpose.
The issue is not that these problems should not be discussed. They certainly should be.
The question is where, when and with whom they should be discussed.
A good business review should help the management team stay focused on overall performance, significant deviations, decisions required and actions that need follow-up.
Detailed problem solving can happen outside the review with the relevant people.
This distinction looks simple, but it can make a significant difference to the effectiveness of business review meetings.
What is the real purpose of a business review meeting?
Before conducting any review meeting, I believe there should be clarity on one basic question:
What do we want to achieve through this review?
It may look obvious, but this clarity is often missing.
A business review meeting is not merely a forum for different functional heads to present what happened during the previous week or month. Sharing information is necessary, but that alone does not improve performance.
The review should help us understand:
Are we performing as planned?
Where are the significant gaps?
What is causing those gaps?
What decisions or support are required?
What actions need to be taken and by whom?
In my consulting engagements, I have always found it useful to define the expected outcome of the review before getting into the details.
For example, if delivery performance is below the expected level, knowing that delivery is poor is not enough. The review should help the team understand what is preventing delivery, what needs management attention and what actions are required to improve it.
Similarly, if sales are below plan, repeatedly presenting the sales number does not change anything. The discussion needs to move towards the pipeline, conversion, customer opportunities, constraints and specific actions required.
This is where I see an important difference between reviewing information and reviewing performance.
Information tells us what happened.
A good review helps us decide what to do about it.
That is why I see business review meetings as an important part of the execution process. The meeting should provide clarity, lead to decisions, and translate those decisions into actions that can be followed through on.
Otherwise, we may conduct reviews regularly without necessarily improving the business.
Why should founders avoid managing everything through one-to-one follow-ups?
In some SMEs, I have seen founders prefer to discuss issues individually with their functional heads rather than through a structured business review.
There is a practical reason for this.
The founder knows the business well. He may already know many of the issues and may feel that discussing them directly with the concerned person is faster. Sometimes, it is.
But as the business grows, this approach begins to create limitations.
When most issues are discussed one-to-one, other functional heads may not understand what is happening in the business or how one function is affecting another.
For example, a delivery problem may not be solely an operations problem. It could be related to material availability, planning, quality, capacity, or even a commitment made by the sales team.
If each issue is discussed separately, people tend to view the problem primarily from their own functional perspective.
A structured business review brings the relevant people together. They can see the same performance gaps, understand the interdependencies and agree on what each function needs to do.
There is another concern.
When the founder continuously follows up with people individually, execution can slowly become dependent on the founder’s follow-up.
People start responding because the founder is asking, rather than because a management system makes commitments and accountability visible.
This may work when the organisation is small. But it becomes increasingly difficult as the business grows.
The founder cannot be the point of contact for every issue and every function.
A good review system should gradually enable the management team to discuss business performance together, take ownership of their actions, and resolve more issues without waiting for the founder to drive every follow-up personally.
How can review meetings stay focused on what really matters?
One of the challenges in any business review meeting is maintaining focus.
As I mentioned earlier, I have experienced KPI review meetings where one performance issue gradually took the discussion deep into engineering or design details. The discussion itself may be useful, but if we allow every issue to be examined at that level of detail, the review will never achieve its purpose.
This is why I prefer to have a clear agenda and a defined time for the review.
If we have ten important areas to review, we need to ensure that all ten get the required management attention. One issue should not consume most of the meeting simply because it has generated an interesting or intense discussion.
When a problem requires deeper analysis, we can identify it during the review, decide who needs to work on it and take it up separately with the relevant people.
I also believe the person conducting the meeting has an important role here.
He or she should be able to recognise when a discussion is helping the team make a decision and when it is moving into unnecessary detail.
This does not mean cutting off important discussions to complete the agenda.
The purpose is to maintain the right level of discussion.
A business review should primarily focus on performance gaps, significant concerns, required decisions, and required actions. Detailed technical problem solving can happen in a separate forum.
This simple discipline helps the team use its collective management time much more effectively.
When the purpose, agenda and expected outcome are clear, the review becomes less about discussing everything and more about focusing on what really needs management attention.
How should performance gaps be converted into actions?
One of the biggest gaps I have observed in review meetings is a lack of discussion. There is usually plenty of discussion.
The gap is in converting the discussion into action.
A performance issue is discussed, different views are shared, and somebody may even say, “We will take care of it.”
But when the same issue comes up in the next review, we realise that the expected action has either not happened or has not moved sufficiently.
This is why I have always preferred maintaining a Master Action Plan as part of the review process.
Whenever an important action emerges from the review, it should be captured clearly. What needs to be done? Who will take responsibility? By when should it be completed?
More importantly, the action should come back for review until it is closed.
I have found this simple practice useful because management discussions otherwise tend to get lost between meetings. People may genuinely intend to act, but day-to-day priorities take over.
The Master Action Plan creates continuity from one review to the next.
At the beginning of a review, we can look at the important actions committed in the previous meeting. What has been completed? What is delayed? Where is support required?
This also changes the nature of accountability.
Instead of the founder or business head remembering every commitment and following up with people individually, the review process itself provides visibility into what was agreed.
For me, the real value of a review meeting is not how many issues we discuss.
It is how many important issues are converted into clear actions and how consistently those actions are taken to closure.
That is where review meetings begin to strengthen execution.
Should the leader provide all the answers in a review meeting?
Another pattern I have observed in review meetings is that the business head or senior leader tends to speak more than everyone else.
This is understandable.
The leader may have more experience, may know the business better and may already have a possible solution in mind. So, when an issue is raised, there is a natural tendency to start giving directions.
But when this happens repeatedly, something else can happen.
The team slowly gets used to looking towards the leader for answers.
I have always believed that the person leading a review meeting should also serve as a facilitator.
Instead of immediately giving the solution, ask questions.
What do you think is causing this gap?
What options do we have?
What support do you need?
What do you propose we do next?
These questions encourage people to think and participate rather than simply wait for instructions.
One practice I particularly value is allowing others to speak before the leader offers their view.
When the leader expresses a strong opinion first, particularly in a senior position, the rest of the discussion can easily move in the same direction. People may hesitate to offer a different perspective.
By listening first and speaking later, the leader has an opportunity to understand how the team thinks.
This does not mean that the leader should remain neutral on every issue or avoid making decisions.
There will certainly be situations where the leader needs to provide direction or make the final call.
But a review meeting should also help develop the team’s ability to analyse problems, propose solutions and take responsibility.
Over time, this can make an important difference.
The review becomes not only a mechanism for improving business performance but also a forum for developing stronger ownership and decision-making capability within the team.
Why should the right people participate in business reviews?
Another important aspect of an effective review is having the right people participate.
I have seen situations where a performance issue is discussed without the person who actually owns the process being part of the discussion. The team discusses possible reasons, makes assumptions and sometimes even decides actions for somebody who is not present.
This does not help much.
At the same time, inviting too many people to every review can also make the meeting ineffective.
The question is not how many people should attend.
The question is who needs to be there for the review to result in better understanding, decisions and actions.
This becomes particularly important when issues are cross-functional.
For example, if delivery performance is poor, operations may have one perspective. Planning may see another constraint. Purchase may have a material issue and sales may have committed a delivery date based on a different understanding.
When the relevant people look at the same performance issue together, the discussion becomes more meaningful.
I have also found that this creates better understanding between functions.
Instead of looking at an issue only from their own functional point of view, people begin to understand how their decisions and actions affect other parts of the business.
That is one of the important benefits of a good business review.
It should not become a meeting where each functional head reports to the founder.
It should help the management team review the business together and take collective responsibility for improving performance.
How can a regular review rhythm strengthen execution discipline?
Conducting a single good review meeting will not change how an organisation executes.
What makes the difference is consistency.
I have seen organisations start review meetings with great enthusiasm. For the first few weeks, the agenda is followed, actions are captured, and people come prepared.
Then, gradually, the discipline starts to slip.
A review gets postponed because something urgent comes up. The next one gets cancelled because the business head is travelling. Actions from the previous meeting are not reviewed, and after some time, the meeting itself becomes irregular.
When this happens, the organisation loses the rhythm.
I believe important business reviews should occur at a defined frequency, preferably at a fixed time.
People should know when the review will happen, which performance measures will be reviewed, and what preparation is expected of them.
More importantly, every review should have continuity with the previous one.
If we agreed on certain actions last week, those actions should come back for review. If a performance gap was identified, we should know whether it is improving. If a decision was taken, we should see whether it has been implemented.
This creates a simple but powerful discipline.
Review. Decide. Act. Follow up.
Over time, people know that commitments made during the review will not disappear after the meeting.
This is when the review starts to become part of the organisation’s execution system rather than another meeting on the calendar.
For me, consistency in the review process is as important as the quality of the meeting itself.
A good review rhythm keeps important priorities visible and helps the team stay focused on taking actions to closure.
How do effective business reviews reduce founder dependency?
In many SMEs, the founder becomes the centre of execution.
When something is delayed, the founder follows up.
When two functions are not aligned, the founder brings them together.
When an important decision is pending, people wait for the founder.
This may work when the business is relatively small. But as the organisation grows, the founder cannot continue to be the person connecting every issue, following up on every action and resolving every cross-functional problem.
This is where I see a well-established business review process making a larger difference.
When performance measures are clearly reviewed, gaps become visible to the team.
When actions have owners and timelines, the founder does not have to remember every commitment personally.
When functional heads discuss issues together, many cross-functional problems can be resolved without escalating everything to the founder.
And when leaders ask questions rather than provide all the answers, people gradually develop the confidence to think, decide, and take ownership.
This transition does not happen because we conduct a few good meetings.
It happens when the review process becomes a consistent way of managing the business.
Over time, the founder’s role can also begin to change.
Instead of continuously chasing actions and solving day-to-day issues, the founder can spend more time focusing on business performance, key risks, future priorities, and decisions that genuinely require their attention.
That, in my view, is one of the real measures of an effective business review system.
The review should not make the organisation more dependent on the founder. It should help build a management team that can execute with greater clarity and ownership.
This is why I see an effective business review system as an important part of building Leadership & Organisation Capability. As the business grows, the founder cannot personally drive every action. The organisation needs a management rhythm through which performance is reviewed, decisions are made, accountability is established, and actions are consistently taken to closure.