
Increasingly, organizations are turning to machine learning to augment their analytics strategies and drive decision-making. But are business leaders using the right tools to make those choices efficient and effective?
James Taylor (@jamet123), CEO at Decision Management Solutions, has never been short of opinions. Recently, Taylor commented on the state of machine learning following a comedic post by XKCD that parodied people's misinterpretation of how to succeed with machine learning.
Taylor's observations included:
1) Just because the data can tell you something, there's no guarantee that the business cares about it, can use it, or will use it for decision-making.
2) Most business decisions require policies and regulations to be applied too, not just the analytic insight from your data. Simply pushing data through machine learning or other analytic algorithms won't tell you this.
In the end, Taylor says there is no substitute for clearly identifying a business problem and knowing what decision (or decisions) the business needs to make more accurately to achieve this.
We spoke with Taylor about machine learning and determining how enterprises can use advanced analytics to improve their outcomes:
Michael Singer: Let's talk a little bit about your recent thoughts on machine learning. This is obviously a very hot topic for enterprises that are trying to get either the vision of what's going on or trying to do some predictive style conversations. What is driving people to think more about this?
James Taylor: There are a couple of things. There are the people who already knew about data science and analytics and predictive analytics, and they're looking at machine learning to process whole new data sets. Then there's another group of people who are looking at machine learning and going, "Gosh, this lets us get advanced analytics without hiring data scientists. We can just pile the data up and run it through machine learning algorithms and we'll be like Google."
That second group is going to be bitterly disappointed because there's still no substitute for knowing what your problem is and having a way to use it.
I think people need to recognize that they've got to tease out the problem more before they apply machine learning to it.
Michael Singer: Can you give some examples of companies that are successful with machine learning that are asking the right kinds of questions?
James Taylor: The best examples are the places where you have constantly changing data, or complex and new kinds of data, or new kinds of data sources, or new kinds of data getting added. It's not always obvious what the best way to analyze that data is going to be to come up with the prediction that you need.
New data keeps coming up. There are existing data sources; you can buy new data; your customers start generating more data; and now you've digitized a new thing. So the ability of machine learning to try lots of different algorithms and say, "OK, if you're trying to predict this, and you've got this data, you know, you should use this combination of things."
I think this is very helpful. Coming up with combinations on your own can be a real slog if you're trying to do that by hand. There's a danger, however. Companies will often keep applying the same algorithms they've always used. If you look at the data mining surveys, regression, classification, and decision trees, those still get used more than all the other algorithms added together.
I think machine learning helps to push on that a little bit. You know, it gives an analytically minded person a way of saying, "OK, we got a bunch of new kinds of data here. I don't know what the best way to do it is. Try different things."
Michael Singer: What would you say are the most critical issues facing companies looking to implement machine learning?
James Taylor: The most important thing is to know what problem you're trying to solve. There is a value for pure research in data, right? Just piling up the data and hiring smart people to look at your data and say, "Tell me an interesting story about this data."
Look at the data and tell me things that will help me do those things in a more profitable way. I don't care how accurate the model is, or how interesting it is, or how cute an algorithm it uses, or how much data it uses. What I want to know is, how is it going to help me make more money?
Pushing back on this idea that you can begin with the data and always work from the data, and always begin with the business problem and work backward to the data. And sure, that's going to drive the data into a data lake, because you're going to say, "To solve that business problem, I need to build these kinds of algorithms."
Those kinds of algorithms, frankly, require access to all the emails people have ever sent us, and the only way I can do that is if I put all the emails in the data lake. OK, fine. Put them in a data lake. But you've got a business problem in mind, right?
The second thing is to think about this as an industrial process, right? It's a little bit like when IT started in most companies. The first few IT things built were handcrafted, and what I do is hire one really smart guy who writes this code in the back, or assembly, or whatever it is.
Unfortunately, you can't just go out and magically hire data science unicorns who are going to solve your problem for you. You've got to find people internally. You've got to retrain people. You've got to come up with processes. You've got to put this infrastructure in place, and you've just got to do the hard work of making this a core business capability.
Michael Singer: It sounds like you have to be a cynic to be able to answer these questions, right?
James Taylor: Right. Many years ago, I worked for a consulting firm. We were merging the IT methodology with the process improvement methodology. And one of the guys there turned to me and said, "James, the thing you IT people forget is that in the end, all projects are organizational change projects." And I think of that often when I see the analytics people. "Oh, it's an analytics project." And I'm like, "No, in the end, it's not." In the end, it's an organizational change problem.