≡ Menu

Agile AND industrial analytics


Syndicated from International Institute for Analytics

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.

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.


Comments on this entry are closed.

  • Ned Kumar August 31, 2010, 11:56 pm

    I have been following the agile vs industrialized debate :-). From where I stand and based on my experience, I see pros and cons of each approach and more importantly a place where one is more appropriate than the other.

    One thing I would like to throw out is that organizations should do an audit on where they stand in terms of analytical maturity. They could be at the low end with low-end tool, no established process capabilities, and no highly-skilled analyst or they could be at the high end with dedicated teams of analysts with advanced skillset, enterprise data warehouse, BI, cross-channel analytics and the whole 9 yards.

    Depending on where they fall in the continuum, I would then recommend whether they should operationalize their analytics or not and if yes, what parts they should. I am in agreement with you that certain things need a structure if the organization has to benefit – however, the management team has to decide on the cost-benefit of giving this structure as it relates to their business and maturity.

    Thanks for a good read.