Many HR software packages include built-in analytics. This is a good thing, some data is better than no data. However, as HR gets more sophisticated, we need to move beyond accepting a vendor’s claim about built-in analytics and understand exactly what those analytics can and cannot do.
The first observation is that for most HR software it would be better to describe the built-in capability as “reporting” rather than “analytics.” Again, reporting is a good thing, but at this point HR should be distinguishing between reporting data and doing an analysis — even if there is no sharp line between the two.
An example of the sort of thing built-in reporting usually cannot do is determining how (retail) store revenue is affected by engagement. The reason the analytics/reporting tools that comes built into a software package can’t do this kind of analysis is that the two key sets of data (in this case engagement and store revenue) come from different sources.
The need to combine data from different sources is one of the main reasons companies, even companies with a modern HRMS or ATS, will buy specialized HR analytics software like PeopleInsights (small to mid-sized firms) or Visier (mid-sized to large firms). These packages can pull data from many sources into a data warehouse where it can easily be manipulated. Macromicro, a standalone analytics and visualization package, also uses a data warehouse.
Specialized analytics packages using a data warehouse model generally outperform built-in analytics/reporting for several reasons:
John Pensom, CEO of PeopleInsights, says that cloud-based technology has really leveled the playing field for small and mid-sized companies. They now can have HR software, including analytics software, that rivals what the big companies have. In fact, sometimes big companies are stuck with legacy on-premise systems which are not as capable as the HR software a much smaller firm gets via the cloud (i.e. SaaS)