Sales Management Customer Relationship Human Resources Business Performance BI & Data Quality IT Tools & Vendors

Sign-in   Register
Establishing 'Making it Happen' as a 'Formal & Predictable' Discipline
Principles and Rules Listing Page

Never design your Business performance management systems on base of a specific KPI

A specific KPI is a good management practice. However, as you design your infrastructure to deliver the information around that KPI, you have to design around the KPI-class to which this KPI belongs.
 
This page of 'Principles and Rules' is linked to:  'Executable' Strategy, Execution Scorecard,

As we were designing the BPM for a client, the customer came out with the list of well thought out KPIs like:

  • %age growth of average sales velocity over last quarter
  • Average sales productivity for product-X over last 6 months etc...

We asked the customer to add one more specific to these KPIs. That is KPI class. You can have million KPIs from a given KPI class. For example, sales Velocity (the speed at which one converts a lead into a sale) is a KPI class. One can have following KPIs under this KPI-Class:

  • Average sales velocity for a given product over past one year
  • %age growth in the average sales velocity over last quarter.

Therefore, typically, when you gather the specifications around a KPI, one should focus on KPI-class instead of the exact KPI, which you want to track. The reason is that the specific KPI could change with time. As you design your performance management systems around a KPI-class, the data Extraction, transformation and loading and other foundation elements, will be more sustainable. For example out of the sales velocity KPI-class, one needs to design your infrastructure in such a way that you can get the value  of that KPI by different cuts (location, products, sales channel) as well a s operations (like average sales velocity, %age growth in sales velocity, standard deviation in sales velocity, time trending analysis etc..). Here is the flow that Execution-MiH would recommend:

Step 1- To begin with one may not need to bog the client down on KPI-classes. Let the client do his own thinking on KPIs he want to manage, and create the KPI business requirement accordingly.

Step II- Once the thinking has been done (hopefully driven by the strategic business plan), one can analyze on which KPI-class a given KPI belongs to. For example, if the client is asking for the KPI  "Average sales productivity for product-X over last 6 months", one can assign it to sales productivity by value KPI-Class
.

Step III- Discuss the KPI-class with the client and check his comfort. Once client confirms the KPI class- expand the definition of the KPI class. This is important. In step I, the client identified a specific KPI and now the client is thinking in terms of the KPI class. The thinking will lead to the similar questions asked for a given KPI, but will be more holistic. Some of the holistic questions will be:

- What are the different cuts I can make of the KPI class? For example, you can have 'sales productivity by volume' KPI class on the following cuts:

  • Product
  • Location
  • Sales Channel
  • Sales unit
  • Sales lead category

What are the various operations that I can do around this KPI class? The examples are:

  • Average
  • standard Deviation
  • Time trending

Step IV- Design your infrastructure on the basis of the KPI-class. You will do the following activities:

Get the data on all the dimensions related to that KPI-Class. For example, when you get the data on a given sales transaction, you will not only get the velocity related data, but also the information on various dimensions linked to that sale like -

  • Which product the sale was for?
  • What was the location of that sale?
  • What was the value of the sales?
  • What was the volume of the sale etc...?

The idea is that one should design for the holistic analysis around the KPI class. If you don't take this approach, you will have a risk of too frequent changes in your BPM configuration and business intelligence modeling.


Quick Feedback- Was this information helpful ?
Relevant Links to this page
Principles & Rules → Go sequentially in performance management → Principles & Rules → Business scorecard review can be typically with monthly frequency → Practice Techniques → Aligning your rewards to your strategy- Aggressive Methods → Principles & Rules → Decision Management Process- An enabler to a Science and an Art → Principles & Rules → Performance Review Session is last place to know the action-status → Principles & Rules → Shifting the mind-set to leading Indicators- KPIs → Principles & Rules → For important KPIs- Install first and Fix later- though cautiously → Principles & Rules → Define the interpretation and actions related to KPIs → Principles & Rules → A KPI should be easy to understand- but depends on the level → 
 
Back
 
Relevant links to this page
Go sequentially in performance management
Business scorecard review can be typically with monthly frequency
Aligning your rewards to your strategy- Aggressive Methods
Decision Management Process- An enabler to a Science and an Art
Performance Review Session is last place to know the action-status
Shifting the mind-set to leading Indicators- KPIs
For important KPIs- Install first and Fix later- though cautiously
Define the interpretation and actions related to KPIs
A KPI should be easy to understand- but depends on the level
Additional Channels
Principles & Rules
Free Templates
Glossary
Key Performance Indicators

Most Popular Zones with list of pages crossing 25000 hits  →→→ 
Maximising Sales Performance
Sales Compensation Analysis
Sales geographic expansion
Sales Objectives Clarity
Sales Campaign Management
Sales Leads Allocation and Distribution
Read more...
  Customer Relationship Management
Customer Value and Profitability- BI
Exit barriers for Customer Retention
Customer Segmentation Actions
Customer-Centric product-service management
Customer Value and Profitability Data Management
Read more...
  Human Resources & Leadership
Business and Financial Acumen
Give feedback closer to the observation
Roles and Level based Competency Segregation
Lead diverse and collaborative teams
Feedback does not mean only negative feedback
Read more...
 
 
Business Performance & Planning
Review Session should stay focused
Strategy Map Objectives Measures and Initiatives
Individual goal Sheet
Stakeholder test for Scorecard
Strategic Business Plan
Read more...
  Business Intelligence & Data Quality
Dimensional Model to source mapping
Business Process Controls
Technical Metadata for IT
Exception Analysis
ROLAP- Relational OLAP architecture
Read more...
  IT Vendors & Tools Management
Vendor Quality Evaluation
Vendor Credentials and Track-Record Evaluation
End User Reporting Features
Technical Customization Evaluation
Connectivity and Computing Support
Read more...