Throughout my experience on client engagements, I’ve encountered a common issue: reports. In Part 1 of my blog I will address the reporting challenge, highlight some key benefits of standardized reporting, and outline an approach for implementing a standard enterprise reporting system.
On some engagements, clients want to reproduce the same old reports they had in the previous system, assuming that if users were complacent before, they would be happy with the same reports going forward. This is not the case. On a recent project, the client was in the midst of replacing a 10 year old system. Several business users were not happy at the prospect of continuing with reports that were created a decade ago! Other clients think that because the finance team has been getting the same reports for the past few years, that’s all they need. This is another incorrect assumption. In many cases these reports are not being utilized and users may even be using Excel to manipulate and turn the reports into something more useful. So why would you give users the same old reports, when, with a bit of foresight and planning, you can give them reports which enhance the way they do business and actually make it easier for them?
Some of the key benefits of an enterprise reporting system are:
- Single version of the truth – everyone has the same revenue /cogs/opex numbers
- Analysts have more time to analyze data and trends rather than consolidate data to make reports
To provide users with the necessary reports, it actually takes a multi-disciplined approach, focusing on usability and data visualization. This assumes you have created the back end databases with appropriate structures to support your reporting needs. It’s also critical to have a single definition for accounts and key metrics. This makes a big difference in reporting and getting everyone aligned to the single version of the truth you are about to create.
In Part 2 of my blog, I’ll look at usability and what it actually means for report design.