A business can have more dashboards, better-looking reports and a growing software bill without knowing whether the investment has helped. Activity shows that work has happened. It does not, on its own, show that the business is better off.
The useful question is whether a decision, process or outcome has improved. Answering it requires a starting point, a relevant measure and an honest review of what else changed.
Return to the original problem
Begin with the reason for the project. Was reporting too slow? Were stock records unreliable? Did managers lack the information needed to compare selling costs?
Choose measures that reflect that problem. If the aim was faster reporting, measure preparation time and the corrections needed. If the aim was better replenishment, review stock availability alongside the amount held.
The number of dashboards created may help track delivery. It should not be mistaken for the result the business wanted.
Keep a starting point
Without a baseline, an improvement can become a matter of impression. Record how the process worked before the change, using information you can collect consistently.
You might track the time spent preparing a weekly report, discrepancies found during checks or how often a stock decision lacked current information.
If no reliable baseline exists, say so. Begin collecting one rather than inventing a before-and-after comparison.
Check whether the information leads to action
A report is useful when someone can interpret it and use it appropriately. Review what decisions were made, who made them and what happened afterwards.
In a retailer's replenishment process, this could mean recording which products were reordered, why the quantities were chosen and whether the stock arrived in time.
This record helps distinguish a report that people open from information that changes how the business operates.
Look for trade-offs
An improvement in one measure can hide a problem elsewhere. Faster reporting is less useful if accuracy falls. Fewer stockouts may come at the cost of holding much more stock.
Pair the main measure with a check on the potential downside. Review speed alongside accuracy, availability alongside stock held, or sales alongside the costs needed to generate them.
Hypothetical before-and-after example
Faster reporting. More corrections.
Preparation time
Minutes per report · 0–60 scale
Corrections needed
Corrections per report · 0–6 scale
Include the effort required to maintain the process. A result that depends on constant manual correction may need further work before it can scale.
Do not give the project credit for everything
A better result after a change does not prove the change caused it. Promotions, seasonality, staffing and supplier performance can affect the same measures.
Where possible, compare similar periods and record other changes that could influence the result. Separate what you observed from what you believe explains it.
You can still make a useful business judgement without claiming certainty. State what improved, what remains unclear and what you will check next.
Decide what happens next
A review should end with a choice. Continue what is useful, adjust what is underperforming and stop work that no longer serves the business.
Bring these to your next review.
- 01The original goalWhat problem were we trying to solve?
- 02The starting positionWhat reliable baseline can we compare against?
- 03The latest resultWhat changed in the measure that matters?
- 04The wider contextWhat trade-offs or other changes could affect the result?
For your next review, bring the original goal, the starting position, the latest results and the main trade-offs. Agree on the next action, its owner and the date for another check.
Success is not a finished dashboard. It is a working discipline that helps the business make decisions, learn from the results and improve the next decision.
Editorial guidance by Rawaida Kamarudin, adapted from her digital and data results draft. Examples are illustrative, not reported customer outcomes.