An Architecture for KPI - Most needed but ignored
A branch manager is interested in seeing whether there has been abnormally low or high transactions in a particular day. A Banking regional manager is interested in knowing whether there has been an increase in customers with a recently launched campaign. The country head is more interested in knowing which areas have performed better or worse as compared to a predefined expectation. The global CFO is interested in seeing that if there is a revenue at risk due to any kind of external or internal impact. The HR head is interested in seeing the percentage change in attrition due to an initiative to increase the employee hours in the branches for providing better customer service. The CIO needs to look at the benefits of the discretionary spending over the last year. An IT manager overseeing a multi-million development program wants to estimate the value and even compare the actuals once it is delivered and is ready for measurement.
Most of the information in such examples conventionally have been available as offline reports run through batch jobs scheduled as per the need and convenience or through different other means.
The question is how should an enterprise design its Information Architecture to deliver the right set of KPIs and also make it more usable at all levels. Here are some tips:
Continue reading "An Architecture for KPI - Most needed but ignored" »



