Individual Metrics vs System Performance
Link individual KPIs to enterprise risk appetite so local metric gaming is treated as a control failure requiring audit attention.
CyberTRIZ analysis · Benchmarking contradiction MDM019 · one of 8,235 worked contradictions published by CyberTRIZ.AI
Regulations
Business Context
Individual metrics provide clear accountability. Functions, teams, facilities, and managers can be assigned targets they directly influence. However, organizations operate as interconnected systems. Improving one metric can shift cost, delay, inventory, workload, risk, or defects elsewhere. Procurement may reduce purchase price while increasing total lifecycle cost; production may maximize utilization while increasing inventory; service teams may shorten calls while reducing first-contact resolution.
Benchmarking TRIZ Resolution
Local metrics should be connected to system-level outcomes and boundary measures. Teams can retain operational indicators for control, but success should also depend on whether local improvement contributes positively to the broader value stream. Benchmarking should investigate how superior systems coordinate metrics across organizational boundaries rather than simply identifying the strongest individual functional results.
Applicable TRIZ Principles
Principle 5 – Merging connects local performance measures with system-level outcomes.
Principle 17 – Another Dimension adds cross-functional and value-stream measures to local KPI structures.
Principle 23 – Feedback reveals downstream consequences of local performance changes.
Expected Outcome
Better alignment of local and system performance
Reduced metric gaming
Fewer transferred costs and problems
Stronger enterprise outcomes
Decision Indicators
Early indicators include:
Functions meet targets while enterprise performance deteriorates.
Improvement in one area creates additional workload elsewhere.
Teams optimize measures they control while ignoring downstream effects.
Functional benchmarks identify multiple local leaders but no corresponding system advantage.
Cross-functional disputes arise because metrics reward conflicting behaviors.
These conditions indicate that accountability measures are encouraging local optimization rather than system performance.