Cookies help us display personalized product recommendations and ensure you have great shopping experience.

By using this site, you agree to the Privacy Policy and Terms of Use.
Accept
SmartData CollectiveSmartData Collective
  • Analytics
    AnalyticsShow More
    sales and data analytics
    How Data Analytics Improves Lead Management and Sales Results
    9 Min Read
    data analytics and truck accident claims
    How Data Analytics Reduces Truck Accidents and Speeds Up Claims
    7 Min Read
    predictive analytics for interior designers
    Interior Designers Boost Profits with Predictive Analytics
    8 Min Read
    image fx (67)
    Improving LinkedIn Ad Strategies with Data Analytics
    9 Min Read
    big data and remote work
    Data Helps Speech-Language Pathologists Deliver Better Results
    6 Min Read
  • Big Data
  • BI
  • Exclusive
  • IT
  • Marketing
  • Software
Search
© 2008-25 SmartData Collective. All Rights Reserved.
Reading: Agile AND Industrial Analytics
Share
Notification
Font ResizerAa
SmartData CollectiveSmartData Collective
Font ResizerAa
Search
  • About
  • Help
  • Privacy
Follow US
© 2008-23 SmartData Collective. All Rights Reserved.
SmartData Collective > Uncategorized > Agile AND Industrial Analytics
Uncategorized

Agile AND Industrial Analytics

JamesTaylor
JamesTaylor
4 Min Read
SHARE

I wrote a post called “It’s time to industrialize analytics” for Smart Data Collective a little while ago and it prompted Tom to reply with Agile vs Industrialized.

I wrote a post called “It’s time to industrialize analytics” for Smart Data Collective a little while ago and it prompted Tom to reply with Agile vs Industrialized.

To recap, the key point of my post was that we need to move away from analytics as a pure craft to one that has a more systematic focus. We need analytic teams that are focused on the end goal, whether that is a high-throughput operational system (a propensity model for use in a web marketing system for instance), a dashboard, report or visualization. Such a focus necessitates limitations on the freedom of the analytic team to use their favorite tools or bring whatever data seems helpful into the model. If we focus on the need to operationalize this model – to make it affect our business – then we will not be able to have total freedom in our analytic work. This is more true when models are being deployed into operational systems than when they are being deployed into more interactive, low-volume environments but it is always true at some level. Rolls Royce cars may be hand made in places but this work is still part of an industrial process – the need for it to fit into a finished product is still paramount. So it is with analytics – even when we are hand-tooling something, we should be aware of the “industrial” context in which we operate.

More Read

A look ahead: Some technology developments to expect in 2009
Thoughts on APIs – IB, Lime, WEX
Managed Services: Freeing Corporate IT for Business Strategies
The Hadoop Ecosystem: HDFS, Yarn, Hive, Pig, HBase and Growing
Defining Analytics: Analytics

Tom’s follow-on point that industrialization is not appropriate for analytic discovery work is a valid one. Organizations often don’t know how analytics might be able to improve their business and must spend time and effort in a discovery phase. It is entirely appropriate to try new things, to do things one-off while figuring out what might be helpful. Analytics are not yet, in most companies, a standard part of the way they do business. Even if they are there will be times when the area being investigated is not well known enough to allow for a systematic approach – we will need to be agile about where and how to investigate. But remember, as I said in my original post

If the model is accurate but impractical to implement then it adds no business value and should, therefore, be considered a bad  model.

It does not matter if operationalization means putting the model into a high-volume process, an executive dashboard or sophisticated visualization. If you don’t impact business results then the model is no good. You can, and should, be agile about developing new analytics. But you should keep an eye on the end objective and make sure you can deliver business results.

 

Copyright © 2010 http://jtonedm.com James Taylor

Syndicated from International Institute for Analytics

TAGGED:analytics
Share This Article
Facebook Pinterest LinkedIn
Share

Follow us on Facebook

Latest News

sales and data analytics
How Data Analytics Improves Lead Management and Sales Results
Analytics Big Data Exclusive
ai in marketing
How AI and Smart Platforms Improve Email Marketing
Artificial Intelligence Exclusive Marketing
AI Document Verification for Legal Firms: Importance & Top Tools
AI Document Verification for Legal Firms: Importance & Top Tools
Artificial Intelligence Exclusive
AI supply chain
AI Tools Are Strengthening Global Supply Chains
Artificial Intelligence Exclusive

Stay Connected

1.2kFollowersLike
33.7kFollowersFollow
222FollowersPin

You Might also Like

Business Intelligence or Business Analytics?

3 Min Read

The Future of BI in Two Words

6 Min Read

The Fallacy of the Data Scientist Shortage

8 Min Read

Business Analytics and IBM

7 Min Read

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

ai chatbot
The Art of Conversation: Enhancing Chatbots with Advanced AI Prompts
Chatbots
ai in ecommerce
Artificial Intelligence for eCommerce: A Closer Look
Artificial Intelligence

Quick Link

  • About
  • Contact
  • Privacy
Follow US
© 2008-25 SmartData Collective. All Rights Reserved.
Go to mobile version
Welcome Back!

Sign in to your account

Username or Email Address
Password

Lost your password?