MaBrain | A Well-Run Business Review Meeting Can Solve 80% of Management Problems
Building stronger management capabilities is a key pillar for companies looking to capture the "organizational dividend" ahead. To navigate external uncertainty, you need internal certainty — and the "business review meeting" is one of the most powerful management levers for making a company's operating performance visible and explicit.
Management doesn't deliver miracles overnight — it slowly surprises you.
Improving management capabilities is critical to capturing what companies call "organizational dividends" in the future. To navigate external uncertainty, you need internal certainty, and the "business review meeting" is one of the most important levers for making your company's performance visible and concrete.
So where do you start building management fundamentals? Running effective business review meetings is the best entry point.
Author: Zhiguo Huang, former senior executive at Midea Group, founding dean of Midea Academy, and former member of the Midea Small Appliances Group Management Committee
Source: Lanmei Consulting
Business analysis matters, and the business review meeting is one of its most important rituals. Through these meetings, companies summarize and analyze operational results and existing problems — comparing year-over-year, against budget, and against benchmarks. This grounded approach pushes management teams to do the real "business math" and clearly grasp where things stand. Stick with it, and you'll steadily improve and solidify operational performance, boosting both business results and management efficiency.
How do you run a good business review meeting? It's a craft. Companies that do this well are rare. Many don't hold them at all.
01
Common Problems with Business Review Meetings
▇01 Problem 1: Not holding them at all
Some companies simply don't hold business review meetings, or do so sporadically and casually. Why?
- Some say operational data must stay confidential — only a few core people need to know
- Some say meetings are useless, everyone's busy, better to just do the work
- Some say they tried it and it didn't work, so why bother
- Some say other work meetings already cover this, no need to duplicate
- Or that executives' schedules are too hard to coordinate...
▇02 Problem 2: Holding them at irregular or poorly chosen times
First, no fixed schedule. Early month, mid-month, late month — whatever feels right. The spontaneity means attendees are often missing, or people use prior commitments to skip, leading to low-quality meetings that nobody takes seriously.
Second, holding meetings in mid-to-late month. Maybe financial statements come out late, maybe early month is busy, maybe other meetings conflict... By late month, the month's operations are basically over, and it's too early to plan next month. Monthly reviews need to both close last month and guide this month.
Third, holding them only quarterly, semi-annually, or annually. To save time, or thinking they're optional, or that monthly analysis yields nothing, or that departments resist preparing materials... analyzing operations only 1-4 times per year. In today's rapidly changing market with ever-shorter business cycles, is that enough?
▇03 Problem 3: Lacking effective operational data
Due to accounting limitations, incomplete internal metrics, missing historical data, reluctance to spell out problems, or leaders who'd rather hear determination than numbers... many review meetings devolve into social gatherings, coordination sessions, announcement sessions, or pep rallies. I've long argued that business review meetings should teach "math," not "language arts," and certainly not "activity time." I recently read that Guo Ping, Huawei's rotating chairman, says the same: management must solve math problems, not language exercises.
▇04 Problem 4: No gap analysis, no uncomfortable truths
Some meetings with data merely report financial results so people know the score, but fail to systematically expose deeper operational problems, analyze root causes, assign accountability, or establish improvement plans.
Others become celebration sessions — showcasing achievements, claiming credit, selectively highlighting wins while avoiding targets, gaps, and problems. There's no cross-functional challenge or professional diagnosis. Problems fester until they explode later at greater cost.
Huawei executives reportedly say if you spend more than three sentences on achievements, you risk getting kicked off stage. The logic: valuable contributions are already rewarded through bonuses and promotions. The business review meeting exists to analyze gaps and figure out how to keep winning.
▇05 Problem 5: Failing to find real problems, real causes, real solutions
Blaming external factors. Always citing market conditions, unexpected issues, uncontrollable forces, bosses, or sister departments — never looking inward. This doesn't solve problems; it breeds conflict.
Superficial treatment. Listing shallow, surface-level causes without digging into subjective or root causes. Or finding root causes but deeming them too complex to address, or avoiding them to not "offend" other departments. Sometimes you see dominant departments or leaders shut down others trying to raise issues, forcing quick gloss-overs.
Scratching where it doesn't itch. Problems and causes identified, some solutions proposed, but improvement actions are just meeting theater — addressing symptoms or isolated points. I've seen absurd cases where the solution is always: "We'll make up the numbers next month." No targeted, specific, actionable strategy, so next month there's nothing to verify. Come year-end, explanations proliferate, accountability becomes impossible, and the cycle repeats.
Repeating the same mistakes. Problems solved at the surface but not at the root, so they recur. Good solutions include not just corrective actions but building processes, systems, tools, and templates to thoroughly eliminate the problem and similar ones. The goal is to never repeat mistakes — using each problem to continuously correct and improve internal management standards and processes, so management keeps advancing.
▇06 Problem 6: Not holding meetings at every organizational level
Many companies hold review meetings at only one level. For organizations of any scale, this makes it hard to truly discover and solve problems or build organizational awareness. If the organization has layers, so should the meetings. You can't cram everything into one session — too messy, no focus, no priorities. Start from the smallest operating units and work upward, providing increasingly clear data for higher-level reviews. Some meetings can even be held on-site for better effect.
02
What Business Review Meetings Are For
▇01 An indispensable management ritual
Companies have many business activities, projects, and targets. While there may be various work meetings and operational sessions, business activities form an integrated whole. Departments and businesses interconnect; many initiatives, projects, and issues have company-wide implications. Business review meetings must show the full picture and enable inspection, discussion, and deployment. They're not optional, and other meetings can't substitute for them.
▇02 A measuring stick for operations and strategy
Strategic planning typically spans 3-5 years — somewhat distant. How do you verify strategic actions are being implemented? Annual operating plans are long too — how do you confirm item-by-item execution? Whether original business logic and plans remain sound, whether resource allocation is reasonable?
Business review meetings enable lean, efficient, orderly inspection and implementation. Without them, strategy and plans become empty talk, or you try to review everything annually and fail to truly examine anything.
▇03 Building a performance-oriented, data-driven culture
Business review meetings are about "hard" work, "hard" data, "getting to the bottom of" problems, real logic and verification. They cultivate a culture where teams value data, logic, and targets; where words match actions and actions produce results; where plan discipline and execution resolve are respected — building genuine operational discipline.
▇04 Improving organizational and operational effectiveness
The data in these meetings reflects real operations. Efficiency metrics especially reveal organizational truth: expense ratios, cost ratios, per-capita productivity, inventory turns, cash flow, etc. Analyzing these data and gaps drives continuous optimization, change, even accountability — then elevating solutions to process, standard, and system levels. This enables ever more ambitious targets. The cycle continuously improves organizational efficiency and capability, and thus operational effectiveness.
03
How to Run Effective Business Review Meetings
▇01 Key 1: Data-driven targets and budgets
Business review meetings aren't post-hoc announcements, self-directed monologues, or free-for-alls. They must operate on tracks: budgets, meaning preset operating targets and associated data.
Budgets derive from strategic vision, annual operating plans, and actual business conditions. They provide the framework for review meetings. Without data-driven target decomposition and budget management, no matter how well-organized or earnest the meeting, it won't succeed.
Generally, business analysis compares against history, budget, and industry benchmarks. Without benchmarks, it's just talking to yourself — insufficiently deep or systematic.
▇02 Key 2: Clear themes based on operational priorities or phase-specific focus
Each year, each phase, and each business unit in a multi-unit group may have different priorities. Review meeting themes should reflect this. What matters for a startup unit? A mature one? A unit with weak revenue? One with poor receivables and margins? And so on.
Regardless, finding gaps, finding problems, and winning is the eternal purpose. Agendas should center on three core themes:
(1) Did we win the last battle (big or small, whole or partial)? If yes, can we extract key moves and turn them into organizational capability? (2) If we lost, why? If we fought again, how would we win? (3) What's the target and action plan for the next battle?
Next month, analyze whether these moves worked, whether they landed, continuously adjusting and optimizing.
▇03 Key 3: Clear meeting discipline
First, make it monthly. Quarterly or semi-annual is too long; weekly or daily too short. Natural months align with financial reporting and data cycles. So commit to monthly — 12 review meetings per year (some combined with quarterly, semi-annual, or annual meetings). This turns one "long operating cycle" into 12 "short cycles." Given already-shortening external cycles, I call this "fighting short cycles with short cycles."
Second, fix the monthly date. Hold meetings early in the month, ideally at a fixed time that builds "temporal memory." Everyone knows to reserve this slot. This also allows time for bottom-up meetings at each level, avoiding chaos. Finance must deliver data on schedule.
Third, limit reporting time. Content follows budget, so deviations get more airtime; on-budget items pass quickly. One reporting unit generally needs only about 1.5 hours. Don't drag on; not everything belongs here — some topics warrant separate specialized meetings. At Midea, with 200+ billion RMB scale and 10+ operating units, Fang Hongbo says review meetings typically wrap in 1-2 days.
Fourth, organize effectively. Given extensive financial data, finance should lead — or operations/administration can organize. Finance reports data; business heads supplement with operational context; attendees analyze and discuss; superiors or functional departments ask professional questions; relevant departments or personnel supplement as needed. Use PPT format, minimal text, maximum charts, immediately comprehensible. Meetings should cascade from smallest units (product lines, regions, subsidiaries) to medium units (product companies, regions), to divisions, to headquarters.
Key 4: Follow-up and meeting management
First, pre-meeting management. Good meetings don't surprise attendees. Materials should be submitted to superiors in advance. Finance, HR, operations can pre-study, clarifying data, exposing problems, or preparing support so the live meeting produces immediate solutions. This demonstrates functional capability.
Second, effective in-meeting management. Many topics may arise. For items requiring separate sessions, or affecting few people, table them promptly to avoid derailing the meeting. Especially the top leader must respect meeting discipline and not go off-script. As noted, meetings should have strict time limits. But for discussable, major operational issues — don't let them go. They need resolution.
Third, quantitative analysis. Gap analysis needs clear data. Budgeted gross margin was 30%, actual was 28% — why the two-point gap? Raw material prices? Manufacturing overhead? Delivery delays? New product quality losses? Planned sales were 130 million, actual was 150 million — why the miss, and how to avoid it? Why did cash flow decrease versus plan — inventory, receivables, other causes? Only continuous quantitative analysis drives real problem-solving and strengthens data thinking. Without data, gaps can't be thoroughly analyzed, operational capability won't improve, and the next battle relies on luck and inertia — unlikely to go better. Only data enables layered, categorized understanding of gaps and problems.
Fourth, post-meeting follow-up. Minutes should clearly record proceedings, especially next-phase action items with deadlines, responsible departments, and owners. Consider a priority action table as attachment. Items not immediately actionable (minutes should issue within 1-2 days) should be noted, with prompt scheduling of follow-up sessions or required departmental proposals.
Fifth, meeting atmosphere and culture. These meetings matter deeply for thorough work discussion. Don't create excessive tension, direct accountability, or suppress responsible parties — this kills effective review. Except in extreme cases, separate accountability from analysis. In the meeting, face gaps and problems honestly, think from the whole-company perspective, to find causes and improvements. Operational problems usually involve multiple departments and factors; responsibility is rarely immediately clear. Overemphasizing accountability turns meetings into "struggle sessions," defeating their purpose. Where accountability is truly warranted, handle it post-meeting through professional audit and notification.
In today's rapidly shifting, intensely competitive market, not holding business review meetings is incomprehensible. Continuously improving their quality is a low-cost, high-return management practice for better operations.