Interdictive Analytics: Catching Baddies At The Pass And In The Nick Of Time

Predictive analytics is not just about forecasting what’s coming down the pike. It’s also about keeping the bad alternative futures from happening. If you can see the nasty things that might happen far enough in advance, you have a better chance of neutralizing or squelching them entirely.

In fact, many real-world applications of predictive analytics are “interdictive,” a term often used in military and law enforcement contexts to refer to tactics that delay, disrupt, or shut down an adversary’s forces or supply routes before they can do damage. Anti-fraud is one of the principal interdictive applications of predictive analytics technology. Companies everywhere rely on data mining to determine who’s been engaging, alone or in groups, in stealing money, supplies, finished goods, cellular airtime, and other valuables — and also where they’re likely to strike next. Likewise, anti-terrorism efforts rely on predictive models to sift through massive collections of historical and real-time intelligence in a Jack Bauer-like race against time and imminent disaster. You best believe that social network analysis is a key weapon in your arsenal for predicting and interdicting these sorts of malignant social patterns.

That all sounds so melodramatic, but predictive analysis is often used for something more mundane, but which might also have life-threatening consequences. You can employ statistical tools to predict breakdowns and other bad things that might result from faulty engineering — unless we fix them in time. I’m referring to the widely established discipline of “survival analysis,” also known as “reliability analysis” or “duration analysis.” If you can find patterns of imminent failure of some complex engineering assembly, such as an offshore oil rig — or even incremental service degradation in consumer products such as smartphones — you can implement corrective measures in the nick of time. This is the art of preventive maintenance: interdicting potential failures before they become showstoppers.

And if we push this line of thought even further, we can see that most real-world predictive models have predominantly interdictive applications. Churn models give us the power to see some bad future scenario — specific customers jumping to the competition — so that we can make them an offer that might change their minds before it’s too late. Likewise, upsell and cross-sell models empower us to see another unfortunate potentiality — specific customers failing to buy some hot new product — so that we can make the perfect pitch before the window of opportunity closes.

Clearly, you can interpret next best offers in both a predictive and an interdictive context. It’s not enough to see the future. You have to take effective action to shape the future to your ends. As I pointed out in this recent blog post on predictive processes, many enterprises are equipping customer relationship management (CRM) and other applications with the ability to automatically anticipate a changing environment and drive optimal actions across all process steps.

A self-optimizing business process is one that continually interdicts the bad events and circumstances that might derail you.

Comments

Don't see the relevance

Yvonne:

How exactly is this company relevant to the subject of the blog?

Jim

predictive customer attrition => interdictive

I enjoyed your post, Jim. My company's most frequent use of predictive analytics is catching those customers most likely to defect (whether to the competition or not is frequently not known). Most of the time, for B to B clients, a simple touch by the account rep prevents the attrition--and there's the interdiction; never thought to call it that before, but I believe we will now!

I'm flattered, but don't use terms customers may not understand

Alan:

I'm flattered you like the term "interdiction." I do refer to your application, customer churn reduction, in the blog post, as an example of an interdictive app of predictive analytics.

You might want to continue to refer to your app as "customer churn reduction," "customer retention," or something to that effect. Customers may not understand some new term from some industry analyst. Don't want to confuse them unnecessarily.

Jim

Slightly off-topic

James:

I was reading your report from Nov, 2009 on "In-Database Analytics..". You end with -

“Within the world of comprehensive cloud analytics, MapReduce/Hadoop will be a key — but not the only — development framework. Rather, these specifications will form part of a broader — but still largely undefined — SOA-based virtualization architecture for inline analytics. Under the comprehensive cloud analytics architecture, developers will create inline analytic models that deploy to a dizzying range of clouds, event streams, file systems, databases, file systems, complex
event processing platforms, business process management systems, information-as-a-service environments, and other applications”

Can you write a blog post to elaborate on this more? It seems like a fascinating idea..

I've already developed this idea in a Forrester report

Naren:

Thanks. Actually, I already published my extended thoughts on this very topic last year in "In-Database Analytics: The Heart Of The Predictive Enterprise," available to Forrester customers at http://www.forrester.com/rb/Research/in-database_analytics_heart_of_pred...

Jim