Decision Latency… Just Part of the Same Problem as Data & Process Latency

Interesting read from Gartner’s Jim Sinur, talking about decision and action latency. Jim’s talks about how Big Data is meant to solve decision latency – but it’s not at all clear how or why Big Data affects the latency of either designing or making decisions. Surely Big Data is about extractable information for improving the quality of decisions? Maybe I missed something critical in the Big Data hype. If anything, running analytics on larger data sets is sure to increase latency rather than reduce it! Of course, this is why real-time analytics are increasingly important to complement the traditional data analytics…

I would, however, agree that decision, data and process latency are key weapons in the fight against the costs of Big Data; you want to respond effectively to events as they occur, despite those event rates increasing: that means efficient decision engines, high performance data access, as well as responsive process engines.

Jim also talks about recognise (events, via rules), reflect (analytics, generating context presumably, for decisions) and respond (business operation processes). It’s not clear whether Gartner is clear on the differentiation of decisions and processes (do I reflect a decision, or respond with a decision?). So I still prefer the OODA terms, where context or “orientation” and “decision” are directly called out, with the  “Event Server” implementation of event-decision-action patterns. Then again, the latter probably equates to Jim’s:

next generation process management (the iBPMs) … incorporating events, BI, real time, rules leveraging on demand and/or in-line analytics to help with the “complete latency” going forward for intelligent business operations…