Qué es realmente un KPI
The term "KPI" is applied to almost any quantified performance measure in organisational practice. In some contexts it refers to financial ratios, in others to operational throughput metrics, in others to strategic objectives with numerical targets attached. This ambiguity is not a communication problem. It is a structural symptom: without a stack, every metric is implicitly the same type of thing.
In the MetriqOne architecture, what most organisations call a KPI is a Performance Indicator – a PI. The PI sits three layers below the MCA, beneath the CSI and the Module. It measures observable activity at the operational layer. It generates evidence for its Module. It does not make strategic claims. Calling it "key" does not give it strategic architecture.
A list of KPIs without stack logic is a collection of data points. It is not a measurement system. The MCA establishes the context – who the organisation is, what conditions it faces, what it is working toward. The rollout proceeds from that context. Without the stack, the indicator has no architectural home.
The Stack Architecture
The MCA is the precondition for configuration – the structured account of the organisation's actual context, Challenges, and Aspirations. The CSI is the second layer. Its function is to define the strategic domain – not what is measured, but what must remain true for the Aspirations to hold. Beneath each CSI sit Modules: the operational conditions that, when confirmed, confirm the CSI. Beneath each Module sit PIs: the observable indicators that generate the evidence the Module needs.
Evidence aggregates upward through the stack. PI observations, calibrated against pre-declared thresholds, produce Module evidence. Module evidence produces the CSI signal. The CSI signal produces the Critical Result Indicator – a confirmed claim about the strategic domain, not a score.
Los tres CSI canónicos
For the MetriqOne base deployment – MSMEs, cooperatives, NGOs, and local government units operating in real conditions – three CSIs govern the stack.
The organisation's operational foundation. Financial, physical, and structural conditions required for continuity of function.
The conditions under which people – staff, beneficiaries, partners – operate without unnecessary risk.
The organisation's capacity to deliver its purpose over time. Programme continuity, learning, and institutional knowledge.
La diferencia arquitectónica
What happened on this indicator this period? Did it meet the target? The answer is a performance score. No stack. No confirmation logic. No strategic claim.
Is this domain performing within the bounds required for the Aspirations to remain achievable? The answer is a confirmed claim, derived from aggregated PI evidence through a defined confirmation logic.
Por qué esta distinción es importante en la práctica.
Organisations that confuse PIs with strategic indicators respond to operational noise as if it were a strategic signal. A single PI moving below threshold triggers an executive response. Neither response may be warranted – the PI is a component of the Module evidence, which is a component of the CSI signal. Responding to a PI in isolation is responding to a part of a system as if it were the whole.
CSIs provide the structural boundary that filters noise from evidence. Without the CSI layer, every PI is implicitly treated as strategic. Everything is therefore strategic, which means the organisation has no way to distinguish between an operational variance and a strategic threat.
A disaster response organisation tracked 34 operational metrics across logistics, personnel, community engagement, and financial compliance. When field conditions deteriorated, 22 metrics showed deterioration. The remaining 12 showed improvement. No architectural logic existed to resolve the contradiction.
When a CSI structure was introduced – Stability, Safety, Continuity – the 34 metrics were redistributed into the stack as PIs within Modules. The contradiction resolved immediately: 19 of the deteriorating metrics were Stability PIs; 3 of the improving metrics were Safety PIs. The CSI signals told a coherent story. The organisation responded to a Stability threat, not to 22 simultaneous crises.
Llevar
A CSI is a domain definition, not a metric. It states what must remain true. The measurement happens at the PI layer, three levels below.
The CSI layer is what makes evidence aggregation possible. Without it, PI observations have nowhere to go. They accumulate as data, not as evidence for a confirmable claim.
The three canonical CSIs are Stability, Safety, and Continuity. These are context-adjustable within the structural requirement that each CSI defines a domain whose loss would make the Aspirations unachievable.
Responding to individual PIs as strategic signals is a stack failure. PI evidence is processed through Modules. The CSI is the strategic signal. The PI is the evidence generator.
A list of KPIs is not a stack. It is a monitoring system. The stack is what converts the monitoring system into a measurement system.