We use cookies, including third-party cookies from Google to serve personalized ads through AdSense, to operate this site and understand how it is used. By continuing to browse, you accept this use. See our Privacy Policy and Terms of Use for details, including how to opt out of personalized advertising.
Accept
SmartData CollectiveSmartData Collective
  • Analytics
    AnalyticsShow More
    Flat editorial illustration: The article is about joining public web signals with internal business metrics so BI teams can inter
    Alternative Data in BI: Bringing Public Web Data Into Your Dashboards
    23 Min Read
    Flat editorial illustration: The article is about automating the collection, preparation, and delivery of marketing data across p
    From Data to Dashboards: 5 Marketing Reporting Automation Software Picks
    12 Min Read
    Flat editorial illustration: The article contrasts passive follower totals with a behavioral path from attention and trust to cli
    Creator Analytics Beyond Follower Count: Seven Metrics That Measure Audience Behavior
    11 Min Read
    Flat editorial illustration: The article connects AI and marketing analytics with managerial judgment grounded in consumer behavi
    How an Online MBA in Marketing Connects AI and Data Analytics
    11 Min Read
    What Kind of Problem-Solving Distinguishes Data Analysts From Software Engineers -- AI-generated illustration
    What Kind of Problem-Solving Distinguishes Data Analysts From Software Engineers
    7 Min Read
  • Big Data
  • BI
  • Exclusive
  • IT
  • Marketing
  • Software
Search
© 2008-25 SmartData Collective. All Rights Reserved.
Reading: Who Gets the Call When Your Analytics Process Crashes?
Share
Notification
Font ResizerAa
SmartData CollectiveSmartData Collective
Font ResizerAa
Search
  • About
  • Help
  • Privacy
Follow US
© 2008-23 SmartData Collective. All Rights Reserved.
SmartData Collective > Big Data > Data Mining > Who Gets the Call When Your Analytics Process Crashes?
AnalyticsBig DataData ManagementData MiningModelingPolicy and GovernancePredictive AnalyticsStatistics

Who Gets the Call When Your Analytics Process Crashes?

BillFranks
BillFranks
6 Min Read
Who Gets the Call When Your Analytics Process Crashes?
Illustration generated with FLUX.2 [klein 4B] via Cloudflare Workers AI.
SHARE

I recently had a meeting with one of the largest companies in the world, where we discussed concerns about ongoing maintenance and, more importantly, ongoing repair required for analytics processes. The conversation helped solidify in my mind a major disconnect that often occurs when organizations deploy an analytics process into a production setting. Let’s walk through that disconnect here.

Contents
  • The Background
  • Who Gets The Call?

The Background

In this case, I was speaking with the IT leadership team that was responsible for the systems used for production analytics. As is the case with many companies, demand for analytics had been increasing and the IT team wanted to figure out how to best handle the anticipated influx of additional analytics processes that would be coming their way. As our discussion turned to the policies that should guide a process from the discovery phase to the production phase, an interesting issue was raised.

At this client, once a process is turned over to production, it is considered fully IT’s responsibility. This includes even the accuracy and maintenance of the analytic logic within the processes. The IT team is understandably quite concerned about taking ownership and responsibility for the logic of increasingly complex analytics processes. They just don’t have people with the analytical knowledge to effectively take that ownership. The only spots in the company with the requisite skills are the analytic teams creating the processes.

IT feels it has been burned too many times in the past when analytics processes were thrown over the wall to them and then they had to scramble to deal with issues that arose. They were hesitant to continue to add more processes without a better way to handle maintenance. I believe that my client’s real problem is with the contract that IT has with the analytics teams when it comes to placing something into production.

More Read

How to Compare Business Intelligence Cloud Costs and Features
How to Compare Business Intelligence Cloud Costs and Features
BI Advice for Midsize Organizations: Keep It Simple
Encryption is the key to the data kingdom
First Look – G Stat
Social Media Insights from Predictive Analytics

Who Gets The Call?

In this case, I see a serious issue in the precedents that have been set for production processes that must be addressed. Namely, it makes no sense to me that IT should have full responsibility for complex analytics processes built by an analytics team. IT should ensure that the systems are up, the data is accessible, and the necessary system resources are available so that the processes run smoothly. The logic of those processes, however, should remain under ownership of those who built them even when it is in production.

When logic is simple, such as standard reporting, it is reasonable to hand over all responsibility to IT. It does not make sense for complex analytics that may include predictive modeling, machine learning, or other advanced techniques in addition to all the requisite data preparation logic for those techniques. Analytics teams have to step up to the job of maintaining ownership of the processes they build in the long term. That means getting the phone call that something has broken at an inconvenient time. In the end, an organization needs problems with an analytics process solved as swiftly, completely, and accurately as possible. Only those with the knowledge to build such a process have the ability to meet this requirement. The responsibility rests squarely on analytics teams.

In the old days when a new analytics process had to be built on different systems and with different toolsets than the production environment, it was hard to avoid this disconnect. For example, IT often re-coded a process written in SAS to run directly within a mainframe or other operational system. While the analytics team built the initial logic, they weren’t familiar with the deployment environment or the language used to code the production process. Therefore, IT was stuck owning it all. This scenario was never a good one but was a necessary evil. With today’s technology, it is entirely possible for an analytics team to both develop and deploy an analytics process at scale using the same toolsets and to take full advantage of the power of the production system.

I don’t believe that most analytics professionals will balk at maintaining ownership of what they build. I know I wouldn’t. It is just a matter of asking them to maintain ownership and updating the “contract” with IT so that the split of who owns what pieces of the production process is changed. Unfortunately, in many organizations IT has not asked for this change nor has the analytics team suggested it. As a result, the deployment of analytics is much more stressful and carries much more risk than it needs to. Take a few moments to assess if your organization needs to update its deployment policies.

Share This Article
Facebook Pinterest LinkedIn
Share
ByBillFranks
Follow:
Bill Franks is Chief Analytics Officer for The International Institute For Analytics (IIA). Franks is also the author of Taming The Big Data Tidal Wave and The Analytics Revolution. His work has spanned clients in a variety of industries for companies ranging in size from Fortune 100 companies to small non-profit organizations. You can learn more at http://www.bill-franks.com.

Follow us on Facebook

Latest News

Flat editorial illustration: The article is about joining public web signals with internal business metrics so BI teams can inter
Alternative Data in BI: Bringing Public Web Data Into Your Dashboards
Big Data Business Intelligence Exclusive Web Analytics
Flat editorial illustration: A SaaS-editorial scene showing product usage, support patterns, and renewal feedback informing a fle
Using Product Usage Analytics and Support Data to Build a B2B Product Roadmap
Business Intelligence Infographic
From Hiring To Payroll: Managing HR Data Across Business Systems -- AI-generated illustration
From Hiring To Payroll: Managing HR Data Across Business Systems
Big Data Business Intelligence Infographic
Flat editorial illustration: The article is about automating the collection, preparation, and delivery of marketing data across p
From Data to Dashboards: 5 Marketing Reporting Automation Software Picks
Analytics Business Intelligence Exclusive Marketing

Stay Connected

1.2KFollowersLike
33.7KFollowersFollow
222FollowersPin

You Might also Like

Protecting Your Data From Attackers Using Top Spy Gear Technology
Big DataData QualityData Visualization

Protecting Your Data From Attackers Using Top Spy Gear Technology

7 Min Read
Data Mining Guest Post: Eric Greenwood
Data Mining

Data Mining Guest Post: Eric Greenwood

5 Min Read
Big Data is Transforming Every Industry on the Face of the Globe
AnalyticsBig Data

Big Data is Transforming Every Industry on the Face of the Globe

8 Min Read
Big Data Analytics Require Best Practices in Using Technology
AnalyticsBig Data

Big Data Analytics Require Best Practices in Using Technology

9 Min Read

SmartData Collective is one of the largest & trusted community covering technical content about Big Data, BI, Cloud, Analytics, Artificial Intelligence, IoT & more.

5 Great Tips for Using Data Analytics for Website UX
5 Great Tips for Using Data Analytics for Website UX
Big Data
From Bolts to Bots: How AI Is Fortifying the Automotive Industry
From Bolts to Bots: How AI Is Fortifying the Automotive Industry
Artificial Intelligence

Quick Link

  • About
  • Contact
  • Privacy
Follow US
© 2008-26 SmartData Collective. All Rights Reserved.
Welcome Back!

Sign in to your account

Username or Email Address
Password

Lost your password?