Translate KPI differences and root causes into management action.
Performance reports do not create improvement by themselves. They show differences between actual results and objectives, but management still has to identify the cause, decide whether the difference is controllable, and choose an action that addresses the underlying problem.
In Core 2, this topic often appears after a dashboard, variance table, scorecard, budget comparison, or operating summary. The expected response is not simply “performance was worse than target.” The response should explain why performance changed, what management can influence, and what action is proportionate to the evidence.
Performance action questions test judgement. The case may show a revenue shortfall, cost overrun, margin decline, quality problem, delay, employee turnover, customer complaint trend, or service backlog. The strongest answer connects the KPI to the business driver and then recommends a response.
| Task | What the response should do |
|---|---|
| Identify the performance gap | Compare actual results with target, budget, prior period, benchmark, or stated objective. |
| Explain the likely cause | Use operating facts, not speculation. |
| Assess controllability | Decide whether management can influence the cause. |
| Rank significance | Focus on differences that matter for strategy, cash, service, risk, or compliance. |
| Recommend action | Address the cause rather than the visible symptom. |
| Monitor follow-up | Identify the KPI or evidence that will show whether the action worked. |
A KPI is a signal. It is not automatically the cause of the problem. A decline in gross margin may result from price discounts, input cost increases, product mix, waste, rework, or theft. A longer cycle time may result from staffing shortages, bottleneck equipment, poor scheduling, unclear approvals, or supplier delays.
| KPI result | Possible root causes | Action depends on |
|---|---|---|
| Revenue below target | Lower volume, lower price, lost customers, weak sales mix, delayed launch. | Whether the issue is demand, pricing, capacity, or execution. |
| Gross margin decline | Input cost increases, discounting, waste, unfavourable mix, quality problems. | Whether management can change price, supplier, process, or product mix. |
| Labour efficiency worsens | Training gaps, overtime, poor scheduling, machine downtime, rework. | Whether the cause is controllable by operations. |
| Customer complaints rise | Defects, delays, service inconsistency, unclear communication. | Which process step creates the complaint. |
| Inventory turnover falls | Excess purchasing, weak demand, obsolete stock, poor forecasting. | Whether inventory can be sold, returned, written down, or prevented in future. |
| Employee turnover increases | Compensation, workload, culture, management, hiring mismatch. | Whether retention actions address the actual driver. |
The case facts should support the cause. If the evidence is incomplete, recommend follow-up analysis before a major corrective action.
Management action should be assigned to the level that can influence the cause. Holding a store manager responsible for a national supplier shortage may be unfair. Holding a production manager responsible for poor scheduling, avoidable overtime, or rework may be appropriate if those factors are within local control.
| Cause type | Typical response |
|---|---|
| Controllable operating issue | Change process, staffing, training, scheduling, quality controls, or supervision. |
| External market issue | Adjust forecasts, pricing, product mix, procurement, or risk mitigation. |
| Target-setting issue | Revise targets if they were unrealistic or based on outdated assumptions. |
| Data-quality issue | Improve system capture, definitions, reconciliations, or KPI design before acting. |
| Strategy mismatch | Reconsider objectives, resource allocation, customer segment, or service model. |
A good response avoids blame language. It explains who should act, what should change, and how management should measure the result.
Sometimes the best immediate recommendation is not a large corrective action. If the case facts do not prove the cause, management may need targeted follow-up analysis.
Examples include:
| Performance issue | Useful follow-up |
|---|---|
| Margin decline | Separate price, volume, cost, and mix effects. |
| Overtime increase | Analyse overtime by department, shift, job type, and cause code. |
| Defect increase | Trace defects by supplier, production line, employee training group, and product. |
| Sales decline | Analyse customer segment, channel, geography, price change, and competitor activity. |
| Budget overrun | Separate volume-driven cost from rate, efficiency, and scope changes. |
| Service backlog | Measure arrivals, completions, staffing, rework, and bottleneck steps. |
Follow-up analysis should be specific. “Investigate further” is weak unless the answer says what to investigate and why it matters.
Corrective action should match the root cause and the importance of the difference. A small one-time variance may need monitoring. A recurring variance tied to strategy may need process redesign or governance attention.
| Root cause | Stronger action | Weaker action |
|---|---|---|
| Training gaps cause rework. | Retrain staff, update procedures, and monitor first-pass quality. | Tell staff to work faster. |
| Supplier defects drive warranty claims. | Review supplier quality, contract terms, inspections, and alternate suppliers. | Increase sales targets to offset warranty cost. |
| Demand is below forecast. | Reassess pricing, marketing, product-market fit, and inventory purchases. | Produce more units to absorb fixed overhead. |
| KPI target is unrealistic. | Reset target using current capacity and strategy. | Penalize managers for missing an impossible target. |
| Data definitions are inconsistent. | Standardize KPI definitions and reporting controls. | Make decisions from unreliable dashboard trends. |
The action should also reflect cost-benefit. Expensive system changes may be justified for recurring, material, and strategic problems. They may be excessive for a small temporary difference.
Core 2 written responses should communicate to management, not just calculate for the marker. The language should be clear, decision-oriented, and appropriately cautious.
Better performance commentary has four parts:
For example: “Gross margin fell despite higher sales volume because discounting and input cost increases offset the volume benefit. This weakens the expansion plan because additional sales are not producing expected contribution. Management should separate price, mix, and cost effects by product line before committing to further promotional discounts.”
This style is stronger than writing only: “Gross margin is unfavourable and management should monitor it.”
Use this structure when a case gives KPI differences:
This framework keeps the response from becoming a list of unfavourable variances. It shows management what to do next.
| Pitfall | Correction |
|---|---|
| Treating the KPI as the root cause. | Use operating facts to explain why the KPI changed. |
| Recommending action without controllability analysis. | Assign action to the manager or process that can influence the cause. |
| Overreacting to a small or one-time difference. | Consider materiality, trend, and strategic importance. |
| Saying “investigate” without focus. | State the specific analysis needed and how it will inform the decision. |
| Ignoring non-financial effects. | Include quality, customer, employee, compliance, and service outcomes where relevant. |