This post was originally published on this site
Many years ago, when I was still working as an HR specialist for Reporting & Analytics, our team was asked to build a Recruiting Dashboard for the head of Talent Acquisition. One of the things the management wanted to report on is ‘Source of Hire’. I said to myself, oh that’s easy – I can pull that up quickly. But then, as I was looking into our Recruiting System, I found that we have 3 different ‘Source of Hire’ data fields in the system, each with different but also overlapping sets of values. To confirm which is the correct data field to use, I consulted my colleagues from the Recruiting team to understand the definition and process relevance of each ‘Source of Hire’ data field, only to get different answers from each person I asked. It turned out that the Recruiting team has a different understanding of each ‘Source of Hire’ data field and therefore has been using it in different ways and purposes. It was the same scenario with many other data we needed for the dashboard. It was almost an impossible task to build the dashboard without a lot of manual work and data clean-up.
Does this
