Business Reviews That Lead to Decisions
By Akkul Dhand · Published 26 October 2026
Replace the monthly reporting recital with a short review that changes what happens next.
Who this is for: Founders and leadership teams whose meetings produce discussion but little decision or follow-through.
A business review should explain what changed, why it matters and what decision is needed. The dashboard is preparation, not the meeting.
1. Diagnose before acting
Answer each question with a concrete example or piece of evidence. Mark unknowns openly. This is a discussion aid, not a validated scoring instrument.
- Do attendees receive consistent numbers before the review?
- Does the agenda distinguish information from a decision request?
- Are actual results compared with a meaningful plan and prior period?
- Are earlier actions checked for completion and effect?
- Can someone absent from the meeting understand its decisions afterwards?
2. Put the method to work
1. Agree the management view
Select a small set of measures covering commercial performance, margin, cash, delivery, quality and people risks as relevant. Define source, owner, period and calculation. Reconcile material discrepancies before debating performance.
2. Ask for explanation in advance
Use a one-page pre-read: result versus plan, important changes, likely causes, risks, proposed actions and decisions needed. State uncertainty. The person requesting a decision should bring options and a recommendation, including the consequences of doing nothing.
3. Use a decision-focused agenda
An example 60-minute review: 10 minutes on previous actions, 10 on headline changes, 25 on the two most material issues, 10 on decisions and 5 on commitments. Adjust to the business; do not force every department to present equal numbers of slides.
4. Make choices and record limits
For each decision, record the owner, rationale, resources, deadline and conditions that would trigger reconsideration. Where the group cannot decide, name the person responsible for obtaining the missing evidence and set a decision date.
5. Check the effect next time
Review whether actions completed and whether they improved the intended result. Preserve the original baseline. Stop initiatives that fail their test rather than allowing every decision to become permanent by default.
3. A worked example
Illustrative example: revenue exceeds plan but cash collection falls behind. Instead of celebrating revenue alone, the review separates overdue invoices by age and cause. Leaders choose a specific collection and billing fix, assign owners and monitor cash and customer disputes. Additional sales activity does not become the automatic answer to a cash problem.
4. Working sheet
The first row shows how to fill this in. Use the blank rows for your own business. Add evidence links and review dates to your working copy.
| Issue and evidence | Decision / options | Decision owner | Action and date | Result to review |
|---|---|---|---|---|
| Revenue ahead; overdue cash rising | Fix invoice disputes before extending credit | Finance lead with sales input | Resolve prioritised disputes by agreed date | Collections, ageing and customer impact |
5. Action plan
- Before the first review: define measures and circulate the pre-read.
- At the meeting: concentrate on the most consequential exceptions.
- Within one working day: circulate decisions and accepted actions.
- At the next review: check outcomes and amend or stop weak actions.
6. Check whether it worked
- Material decisions made versus deferred, with reasons.
- Actions completed with evidence by the original due date.
- Change in the business measure each decision was intended to improve.
Do not confuse a positive revenue variance with business health. Avoid selective periods, changing definitions or slide packs that hide deterioration behind activity numbers.
What you should leave with: One management view, a decision log and a short action register linked to business outcomes.