Where Analytics Projects Go Wrong - InformationWeek

InformationWeek is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

IoT
IoT
Data Management // Big Data Analytics
Commentary
10/26/2016
01:00 PM
50%
50%

Where Analytics Projects Go Wrong

Of all the things that can go wrong with an analytics project, it appears that failure to properly define the business problem is the runaway leader.

Walk the exhibit floor at any tech trade show and you will won't be able to ignore the noise about big data and analytics. The solution vendors virtually shout, "Pick me, pick me. You can't go wrong."

But "going wrong" with an analytics project may not even reach the point of vendor selection. It appears that the real pitfalls for a data project are independent of technology choice.

Credit: Pixabay
Credit: Pixabay

So far, the voting in our current All Analytics Unknown Document 281807 makes it clear that respondents see the biggest threat to a project's success in the earliest of stages, identifying the business problem that needs to be solved. As of this morning, 40% of voters listed the problem definition process as the greatest danger point for an analytics project. It was followed by "data sourcing" at 25.7%.

Of course, this doesn't mean that just any data technology will do the job. Rather, two-thirds of our voters seem to be saying that if you don't get off on the right foot with the right data for the right business problem, what happens after that -- technology choice, delivering business results, etc. -- just doesn't matter so much. Mess up the first stage and nothing that follows will fix the mistake.

When it comes to identifying the business problem, one trend I've noticed in numerous case studies is that defining the problem takes hard work. In many instances, the real problem isn't the one that seems most apparent. Instead, that real problem is a subset or a dependency of what seems to be an obvious issue.

How does that play out in real life?

Take the case of slow sales in a given region. The immediate management assumption is that the local sales force is doing something wrong, and the executives will want data showing just what the sales team is doing wrong in comparison with what other teams are doing. However, some initial exploration could lead the analytics pros to look beyond the actual sales strategy.

The problems could be highlighted in customer social media posts complaining about product pricing, or in tech support calls that indicate product quality issues. So, the real problem could be in customer satisfaction rather than in the sales strategy or talent.

I know, it seems logical that a manager should take a holistic view of the problem and work to narrow down the real issues. But, have you ever witnessed a manager ignoring logic?

 

We welcome your comments on this topic on our social media channels, or [contact us directly] with questions about the site.
Comment  | 
Print  | 
More Insights
Commentary
Enterprise Guide to Edge Computing
Cathleen Gagne, Managing Editor, InformationWeek,  10/15/2019
News
Rethinking IT: Tech Investments that Drive Business Growth
Jessica Davis, Senior Editor, Enterprise Apps,  10/3/2019
Slideshows
IT Careers: 12 Job Skills in Demand for 2020
Cynthia Harvey, Freelance Journalist, InformationWeek,  10/1/2019
White Papers
Register for InformationWeek Newsletters
Video
Current Issue
Getting Started With Emerging Technologies
Looking to help your enterprise IT team ease the stress of putting new/emerging technologies such as AI, machine learning and IoT to work for their organizations? There are a few ways to get off on the right foot. In this report we share some expert advice on how to approach some of these seemingly daunting tech challenges.
Slideshows
Flash Poll