IBM has just announced that one of Australia’s “big four” banks, the ANZ, will adopt the IBM Watson technology in their wealth management division for customer service and engagement. Australia has always been an early adopter of new technologies but I’d also like to think that we’re a little smarter and savvier than your average geek back in high school in 1982.
IBM’s Watson announcement is significant, not necessarily because of the sophistication of the Watson technology, but because of IBM's ability to successfully market the Watson concept.
To take us all back a little, the term ‘cognitive computing’ emerged in response to the failings of what was once termed ‘artificial intelligence’. Though the underlying concepts have been around for 50 years or more, AI remains a niche and specialist market with limited applications and a significant trail of failed or aborted projects. That’s not to say that we haven’t seen some sophisticated algorithmic based systems evolve. There’s already a good portfolio of large scale, deep analytic systems developed in the areas of fraud, risk, forensics, medicine, physics and more.
BI professionals spend a significant portion of their time trying to instill the discipline of datadriven performance management into their business partners. However, isn’t there something wrong with teaching someone else to fly when you’re still learning to walk? Few BI pros have a way to measure their BI performance quantitatively (46% do not measure BI performance efficiencies and 55% do not measure effectiveness). Everyone collects statistics on the database and BI application server performance, and many conduct periodic surveys to gauge business users’ level of satisfaction. But how do you really know if you have a high-performing, widely used, popular BI environment? For example, you should know BI performance
Efficiency metrics such as number of times a report is used or a number of duplicate/similar reports, etc
Effectiveness metrics such as average number of clicks to find a report and clicks within a report to find an answer to a question and many others
Metric attributes/dimensions such as users, roles, departments, LOBs, regions and others