Most KPI frameworks in Nigerian organisations measure what is easy to count rather than what actually drives performance. The result is a dashboard that looks busy and tells leadership almost nothing useful. Here is how to identify the problem and fix it.
The activity trap
Activity metrics are seductive because they are easy to collect, easy to report, and easy to influence. Number of customer visits made. Number of proposals submitted. Number of training hours completed. Number of calls logged. These metrics are real, they change frequently, and they create the comforting appearance of management control.
The problem is that they measure inputs, not outputs. A salesperson can make thirty customer visits in a month and close nothing. A training department can log five hundred training hours and produce no measurable change in employee capability. A customer service team can resolve ninety percent of calls on first contact and still have a net promoter score that is declining — because the calls that require escalation are disproportionately the ones that matter most to customers.
Activity metrics do not tell you whether the activity is producing the outcome the business needs. They tell you only that people were busy.
Why outcome metrics are harder — and why that matters
Outcome metrics are less popular not because they are less valuable but because they are harder to collect, slower to move, and more politically uncomfortable. Revenue per customer over a twelve-month period is a better measure of sales effectiveness than calls made per week — but it takes twelve months to produce, requires clean CRM data, and will make some salespeople look significantly less productive than their call logs suggest.
This political discomfort is often the real reason organisations default to activity metrics. They are safer. They are less likely to create difficult conversations with high-activity but low-effectiveness performers. And in organisations where senior leaders are themselves measured on activity proxies — budget utilisation, headcount, meetings attended — there is limited appetite for outcome accountability lower in the hierarchy.
The cost of this comfort is strategic blindness. If your KPI framework cannot tell you whether your commercial activities are producing revenue, whether your operational activities are producing efficiency, or whether your people activities are producing capability, you are flying without instruments.
The diagnostic: five questions to test your current KPIs
Apply these five questions to each KPI in your current framework:
- Could this metric be high even if the business outcome we care about is failing? If yes, it is an activity metric masquerading as a performance measure.
- Does this metric tell us what to do differently, or only whether we did it? A useful KPI generates a management action. A metric that only confirms whether something happened is a reporting metric, not a decision metric.
- Who controls this metric? If the answer is "the person being measured," the metric is gameable and will be gamed.
- How long does it take for this metric to respond to a change in management action? Metrics that lag more than 90 days provide feedback too slowly to drive real-time management decisions.
- Is this metric causally linked to financial performance? A KPI that has no plausible causal pathway to revenue, cost, or risk is measuring something that does not matter to the business.
Building a better KPI architecture
A well-designed KPI framework has three layers:
Layer 1: Outcome KPIs (what we are trying to achieve)
These are your ultimate performance measures — the ones that determine whether the business is succeeding. Typically three to five metrics covering revenue quality (not just volume), margin, customer retention, and cash conversion. These move slowly, are difficult to influence directly, and are the measures against which everything else is justified. Examples: net revenue retention rate, gross margin by product line, customer lifetime value, cash conversion cycle.
Layer 2: Leading indicator KPIs (what predicts future outcomes)
These are the metrics that research and experience show are causally linked to your Layer 1 outcomes — and that move faster, allowing earlier course correction. Examples: pipeline conversion rate at each stage (predicts revenue), net promoter score (predicts retention), average deal size trend (predicts margin), days sales outstanding trend (predicts cash). The test for a leading indicator is that changes in it reliably precede changes in the outcome it predicts.
Layer 3: Activity KPIs (what we are doing)
These belong at the team and individual level — not at the board or senior leadership level. Calls made, proposals submitted, training hours completed: these are useful for managers calibrating workload and identifying where support is needed. They should not appear in a board pack as evidence of organisational performance. When they do, it signals a measurement framework that has inverted its own logic.
The implementation principle
When redesigning a KPI framework, the most common mistake is adding new outcome metrics on top of the existing activity metrics rather than replacing them. The result is a longer dashboard that is even less useful. The discipline is subtraction: for every outcome metric added, remove two activity metrics from the leadership reporting framework. Push those activity metrics down to operational management where they belong.
A board-level KPI pack should have five to eight metrics. A management team pack should have ten to fifteen. If yours has more, the signal is being buried in the noise.