It was not long ago when computer systems used to suppress the use of ‘century’ in date fields to save space in the (very) expensive database storage. The same happened when displaying the dates in the fixed size for terminal screens (80 columns × 24 rows), or when printing amounts with zero quantities or zero dollars. It was extremely important and economically savvy to code and design systems for better use of the hard disk space, screens real-estate and printer toner. Millions of dollars were actually saved for not storing, displaying and printing zeros.
Having all of those technical barriers economically minimized almost to the point of nonimportance, should we still see (or not see) the zeros in reports and screens rendered by BI tools? What are the best practices for BI reports in that sense? Despite the nature of the reports either informational, analytical or comparative, it is a must that reporting platforms in the organization share the same data and some basic presentation rules to achieve a consistent global picture. You might think that not everything should be as straightforward as design, decide, and implement. Basic rules should not apply for all reporting. It is well known that many area managers think they know what they want in reports and like to define how they need their reports formatted. In doing this, a general consensus would be necessary to avoid having different report standards throughout the different departments within your organization. Usually, the best practices are focused on one or more of the following areas:
Customize the report to the target audience/Identify Report requirements
Identify the KPIs and metrics/Tell Story clearly
Choose the right visualization for each metric/Highlight key messages/And other shading or graphical suggestions
Layer the information/Drill Down
Take advantage of online capabilities/Create a controlled and audit-able environment for business users to adjust or manipulate data for reporting.
Gray areas can be found while defining best practices for reporting within your organization. Especially when that definition is purely based either on best practices in other organizations, or in the literature that fails to differentiate best practices based on their maturity level of the BI in the organization. If we detailed, even more, we can find suggestions like, how to customize the report:
Keep it simple and short! Shorter is better and for performance monitoring a one-page report is ideal.
Don’t overload the user with too many numbers; Pages of detailed data is not a report, despite some managers wanting all the details in a report.
Discuss report design with managers/users who request the report.
Observing the above short list of report guidelines, we might find them difficult to implement when the maturity level for BI is at the earliest stage. Which is usually involving: The supply of operational reporting, which the main value is business tracking (since their antique application doesn’t supply enough insight); Reports that are based in multiple spreadsheets and SQL output, focused on basic data access; Reports that are still used to upload information into different systems making the BI solution work as an ETL tool; Front line users looking for a single version of the true, creating data aggregations outside the BI tool supplied and comparing against other reports or different data sources.
During an organization’s early stages, despite the suggested best practices for reporting, many users require as much data as possible in the report. This is usually because they do not trust the accuracy of the summarized data. In this stage as much data as possible is golden.
Wrapping it up:
Rather than strictly implementing a series of Best Practices for BI reporting in an organization, sometimes it is worth it to incorporate elements that could be considered aesthetic or not in line with design trends. This will allow a certain confidence in the data or process (calculations/data load). Even if that means displaying any leading zeroes to the left of a number with no effect on the number’s value.
Written By Reinaldo Nunez