Skip to main content

Blog entry by Matthew Gierc

Do Not Let Ad Hoc Analysis Drag you Down

Do Not Let Ad Hoc Analysis Drag you Down

Maybe your boss isn’t Bill Lumbergh, but if his understanding of analytics is limited to green and red, chances are you’ve rolled your eyes more than once.

Hello Peter, what's happening? Ummm, I'm gonna need you to go ahead come in tomorrow to build that report. So if you could be here around 9 that would be great, mmmk... oh oh! and I almost forgot ahh, I'm also gonna need you to go ahead and come in on Sunday too, kay. We ahh don’t understand why our sales dropped this week and ah, we sorta need to play catch up and analyze it.

Honestly how many times has this happened to you? Maybe your boss isn’t a Bill Lumbergh, but if his understanding of analytics is limited to green = good and red = bad, chances are you’ve rolled your eyes in disgust more than once.

It happens a lot

And you’re not alone. Ad hoc analytics requests can make up 50% of an analytics team’s time. So what is a pragmatic analyst to do? According to Phil Kemelor, one strategy is to adopt a “don’t say yes” approach. Before committing to a request, ask yourself:
• What is the business reason behind the request?
• Will this kind of analysis answer the business question?
• Do we know how long this will take?
• Can we fit this into our funnel?

In other words, having an intake process to prioritize analytics requests can save teams a lot of weekend work.

When deciding whether to commit or pushback on a request, it’s also important to remember that your efforts will be wasted if the analysis cannot be acted upon. In other words, what will the business unit be able to do when they get access to your analysis? Will the organization be able to make changes to improve a bad situation? Nothing is more frustrating than spending a weekend building a report that subsequently gets printed out and put on a shelf to collect dust.

Knowing the difference between driving the car and fixing the engine

Brent Dykes also emphasizes the importance of understanding the difference between reporting and analysis. Reporting is the process of organizing data to monitor performance; analysis is the process of exploring data and reports to extract insights. The former helps a company ensure that everything is running well, the latter is an investigative tool used to figure out what’s going on “underneath the hood.” Organizations that don’t understand the difference between the two are more susceptible to ask for more ad hoc requests.

Doesn’t self-serve solve this problem?

What about self-service tools? After all, if any employee has the potential to become a citizen data scientist, then the demand for ad hoc requests should drop, right? Perhaps, but the costs to the organization might outweigh the benefits. Literally. The ad hoc reporting promise fails when ad hoc reports:
• Are treated like official reports shared broadly across the organization
• Perform shallow analysis that lacks real insight
• Are subject to the author’s own confirmation bias

Take a stand, for the right reason

Not everyone has the luxury of saying no to their Bill Lumbergh. But, as a recognized data expert in your organization you do have something much more powerful – credibility. In the long run, this means that you have the ability to shape your company’s data strategy, and ultimately wean the business off random ad hoc analysis. Start flexing those muscles today.

  • Share