Thanks for signing up!
You're almost done.
You need to do one more thing before you’ll start receiving information from us.
We get it. Looking for work can be scary, especially if you’ve been at it for a long time and haven’t gotten any results.
Understanding which fears are getting in the way and how to overcome them will make all the difference. Sometimes you might not be aware of which obstacle is getting in the way of your goals. If you want to overcome these fears once and for all, we invite you to join us!
In this training, you’ll learn how to:
Join our CEO, J.T. O'Donnell, and Director of Training Development & Coaching, Christina Burgio, for this live event on Wednesday, October 5th at 12 pm ET.
CAN'T ATTEND LIVE? That's okay. You'll have access to the recording and the workbook after the session!
Most COTS (commercial-off-the-shelf) applications will have standard/canned reports. These are the “common” reports used by customers. If you’re implementing a new system and there are many standard reports, start with 10 top reports so you don’t overwhelm the end users. If you’re not sure what these are, ask the vendor to recommend them (especially if you’re changing your process and following the vendor’s best practice). Then the end users can utilize other standard reports as they get more comfortable and familiar with the application.
For example, if you just purchased a new phone system for the call center, find the reports that detail measurements such as the number of calls, dropped calls, wait time, peak times, etc.
Identify and define key performance indicators (KPIs), which are measurable values to analyze for better decision making. KPIs may be related to a specific function, line of business, or group of individuals. You can take a group of KPIs and create a dashboard. For example, some KPIs related to the help desk are:
Once you’re comfortably leveraging the standard reports, you may want to ask the vendor (or your team’s developer/programmer) to customize standard reports or create custom reports with additional specific information you’re looking for. This may involve combining data from multiple tables within the application.
Two typical ways to serve these reports: 1) “push” reports to the end users on a scheduled frequency such as via email daily; or 2) have the end user “pull” reports which gives them the ability to access the reports as needed.
But reporting isn’t limited to COTS applications. You can create remarkable reports using Excel such as PivotTables, Pivot Charts, or Slicers.
Another phenomenal visualization tool that is part of Office 365 is Power BI. It’s part of the Microsoft family (similar to Excel) so it’s straightforward to use. You can create a dashboard visualizing year-over-year comparisons, market segmentations, drill downs, etc.
If you’re new to Power BI, you can download the free desktop version (which admittedly does have limitations). If you find that Power BI does meet your basic reporting needs and you want more, then you can upgrade to the Pro license.
If you have enormous amounts of data, you may want to consider creating a data lake (raw data) or data warehouse (structured data). You can pull in data from multiple disparate systems into one central repository. There are ETL (extract transform load) tools to load the data into the data warehouse. You can cube the data so that the end users can roll up, drill down, and slice the data, do “what if” scenarios, etc.
TIP: If you allow end users to create their own reports, it’s critical that they understand the various data fields. Are you able to give them some type of data dictionary, or are they able to certify the results? It would be disastrous if they selected the wrong date or revenue field which produced incorrect results and sent the report to the board of directors.
Other reporting considerations:
1. Have a separate reporting database so that you don’t affect the production database. You don’t want an end user to kick off a complex query inadvertently causing production response to come to a crawl or even freeze.
2. Data needs to be secured appropriately (security). Who should have access to specific data fields should be determined by the data owner. For example, only a small handful of people should be able to access salary/payroll information.
3. Data should be classified such as public, internal, confidential, or restricted. Access should be controlled as appropriate.
4. Create a customer portal (extranet) to empower your customers (also partners and vendors) so that they can pull their own reports and information.
There is a quote by Lois Horowitz: “Not having the information you need when you need it leaves you wanting. Not knowing where to look for that information leaves you powerless. In a society where information is king, none of us can afford that.”
For more information on actionable reporting, follow me on LinkedIn!
