>>from around the globe If the cube with digital coverage of M I t. Chief data officer and Information quality symposium brought to you by Silicon Angle Media >>Hello, everyone. This is Day Volonte and welcome back to our continuing coverage of the M I t. Chief Data Officer CDO I Q event Interpol Bhandari is here. He's a leading voice in the CDO community and a longtime Cubillan Interpol. Great to see you. Thanks for coming on for this. Especially >>program. My pleasure. >>So when you you and I first met, you laid out what I thought was, you know, one of the most cogent frameworks to understand what a CDO is job was where the priority should be. And one of those was really understanding how, how, how data contributes to the monetization of station aligning with lines of business, a number of other things. And that was several years ago. A lot of change since then. You know, we've been doing this conference since probably twenty thirteen and back then, you know, Hadoop was coming on strong. A lot of CEOs didn't want to go near the technology that's beginning to change. CDOs and cto Zehr becoming much more aligned at the hip. The reporting organizations have changed. But I love your perspective on what you've observed as changing in the CDO roll over the last half decade or so. >>Well, did you know that I became chief data officer in two thousand six? December two thousand and six And I have done this job four times four major overnight have created of the organization from scratch each time. Now, in December of two thousand six, when I became chief data officer, there were only four. Chief Data Officer, uh, boom and I was the first in health care, and there were three, three others, you know, one of the Internet one and credit guns one and banking. And I think I'm the only one actually left standing still doing this job. That's a good thing or a bad thing. But like, you know, it certainly has allowed me to love the craft and then also scripted down to the level that, you know, I actually do think of it purely as a craft. That is. I know, going into a mutual what I'm gonna do. They were on the central second. No, the interesting things that have unfolded. Obviously, the professions taken off There are literally thousands off chief data officers now, and there are plenty off changes. I think the main change, but the job is it's, I think, a little less daunting in terms off convincing the senior leadership that it's need it because I think the awareness at the CEO level is much, much, much better than what it waas in two thousand six. Across the world. Now, having said that, I think it is still only awareness and don't think that there's really a deep understanding of those levels. And so there's a lot off infusion, which is why you will. You kind of think this is my period. But you saw all these professions take off with C titles, right? Chief Data officer, chief analytics officer, chief digital officer and chief technology officer. See, I off course is being there for a long time. And but I think these newer see positions. They're all very, very related, and they all kind of went to the same need which had to do with enterprise transformation, digital transformation, that enterprises chief digital officer, that's another and and people were all trying to essentially feel the elephants and they could only see part of it at the senior levels, and they came up with which have a role you know, seemed most meaningful to them. But really, all of us are trying to do the same job, which is to accelerate digital transformation in the enterprise. Your comment about you kind of see that the seat eels and sea deals now, uh, partnering up much more than in the past, and I think that's in available the major driving force full. That is, in my view, anyway. It's is artificial intelligence as people try to infuse artificial intelligence. Well, then it's very technical field. Still, it's not something that you know you can just hand over to somebody who has the business jobs, but not the deep technical chops to pull that off. And so, in the case off chief data officers that do have the technical jobs, you'll see them also pretty much heading up the I effort in total and you know, as I do for the IBM case, will be building the Data and AI Enablement internal platform for for IBM. But I think in other cases you you've got Chief date officers who are coming in from a different angle. You know, they built Marghera but the CTO now, because they have to. Otherwise you cannot get a I infused into the organization. >>So there were a lot of other priorities, obviously certainly digital transformation. We've been talking about it for years, but still in many organisations, there was a sense of, well, not on my watch, maybe a sense of complacency or maybe just other priorities. Cove. It obviously has changed that now one hundred percent of the companies that we talked to are really putting this digital transformation on the front burner. So how has that changed the role of CDO? Has it just been interpolate an acceleration of that reality, or has it also somewhat altered the swim lanes? >>I think I think it's It's It's Bolt actually, so I have a way of looking at this in my mind, the CDO role. But if you look at it from a business perspective, they're looking for three things. The CEO is looking for three things from the CDO. One is you know this person is going to help with the revenue off the company by enabling the production of new products, new products of resulting in new revenue and so forth. That's kind of one aspect of the monetization. Another aspect is the CEO is going to help with the efficiency within the organization by making data a lot more accessible, as well as enabling insights that reduce into and cycle time for major processes. And so that's another way that they have monitor. And the last one is a risk reduction that they're going to reduce the risk, you know, as regulations. And as you have cybersecurity exposure on incidents that you know just keep keep accelerating as well. You're gonna have to also step in and help with that. So every CDO, the way their senior leadership looks at them is some mix off three. And in some cases, one has given more importance than the other, and so far, but that's how they are essentially looking at it now. I think what digital transformation has done is it's managed to accelerate, accelerate all three off these outcomes because you need to attend to all three as you move forward. But I think that the individual balance that's struck for individuals reveals really depends on their ah, their company, their situation, who their peers are, who is actually leading the transformation and so >>forth, you know, in the value pie. A lot of the early activity around CDO sort of emanated from the quality portions of the organization. It was sort of a compliance waited roll, not necessarily when you started your own journey here. Obviously been focused on monetization how data contributes to that. But But you saw that generally, organizations, even if they didn't have a CDO, they had this sort of back office alliance thing that has totally changed the the in the value equation. It's really much more about insights, as you mentioned. So one of the big changes we've seen in the organization is that data pipeline you mentioned and and cycle time. And I'd like to dig into that a little bit because you and I have talked about this. This is one of the ways that a chief data officer and the related organizations can add the most value reduction in that cycle time. That's really where the business value comes from. So I wonder if we could talk about that a little bit and how that the constituents in the stakeholders in that in that life cycle across that data pipeline have changed. >>That's a very good question. Very insightful questions. So if you look at ah, company like idea, you know, my role in totally within IBM is to enable Ibn itself to become an AI enterprise. So infuse a on into all our major business processes. You know, things like our supply chain lead to cash well, process, you know, our finance processes like accounts receivable and procurement that soulful every major process that you can think off is using Watson mouth. So that's the That's the That's the vision that's essentially what we've implemented. And that's how we are using that now as a showcase for clients and customers. One of the things that be realized is the data and Ai enablement spots off business. You know, the work that I do also has processes. Now that's the pipeline you refer to. You know, we're setting up the data pipeline. We're setting up the machine learning pipeline, deep learning blank like we're always setting up these pipelines, And so now you have the opportunity to actually turn the so called EI ladder on its head because the Islander has to do with a first You collected data, then you curated. You make sure that it's high quality, etcetera, etcetera, fit for EI. And then eventually you get to applying, you know, ai and then infusing it into business processes. And so far, But once you recognize that the very first the earliest creases of work with the data those themselves are essentially processes. You can infuse AI into those processes, and that's what's made the cycle time reduction. And although things that I'm talking about possible because it just makes it much, much easier for somebody to then implement ai within a lot enterprise, I mean, AI requires specialized knowledge. There are pieces of a I like deep learning, but there are, you know, typically a company's gonna have, like a handful of people who even understand what that is, how to apply it. You know how models drift when they need to be refreshed, etcetera, etcetera, and so that's difficult. You can't possibly expect every business process, every business area to have that expertise, and so you've then got to rely on some core group which is going to enable them to do so. But that group can't do it manually because I get otherwise. That doesn't scale again. So then you come down to these pipelines and you've got to actually infuse AI into these data and ai enablement processes so that it becomes much, much easier to scale across another. >>Some of the CEOs, maybe they don't have the reporting structure that you do, or or maybe it's more of a far flung organization. Not that IBM is not far flung, but they may not have the ability to sort of inject AI. Maybe they can advocate for it. Do you see that as a challenge for some CEOs? And how do they so to get through that, what's what's the way in which they should be working with their constituents across the organization to successfully infuse ai? >>Yeah, that's it's. In fact, you get a very good point. I mean, when I joined IBM, one of the first observations I made and I in fact made it to a senior leadership, is that I didn't think that from a business standpoint, people really understood what a I met. So when we talked about a cognitive enterprise on the I enterprise a zaydi em. You know, our clients don't really understand what that meant, which is why it became really important to enable IBM itself to be any I enterprise. You know that. That's my data strategy. Your you kind of alluded to the fact that I have this approach. There are these five steps, while the very first step is to come up with the data strategy that enables a business strategy that the company's on. And in my case, it was, Hey, I'm going to enable the company because it wants to become a cloud and cognitive company. I'm going to enable that. And so we essentially are data strategy became one off making IBM. It's something I enterprise, but the reason for doing that the reason why that was so important was because then we could use it as a showcase for clients and customers. And so But I'm talking with our clients and customers. That's my role. I'm really the only role I'm playing is what I call an experiential selling there. I'm saying, Forget about you know, the fact that we're selling this particular product or that particular product that you got GPU servers. We've got you know what's an open scale or whatever? It doesn't really matter. Why don't you come and see what we've done internally at scale? And then we'll also lay out for you all the different pain points that we have to work through using our products so that you can kind of make the same case when you when you when you apply it internally and same common with regard to the benefit, you know the cycle, time reduction, some of the cycle time reductions that we've seen in my process is itself, you know, like this. Think about metadata business metadata generating that is so difficult. And it's again, something that's critical if you want to scale your data because you know you can't really have a good catalogue of data if you don't have good business, meditate. Eso. Anybody looking at what's in your catalog won't understand what it is. They won't be able to use it etcetera. And so we've essentially automated business metadata generation using AI and the cycle time reduction that was like ninety five percent, you know, haven't actually argue. It's more than that, because in the past, most people would not. For many many data sets, the pragmatic approach would be. Don't even bother with the business matter data. Then it becomes just put somewhere in the are, you know, data architecture somewhere in your data leg or whatever, you have data warehouse, and then it becomes the data swamp because nobody understands it now with regard to our experience applying AI, infusing it across all our major business processes are average cycle time reduction is seventy percent, so just a tremendous amount of gains are there. But to your point, unless you're able to point to some application at scale within the enterprise, you know that's meaningful for the enterprise, Which is kind of what the what the role I play in terms of bringing it forward to our clients and customers. It's harder to argue. I'll make a case or investment into A I would then be enterprise without actually being able to point to those types of use cases that have been scaled where you can demonstrate the value. So that's extremely important part of the equation. To make sure that that happens on a regular basis with our clients and customers, I will say that you know your point is vomited a lot off. Our clients and customers come back and say, Tell me when they're having a conversation. I was having a conversation just last week with major major financial service of all nations, and I got the same point saying, If you're coming out of regulation, how do I convince my leadership about the value of a I and you know, I basically responded. He asked me about the scale use cases You can show that. But perhaps the biggest point that you can make as a CDO after the senior readership is can we afford to be left up? That is the I think the biggest, you know, point that the leadership has to appreciate. Can you afford to be left up? >>I want to come back to this notion of seventy percent on average, the cycle time reduction. That's astounding. And I want to make sure people understand the potential impacts. And, I would say suspected many CEOs, if not most understand sort of system thinking. It's obviously something that you're big on but often times within organisations. You might see them trying to optimize one little portion of the data lifecycle and you know having. Okay, hey, celebrate that success. But unless you can take that systems view and reduce that overall cycle time, that's really where the business value is. And I guess my we're real question around. This is Every organization has some kind of Northstar, many about profit, and you can increase revenue are cut costs, and you can do that with data. It might be saving lives, but ultimately to drive this data culture, you've got to get people thinking about getting insights that help you with that North Star, that mission of the company, but then taking a systems view and that's seventy percent cycle time reduction is just the enormous business value that that drives, I think, sometimes gets lost on people. And these air telephone numbers in the business case aren't >>yes, No, absolutely. It's, you know, there's just a tremendous amount of potential on, and it's it's not an easy, easy thing to do by any means. So we've been always very transparent about the Dave. As you know, we put forward this this blueprint right, the cognitive enterprise blueprint, how you get to it, and I kind of have these four major pillars for the blueprint. There's obviously does this data and you're getting the data ready for the consummation that you want to do but also things like training data sets. How do you kind of run hundreds of thousands of experiments on a regular basis, which kind of review to the other pillar, which is techology? But then the last two pillars are business process, change and the culture organizational culture, you know, managing organizational considerations, that culture. If you don't keep all four in lockstep, the transformation is usually not successful at an end to end level, then it becomes much more what you pointed out, which is you have kind of point solutions and the role, you know, the CEO role doesn't make the kind of strategic impact that otherwise it could do so and this also comes back to some of the only appointee of you to do. If you think about how do you keep those four pillars and lock sync? It means you've gotta have the data leader. You also gotta have the technology, and in some cases they might be the same people. Hey, just for the moment, sake of argument, let's say they're all different people and many, many times. They are so the data leader of the technology of you and the operations leaders because the other ones own the business processes as well as the organizational years. You know, they've got it all worked together to make it an effective conservation. And so the organization structure that you talked about that in some cases my peers may not have that. You know, that's that. That is true. If the if the senior leadership is not thinking overall digital transformation, it's going to be difficult for them to them go out that >>you've also seen that culturally, historically, when it comes to data and analytics, a lot of times that the lines of business you know their their first response is to attack the quality of the data because the data may not support their agenda. So there's this idea of a data culture on, and I want to ask you how self serve fits into that. I mean, to the degree that the business feels as though they actually have some kind of ownership in the data, and it's largely, you know, their responsibility as opposed to a lot of the finger pointing that has historically gone on. Whether it's been decision support or enterprise data, warehousing or even, you know, Data Lakes. They've sort of failed toe live up to that. That promise, particularly from a cultural standpoint, it and so I wonder, How have you guys done in that regard? How did you get there? Many Any other observations you could make in that regard? >>Yeah. So, you know, I think culture is probably the hardest nut to crack all of those four pillars that I back up and you've got You've got to address that, Uh, not, you know, not just stop down, but also bottom up as well. As you know, period. Appear I'll give you some some examples based on our experience, that idea. So the way my organization is set up is there is a obviously a technology on the other. People who are doing all the data engineering were kind of laying out the foundational technical elements or the transformation. You know, the the AI enabled one be planning networks, and so so that are those people. And then there is another senior leader who reports directly to me, and his organization is all around adoptions. He's responsible for essentially taking what's available in the technology and then working with the business areas to move forward and make this make and infuse. A. I do the processes that the business and he is looking. It's done in a bottom upwards, deliberately set up, designed it to be bottom up. So what I mean by that is the team on my side is fully empowered to move forward. Why did they find a like minded team on the other side and go ahead and do it? They don't have to come back for funding they don't have, You know, they just go ahead and do it. They're basically empowered to do that. And that particular set up enabled enabled us in a couple of years to have one hundred thousand internal users on our Central data and AI enabled platform. And when I mean hundred thousand users, I mean users who were using it on a monthly basis. We company, you know, So if you haven't used it in a month, we won't come. So there it's over one hundred thousand, even very rapidly to that. That's kind of the enterprise wide storm. That's kind of the bottom up direction. The top down direction Waas the strategic element that I talked with you about what I said, Hey, be our data strategy is going to be to create, make IBM itself into any I enterprise and then use that as a showcase for plants and customers That kind of and be reiterated back. And I worked the senior leadership on that view all the time talking to customers, the central and our senior leaders. And so that's kind of the air cover to do this, you know, that mix gives you, gives you that possibility. I think from a peer to peer standpoint, but you get to these lot scale and to end processes, and that there, a couple of ways I worked that one way is we've kind of looked at our enterprise data and said, Okay, therefore, major pillars off data that we want to go after data, tomato plants, data about our offerings, data about financial data, that s and then our work full student and then within that there are obviously some pillars, like some sales data that comes in and, you know, been workforce. You could have contractors. Was his employees a center But I think for the moment, about these four major pillars off data. And so let me map that to end to end large business processes within the company. You know, the really large ones, like Enterprise Performance Management, into a or lead to cash generation into and risk insides across our full supply chain and to and things like that. And we've kind of tied these four major data pillars to those major into and processes Well, well, yes, that there's a mechanism they're obviously in terms off facilitating, and to some extent one might argue, even forcing some interaction between teams that are the way they talk. But it also brings me and my peers much closer together when you set it up that way. And that means, you know, people from the HR side people from the operation side, the data side technology side, all coming together to really move things forward. So all three tracks being hit very, very hard to move the culture fall. >>Am I also correct that you have, uh, chief data officers that reporting to you whether it's a matrix or direct within the division's? Is that right? >>Yeah, so? So I mean, you know, for in terms off our structure, as you know, way our global company, we're also far flung company. We have many different products in business units and so forth. And so, uh, one of the things that I realized early on waas we are going to need data officers, each of those business units and the business units. There's obviously the enterprise objective. And, you know, you could think of the enterprise objectives in terms of some examples based on what I said in the past, which is so enterprise objective would be We've gotta have a data foundation by essentially making data along these four pillars. I talked about clients offerings, etcetera, you know, very accessible self service. You have mentioned south, so thank you. This is where the South seven speaks. Comes it right. So you can you can get at that data quickly and appropriately, right? You want to make sure that the access control, all that stuff is designed out and you're able to change your policies and you'd swap manual. But, you know, those things got implemented very rapidly and quickly. And so you've got you've got that piece off off the off the puzzle due to go after. And then I think the other aspect off off. This is, though, when you recognize that every business unit also has its own objectives and they are looking at some of those things somewhat differently. So I'll give you an example. We've got data any our product units. Now, those CEOs right there, concern is going to be a lot more around the products themselves And how were monetizing those box and so they're not per se concerned with, You know, how you reduce the enter and cycle time off IBM in total supply chain so that this is my point. So they but they're gonna have substantial considerations and objectives that they want to accomplish. And so I recognize that early on, and we came up with this notion off a data officer council and I helped staff the council s. So this is why that's the Matrix to reporting that we talked about. But I selected some of the key Blair's that we have in those units, and I also made sure they were funded by the unit. So they report into the units because their paycheck is actually determined. Pilot unit and which makes them than aligned with the objectives off the unit, but also obviously part of my central approach so that I can disseminate it out to the organization. It comes in very, very handy when you are trying to do things across the company as well. So when we you know GDP our way, we have to get the company ready for Judy PR, I would say that this mechanism became a key key aspect of what enabled us to move forward and do it rapidly. Trouble them >>be because you had the structure that perhaps the lines of business weren't. Maybe is concerned about GDP are, but you had to be concerned with it overall. And this allowed you to sort of hiding their importance, >>right? Because think of in the case of Jeannie PR, they have to be a company wide policy and implementation, right? And if he did not have that structure already in place, it would have made it that much harder. Do you get that uniformity and consistency across the company, right, You know, So you will have to in the weapon that structure, but we already have it because way said Hey, this is around for data. We're gonna have these types of considerations that they are. And so we have this thing regular. You know, this man network that meat meets regularly every month, actually, and you know, when things like GDP are much more frequently than that, >>right? So that makes sense. We're out of time. But I wonder if we could just close if you could address the M I t CDO audience that probably this is the largest audience, Believe or not, now that it's that's virtual definitely expanded the audience, but it's still a very elite group. And the reason why I was so pleased that you agreed to do this is because you've got one of the more complex organizations out there and you've succeeded. And, ah, a lot of the hard, hard work. So what? What message would you leave the M I t CDO audience Interpol? >>So I would say that you know, it's it's this particular professional. Receiving a profession is, uh, if I have to pick one trait of let me pick two traits, I think what is your A change agent? So you have to be really comfortable with change things are going to change, the organization is going to look to you to make those changes. And so that's what aspect off your job, you know, may or may not be part of me immediately. But the those particular set of skills and characteristics and something that you know, one has to, uh one has to develop or time, And I think the other thing I would say is it's a continuous looming jaw. So you continue sexism and things keep changing around you and changing rapidly. And, you know, if you just even think just in terms off the subject areas, I mean this Syria today you've got to understand technology. Obviously, you've gotta understand data you've got to understand in a I and data science. You've got to understand cybersecurity. You've gotta understand the regulatory framework, and you've got to keep all that in mind, and you've got to distill it down to certain trends. That's that's happening, right? I mean, so this is an example of that is that there's a trend towards more regulation around privacy and also in terms off individual ownership of data, which is very different from what's before the that's kind of weather. Bucket's going and so you've got to be on top off all those things. And so the you know, the characteristic of being a continual learner, I think is a is a key aspect off this job. One other thing I would add. And this is All Star Coleman nineteen, you know, prik over nineteen in terms of those four pillars that we talked about, you know, which had to do with the data technology, business process and organization and culture. From a CDO perspective, the data and technology will obviously from consent, I would say most covert nineteen most the civil unrest. And so far, you know, the other two aspects are going to be critical as we move forward. And so the people aspect of the job has never bean, you know, more important down it's today, right? That's something that I find myself regularly doing the stalking at all levels of the organization, one on a one, which is something that we never really did before. But now we find time to do it so obviously is doable. I don't think it's just it's a change that's here to stay, and it ships >>well to your to your point about change if you were in your comfort zone before twenty twenty two things years certainly taking you out of it into Parliament. All right, thanks so much for coming back in. The Cuban addressing the M I t CDO audience really appreciate it. >>Thank you for having me. That my pleasant >>You're very welcome. And thank you for watching everybody. This is Dave a lot. They will be right back after this short >>break. You're watching the queue.

>> Announcer: From Austin, Texas, it's theCUBE Covering Pure Storage Accelerate 2019. Brought to you by Pure Storage. >> Welcome back to theCUBE, Lisa Martin live on the Pure Accelerate floor in Austin, Texas. Dave Vellante is joining me and we're pleased to welcome a couple of guests from Core Scientific for the first time to theCUBE. We have Jim Benedetto, Chief Data Officer and John Curran, the SVP of Business Development. Gentlemen, welcome to theCUBE. >> Both: Thank you. >> Pleasure to be here. >> So John, we're going to start with you. Give our audience an overview of who Core Scientific is, what you guys do, what you deliver. >> Sure, well, we're a two year old start up. Headquartered out of Bellevue, Washington and we really focus on two primary businesses. We have a blockchain business and we have an AI business. In blockchain, we are one of the largest blockchain cryptocurrency hosting companies in North America. We've got facilities, four facilities in North Carolina, South Carolina, Georgia, and Kentucky. And really the business there is helping companies to be able to take advantage of blockchain and then position them for the future, you know. And then on the AI side of our business, really we operate that in two ways. One is we can also co-locate and host people, just like we do on the blockchain side. But primarily, we're focused on creating a public cloud focused on GPU centric computing and artificial intelligence and we're there to help really usher in the new age of AI. >> So you guys you founded, you said two years ago. >> Yes. >> From what I can tell you haven't raised a ton of dough. Is that true or are you guys quiet about that? >> John: We're very well capitalized. >> Okay, so it hasn't hit crunch base yet. >> Yeah, no. So we're a very well capitalized company. We've got, you know, to give you-- >> 'Cause what you do is not cheap. >> No, no, we've got about 675 megawatts of power under contract so each one of our facilities is about 50 megawatts plus in size. So no, it's not cheap. They're large installations and large build outs. >> And to even give you a comparison, a standard data center is about five to 10 megawatts. We won't even look at a facility or a plot of land unless we can supply at least 50 megawatts of power. >> So I was going to ask you kind of describe what's different between sort of blockchain hosting at conventional data bases or data centers. You kind of just did, but are there other sort of technical factors that you guys consider? >> Absolutely. We custom build our own data centers from the ground up. We've got patent pending technology, and if you look at virtually every data center in the world today, it's built with one thing at it's core and that's the CPU. The CPU is fundamentally different than the GPU and if you try to retrofit CPU based data centers for GPUs you're not going to fully maximize the performance and the capabilities of the GPU. So we build from the ground up data centers focused with the GPU at the center and not the CPU at the center. >> And is center in quotes because I mean, you have all this alternative processing, GPUs in particular that are popping up all over the place. As opposed to traditional CPU, which is, okay, just jam as much as I can on the real estate as possible, is that a factor? >> Well there's also a lot, the GPU at the center but there's also a lot of supporting infrastructure. So you got to look at first off the power density is very, very different. GPU, they require significantly a lot more power than CPUs do and then also just from a fluid dynamic prospective, it's very, the heating and cooling of them is again fundamentally different. You're not looking at standard hot, cold aisles and raised floors. But the overall goal also is to be able to provide a supporting infrastructure, which is from an AI ready design, is the interconnected networking and also the incredibly fast storage behind it. Because the name of the game with GPUs is different than with CPUs. With GPUs, the one thing you want to do is you want to get as much data into the GPU as fast as possible. Because compute will very rarely be your limiting factor with the GPU so the supporting infrastructure is significantly more important than it is when you're dealing with CPUs. >> So the standard narrative is, well, I don't know about cryptocurrency but the underlying technology of blockchain has a lot of potential. I personally think they're very much related and I wonder if you guys can comment on that. You started during the real, sort of the latest, most recent sort of big uptick, I know it's bounced back in cryptocurrency and so must you must've had a lot of activity in really, in your early days. And then maybe the crypto winter affected you, maybe it didn't. Some of those companies were so well capitalized, it was kind of their time to innovate, right? And yeah, there were some bad actors but that's really not the core of it. So I wonder what you guys have seen in the blockchain market. We'll get to AI and Pure and all that other stuff but this is a great topic, so I wonder if you could comment. >> So you know, yes, there's certainly classicality in the blockchain market, right? I think one of the key things is being well capitalized allows you to invest through the down turns to position to come out stronger as the market came out and you know, we've certainly seen that. Our growth in blockchain continues to really be substantial. And you know, we're making all the right strategic investments, right? Whether it's blockchain or AI, because you have such significant power requirements you know, you got to be very strategic about where you put the facilities. You're looking for facilities that have large sustained power capabilities, green. You know we've seen carbon taxes come in, that'll adversely affect folks. We want to make sure we're positioned for long term in terms of the capabilities. And then some geo political uncertainty is certainly affected, you know. The blockchain side of the business and it's driven more business to North America which has been fantastic for us. >> To me you're hosting innovation, you're talking blockchain and AI and like you're saying include crypto in there, you have some cryptocurrency guys, right? >> We do blockchain or cryptocurrency mining for ourselves as well. >> For yourselves, okay. But so my take on it is a whole new internet is being built and the crypto craze actually has funded a lot of that innovation. New protocol, when's the last time, the protocols of the internet, SMTP, HTDP, they're all government funded or education funded, academic institutions and the big internet companies sort of co-opted them. So you had a dirt of innovation, that's now come back. And you guys are hosting that innovation, that's kind of how I look at it. And I feel like we've seated the base and there's going to be this massive explosion of innovation, both in blockchain, crypto, AI automation and you're in the heart of it. >> Yeah I agree, I think cryptocurrencies or digital currencies are really just the first successful experiment of the blockchain and I agree with you, I think that is is as revolutionary and is going to change as many industries as the internet did and we're still very in a nascent stage of the technology but at Core, we're working to position ourselves to really be the underlying platform, almost like the alchemy of the early days of the internet. The underlying platform and the plumbing for both blockchain and AI applications. >> Right, whether it's smart contracts, like I say, new innovation, AI, it's all powering next generation of distributed apps. Really okay, so, sorry, I love this topic. >> I know you do. (laughs) >> Okay so where do these guys fit in? >> John: So do we. >> I mean, it's just so exciting. I think it's misunderstood. I mean the people who are into it are believers. I mean like myself, I really believe in a value store, I believe in smart contracts, immutability, you know, and I believe in responsibility too and that other good stuff but so. >> Innovation in private blockchain is just starting. If you look at it, I think there's going to be multiple waves in the blockchain side and we want to be there to make sure that we're helping power and position folks from both an infrastructure as well as a software perspective. >> Every financial institution, you got VMware doing stuff, Libra, I love Libra even though it's getting a lot of criticism, it just shined a light on the whole topic but bring us back to sort of commercial mainstream, what are you guys doing here, what's going on with Pure? >> So we have built, we're the first AI ready certified data center and we've actually partnered very closely with Pure and INVIDIA. As we went through the selection process of what type of storage we're going to be using to back our GPUs, we went through a variety of different evaluation criteria and Pure came out ahead and we've decided that we're going with Pure and we, again, for me it boils down to one thing as a Chief Data Officer is how much data can I get into those GPUs as fast as possible? And what you see is if you look at a existing, current Cloud providers, you'll see that their retro fitting CPU based centers for GPUs and you see a lot of problems with that where the storage that they provide is not fast enough to drive quote unquote warm or cold data into the GPUs so people end up adding more and more GPUs, it's actually just increased GPU memory when they're usually running around a couple percents, like one or two percent, five percent compute but you have to add more just for the memory because the storage is so slow. >> So you, how Jim you were saying before when we were chatting earlier, that you have had 20 years of experience looking at different storage vendors, working with them, what were some of the criteria, you talked about the speed and the performance, but in terms of, you also mentioned John that green was, is an important component of the way that you build data centers, where was Pure's vision on sustainability, ever green, where was that a factor in the decision to go with Pure? >> If you look at Pure's power density requirements and things like that, I think it's important. One thing that also, and this does apply from the sustainability perspective, where a lot of other storage vendors say that they're horizontally scalable forever but they're actually running different heads and in a variety of different ways. Pure is the only storage vendor that I've ever come across that is truly horizontally scalable. And when you start to try to build stuff like that you get into all the different things of super computing where you got, you know, split brain scenarios and fencing and it's very complex but their ability to scale horizontally with just, not even disc, but just the storage is something that was really important to us. >> I think the other thing that's certainly interesting for our customers is you're looking at important workloads that they're driving out and so the ability to do in place upgrades, business continuity, right, to make sure that we're able to deliver them technology that doesn't disrupt their business when their business needs the results, it's critically important so Pure is a great choice for us from that perspective and the innovations they're driving on that side of the business has really been helpful. >> I read a stat on the Pure website where users of Core Scientific infrastructure are seeing performance improvements of up to 800%. Are you delighting the heck out of data scientists now? >> Yeah, I mean. >> Are those the primary users? >> That is, it again references what we see with people using GPUs in the public Cloud. Again, going back to the thing that I keep hammering on, driving data into that GPU. We had one customer that had somewhere 14 or 15 GPUs running an analytics application in the public Cloud and we told them keep all your CPU compute in one of the largest Cloud providers but move just your GPU compute to us and they went from 14 or 15 GPUs down to two. GV-100 and a DGX-1 and backed by Pure Storage with Arista and from 14 GPUs to two GPUs, they saw an 800% in performance. >> Wow. >> And there's a really important additional part to that, let's say if I'm running a dashboard or running a query and a .5 second query gets an 800% increase in performance, how much do I really care? Now if I'm the guy running a 100 queries every single day, I probably do but it's not just that, it's the fact that it allows, it doesn't just speed up things, it allows you to look at data you were never able to look at before. So it's not just that they have an 800% performance increase, it's that instead of having tables with 100s of millions of rows, they now can have tables with billions of rows. So data that was previously not looked at before, data that was previously not turned into the actionable information to help drive their business, is now, they're now getting visibility into data they didn't have access to before. >> So you're a CDO that, it sounds like you have technical chops. >> Yeah, I'm a tech nerd at heart. >> It's kind rare actually for a CDO, I've interviewed a lot of CDOs and most of them are kind of come from a data quality background or a governance and compliance world, they don't dress like you (laughs) They dress like I do. (laughs) Even quite a bit better. But the reason I ask that, it sounds like you're a different type of CDO, like even a business like yours, I almost think you're a data scientist. So describe your role. >> I've actually held, I was with the company from the beginning so I've held quite a few roles actually. I think this might be my third title at this point. >> Okay. >> But in general, I'm a very technical person. I'm hands on, I love technology. I've held CTO titles in the past as well. >> Dave: Right. >> But I kind of, I've always been very interested in data and interested in storage because that's where data lives and it's a great fit for me. >> So I've always been interested in this because you know the narrative is that CDOs shouldn't be technical, they should be business and I get all that but the flip side of that is when you talk to CDOs about AI projects, which is you know, not digital transformation but specifically AI projects, they're not, most CDOs in healthcare, financial services, even government, they're not intimately involved, they're kind of like yeah, Chief Data Officer, we'll let you know when we have a data quality problem and I don't think that's right. I mean the CDO should be intimately involved. >> I agree. >> In those AI projects. >> I think a lot of times if you ask them, you ask, a lot of people, they'll say are you interested in deploying AI in your organization? And the answer is 100% yes and then the next follow up question is what would you like to do with it? And most of the time the answer is we don't know. I don't know. So what I have found is I go into organizations, I don't ask if people want to use AI, I ask what are your problems and I think what problems are you facing, what KPIs are you trying to optimize for and there are some of those problems, there are some problems on that list that might not be able to be helped by AI but usually there are problems on that list that can be helped by AI with the right data and the right place. >> So my translation of what you're asking is how can you make more money? (laughs) >> That what it comes down to. >> That's what you're asking, how can you cut costs or raise revenue, that's really ultimately what you're getting to. >> Data. >> Find new customers. I think the other interesting thing about our partnership with Pure and especially with regards to AIRE, AIRE's is an exciting technology but for a lot of companies is they're looking to get started in AI, there's almost this moment of pause, of how do I get started and then if I look at some of the greatest technology out there, it's like, okay, well now I have to retrofit my data center to get it in there, right. There's a bunch of technical barriers that slow down the progression and what we've been able to do with AIRE and the Cloud is really to be able to help people jumpstart, to get started right away. So rather than you know, let me think for six months or 12 months or 18 months on what would I analyze, start analyzing, get started and you can do it on a very cost effective outback's model as opposed to a capital intensive CAMP-X model. >> Alright, so I got to ask you. >> Yeah. >> And Pure will be pissed off I'm asking this question because you're talking about AIRE as a, it's real and I want some color on that but I felt like when the first announcement came out with Invida, it was rushed so that Pure could have another first. (laughs) Ink was drying, like we beat the competition but the way you're talking is AIRE is real, you're using it, it's a tangible solution. It's a value to your business. >> It's a core solution in our facility. >> Dave: It's a year ago. >> It's a core thing that we go to market with and it's something that you know, we're seeing customer demand to go out and really start to drive some business value. So you know, absolutely. >> A core component of helping them jumpstart that AI. Well you guys just, I think an hour or so ago, announced your new partnership level with Pure. John, take us away as we wrap here with the news please. >> Yeah, so well we're really excited. We're one of a handful of elite level MSP partners for Pure. I think there's only a few of us in the world so that's something and we're really the one who is focused on bringing ARIE to the Cloud and so it's a unique partnership. It's a deep partnership and it allows us to really coordinate our technical teams, our sales teams, you know, and be able to bring this technology across the industry and so we're excited, it's just the start but it's a great start and we're looking forward to nothing but upside from here. >> Fantastic, you'll have to come back guys and talk to us about a customer's who's done a jumpstart with ARIE and just taking the world by storm. So we thank you both for stopping by theCUBE. >> Absolutely, we'll love to do that. >> Lisa: Alright John, Jim, thank you so much for your time. >> Thank you. >> Absolutely. >> John: Really appreciate it. >> For Dave Vellante, I'm Lisa Martin, you're watching theCUBE from Pure Accelerate 2019. (upbeat techno music)

>> Live from San Francisco, California, it's theCUBE covering the IBM Chief Data Officers Summit, brought to you by IBM. >> Welcome back to San Francisco everybody. I'm Dave Vellante and you're watching theCUBE, the leader in live tech coverage. This is the end of the day panel at the IBM Chief Data Officer Summit. This is the 10th CDO event that IBM has held and we love to to gather these panels. This is a data all-star panel and I've recruited Seth Dobrin who is the CDO of the analytics group at IBM. Seth, thank you for agreeing to chip in and be my co-host in this segment. >> Yeah, thanks Dave. Like I said before we started, I don't know if this is a promotion or a demotion. (Dave laughing) >> We'll let you know after the segment. So, the data all-star panel and the data all-star awards that you guys are giving out a little later in the event here, what's that all about? >> Yeah so this is our 10th CDU Summit. So two a year, so we've been doing this for 5 years. The data all-stars are those people that have been to four at least of the ten. And so these are five of the 16 people that got the award. And so thank you all for participating and I attended these like I said earlier, before I joined IBM they were immensely valuable to me and I was glad to see 16 other people that think it's valuable too. >> That is awesome. Thank you guys for coming on. So, here's the format. I'm going to introduce each of you individually and then ask you to talk about your role in your organization. What role you play, how you're using data, however you want to frame that. And the first question I want to ask is, what's a good day in the life of a data person? Or if you want to answer what's a bad day, that's fine too, you choose. So let's start with Lucia Mendoza-Ronquillo. Welcome, she's the Senior Vice President and the Head of BI and Data Governance at Wells Fargo. You told us that you work within the line of business group, right? So introduce your role and what's a good day for a data person? >> Okay, so my role basically is again business intelligence so I support what's called cards and retail services within Wells Fargo. And I also am responsible for data governance within the business. We roll up into what's called a data governance enterprise. So we comply with all the enterprise policies and my role is to make sure our line of business complies with data governance policies for enterprise. >> Okay, good day? What's a good day for you? >> A good day for me is really when I don't get a call that the regulators are knocking on our doors. (group laughs) Asking for additional reports or have questions on the data and so that would be a good day. >> Yeah, especially in your business. Okay, great. Parag Shrivastava is the Director of Data Architecture at McKesson, welcome. Thanks so much for coming on. So we got a healthcare, couple of healthcare examples here. But, Parag, introduce yourself, your role, and then what's a good day or if you want to choose a bad day, be fun the mix that up. >> Yeah, sounds good. Yeah, so mainly I'm responsible for the leader strategy and architecture at McKesson. What that means is McKesson has a lot of data around the pharmaceutical supply chain, around one-third of the world's pharmaceutical supply chain, clinical data, also around pharmacy automation data, and we want to leverage it for the better engagement of the patients and better engagement of our customers. And my team, which includes the data product owners, and data architects, we are all responsible for looking at the data holistically and creating the data foundation layer. So I lead the team across North America. So that's my current role. And going back to the question around what's a good day, I think I would say the good day, I'll start at the good day. Is really looking at when the data improves the business. And the first thing that comes to my mind is sort of like an example, of McKesson did an acquisition of an eight billion dollar pharmaceutical company in Europe and we were creating the synergy solution which was based around the analytics and data. And actually IBM was one of the partners in implementing that solution. When the solution got really implemented, I mean that was a big deal for me to see that all the effort that we did in plumbing the data, making sure doing some analytics, is really helping improve the business. I think that is really a good day I would say. I mean I wouldn't say a bad day is such, there are challenges, constant challenges, but I think one of the top priorities that we are having right now is to deal with the demand. As we look at the demand around the data, the role of data has got multiple facets to it now. For example, some of the very foundational, evidentiary, and compliance type of needs as you just talked about and then also profitability and the cost avoidance and those kind of aspects. So how to balance between that demand is the other aspect. >> All right good. And we'll get into a lot of that. So Carl Gold is the Chief Data Scientist at Zuora. Carl, tell us a little bit about Zuora. People might not be as familiar with how you guys do software for billing et cetera. Tell us about your role and what's a good day for a data scientist? >> Okay, sure, I'll start by a little bit about Zuora. Zuora is a subscription management platform. So any company who wants to offer a product or service as subscription and you don't want to build your billing and subscription management, revenue recognition, from scratch, you can use a product like ours. I say it lets anyone build a telco with a complicated plan, with tiers and stuff like that. I don't know if that's a good thing or not. You guys'll have to make up your own mind. My role is an interesting one. It's split, so I said I'm a chief data scientist and we work about 50% on product features based on data science. Things like churn prediction, or predictive payment retries are product areas where we offer AI-based solutions. And then but because Zuora is a subscription platform, we have an amazing set of data on the actual performance of companies using our product. So a really interesting part of my role has been leading what we call the subscription economy index and subscription economy benchmarks which are reports around best practices for subscription companies. And it's all based off this amazing dataset created from an anonymized data of our customers. So that's a really exciting part of my role. And for me, maybe this speaks to our level of data governance, I might be able to get some tips from some of my co-panelists, but for me a good day is when all the data for me and everyone on my team is where we left it the night before. And no schema changes, no data, you know records that you were depending on finding removed >> Pipeline failures. >> Yeah pipeline failures. And on a bad day is a schema change, some crucial data just went missing and someone on my team is like, "The code's broken." >> And everybody's stressed >> Yeah, so those are bad days. But, data governance issues maybe. >> Great, okay thank you. Jung Park is the COO of Latitude Food Allergy Care. Jung welcome. >> Yeah hi, thanks for having me and the rest of us here. So, I guess my role I like to put it as I'm really the support team. I'm part of the support team really for the medical practice so, Latitude Food Allergy Care is a specialty practice that treats patients with food allergies. So, I don't know if any of you guys have food allergies or maybe have friends, kids, who have food allergies, but, food allergies unfortunately have become a lot more prevalent. And what we've been able to do is take research and data really from clinical trials and other research institutions and really use that from the clinical trial setting, back to the clinical care model so that we can now treat patients who have food allergies by using a process called oral immunotherapy. It's fascinating and this is really personal to me because my son as food allergies and he's been to the ER four times. >> Wow. >> And one of the scariest events was when he went to an ER out of the country and as a parent, you know you prepare your child right? With the food, he takes the food. He was 13 years old and you had the chaperones, everyone all set up, but you get this call because accidentally he ate some peanut, right. And so I saw this unfold and it scared me so much that this is something I believe we just have to get people treated. So this process allows people to really eat a little bit of the food at a time and then you eat the food at the clinic and then you go home and eat it. Then you come back two weeks later and then you eat a little bit more until your body desensitizes. >> So you build up that immunity >> Exactly. >> and then you watch the data obviously. >> Yeah. So what's a good day for me? When our patients are done for the day and they have a smile on their face because they were able to progress to that next level. >> Now do you have a chief data officer or are you the de facto CFO? >> I'm the de facto. So, my career has been pretty varied. So I've been essentially chief data officer, CIO, at companies small and big. And what's unique about I guess in this role is that I'm able to really think about the data holistically through every component of the practice. So I like to think of it as a patient journey and I'm sure you guys all think of it similarly when you talk about your customers, but from a patient's perspective, before they even come in, you have to make sure the data behind the science of whatever you're treating is proper, right? Once that's there, then you have to have the acquisition part. How do you actually work with the community to make sure people are aware of really the services that you're providing? And when they're with you, how do you engage them? How do you make sure that they are compliant with the process? So in healthcare especially, oftentimes patients don't actually succeed all the way through because they don't continue all the way through. So it's that compliance. And then finally, it's really long-term care. And when you get the long-term care, you know that the patient that you've treated is able to really continue on six months, a year from now, and be able to eat the food. >> Great, thank you for that description. Awesome mission. Rolland Ho is the Vice President of Data and Analytics at Clover Health. Tell us a little bit about Clover Health and then your role. >> Yeah, sure. So Clover is a startup Medicare Advantage plan. So we provide Medicare, private Medicare to seniors. And what we do is we're because of the way we run our health plan, we're able to really lower a lot of the copay costs and protect seniors against out of pocket. If you're on regular Medicare, you get cancer, you have some horrible accident, your out of pocket is infinite potentially. Whereas with Medicare Advantage Plan it's limited to like five, $6,000 and you're always protected. One of the things I'm excited about being at Clover is our ability to really look at how can we bring the value of data analytics to healthcare? Something I've been in this industry for close to 20 years at this point and there's a lot of waste in healthcare. And there's also a lot of very poor application of preventive measures to the right populations. So one of the things that I'm excited about is that with today's models, if you're able to better identify with precision, the right patients to intervene with, then you fundamentally transform the economics of what can be done. Like if you had to pa $1,000 to intervene, but you were only 20% of the chance right, that's very expensive for each success. But, now if your model is 60, 70% right, then now it opens up a whole new world of what you can do. And that's what excites me. In terms of my best day? I'll give you two different angles. One as an MBA, one of my best days was, client calls me up, says, "Hey Rolland, you know, "your analytics brought us over $100 million "in new revenue last year." and I was like, cha-ching! Excellent! >> Which is my half? >> Yeah right. And then on the data geek side the best day was really, run a model, you train a model, you get ridiculous AUC score, so area under the curve, and then you expect that to just disintegrate as you go into validation testing and actual live production. But the 98 AUC score held up through production. And it's like holy cow, the model actually works! And literally we could cut out half of the workload because of how good that model was. >> Great, excellent, thank you. Seth, anything you'd add to the good day, bad day, as a CDO? >> So for me, well as a CDO or as CDO at IBM? 'Cause at IBM I spend most of my time traveling. So a good day is a day I'm home. >> Yeah, when you're not in an (group laughing) aluminum tube. >> Yeah. Hurdling through space (laughs). No, but a good day is when a GDPR compliance just happened, a good day for me was May 20th of last year when IBM was done and we were, or as done as we needed to be for GDPR so that was a good day for me last year. This year is really a good day is when we start implementing some new models to help IBM become a more effective company and increase our bottom line or increase our margins. >> Great, all right so I got a lot of questions as you know and so I want to give you a chance to jump in. >> All right. >> But, I can get it started or have you got something? >> I'll go ahead and get started. So this is a the 10th CDO Summit. So five years. I know personally I've had three jobs at two different companies. So over the course of the last five years, how many jobs, how many companies? Lucia? >> One job with one company. >> Oh my gosh you're boring. (group laughing) >> No, but actually, because I support basically the head of the business, we go into various areas. So, we're not just from an analytics perspective and business intelligence perspective and of course data governance, right? It's been a real journey. I mean there's a lot of work to be done. A lot of work has been accomplished and constantly improving the business, which is the first goal, right? Increasing market share through insights and business intelligence, tracking product performance to really helping us respond to regulators (laughs). So it's a variety of areas I've had to be involved in. >> So one company, 50 jobs. >> Exactly. So right now I wear different hats depending on the day. So that's really what's happening. >> So it's a good question, have you guys been jumping around? Sure, I mean I think of same company, one company, but two jobs. And I think those two jobs have two different layers. When I started at McKesson I was a solution leader or solution director for business intelligence and I think that's how I started. And over the five years I've seen the complete shift towards machine learning and my new role is actually focused around machine learning and AI. That's why we created this layer, so our own data product owners who understand the data science side of things and the ongoing and business architecture. So, same company but has seen a very different shift of data over the last five years. >> Anybody else? >> Sure, I'll say two companies. I'm going on four years at Zuora. I was at a different company for a year before that, although it was kind of the same job, first at the first company, and then at Zuora I was really focused on subscriber analytics and churn for my first couple a years. And then actually I kind of got a new job at Zuora by becoming the subscription economy expert. I become like an economist, even though I don't honestly have a background. My PhD's in biology, but now I'm a subscription economy guru. And a book author, I'm writing a book about my experiences in the area. >> Awesome. That's great. >> All right, I'll give a bit of a riddle. Four, how do you have four jobs, five companies? >> In five years. >> In five years. (group laughing) >> Through a series of acquisition, acquisition, acquisition, acquisition. Exactly, so yeah, I have to really, really count on that one (laughs). >> I've been with three companies over the past five years and I would say I've had seven jobs. But what's interesting is I think it kind of mirrors and kind of mimics what's been going on in the data world. So I started my career in data analytics and business intelligence. But then along with that I had the fortune to work with the IT team. So the IT came under me. And then after that, the opportunity came about in which I was presented to work with compliance. So I became a compliance officer. So in healthcare, it's very interesting because these things are tied together. When you look about the data, and then the IT, and then the regulations as it relates to healthcare, you have to have the proper compliance, both internal compliance, as well as external regulatory compliance. And then from there I became CIO and then ultimately the chief operating officer. But what's interesting is as I go through this it's all still the same common themes. It's how do you use the data? And if anything it just gets to a level in which you become closer with the business and that is the most important part. If you stand alone as a data scientist, or a data analyst, or the data officer, and you don't incorporate the business, you alienate the folks. There's a math I like to do. It's different from your basic math, right? I believe one plus one is equal to three because when you get the data and the business together, you create that synergy and then that's where the value is created. >> Yeah, I mean if you think about it, data's the only commodity that increases value when you use it correctly. >> Yeah. >> Yeah so then that kind of leads to a question that I had. There's this mantra, the more data the better. Or is it more of an Einstein derivative? Collect as much data as possible but not too much. What are your thoughts? Is more data better? >> I'll take it. So, I would say the curve has shifted over the years. Before it used to be data was the bottleneck. But now especially over the last five to 10 years, I feel like data is no longer oftentimes the bottleneck as much as the use case. The definition of what exactly we're going to apply to, how we're going to apply it to. Oftentimes once you have that clear, you can go get the data. And then in the case where there is not data, like in Mechanical Turk, you can all set up experiments, gather data, the cost of that is now so cheap to experiment that I think the bottleneck's really around the business understanding the use case. >> Mm-hmm. >> Mm-hmm. >> And I think the wave that we are seeing, I'm seeing this as there are, in some cases, more data is good, in some cases more data is not good. And I think I'll start it where it is not good. I think where quality is more required is the area where more data is not good. For example like regulation and compliance. So for example in McKesson's case, we have to report on opioid compliance for different states. How much opioid drugs we are giving to states and making sure we have very, very tight reporting and compliance regulations. There, highest quality of data is important. In our data organization, we have very, very dedicated focus around maintaining that quality. So, quality is most important, quantity is not if you will, in that case. Having the right data. Now on the other side of things, where we are doing some kind of exploratory analysis. Like what could be a right category management for our stores? Or where the product pricing could be the right ones. Product has around 140 attributes. We would like to look at all of them and see what patterns are we finding in our models. So there you could say more data is good. >> Well you could definitely see a lot of cases. But certainly in financial services and a lot of healthcare, particularly in pharmaceutical where you don't want work in process hanging around. >> Yeah. >> Some lawyer could find a smoking gun and say, "Ooh see." And then if that data doesn't get deleted. So, let's see, I would imagine it's a challenge in your business, I've heard people say, "Oh keep all the, now we can keep all the data, "it's so inexpensive to store." But that's not necessarily such a good thing is it? >> Well, we're required to store data. >> For N number of years, right? >> Yeah, N number of years. But, sometimes they go beyond those number of years when there's a legal requirements to comply or to answer questions. So we do keep more than, >> Like a legal hold for example. >> Yeah. So we keep more than seven years for example and seven years is the regulatory requirement. But in the case of more data, I'm a data junkie, so I like more data (laughs). Whenever I'm asked, "Is the data available?" I always say, "Give me time I'll find it for you." so that's really how we operate because again, we're the go-to team, we need to be able to respond to regulators to the business and make sure we understand the data. So that's the other key. I mean more data, but make sure you understand what that means. >> But has that perspective changed? Maybe go back 10 years, maybe 15 years ago, when you didn't have the tooling to be able to say, "Give me more data." "I'll get you the answer." Maybe, "Give me more data." "I'll get you the answer in three years." Whereas today, you're able to, >> I'm going to go get it off the backup tapes (laughs). >> (laughs) Yeah, right, exactly. (group laughing) >> That's fortunately for us, Wells Fargo has implemented data warehouse for so many number of years, I think more than 10 years. So we do have that capability. There's certainly a lot of platforms you have to navigate through, but if you are able to navigate, you can get to the data >> Yeah. >> within the required timeline. So I have, astonished you have the technology, team behind you. Jung, you want to add something? >> Yeah, so that's an interesting question. So, clearly in healthcare, there is a lot of data and as I've kind of come closer to the business, I also realize that there's a fine line between collecting the data and actually asking our folks, our clinicians, to generate the data. Because if you are focused only on generating data, the electronic medical records systems for example. There's burnout, you don't want the clinicians to be working to make sure you capture every element because if you do so, yes on the back end you have all kinds of great data, but on the other side, on the business side, it may not be necessarily a productive thing. And so we have to make a fine line judgment as to the data that's generated and who's generating that data and then ultimately how you end up using it. >> And I think there's a bit of a paradox here too, right? The geneticist in me says, "Don't ever throw anything away." >> Right. >> Right? I want to keep everything. But, the most interesting insights often come from small data which are a subset of that larger, keep everything inclination that we as data geeks have. I think also, as we're moving in to kind of the next phase of AI when you can start doing really, really doing things like transfer learning. That small data becomes even more valuable because you can take a model trained on one thing or a different domain and move it over to yours to have a starting point where you don't need as much data to get the insight. So, I think in my perspective, the answer is yes. >> Yeah (laughs). >> Okay, go. >> I'll go with that just to run with that question. I think it's a little bit of both 'cause people touched on different definitions of more data. In general, more observations can never hurt you. But, more features, or more types of things associated with those observations actually can if you bring in irrelevant stuff. So going back to Rolland's answer, the first thing that's good is like a good mental model. My PhD is actually in physical science, so I think about physical science, where you actually have a theory of how the thing works and you collect data around that theory. I think the approach of just, oh let's put in 2,000 features and see what sticks, you know you're leaving yourself open to all kinds of problems. >> That's why data science is not democratized, >> Yeah (laughing). >> because (laughing). >> Right, but first Carl, in your world, you don't have to guess anymore right, 'cause you have real data. >> Well yeah, of course, we have real data, but the collection, I mean for example, I've worked on a lot of customer churn problems. It's very easy to predict customer churn if you capture data that pertains to the value customers are receiving. If you don't capture that data, then you'll never predict churn by counting how many times they login or more crude measures of engagement. >> Right. >> All right guys, we got to go. The keynotes are spilling out. Seth thank you so much. >> That's it? >> Folks, thank you. I know, I'd love to carry on, right? >> Yeah. >> It goes fast. >> Great. >> Yeah. >> Guys, great, great content. >> Yeah, thanks. And congratulations on participating and being data all-stars. >> We'd love to do this again sometime. All right and thank you for watching everybody, it's a wrap from IBM CDOs, Dave Vellante from theCUBE. We'll see you next time. (light music)

>> Live from Boston, it's theCUBE! Covering IBM Chief Data Officers Summit. Brought to you by IBM. >> Welcome back to theCUBE's live coverage of the IBM CDO Summit here in Boston, Massachusetts. I'm your host Rebecca Knight, along with my co-host Paul Gillin. We're joined by Inderpal Bhandari, he is the Global Chief Data Officer at IBM. Thank you so much for coming back on theCUBE, Inderpal. >> It's my pleasure. >> It's great to have you. >> Thank you for having me. >> So I want to talk, I want to start by talking a little bit about your own career journey. Your first CDO job was in the early 2000s. You were one of the first CDOs, ever. In the history of Chief Data Officers. Talk a little bit about the evolution of the role and sort of set the scene for our viewers in terms of what you've seen, in your own career. >> Yes, no thank you, December 2006, I became a Chief Data Officer of a major healthcare company. And you know, it turned out at that time there were only four of us. Two in banking, one in the internet, I was the only one in healthcare. And now of course there are well over 1,999 of us and the professions taken off. And I've had the fortune of actually doing this four times now. So leading a legacy in four different organizations in terms of building that organizational capability. I think initially, when I became Chief Data Officer, the culture was one of viewing data's exhaust. Something that we had to discard, that came out of the transactions that you were, that your business was doing. And then after that you would discard this data, or you didn't really care about it. And over the course of time, people had begun to realize that data is actually a strategic asset and you can really use it to drive not just the data strategy, but the actual business strategy, and enable the business to go to the next level. And that transitions been tremendous to watch and to see. I've just been fortunate that I've been there for the full journey. >> Are you seeing any consensus developing around what background makes for a good CDO? What are the skills that a CDO needs? >> Yeah, no that's a very, very good question. My view has been evolving on that one too, over the last few years, right, as I've had these experiences. So, I'll jump to the conclusion, so that you kind of, to answer your question as opposed to what I started out with. The CDO, has to be the change agent in chief, for the organization. That's really the role of the CDO. So yes, there's the technical sharps that you have to have and you have to be able to deal with people who have advanced technical degrees and to get them to move forward. But you do have to change the entire organization and you have to be adept at going after the culture, changing it. You can't get frustrated with all the push back, that's inevitable. You have to almost develop it as an art, as you move forward. And address it, not just bottom up and lateral, but also top down. And I think that's probably where the art gets the most interesting. Because you've got to push a for change even at the top. But you can push just so far without really derailing everything that you are trying to do. And so, I think if I have to pick one attribute, it would be that the CDO has to be the change agent in chief and they have to be adept at addressing the culture of the organization, and moving it forward. >> You're laying out all of these sort of character traits that someone has to be indefatigable, inspirational, visionary. You also said during the keynote you have six months to really make your first push, the first six months are so important. When we talk about presidents, it's the first 100 days. Describe what you mean by that, you have six months? >> So if a new, and I'm talking here mainly about a large organization like an IBM, a large enterprise. When you go in, the key observation is it's a functioning organization. It's a growing concern. It's already making money, it's doing stuff like that. >> We hope. >> And the people who are running that organization, they have their own needs and demands. So very quickly, you can just become somebody who ends up servicing multiple demands that come from different business units, different people. And so that's kind of one aspect of it. The way the organization takes over if you don't really come in with an overarching strategy. The other way the organizations take over is typically large organizations are very siloed. And even at the lower levels you who have people who developed little fiefdoms, where they control that data, and they say this is mine, I'm not going to let anybody else have it. They're the only one's who really understand that curve. And so, pretty much unless you're able to get them to align to a much larger cause, you'll never be able to break down those silos, culturally. Just because of the way it's set up. So its a pervasive problem, goes across the board and I think, when you walk in you've got that, you call it honeymoon period, or whatever. My estimate is based on my experience, six months. If you don't have it down in six months, in terms of that larger cause that your going to push forward, that you can use to at least align everybody with the vision, or you're not going to really succeed. You'll succeed tactically, but not in a strategic sense. >> You're about to undertake the largest acquisition in IBM's history. And as the Chief Data Officer, you must be thinking right now about what that's going to mean for data governance and data integration. How are you preparing for an acquisition that large? >> Yeah so, the acquisition is still got to work through all the regulations, and so forth. So there's just so much we can do. It's much more from a planning stand point that we can do things. I'll give you a sense of how I've been thinking about it. Now we've been doing acquisitions before. So in that since we do have a set process for how we go about it, in terms of evaluating the data, how we're going to manage the data and so forth. The interesting aspect that was different for me on this one is I also talked back on our data strategy itself. And tried to understand now that there's going to be this big acquisition of move forward, from a planning standpoint how should I be prepared to change? With regard to that acquisition. And because we were so aligned with the overall IBM business strategy, to pursue cognition. I think you could see that in my remarks that when you push forward AI in a large enterprise, you very quickly run into this multi-cloud issue. Where you've got, not just different clouds but also unprime and private clouds, and you have to manage across all that and that becomes the pin point that you have to scale. To scale you have to get past that pin point. And so we were already thinking about that. Actually, I just did a check after the acquisition was announced, asking my team to figure out well how standardized are we with Red Hat Linux? And I find that we're actually completely standardized across with Red Hat Linux. We pretty much will have use cases ready to go, and I think that's the facet of the goal, because we were so aligned with the business strategy to begin with. So we were discovering that pinpoint, just as all our customers were. And so when the cooperation acted as it did, in some extent we're already ready to go with used cases that we can take directly to our clients and customers. I think it also has to do with the fact that we've had a partnership with Red Hat for some time, we've been pretty strategic. >> Do you think people understand AI in a business context? >> I actually think that that's, people don't really understand that. That's was the biggest, in my mind anyway, was the biggest barrier to the business strategy that we had embarked on several years ago. To take AI or cognition to the enterprise. People never really understood it. And so our own data strategy became one of enabling IBM itself to become an AI enterprise. And use that as a showcase for our clients and customers, and over the journey in the last two, three years that I've been with IBM. We've become more, we've been putting forward more and more collateral, but also technology, but also business process change ideas, organizational change ideas. So that our clients and customers can see exactly how it's done. Not that i'ts perfect yet, but that too they benefit from, right? They don't make the same mistakes that we do. And so we've become, your colleagues have been covering this conference so they will know that it's become more and more clear, exactly what we're doing. >> You made an interesting comment, in the keynote this morning you said nobody understands AI in a business context. What did you mean by that? >> So in a business context, what does it look like? What does AI look like from an AI enterprise standpoint? From a business context. So excuse me I just trouble them for a tissue, I don't know why. >> Okay, alright, well we can talk about this a little bit too while he-- >> Yeah, well I think we understand AI as an Amazon Echo. We understand it as interface medium but I think what he was getting at is that impacting business processes is a lot more complicated. >> Right. >> And so we tend to think of AI in terms of how we relate to technology rather than how technology changes the rules. >> Right and clearly its such, on the consumers side, we've all grasped this and we all are excited by its possibilities but in terms of the business context. >> I'm back! >> It's the season, yes. >> Yeah, it is the season, don't want to get in closer. So to your question with regard to how-- >> AI in a business context. >> AI in a business context. Consumer context everybody understands, but in a business context what does it really mean? That's difficult for people to understand. But eventually it's all around making decisions. But in my mind its not the big decisions, it's not the decisions we going to acquire Red Hat. It's not those decisions. It's the thousands and thousands of little decisions that are made day in and night out by people who are working the rank and file who are actually working the different processes. That's what we really need to go after. And if you're able to do that, it completely changes the process and you're going to get just such a lot more out of it, not just terms of productivity but also in terms of new ideas that lead to revenue enhancement, new products, et cetera, et cetera. That's what a business AI enterprise looks like. And that's what we've been bringing forward and show casing. In today's keynote I actually had Sonya, who is one of our data governance people, SMEs, who works on metadata generation. Really a very difficult manual problem. Data about data, specifically labeling data so that a business person could understand it. Its all been done manually but now it's done automatically using AI and its completely changed the process. But Sonya is the person who's at the forefront of that and I don't think people really understand that. They think in terms of AI and business and they think this is going to be somebody who's a data scientist, a technologist, somebody who's a very talented technical engineer, but it's not that. It's actually the rank and file people, who've been working these business processes, now working with an intelligent system, to take it to the next level. >> And that's why as you've said it's so important that the CDO is a change agent in chief. Because it is, it does require so much buy-in from, as you say, the rank and file, its not just the top decision makers that you're trying to persuade. >> Yes, you are affecting change at all levels. Top down, bottom up, laterally. >> Exactly. >> You have to go after it across the board. >> And in terms of talking about the data, it's not just data for data's sake. You need to talk about it in terms that a business person can understand. During the keynote, you described an earlier work that you were doing with the NBA. Can you tell our viewers a little bit about that? And sort of how the data had to tell a story? >> Yes, so that was in my first go 'round with IBM, from 1990 through '97. I was with IBM Research, at the Watson Research Lab, as a research staff member. And I created this program called Advanced Scout for the National Basketball Association. Ended up being used by every team on the NBA. And it would essentially suggest who to put in the line up, when you're matching lines up and so forth. By looking at a lot of game data and it was particularly useful during the Playoff games. The major lesson that came out of that experience for me, at that time, alright, this was before Moneyball, and before all this stuff. I think it was like '90, '93, '92. I think if you Google it you will still see articles about this. But the main lesson that came out for me was the first time when the program identified a pattern and suggested that to a coach during a playoff game where they were down two, zero, it suggested they start two backup players. And the coach was just completely flabbergasted, and said there's no way I'm going to do this. This is the kind of thing that would not only get me fired, but make me look really silly. And it hit me then that there was context that was missing, that the coach could not really make a decision. And the way we solved it then was we tied it to the snippets of video when those two players were on call. And then they made the decision that went on and won that game, and so forth. Today's AI systems can actually fathom all that automatically from the video itself. And I think that's what's really advanced the technology and the approaches that we've got today to move forward as quickly as they have. And they've taken hold across the board, right? In the sense of a consumer setting but now also in the sense of a business setting. Where we're applying it pretty much to every business process that we have. >> Exciting. Well Inderpal, thank you so much for coming back on theCUBE, it was always a pleasure talking to you. >> It's my pleasure, thank you. >> I'm Rebecca Knight for Paul Gillin, we will have more from theCUBE's live coverage of IBM CDO coming up in just a little bit. (upbeat music)

>> Narrator: Live, from downtown San Francisco. It's theCUBE. Covering IBM Chief Data Officer Strategy Summit 2018. Brought to you by IBM. (techno music) >> Welcome back to San Francisco everybody. You're watching theCUBE, the leader in live tech coverage. My name is Dave Vellante. And we are here at the IBM CDO Strategy Summit hashtag IBMCDO. Caitlin Halferty is here. She's a client engagement executive for the chief data officer at IBM. Caitlin great to see you again. >> Great to be here, thank you. >> And she's joined by Brandon Purcell, who's principal analyst at Forrester Research. Good to have you on. >> Thanks very much, thanks for having me. >> First time on theCUBE. >> Yeah. >> You're very welcome. >> I'm a newbie. >> Caitlin... that's right, you're a newbie. You'll be a Cube alum in no time, I promise you. So Caitlin let's start with you. This is, you've done a number of these CDO events. You do some in Boston, you do some in San Francisco. And it's really great to see the practitioners here. You guys are bringing guys like Inderpal to the table. You've announced your blueprint in it. The audience seems to be lapping up the knowledge transfer. So what's the purpose of these events? How has it evolved? And just set the table for us. >> Sure, so we started back in 2014 with our first Chief Data Officer Summit and we held that here in San Francisco. Small group, probably only had about 30 or 40 attendees. And we said let's make this community focused, peer to peer networking. We're all trying to, ya know, build the role of either the Chief Data Officer or whomever is responsible for enterprise wide data strategy for their company, a variety of different titles. And we've grown that event over, since 2014. We do Spring, in San Francisco, which tends to be a bit more on the technical side, given where we are here in San Francisco in Silicon Valley. And then we do our business focused sessions in Fall in Boston. And I have to say, it's been really nice to see the community grow from a small set of attendees. And now was are at about 130 that join us on each coast. So we've built a community in total of about 500 CDOs and data executives, >> Nice. that are with us on this journey, so they're great. >> And Brandon, your focus at Forrester, part of it is AI, I know you did some other things in analytics, the ethics of AI, which we're going to talk about. I have to ask you from Forrester's perspective, we're enter... it feels like we're entering this new era of there's digital, there's data, there's AI. They seem to all overlap. What's your point of view on all this? >> So, I'm extremely optimistic about the future of AI. I realize that the term artificial intelligence is incredibly hyped right now. But I think it will ultimately fulfill it's promise. If you think about the life cycle of analytics, analytics start their lives as customer data. As customers interact and transact with you, that creates a foot print that you then have to analyze to unleash some sort of insight. This customer's likely to buy, or churn, or belongs to a specific segment. Then you have to take action. The buzzwords of the past have really focused on one piece of that life cycle. Big data, the data piece. Not much value unless you analyze that. So then predictive analytics, machine learning. What AI promises to do is to synthesize all of those pieces, from data, to insights, to action. And continuously learn and optimize. >> It's interesting you talk about that in terms of customer churn. I mean, with the internet, there was like a shift in the balance of power to the consumer. There used to be that the brand had all the knowledge about the buyer. And then with the internet, we shop around, we walk into a store and, look at them. Then we go buy it on the internet right? Now that AI maybe brings back more balance, symmetry. I mean, what are your thoughts on that? Are the clients that you work with, trying to sort of regain that advantage? So they can better understand the customer. >> Yeah, well that's a great question. I mean, if there's one kind of central ethos to Forrester's research it's that we live in the age of the customer and understanding and anticipating customer needs is paramount to be able to compete, right? And so it's the businesses in the age of AI and the age of the customer that have the data on the customer and enable the ability to distill that into insights that will ultimately succeed. And so the companies that have been able to identify the right value exchange with consumers, to give us a sense of convenience, so that we're willing to give up enough personal data to satisfy that convenience are the ones that I think are doing well. And certainly Netflix and Amazon come to mind there. >> Well for sure, and of course that gets into the privacy and the ethics of AI. I mean everyone's making a big deal out of this. You own your data. >> Yeah. >> You're not trying to monetize, ya know, figure out which ad to click on. Maybe give us your perspective, Caitlin, on IBMs point of view there? >> Sure, so we lead with this thought around trusting your data. You're data's your data. Insights derive from that data, your insights. We spend a lot of time with our Watson Legal folks. And one of the things, pieces of material we've released today is the real detail at every level how you engage the traceability of where your data is. So you have a sense of confidence that you know how it's treated, how it's curated. If it's used in some third party fashion. The ability to know that, have visibility into it. The opt-out, opt-in opt-out set of choices. Making sure that we're not exploiting the network effect, where perhaps party C benefits from data exchange between A and B. That A and B do not, or do not have an opportunity to influence. And so what we wanted to do, here at the summit over the next couple of days is really share that in detail and our thoughts around it. And it comes back to trust and being able to have that viability and traceability of your data through the value chain. >> So of course Brandon, as a customer I'm paying IBM so I would expect that IBM would look out for my privacy and make that promise. I don't really pay Facebook right? But I get some value out of it. So what are the ethics of that? Is it a pay or no pay? Or is it a value or no value? Is it everybody really needs to play by the same rules? How to you parse all that? >> Ya know, I hate to use a vague term. But it's a reasonable expectation. Like I think that when a person interacts with Facebook, there is a reasonable expectation that they're not going to take that data and sell it or monetize it to some third party, like Cambridge Analytica. And that's where they dropped the ball in that case. But, that's just in the actual data collection itself. There's also, there are also inherent ethical issues in how the data is actually transformed and analyzed. So just because you don't have like specific characteristics or attributes in data, like race and gender and age and socioeconomic status, in a multidimensional data set there are proxies for those through something called redundant encoding. So even if you don't want to use those factors to make decisions, you have to be very careful because they're probably in there anyway. And so you need to really think about what are your values as a brand? And when can you actually differentiate treatment, based on different attributes. >> Because you can make accurate inferences from that. >> Brandon: Yeah you're absolutely (mumbles). >> And is it the case of actually acting on that data? Or actually the ability to act on that data? If that makes sense to you. In other words, if an organization has that data and could, in theory, make the inference, but doesn't. Is that crossing the line? Is it the responsibility of the organization to identify those exposures and make sure that they can not be inferred? >> Yeah, I think it is. I think that that is incumbent upon our organizations today. Eventually regulators are going to get around to writing rules around this. And there's already some going into effect of course in Europe, with GDPR at the end of this month. But regulators are usually slow to catch up. So for now it's going to have to be organizations that think about this. And think about, okay, when is it okay to treat different customers differently? Because if we, if we break that promise, customers are going to ultimately leave us. >> That's a hard problem. >> Right, right. >> You guys have a lot of these discussions internally? >> We do. >> And can you share those with us? >> Yeah, absolutely, we do. And we get a lot of questions. We often engage at the data strategy perspective. And it starts with, hey we've got great activity occurring in our business units, in our functional areas, but we don't really have a handle on the enterprise wide data strategy. And at that point we start talking about trust, and privacy, and security, and what is your what does your data flows look like. So it starts at that initial data strategy discussion. And one other thing I mentioned in my opening remarks this morning is, we released this blueprint and it's intended, as you said, to put a framework in process and reflect a lot of the lessons learned that we're all going through. I know you mentioned that many companies are looking at AI adoption, perhaps more so than we realized. And so the framework was intended to help accelerate that process. And then our big announcement today has been around the showcases, in particular our platform showcase. So it's really the platform we've built, within our organization. The components, the products, the capabilities that drives for us. And then with the intent of hopefully being, illustrative and helpful to clients that are looking to build similar capabilities. >> So let's talk about adoption. >> Brandon: Yeah, sure. >> Ya know, we... you often hear this bromide that we live in a world where, that pace of change is so fast. And things are changing so quickly it's hard to deny that. But then when you look at adoption of some of the big themes in our time. Whether it's big data or AI, digital, block chains, there are some major barriers to adoption. So you see them adopted in pockets. What's your perspective, and Forrester's perspective on adoption of, let's call it machine intelligence? >> Yeah, sure, so I mean, every year Forrester does a global survey of business and technology decision leaders called Business Technographics. And we ask folks about adoptions rates of certain technologies. And so when it comes to AI, globally, 52% of companies have adopted AI in some way. And another 20% plan to in the next 12 months. What's interesting to me, actually, is when you break that down geographically, the highest adoption rate, 60 plus percent, is in APAC, followed by North America, followed by Europe. And when you think about the privacy regulations in each of those geographies, well there are far fewer in APAC than there are, and will be, in Europe. And that's, I think kind of hamstringing adoption in that geography. Now is that a problem for Europe? I don't think so actually. I think AI, the way AI is going to be adopted in Europe is going to be more refined and respectful of customers' intrinsic right to privacy. >> Dave: Ya know I want... Go ahead. >> I've got to, I have to say Dave, I have to put a plug in. I've been a huge fan of Brandon's, for a long time. I've actually, ya know, a few years now of his research. And some of the research that you're mentioning, I hope people are reading it. Because we find these reports to be really helpful to understand, as you said, the specifics of adoptions, the trends. So I've got to put a plug in there. >> Thanks Caitlin. >> Because, the quality of the work and the insights are incredible. So that is why I was quite excited when Brandon accepted our offer to join us here in this session. >> Awesome. Yeah, so, let's dig into that a little bit. >> Brandon: Sure. >> So it seems like, so 52%, I'm wondering, what the other 48 are doing? They probably are, and they just don't know it. So it's possible that the study looks at, a strategy to adopt, presumably. I mean actively adopting. But it seems, I wonder if I could run this by you, get your comment. It seems that people will, organizations will more likely be buying AI as embedded in applications or systems or just kind of invisible. Then they won't necessarily be building it. I know many are trying to probably build it today. And what's your thought on that? In terms of just AI infused everywhere? >> So the first foray for most enterprises into this world of AI is chat bots for customer service. >> Dave: Sure. >> I mean we get a ton of inquires at Forrester about that. And there are a number of solutions. Ya know, IBM certainly has one for, that fulfill that need. And that's a very narrow use case, right? And it's also a value added of use case. If you can take more of those call center agents out of the loop, or at least accelerate or make them better at their jobs, then you're going to see efficiency gains. But this isn't this company wide AI transformation. It's just one very narrow use case. And usually that's, most elements of that are pre-built. We talked this morning, or the speakers this morning talked about commoditization of certain aspects of machine learning and AI. And it's very true. I mean, machine learning algorithms, many of them have been around for a long time, and you can access them for multiple different platforms. Even natural language processing, which a few years ago was highly inaccurate, is getting really, really accurate. So when, in a world where all of these things are commoditized, it's going to end up being how you implement them that's going to drive differentiation. And so, I don't think there's any problem with buying solutions that have been pre-built. You just have to be very thoughtful about how you use them to ultimately make decisions that impact the customer experience. >> I want to, in the time we have remaining, I want to get into the tech radar, the sort of taxonomy of AI or machine intelligence. You've done some work here. How do you describe, can you paint a picture, for what that taxonomy looks like? >> So I think most people watching realize AI is not one specific thing right? It's a bunch of components, technologies that stitched together lead to something that can emulate certain things that humans do, like sense the world around us, see, read, hear, that can think or reason. That's the machine learning piece. And that can then take action. And that's the kind of automation piece. And there are different core technologies that make up each of those faculties. The kind of emerging ones are deep learning. Of course you hear about it all the time. Deep learning is inherently the use of artificial neural networks, usually to take some unstructured data, let's say pictures of cats, and identify this is actually a cat right? >> Who would have thought? That we're led to this boom right? >> Right exactly. That was something you couldn't do five or six years ago, right? You couldn't actually analyze picture data like you analyze row and column data. So that's leading to a transformation. The problem there is that not a lot of people have this massive number of pictures of cats that are consistently and accurately labeled cat, not cat, cat, not cat. And that's what you need to make that viable. So a lot of vendors, and Watson has an API for this have already trained a deep neural network to do that so the enterprises aren't starting from scratch. And I think we'll see more and more of these kind of pre-trained solutions and companies gravitating towards the pre-trained solutions. And looking for differentiation, not in the solutions themselves, but again how they actually implement it to impact the customer experience. >> Hmmm, well that's interesting, just hearing you sense, see, read, hear, reason, act. These are words that describe not the past era. This is a new era that we're entering. We're in the cloud era now. We can sort of all agree with that. But these, the cloud doesn't do these things. We are clearly entering a new wave. Maybe it's driven by Watson's Law, or whatever holds out. Caitlin I'll give you the last word. Put a bumper sticker on this event, and where we're at here in 2018? >> I'll say, it's interesting to watch the themes evolve over the last few years. Ya know, we started with sort of a defensive posture. Most of our data executives were coming perhaps from an IT type background. We see a lot more with line of business, and chief operations type role. And we've seen the, we still king of the data warehouse, that's sort of how we described at the time. And now, I see our data leaders really driving transformation. They're responsible for both the data as well as the digital transformation. On the data side, it's the AI focus. And trying to really understand the deep learning capabilities, machine learning, that they're bringing to bear. So it's been, for me, it's been really interesting to see the topics evolve, see the role in the strategic piece of it. As well as see these guys elevated, in terms of influence within their organization. And then, our big topic this year was around AI and understanding it. And so, having Brandon to share his expertise was very exciting for me because, he's our lead analyst in the AI space. And that's what our attendees are telling us. They want to better understand, and better understand how to take action to implement and see those business results. So I think we're going to continue to see more of that. And yeah, it's been great to see, great to see it evolve. >> Well congratulations on taking the lead, this is a very important space. Ya know, a lot of people didn't really believe in it early on, thought the Chief Data Officer role would just sort of disappear. But you guys, I think, made the right investment and a good call, so congratulations on that. >> I was laughed out of the room when I proposed, I said hey we're hearing of this, doing a market scan of Chief Data Officer, either by title or something similar, titled responsible for enterprise wide data. I was laughed out of the room. I said let me do a qualitative piece. Let me interview 20 and just show, and then you're right, it was the thought was, role's going to go by the wayside. And I think we've seen the opposite. >> Oh yeah, absolutely. >> Data has grown in importance. The associative capabilities have grown. And I'm seeing these individuals, their scope, their sphere of responsibility really grow quite a bit. >> Yeah Forrester's tracked this. I mean, you guys I think just a few years ago was like eh, yeah 20% of organizations have a Chief Data Officer and now it's much much higher than that. >> Yeah, yeah, it's approaching 50%. >> Yeah, so, good. Alright Brandon, Caitlin, thanks very much for coming on theCUBE. >> Thanks for having us. >> Thank you, it was great. >> Keep it right there everybody. We'll be back, at the IBM Chief Data Officer Strategy Summit. You're watching theCUBE. (techno music) (telephone tones)

>> Announcer: Live from downtown San Francisco, it's theCUBE covering IBM Chief Data Officer Strategy Summit, 2018, brought to you by IBM. (techno music) >> Welcome to San Francisco everybody. My name is Dave Vellante and you're watching theCUBE, the leader in live tech coverage, and we're at the IBM CDO Strategy Summit, #IBMCDO. The chief data officer role emerged about a decade ago, and it was typically focused in regulated industries, health care, financial services, and government. And it sort of emerged from a dark, back office role of governance and compliance and data quality. But increasingly as the big data wave came to the market, people realized there was an opportunity to take that sort of wonky back office governance, compliance, discipline, and really point it toward generating value, whether that was with direct monetization of data or contributing to an organization's data strategy. And, over the next five to seven years, that chief data officer role... Couple things happen, one is got much much deeper into those regulated industries, but also permeated other non-regulated industries beyond those three that I mentioned. IBM is an organization that has targeted the chief data officer role as a key constituency as part of what IBM calls the cognitive enterprise. And IBM hosts shows in Boston and San Francisco each year, gathering chief data officers, about 100 to 150 chief data officers, in each city. These are very focused and targeted events that comprise of chief data officers, data analytics officers, and the like, people focused sometimes on compliance and governance. They're very intimate events and today, we heard from a number of IBM experts, Inderpal Bhandari, who's been on theCUBE a number of times, who is IBM's global chief data officer, laying out, sort of a blueprint, an enterprise blueprint, for data strategy. So the audience is filled with practitioners who are really sort of lapping up sort of the how to implement some of these techniques, and ultimately platforms. IBM has put together solutions, that not only involve, of course, Watson, but also some of the other components, whether its cognitive systems, governance systems, compliance systems, to create a solution that chief data officers and their colleagues can implement. So, this morning we heard about the cognitive enterprise blueprint, what IBM calls the AI enterprise, or the cognitive enterprise, talking about organizational issues. How do you break down silos of data? If you think about most incumbent organizations, the data lives in silos. It may be data in the marketing department, data in the sales department, data in the customer service department, data in the maintenance department. So these are sort of separate silos of data. How do you break those down? How do you bring those together so you can compete with some of these born digital AI-oriented companies, the likes of, just the perfect example is Facebook, Google, LinkedIn, et cetera, who have these sort of centralized data models. How do you take an existing organization, break down those silos, and deal with a data model that is accessible by everyone who needs to access that data, and as well, very importantly, make it secure, make it enterprise-ready. The other thing that IBM talked about was process. We always talk about on theCUBE, people, process, and technology. Technology is the easiest piece of that. It's the people and process components of that matrix that you need to really focus on before you even bring in the technology, and then, of course, there is the technology component. IBM is a technology company. We've heard about Watson. IBM has a number of hardware and software components that it brings to bear to try to help organizations affect their data strategy, and be more effective in the marketplace. So, as I say this is about 130, 150 chief data officers. We heard from Kaitlin Lafferty, who's going to come on a little later. She's going to be my quasi-co-host, which will be interesting. Beth Smith, who is the GM of Watson Data. She talked a lot about use cases. She gave an example of Orange Bank, a totally digital bank, using Watson to service customers. You can't call this bank. And they've got some interesting measurements that they'll share with us in terms of customer satisfaction and born-digital or all-digital bank. She also talked about partnerships that they're doing, not directly, sort of indirectly I inferred, she talked about IT service management embedding Watson into the IT service management from an HR perspective. I believe that she was referring to, even though she didn't mention it, a deal that IBM struck with ServiceNow. IBM's got similar deals with Watson with Salesforce. Salesforce Einstein is based on Watson. So what you're seeing is embedding AI into different applications, and we've talked about this a lot at siliconANGLE and theCUBE and at Wikibon. It's really those embedded use cases for AI that are going to drive adoption, as opposed to generalized horizontal AI. That seems to be not the recipe for adoption success, really more so specific use cases. I mean the obvious ones are some consumer ones, and even in the enterprise as well: security, facial recognition, natural language processing, for example. Very specific use cases for AI. We also heard from Inderpal Bhandari, the global chief data officer of IBM, talking about the AI enterprise, really showcasing IBM as a company that is bringing this AI enterprise to itself, and then teaching, sharing that knowledge with its clients and with its customers. I really like talking to Inderpal Bhandari. I learn a lot from him. This is his fourth CDO gig, okay. He was the very first CDO ever in health care when there, I mean I think he was the first of four or one of four, first CDOs in health care. Now there are thousands. So this is his fourth gig as a CDO. He talks about what a CDO has to do to get started, starting with a clear data strategy. When I've talked to him before, he said, he mentioned, how does data contribute to the monetization of your organization? Now it's not always monetization. If it's a non-public company or a health care company, for example, that's not-for-profit, it's not necessarily a monetization component, it's more of a how does it effect your strategy. But that's number one is sort of, how does data drive value for you organization? The second is, how do you implement the system that's based on governance and security? What's the management system look like? Who has data and who has access to that data? How do you affect privacy? And then, how do you become a central source for that AI-framework, being a service organization essentially to the entire organization? And then, developing deep analytics partnerships with lines of business. That's critical, because the domain expertise for the business is obviously going to live in the line of business, not in some centralized data organization. And, then, finally, very importantly, skills. What skills do you need, identify those skills, and then how do you get those people? How do you both train internally and find those people externally? Very hard to find those skills. He talked about AI systems having four attributes. Number one is expertise, domain knowledge. AI systems have to be smart about the problem that they're trying to solve. Natural human interaction, IBM talks about natural language processing, a lot of companies do. Everybody's familiar with the likes of Alexa, Google Home, and Siri. Well IBM Watson also has an NLP capability that's quite powerful. So that's very important. And interestingly he talked about, I'll ask him about this, the black box phenomenon. Most AI is a black box. If you think about it, AI can tell you if you're looking at a dog, but think about your own human frame. How do you know when you're actually seeing a dog? Try to explain to somebody someday how you go about recognizing that animal. It's sort of hard to do. Systems today can tell you that if it's a dog or for you Silicon Valley watchers, hot dog. But, it's a black box. What IBM is saying is no, we can't live with a black box in the enterprise. We have to open up that black box, make it a white box, and share with our customers exactly how that decision is being made. That's an interesting problem that I want to talk to him about. And then, next, the third piece is learning through education. How do you learn at scale? And then the fourth piece was, how do you evolve, how do you iterate, how do you become auto-didactic or self-learning with regard to the system and getting better and better and better over time. And that sets a foundation for this AI enterprise or cognitive enterprise blueprints, where the subject matter expert can actually interact with the system. We had some questions from the audience. One came up on cloud and security concerns, not surprising. Data exposure, how do you automate a lot of this stuff and provide access, at the same time ensuring privacy and security. So IBM's going to be addressing that today. So, we're here all day, wall-to-wall coverage of the IBM CDO Strategy Summit, #IBMCDO. Of course, we're running multiple live programs today. I'm covering this show in San Francisco. John Furrier is in Copenhagen at KubeCon with The Linux Foundation. Stu Miniman is holding down the fort with a very large crew at Dell Technology's World. So keep it right there everybody. This is theCUBE at IBM's CDO Strategy Summit in San Francisco. We'll be right back after this short break. (techno music) (dial tones)

>> Announcer: Live, from Las Vegas, it's theCUBE. Covering IBM Think 2018. Brought to you by IBM. >> Welcome back to IBM Think 2018. This is theCUBE, the leader in live tech coverage. My name is Dave Vellante and I'm here with Peter Burress. Our wall-to-wall coverage, this is day two. Everything AI, Blockchain, cognitive, quantum computing, smart ledger, storage, data. Bina Hallman is here, she's the Vice President of Offering Management for Storage and Software Defined. Welcome back to theCUBE, Bina. >> Bina: Thanks for having me back. >> Steve Elliot is here. He's the Vice President of Deep Learning in the Global Chief Data Office at IBM. >> Thank you sir. >> Dave: Welcome to the Cube, Steve. Thanks, you guys, for coming on. >> Pleasure to be here. >> That was a great introduction, Dave. >> Thank you, appreciate that. Yeah, so this has been quite an event, consolidating all of your events, bringing your customers together. 30,000 40,000, too many people to count. >> Very large event, yes. >> Standing room only at all the sessions. It's been unbelievable, your thoughts? >> It's been fantastic. Lots of participation, lots of sessions. We brought, as you said, all of our conferences together and it's a great event. >> So, Steve, tell us more about your role. We were talking off the camera, we've had here Paul Bhandari on before, Chief Data Officer at IBM. You're in that office, but you've got other roles around Deep Learning, so explain that. >> Absolutely. >> Sort of multi-tool star here. >> For sure, so, roles and responsibility at IBM and the Chief Data Office, kind of two pillars. We focus in the Deep Learning group on foundation platform components. So, how to accelerate the infrastructure and platform behind the scenes, to accelerate the ideation or product phase. We want data scientists to be very effective, and for us to ensure our projects very very quickly. That said, I mentioned projects, so on the applied side, we have a number of internal use cases across IBM. And it's not just hand vault, it's in the orders of hundreds and those applied use cases are part of the cognitive plan, per se, and each one of those is part of the transformation of IBM into our cognitive. >> Okay, now, we were talking to Ed Walsh this morning, Bina, about how you collaborate with colleagues in the storage business. We know you guys have been growing, >> Bina: That's right. >> It's the fourth quarter straight, and that doesn't event count, some of the stuff that you guys ship on the cloud in storage, >> That's right, that's right. >> Dave: So talk about the collaboration across company. >> Yeah, we've had some tremendous collaboration, you know, the broader IBM and bringing all of that together, and that's one of the things that, you know, we're talking about here today with Steve and team is really as they built out their cognitive architecture to be able to then leverage some of our capabilities and the strengths that we bring to the table as part of that overall architecture. And it's been a great story, yeah. >> So what would you add to that, Steve? >> Yeah, absolutely refreshing. You know I've built up super computers in the past, and, specifically for deep learning, and coming on board at IBM about a year ago, seeing the elastic storage solution, or server. >> Bina: Yeah, elastic storage server, yep. >> It handles a number of different aspects of my pipeline, very uniquely, so for starters, I don't want to worry about rolling out new infrastructure all the time. I want to be able to grow my team, to grow my projects, and that's what nice about ESS is it's distensible, I'm able to roll out more projects, more people, multi-tenancy et cetera, and it supports us effectively. Especially, you know, it has very unique attributes like the read only performance feed, and random access of data, is very unique to the offering. >> Okay, so, if you're a customer of Bina's, right? >> I am, 100%. >> What do you need for infrastructure for Deep Learning, AI, what is it, you mentioned some attributes before, but, take it down a little bit. >> Well, the reality is, there's many different aspects and if anything kind of breaks down, then the data science experience breaks down. So, we want to make sure that everything from the interconnect of the pipelines is effective, that you heard Jensen earlier today from Nvidia, we've got to make sure that we have compute devices that, you know, are effective for the computation that we're rolling out on them. But that said, if those GPUs are starved by data, that we don't have the data available which we're drawing from ESS, then we're not making effective use of those GPUs. It means we have to roll out more of them, et cetera, et cetera. And more importantly, the time for experimentation is elongated, so that whole idea, so product timeline that I talked about is elongated. If anything breaks down, so, we've got to make sure that the storage doesn't break down, and that's why this is awesome for us. >> So let me um, especially from a deep learning standpoint, let me throw, kind of a little bit of history, and tell me if you think, let me hear your thoughts. So, years ago, the data was put as close to the application as possible, about 10, 15 years ago, we started breaking the data from the application, the storage from the application, and now we're moving the algorithm down as close to the data as possible. >> Steve: Yeah. >> At what point in time do we stop calling this storage, and start acknowledging that we're talking about a fabric that's actually quite different, because we put a lot more processing power as close to the data as possible. We're not just storing. We're really doing truly, deeply distributing computing. What do you think? >> There's a number of different areas where that's coming from. Everything from switches, to storage, to memory that's doing computing very close to where the data actually residents. Still, I think that, you know, this is, you can look all the way back to Google file system. Moving computation to where the data is, as close as possible, so you don't have to transfer that data. I think that as time goes on, we're going to get closer and closer to that, but still, we're limited by the capacity of very fast storage. NVMe, very interesting technology, still limited. You know, how much memory do we have on the GPUs? 16 gigs, 24 is interesting, 48 is interesting, the models that I want to train is in the 100s of gigabytes. >> Peter: But you can still parallelize that. >> You can parallelize it, but there's not really anything that's true model parallelism out there right now. There's some hacks and things that people are doing, but. I think we're getting there, it's still some time, but moving it closer and closer means we don't have to spend the power, the latency, et cetera, to move the data. >> So, does that mean that the rate of increase of data and the size of the objects we're going to be looking at, is still going to exceed the rate of our ability to bring algorithms and storage, or algorithms and data together? What do you think? >> I think it's getting closer, but I can always just look at the bigger problem. I'm dealing with 30 terabytes of data for one of the problems that I'm solving. I would like to be using 60 terabytes of data. If I could, if I could do it in the same amount of time, and I wasn't having to transfer it. With that said, if you gave me 60, I'd say, "I really wanted 120." So, it doesn't stop. >> David: (laughing) You're one of those kind of guys. >> I'm definitely one of those guys. I'm curious, what would it look like? Because what I see right now is it would be advantageous, and I would like to do it, but I ran 40,000 experiments with 30 terabytes of data. It would be four times the amount of transfer if I had to run that many experiments of 120. >> Bina, what do you think? What is the fundamental, especially from a software defined side, what does the fundamental value proposition of storage become, as we start pushing more of the intelligence close to the data? >> Yeah, but you know the storage layer fundamentally is software defined, you still need that setup, protocols, and the file system, the NFS, right? And, so, some of that still becomes relevant, even as you kind of separate some of the physical storage or flash from the actual compute. I think there's still a relevance when you talk about software defined storage there, yeah. >> So you don't expect that there's going to be any particular architectural change? I mean, NVMe is going to have a real impact. >> NVMe will have a real impact, and there will be this notion of composable systems and we will see some level of advancement there, of course, and that's around the corner, actually, right? So I do see it progressing from that perspective. >> So what's underneath it all, what actually, what products? >> Yeah, let me share a little bit about the product. So, what Steve and team are using is our elastic storage server. So, I talked about software defined storage. As you know, we have a very complete set of software defined storage offerings, and within that, our strategy has always been allow the clients to consume the capabilities the way they want. A software only on their own hardware, or as a service, or as an integrated solution. And so what Steve and team are using is an integrated solution with our spectrum scale software, along with our flash and power nine server power systems. And on the software side from spectrum scale, this is a very rich offering that we've had in our portfolio. Highly scalable file system, it's one of the solutions that powers a lot of our supercomputers. A project that we are still in the process and have delivered on around Whirl, our national labs. So same file system combined with a set of servers and flash system, right? Highly scalable, erasure coding, high availability as well as throughput, right? 40 gigabytes per second, so that's the solution, that's the storage and system underneath what Steve and team are leveraging. >> Steve, you talk about, "you want more," what else is on Bina's to-do-list from your standpoint? >> Specifically targeted at storage, or? >> Dave: Yeah, what do you want from the products? >> Well, I think long stretch goals are multi-tenancy and the wide array of dimensions that, especially in the chief data office, that we're dealing with. We have so many different business units, so many different of those enterprise problems in the orders of hundreds how do you effectively use that storage medium driving so many different users? I think it's still hard, I think we're doing it a hell of a lot better than we ever have, but it's still, it's an open research area. How do you do that? And especially, there's unique attributes towards deep learning, like, most of the data is read only to a certain degree. When data changes there's some consistency checks that could be done, but really, for my experiment that's running right now, it doesn't really matter that it's changed. So there's a lot of nuances specific to deep learning that I would like exploited if I could, and that's some of the interactions that we're working on to kind of alleviate those pains. >> I was at a CDO conference in Boston last October, and Indra Pal was there and he presented this enterprise data architecture, and there were probably about three or four hundred CDOs, chief data officers, in the room, to sort of explain that. Can you, sort of summarize what that is, and how it relates to sort of what you do on a day to day basis, and how customers are using it? >> Yeah, for sure, so the architecture is kind of like the backbone and rules that kind of govern how we work with the data, right? So, the realities are, there's no sort of blueprint out there. What works at Google, or works at Microsoft, what works at Amazon, that's very unique to what they're doing. Now, IBM has a very unique offering as well. We have so many, we're a composition of many, many different businesses put together. And now, with the Chief Data Office that's come to light across many organizations like you said, at the conference, three to 400 people, the requirements are different across the orders. So, bringing the data together is kind of one of the big attributes of it, decreasing the number of silos, making a monolithic kind of reliable, accessible entity that various business units can trust, and that it's governed behind the scenes to make sure that it's adhering to everyone's policies, that their own specific business unit has deemed to be their policy. We have to adhere to that, or the data won't come. And the beauty of the data is, we've moved into this cognitive era, data is valuable but only if we can link it. If the data is there, but there's no linkages there, what do I do with it? I can't really draw new insights. I can't draw, all those hundreds of enterprise use cases, I can't build new value in them, because I don't have any more data. It's all about linking the data, and then looking for alternative data sources, or additional data sources, and bringing that data together, and then looking at the new insights that come from it. So, in a nutshell, we're doing that internally at IBM to help our transformation. But at the same time creating a blueprint that we're making accessible to CDOs around the world, and our enterprise customers around the world, so they can follow us on this new adventure. New adventure being, you know, two years old, but. >> Yeah, sure, but it seems like, if you're going to apply AI, you've got to have your data house in order to do that. So this sounds like a logical first step, is that right? >> Absolutely, 100%. And, the realities are, there's a lot of people that are kicking the tires and trying to figure out the right way to do that, and it's a big investment. Drawing out large sums of money to kind of build this hypothetical better area for data, you need to have a reference design, and once you have that you can actually approach the C-level suite and say, "Hey, this is what we've seen, this is the potential, "and we have an architecture now, "and they've already gone down all the hard paths, "so now we don't have to go down as many hard paths." So, it's incredibly empowering for them to have that reference design and learning from our mistakes. >> Already proven internally now, bringing it to our enterprise alliance. >> Well, and so we heard Jenny this morning talk about incumbent disruptors, so I'm kind of curious as to what, any learnings you have there? It's early days, I realize that, but when you think about, the discussions, are banks going to lose control of the payment systems? Are retail stores going to go away? Is owning and driving your own vehicle going to be the exception, not the norm? Et cetera, et cetera, et cetera, you know, big questions, how far can we take machine intelligence? Have you seen your clients begin to apply this in their businesses, incumbents, we saw three examples today, good examples, I thought. I don't think it's widespread yet, but what are you guys seeing? What are you learning, and how are you applying that to clients? >> Yeah, so, I mean certainly for us, from these new AI workloads, we have a number of clients and a number of different types of solutions. Whether it's in genomics, or it's AI deep learning in analyzing financial data, you know, a variety of different types of use cases where we do see clients leveraging the capabilities, like spectrum scale, ESS, and other flash system solutions, to address some of those problems. We're seeing it now. Autonomous driving as well, right, to analyze data. >> How about a little road map, to end this segment? Where do you want to take this initiative? What should we be looking for as observers from the outside looking in? >> Well, I think drawing from the endeavors that we have within the CDO, what we want to do is take some of those ideas and look at some of the derivative products that we can take out of there, and how do we kind of move those in to products? Because we want to make it as simple as possible for the enterprise customer. Because although, you see these big scale companies, and all the wonderful things that they're doing, what we've had the feedback from, which is similar to our own experiences, is that those use cases aren't directly applicable for most of the enterprise customers. Some of them are, right, some of the stuff in vision and brand targeting and speech recognition and all that type of stuff are, but at the same time the majority and the 90% area are not. So we have to be able to bring down sorry, just the echoes, very distracting. >> It gets loud here sometimes, big party going on. >> Exactly, so, we have to be able to bring that technology to them in a simpler form so they can make it more accessible to their internal data scientists, and get better outcomes for themselves. And we find that they're on a wide spectrum. Some of them are quite advanced. It doesn't mean just because you have a big name you're quite advanced, some of the smaller players have a smaller name, but quite advanced, right? So, there's a wide array, so we want to make that accessible to these various enterprises. So I think that's what you can expect, you know, the reference architecture for the cognitive enterprise data architecture, and you can expect to see some of the products from those internal use cases come out to some of our offerings, like, maybe IGC or information analyzer, things like that, or maybe the Watson studio, things like that. You'll see it trickle out there. >> Okay, alright Bina, we'll give you the final word. You guys, business is good, four straight quarters of growth, you've got some tailwinds, currency is actually a tailwind for a change. Customers seem to be happy here, final word. >> Yeah, no, we've got great momentum, and I think 2018 we've got a great set of roadmap items, and new capabilities coming out, so, we feel like we've got a real strong set of future for our IBM storage here. >> Great, well, Bina, Steve, thanks for coming on theCUBE. We appreciate your time. >> Thank you. >> Nice meeting you. >> Alright, keep it right there everybody. We'll be back with our next guest right after this. This is day two, IBM Think 2018. You're watching theCUBE. (techno jingle)

>> Announcer: Live from Fisherman's Wharf in San Francisco, it's theCUBE, covering IBM Chief Data Officer Strategy Summit Spring 2017. Brought to you by IBM. >> Hey, welcome back, everybody. Jeff Frick here with theCUBE. We're at Fisherman's Wharf in San Francisco at the IBM Chief Data Officer Strategy Summit Spring 2017. It's a mouthful, it's 170 people here, all high-level CXOs learning about data, and it's part of an ongoing series that IBM is doing around chief data officers and data, part of a big initiative with Cognitive and Watson, I'm sure you've heard all about it, Watson TV if nothing else, if not going to the shows, and we're really excited to have the drivers behind this activity with us today, also Peter Burris from Wikibon, chief strategy officer, but we've got Caitlin Lepech who's really driving this whole show. She is the Communications and Client Engagement Executive, IBM Global Chief Data Office. That's a mouthful, she's got a really big card. And Cortnie Abercrombie, who I'm thrilled to see you, seen her many, many times, I'm sure, at the MIT CDOIQ, so she's been playing in this space for a long time. She is a Cognitive and Analytics Offerings leader, IBM Global Business. So first off, welcome. >> Thank you, great to be here. >> Thanks, always a pleasure on theCUBE. It's so comfortable, I forget you guys aren't just buddies hanging out. >> Before we jump into it, let's talk about kind of what is this series? Because it's not World of Watson, it's not InterConnect, it's a much smaller, more intimate event, but you're having a series of them, and in the keynote is a lot of talk about what's coming next and what's coming in October, so I don't know. >> Let me let you start, because this was originally Cortnie's program. >> This was a long time ago. >> 2014. >> Yeah, 2014, the role was just starting, and I was tasked with can we identify and start to build relationships with this new line of business role that's cropping up everywhere. And at that time there were only 50 chief data officers worldwide. And so I-- >> Jeff: 50? In 2014. >> 50, and I can tell you that earnestly because I knew every single of them. >> More than that here today. >> I made it a point of my career over the last three years to get to know every single chief data officer as they took their jobs. I would literally, well, hopefully I'm not a chief data officer stalker, but I basically was calling them once I'd see them on LinkedIn, or if I saw a press announcement, I would call them up and say, "You've got a tough job. "Let me help connect you with each other "and share best practices." And before we knew, it became a whole summit. It became, there were so many always asking to be connected to each other, and how do we share best practices, and what do you guys know as IBM because you're always working with different clients on this stuff? >> And Cortnie and I first started working in 2014, we wrote IBM's first paper on chief data officers, and at the time, there was a lot of skepticism within our organization, why spend the time with data officers? There's other C-suite roles you may want to focus on instead. But we were saying just the rise of data, external data, unstructured data, lot of opportunity to rise in the role, and so, I think we're seeing it reflected in the numbers. Again, first summit three years ago, 30 participants. We have 170 data executives, clients joining us today and tomorrow. >> And six papers later, and we're goin' strong still. >> And six papers later. >> Exactly, exactly. >> Before we jump into the details, some of the really top-level stuff that, again, you talked about with John and David, MIT CDOIQ, in terms of reporting structure. Where do CDOs report? What exactly are they responsible for? You covered some of that earlier in the keynote, I wonder if you can review some of those findings. >> Yeah, that was amazing >> Sure, I can share that, and then, have Cortnie add. So, we find about a third report directly to the CEO, a third report through the CIO's office, sort of the traditional relationship with CIOs, and then, a third, and what we see growing quite a bit, are CXOs, so functional or business line function. Originally, traditionally it was really a spin-off of CIO, a lot of technical folks coming up, and we're seeing more and more the shift to business expertise, and the focus on making sure we're demonstrating the business impact these data programs are driving for our organization. >> Yeah, it kind of started more as a data governance type of role, and so, it was born out of IT to some degree because, but IT was having problems with getting the line of business leaders to come to the table, and we knew that there had to be a shift over to the business leaders to get them to come and share their domain expertise because as every chief data officer will tell you, you can't have lineage or know anything about all of this great data unless you have the experts who have been sitting there creating all of that data through their processes. And so, that's kind of how we came to have this line of business type of function. >> And Inderpal really talked about, in terms of the strategy, if you don't start from the business strategy-- >> Inderpal? >> Yeah, on the keynote. >> Peter: Yeah, yeah, yeah, yeah. >> You are really in big risk of the boiling the ocean problem. I mean, you can't just come at it from the data first. You really have to come at it from the business problem first. >> It was interesting, so Inderpal was one of our clients as a CEO three times prior to rejoining IBM a year ago, and so, Cortnie and I have known him-- >> Express Scripts, Cambia. >> Exactly, we've interviewed him, featured him in our research prior, too, so when he joined IBM in December a year ago, his first task was data strategy. And where we see a lot of our clients struggle is they make data strategy an 18-month, 24-month process, getting the strategy mapped out and implemented. And we say, "You don't have the time for it." You don't have 18 months to come to data, to come to a data strategy and get by and get it implemented. >> Nail something right away. >> Exactly. >> Get it in the door, start showing some results right away. You cannot wait, or your line of business people will just, you know. >> What is a data strategy? >> Sure, so I can say what we've done internally, and then, I know you've worked with a lot of clients on what they're building. For us internally, it started with the value proposition of the data office, and so, we got very clear on what that was, and it was the ability to take internal, external data, structured, unstructured, and pull that together. If I can summarize it, it's drive to cognitive business, and it's infusing cognition across all of our business processes internally. And then, we identified all of these use cases that'll help accelerate, and the catalyst that will get us there faster. And so, Client 360, product catalog, et cetera. We took data strategy, got buy-in at the highest levels at our organization, senior vice president level, and then, once we had that support and mandate from the top, went to the implementation piece. It was moving very quickly to specify, for us, it's about transforming to cognitive business. That then guides what's critical data and critical use cases for us. >> Before you answer, before you get into it, so is a data strategy a means to cognitive, or is it an end in itself? >> I would say it, to be most effective, it's a succinct, one-page description of how you're going to get to that end. And so, we always say-- >> Peter: Of cognitive? >> Exactly, for us, it's cognitive. So, we always ask very simple question, how is your company going to make money? Not today, what's its monetization strategy for the future? For us, it's coming to cognitive business. I have a lot of clients that say, "We're product-centric. "We want to become customer, client-centric. "That's our key piece there." So, it's that key at the highest level for us becoming a cognitive business. >> Well, and data strategies are as big or as small as you want them to be, quite frankly. They're better when they have a larger vision, but let's just face it, some companies have a crisis going on, and they need to know, what's my data strategy to get myself through this crisis and into the next step so that I don't become the person whose cheese moved overnight. Am I giving myself away? Do you all know the cheese, you know, Who Moved My Cheese? >> Every time the new iOS comes up, my wife's like-- >> I don't know if the younger people don't know that term, I don't think. >> Ah, but who cares about them? >> Who cares about the millenials? I do, I love the millenials. But yes, cheese, you don't want your cheese to move overnight. >> But the reason I ask the question, and the reason why I think it's important is because strategy is many things to many people, but anybody who has a view on strategy ultimately concludes that the strategic process is what's important. It's the process of creating consensus amongst planners, executives, financial people about what we're going to do. And so, the concept of a data strategy has to be, I presume, as crucial to getting the organization to build a consensus about the role the data's going to play in business. >> Absolutely. >> And that is the hardest. That is the hardest job. Everybody thinks of a data officer as being a technical, highly technical person, when in fact, the best thing you can be as a chief data officer is political, very, very adept at politics and understanding what drives the business forward and how to bring results that the CEO will get behind and that the C-suite table will get behind. >> And by politics here you mean influencing others to get on board and participate in this process? >> Even just understanding, sometimes leaders of business don't articulate very well in terms of data and analytics, what is it that they actually need to accomplish to get to their end goal, and you find them kind of stammering when it comes to, "Well, I don't really know "how you as Inderpal Bhandari can help me, "but here's what I've got to do." And it's a crisis usually. "I've got to get this done, "and I've got to make these numbers by this date. "How can you help me do that?" And that's when the chief data officer kicks into gear and is very creative and actually brings a whole new mindset to the person to understand their business and really dive in and understand, "Okay, this is how "we're going to help you meet that sales number," or, "This is how we're going to help you "get the new revenue growth." >> In certain respects, there's a business strategy, and then, you have to resource the business strategy. And the data strategy then is how are we going to use data as a resource to achieve our business strategy? >> Cortnie: Yes. >> So, let me test something. The way that we at SiliconANGLE, Wikibon have defined digital business is that a business, a digital business uses data as an asset to differentially create and keep customers. >> Caitlin: Right. >> Does that work for you guys? >> Cortnie: Yeah, sure. >> It's focused on, and therefore, you can look at a business and say is it more or less digital based on how, whether it's more or less focused on data as an asset and as a resource that's going to differentiate how it's business behaves and what it does for customers. >> Cortnie: And it goes from the front office all the way to the back. >> Yes, because it's not just, but that's what, create and keep, I'm borrowing from Peter Drucker, right. Peter Drucker said the goal of business is to create and keep customers. >> Yeah, that's right. Absolutely, at the end of the day-- >> He included front end and back end. >> You got to make money and you got to have customers. >> Exactly. >> You got to have customers to make the money. >> So data becomes a de-differentiating asset in the digital business, and increasingly, digital is becoming the differentiating approach in all business. >> I would argue it's not the data, because everybody's drowning in data, it's how you use the data and how creative you can be to come up with the methods that you're going to employ. And I'll give you an example. Here's just an example that I've been using with retailers lately. I can look at all kinds of digital exhaust, that's what we call it these days. Let's say you have a personal digital shopping experience that you're creating for these new millenials, we'll go with that example, because shoppers, 'cause retailers really do need to get more millenials in the door. They're used to their Amazon.coms and their online shopping, so they're trying to get more of them in the door. When you start to combine all of that data that's underlying all of these cool things that you're doing, so personal shopping, thumbs up, thumb down, you like this dress, you like that cut, you like these heels? Yeah, yes, yes or no, yes or no. I'm getting all this rich data that I'm building with my app, 'cause you got to be opted in, no violating privacy here, but you're opting in all the way along, and we're building and building, and so, we even have, for us, we have this Metro Pulse retail asset that we use that actually has hyperlocal information. So, you could, knowing that millenials like, for example, food trucks, we all like food trucks, let's just face it, but millenials really love food trucks. You could even, if you are a retailer, you could even provide a fashion truck directly to their location outside their office equipped with things that you know they like because you've mined that digital exhaust that's coming off the personal digital shopping experience, and you've understood how they like to pair up what they've got, so you're doing a next best action type of thing where you're cross-selling, up-selling. And now, you bring it into the actual real world for them, and you take it straight to them. That's a new experience, that's a new millennial experience for retail. But it's how creative you are with all that data, 'cause you could have just sat there before and done nothing about that. You could have just looked at it and said, "Well, let's run some reports, "let's look at a dashboard." But unless you actually have someone creative enough, and usually it's a pairing of data scientist, chief data officers, digital officers all working together who come up with these great ideas, and it's all based, if you go back to what my example was, that example is how do I create a new experience that will get millenials through my doors, or at least get them buying from me in a different way. If you think about that was the goal, but how I combined it was data, a digital process, and then, I put it together in a brand new way to take action on it. That's how you get somewhere. >> Let me see if I can summarize very quickly. And again, just as an also test, 'cause this is the way we're looking at it as well, that there's human beings operate and businesses operate in an analog world, so the first test is to take analog data and turn it into digital data. IOT does that. >> Cortnie: Otherwise, there's not digital exhaust. >> Otherwise, there's no digital anything. >> Cortnie: That's right. >> And we call it IOT and P, Internet of Things and People, because of the people element is so crucial in this process. Then we have analytics, big data, that's taking those data streams and turning them into models that have suggestions and predictions about what might be the right way to go about doing things, and then there's these systems of action, or what we've been calling systems of enactment, but we're going to lose that battle, it's probably going to be called systems of action that then take and transduce the output of the model back into the real world, and that's going to be a combination of digital and physical. >> And robotic process automation. We won't even introduce that yet. >> Which is all great. >> But that's fun. >> That's going to be in October. >> But I really like the example that you gave of the fashion truck because people don't look at a truck and say, "Oh, that's digital business." >> Cortnie: Right, but it manifested in that. >> But it absolutely is digital business because the data allows you to bring a more personal experience >> Understand it, that's right. >> right there at that moment, and it's virtually impossible to even conceive of how you can make money doing that unless you're able to intercept that person with that ensemble in a way that makes both parties happy. >> And wouldn't that be cheaper than having big, huge retail stores? Someone's going to take me up on that. Retailers are going to take me up on this, I'm telling you. >> But I think the other part is-- >> Right next to the taco truck. >> There could be other trucks in that, a much cleaner truck, and this and that. But one thing, Cortnie, you talk about and you got to still have a hypothesis, I think of the early false promises of big data and Hadoop, just that you throw all this stuff in, and the answer just comes out. That just isn't the way. You've got to be creative, and you have to have a hypothesis to test, and I'm just curious from your experience, how ready are people to take in the external data sources and the unstructured data sources and start to incorporate that in with the proprietary data, 'cause that's a really important piece of the puzzle? It's very different now. >> I think they're ready to do it, it depends on who in the business you are working with. Digital offices, marketing offices, merchandising offices, medical offices, they're very interested in how can we do this, but they don't know what they need. They need guidance from a data officer or a data science head, or something like this, because it's all about the creativity of what can I bring together to actually reach that patient diagnostic, that whatever the case may be, the right fashion truck mix, or whatever. Taco Tuesday. >> So, does somebody from the chief data office, if you will, you know, get assigned to, you're assigned to marketing and you're assigned to finance, and you're assigned to sales. >> I have somebody assigned to us. >> To put this in-- >> Caitlin: Exactly, exactly. >> To put this in kind of a common or more modern parlance, there's a design element. You have to have use case design, and what are we going, how are we going to get better at designing use cases so we can go off and explore the role that data is going to play, how we're going to combine it with other things, and to your point, and it's a great point, how that turns into a new business activity. >> And if I can connect two points there, the single biggest question I get from clients is how do you prioritize your use cases. >> Oh, gosh, yeah. >> How can you help me select where I'm going to have the biggest impact? And it goes, I think my thing's falling again. (laughing) >> Jeff: It's nice and quiet in here. >> Okay, good. It goes back to what you were saying about data strategy. We say what's your data strategy? What's your overarching mission of the organization? For us, it's becoming cognitive business, so for us, it's selecting projects where we can infuse cognition the quickest way, so Client 360, for example. We'll often say what's your strategy, and that guides your prioritization. That's the question we get the most, what use case do I select? Where am I going to have the most impact for the business, and that's where you have to work with close partnership with the business. >> But is it the most impact, which just sounds scary, and you could get in analysis paralysis, or where can I show some impact the easiest or the fastest? >> You're going to delineate both, right? >> Exactly. >> Inderpal's got his shortlist, and he's got his long list. Here's the long term that we need to be focused on to make sure that we are becoming holistically a cognitive company so that we can be flexible and agile in this marketplace and respond to all kinds of different situations, whether they're HR and we need more skills and talent, 'cause let's face it, we're a technology company who's rapidly evolving to fit with the marketplace, or whether it's just good old-fashioned we need more consultants. Whatever the case may be. >> Always, always. >> Yes! >> I worked my business in. >> More consultants! >> Alright, we could go, we could go and go and go, but we're running out of time, we had a full slate. >> Caitlin: We just started. >> I know. >> I agree, we're just starting this convers, I started a whole other conversation to him. We haven't even hit the robotics yet. >> We need to keep going, guys. >> Get control. >> Cortnie: Less coffee for us. >> What do people think about when they think about this series? What should they look forward to, what's the next one for the people that didn't make it here today, where should they go on the calendar and book in their calendars? >> So, I'll speak to the summits first. It's great, we do Spring in San Francisco. We'll come back, reconvene in Boston in fall, so that'll be September, October frame. I'm seeing two other trends, which I'm quite excited about, we're also looking at more industry-specific CDO summits. So, for those of our friends that are in government sectors, we'll be in June 6th and 7th at a government CDO summit in D.C., so we're starting to see more of the industry-specific, as well as global, so we just ran our first in Rio, Brazil for that area. We're working on a South Africa summit. >> Cortnie: I know, right. >> We actually have a CDO here with us that traveled from South Africa from a bank to see our summit here and hoping to take some of that back. >> We have several from Peru and Mexico and Chile, so yeah. >> We'll continue to do our two flagship North America-based summits, but I'm seeing a lot of growth out in our geographies, which is fantastic. >> And it was interesting, too, in your keynote talking about people's request for more networking time. You know, it is really a sharing of best practices amongst peers, and that cannot be overstated. >> Well, it's community. A community is building. >> It really is. >> It's a family, it really is. >> We joke, this is a reunion. >> We all come in and hug, I don't know if you noticed, but we're all hugging each other. >> Everybody likes to hug their own team. It's a CUBE thing, too. >> It's like therapy. It's like data therapy, that's what it is. >> Alright, well, Caitlin, Cortnie, again, thanks for having us, congratulations on a great event, and I'm sure it's going to be a super productive day. >> Thank you so much. Pleasure. >> Thanks. >> Jeff Frick with Peter Burris, you're watchin' theCUBE from the IBM Chief Data Officer Summit Spring 2017 San Francisco, thanks for watching. (electronic keyboard music)

(orchestral music) (energetic music) >> Narrator: Live from Fisherman's Wharf in San Francisco. It's the Cube! Covering IBM Chief Data Officer Strategy Summit, Spring 2017. Brought to you by IBM. >> Hey, welcome back everybody! Jeff Frick here with the Cube. I am joined by Peter Burris, the Chief Research Officer at Wikibon. We are in downtown San Francisco at the IBM Chief Data Officer Strategy Summit 2017. It's a lot of practitioners. It's almost 200 CDOs here sharing best practices, learning from the IBM team and we're excited to be here and cover it. It's an ongoing series and this is just one of many of these summits. So, if you are a CDO get involved. But, the most important thing is to not just talk to the IBM folks but to talk to the practitioners. And, we are really excited for our next segment to be joined by Allen Crane. He is the assistant VP from USAA. Welcome! >> Thank you. >> Jeff: And also Glenn Finch. He is the Global Managing Partner Cognitive and Analytics at IBM. Welcome! >> Thank you, thank you both. >> It's kind of like the Serengeti of CDOs here, isn't it? >> It is. It's unbelievable! >> So, the overview Allen to just kind of, you know, this opportunity to come together with a bunch of your peers. What's kind of the vibe? What are you taking away? I know it's still pretty early on but it's a cool little event. It's not a big giant event in Vegas. You know, it's a smaller of an affair. >> That's right. I've been coming to this event for the last three years since they had it and started it when Glenn started this event. And, truly it's probably the best conference I come to every year because it's practitioners. You don't have a lot of different tracks to get lost in. This is really about understanding from your own peers what they are going through. Everything from how are you organizing the organization? What are you focused on? Where are you going? And all the way through talent discussions and where do you source these jobs? >> What is always a big discussion is organizational structure which on one hand side is kind of, you know, who really cares? But is vitally important as to how it is executed, how the strategy gets implemented in the business groups. I wonder if you can tell us a little bit about how it works at USAA, your role specifically and how does a Chief Data Officer eat it, work his way into the business bugs trying to make better decisions. >> Absolutely, we are a 27 billion dollar 95 year old company that focuses on the military and their members and their families. And our members, we offer a full range of financial services. So, you can imagine we've got lots of data offices for all of our different lines of business. Because of that, we have elected to go with what we call a hub and spoke model where we centralize certain functions around governance, standards, core data assets, and we subscribe to those things from a standard standpoint so that we're in the spokes like I am. I run all of the data analytics for all of our channels and how our members interact with USAA. So, we can actually have standards that we can apply in our own area as does the bank, as does the insurance company, as does the investments company. And so, it enables the flexibility of business close to the business data and analytics while you also sort of maintain the governance layer on top of that. >> Well, USAA has been at the vanguard of customer experience for many years now. >> Yes >> And the channel world is now starting to apply some of the lessons learned elsewhere. Are you finding that USAA is teaching channels how to think about customer experience? And if so, what is your job as an individual who's, I presume, expected to get data about customer experience out to channel companies. How is that working? >> Well, it's almost like when you borrow a page back from history and in 1922 when we were founded the organization said service is the foundation of our industry. And, it's the foundation of what we do and how we message to our membership. So, take that forward 95 years and we are finding that with the explosion in digital, in mobile, and how does that interact with the phone call. And, when you get a document in the mail is it clear? Or do you have to call us, because of that? We find that there's a lot of interplay between our channels, that our channels had tended to be owned by different silo leaders that weren't really thinking laterally or horizontally across the experience that the member was facing. Now, the member is already multichannel. We all know this. We are all customers in our own right, getting things in the mail. It's not clear. Or getting things in an e-mail. >> Absolutely. >> Or a mobile notice or SMS text message. And, this is confusing. I need to talk to somebody about this. That type of thing. So, we're here to really make sure that we're providing as direct interaction and direct answers and direct access with our membership to make those as compelling experiences as we possibly can. >> So, how is data making that easier? >> We're bringing the data altogether is the first thing. We've got to be able to make sure that our phone data is in the same place as our digital data, is in the same place as our document data, is in the same place as our mobile data because when you are not able to see that path of how the member got here, you're kind of at a loss of what to fix. And so, what we're finding is the more data that we're stitching together, these are really just an extension of a conversation with the membership. If someone is calling you after being online within just a few minutes you kind of know that that's an extension of the same intent that they had before. >> Right. >> So, what was it upfront and upstream that caused them to call. What couldn't you answer for the member upstream that now required a phone call and possibly a couple of transfers to be able to answer that phone interaction. So, that's how we start with bringing all the data together. >> So, how are you working with other functions within USAA to ensure that the data that the channel organizations to ensure those conversations can persist over time with products and underwriters and others that are actually responsible for putting forward the commitments that are being made. >> Yeah. >> How is that coming together? >> I think, simply put it, it's a pull versus push. So, showing the value that we are providing back to our lines of business. So, for example, the bank line of business president looks to us to help them reduce the number of calls which affects their bottom line. And so, when we can do that and show that we are being more efficient with our member, getting them the right place to the right MSR the first time, that is a very material impact in their bottom line. So, connecting into the things that they care about is the pull factor that we often called, that gets us that seat at the table that says we need this channel analyst to come to me and be my advisor as I'm making these decisions. >> You know what, I was just going to say what Allen is describing is probably what I think is the most complicated piece of data analytics, cognitive, all that stuff. That last mile of getting someone whether it's a push or pull. >> Right. >> Fundamentally, you want somebody to do something different whether it's an end consumer, whether it's a research analyst, whether it's a COO or a CFO, you need to do something that causes them to make a different decision. You know, ten years ago as we were just at the dawn of a lot of this new analytical techniques, everybody was focused on amassing data and new machine learning and all that stuff. Now, quite honestly, a lot of that stuff is present and it's about how do we get someone who adapts something that feels completely wrong. That's probably the hardest. I mean, and I joke with people, but you know that thing when your spouse finds something in you and says something immediately about it. >> No, no. >> That's right. (laughs) That's the first thing and you guys are probably better men than I am. The first I want to do is say "prove them wrong". Right? That's the same thing when an artificial intelligence asset tries to tell a knowledge worker what to do. >> Right, right. >> Right? That's what I think the hardest thing is right now. >> So, is it an accumulative kind of knock down or eventually they kind of get it. Alright, I'll stop resisting. Or, is it a AHA moment where people come at 'cause usually for changing behavior, usually there's a carrot or a stick. Either you got to do it. >> Push or pull. >> And the analogy, right. Or save money versus now really trying to transform and reorganize things in new, innovative ways that A. Change the customer experience, but B. Add new revenue streams and unveil a new business opportunity. >> I think it's finding what's important to that business user and sometimes it's an insight that saves them money. In other cases, it's no one can explain to me what's happening. So, in the case of Call Centers for example, we do a lot of forecasting and routing work, getting the call to the right place at the right time. But often, a business leader may say " I want to change the routing rules". But, the contact center, think of it as a closed environment, and something that changes over here, actually ultimately has an effect over here. And, they may not understand the interplay between if I move more calls this way, well those calls that were going there have to go some place else now, right? So, they may not understand the interplay of these things. So, sometimes the analyst comes in in a time of crisis and sometimes it's that crisis, that sort of shared enemy if you will, the enemy of the situation, that is, not your customer. But, the enemy of the shared situation that sort of bonds people together and you sort of have that brothers in arms kind of moment and you build trust that way. It comes down to trust and it comes down to " you have my best interest in mind". And, sometimes it's repeating the message over and over again. Sometimes, it's story telling. Sometimes, it's having that seat at the table during those times of crisis, but we use all of those tools to help us earn that seat at the table with our business customer. >> So, let me build on something that you said (mumbles) 'Cause it's the trying to get many people in the service experience to change. Not just one. So, the end goal is to have the customer to have a great experience. >> Exactly. >> But, the business executive has to be part of that change. >> Exactly. >> The call center individual has to be part of that change. And, ultimately it's the data that ensures that that process of change or those changes are in fact equally manifest. >> Right. >> You need to be across the entire community that's responsible for making something happen. >> Right. >> Is that kind of where your job comes in. That you are making sure that that experience that's impacted by multiple things, that everybody gets a single version of the truth of the data necessary to act as a unit? >> Yeah, I think data, bringing it all together is the first thing so that people can understand where it's all coming from. We brought together dozens of systems that are the systems of record into a new system of record that we can all share and use as a collective resource. That is a great place to start when everyone is operating of the same fact base, if you will. Other disciplines like process disciplines, things that we call designed for measurability so that we're not just building things and seeing how it works when we roll it out as a release on mobile or a release on .com but truly making sure that we are instrumenting these new processes along the way. So, that we can develop these correlations and causal models for what's helping, what's working and what's not working. >> That's an interesting concept. So, you design the measurability in at the beginning. >> I have to. >> As opposed to kind of after the fact. Obviously, you need to measure-- >> Are you participating in that process? >> Absolutely. We have and my role is mainly more from and educational standpoint of knowing why it's important to do this. But, certainly everyone of our analysts is deeply engaged in project work, more upstream than ever. And now, we're doing more work with our design teams so that data is part of the design process. >> You know, this measurability concept, incredibly important in the consultancy as well. You know, for the longest time all the procurement officers said the best thing you can do to hold consults accountable is a fixed priced, milestone based thing, that program number 32 was it red or green? And if it's green, you'll get paid. If not, I am not paying you. You know, we in the cognitive analytics business have tried to move away from that because if we, if our work is not instrumented the same way as Allen's, if I am not looking at that same KPI, first of all I might have project 32 greener than grass, but that KPI isn't moving, right? Secondly, if I don't know that KPI then I am not going to be able to work across multiple levels in an organization, starting often times at the sea suite to make sure that there is a right sponsorship because often times somebody want to change routing and it seems like a great idea two or three levels below. But, when it gets out of whack when it feels uncomfortable and the sea suite needs to step in, that's when everybody's staring at the same set of KPIs and the same metrics. So, you say "No, no. We are going to go after this". We are willing to take these trade offs to go after this because everybody looks at the KPI and says " Wow. I want that KPI". Everybody always forgets that "Oh wait. To get this I got to give these two things up". And, nobody wants to give anything up to get it, right? It is probably the hardest thing that I work on in big transformational things. >> As a consultant? >> Yeah, as a consultant it's to get everybody aligned around. This is what needle we want to move, not what program we want to deliver. Very hard to get the line of business to define it. It's a great challenge. >> It's interesting because in the keynote they laid out exactly what is cognitive. And the 4 E's, I thought they were interesting. Expert. Expression. It's got to be a white box. It's got to be known. Education and Evolution. Those are not kind of traditional consulting benchmarks. You don't want them to evolve, right? >> Right. >> You want to deliver on what you wrote down in the SOW. >> Exactly. >> It doesn't necessarily have a white box element to it because sometimes a little hocus pocus, so just by its very definition, in cognitive and its evolutionary nature and its learning nature, it's this ongoing evolution of it or the processes. It's not a lock it down. You know, this is what I said I'd deliver. This is what we delivered 'cause you might find new things along the path. >> I think this concept of evolution and one of the things we try to be very careful with when you have a brand and a reputation, like USAA, right? It's impeccable, it's flawless, right? You want to make sure that a cognitive asset is trained appropriately and then allowed to learn appropriate things so it doesn't erode the brand. And, that can happen so quickly. So, if you train a cognitive asset with euphemisms, right? Often times the way we speak. And then, you let it surf the internet to get better at using euphemisms, pretty soon you've got a cognitive asset that's going to start to use slang, use racial slurs, all of those things (laughs) because-- No, I am serious. >> Hell you are. >> That's not good. >> Right, that's not bad so, you know, that's one of the things that Ginni has been really, really careful with us about is to make sure that we have a cognitive manifesto that says we'll start here, we'll stop here. We are not going to go in the Ex Machina territory where full cognition and humans are gone, right? That's not what we're going to do because we need to make sure that IBM is protecting the brand reputation of USAA. >> Human discretion still matters. >> Absolutely. >> It has to. >> Alright. Well, we are out of time. Allen, I wanted to give you the last word kind of what you look forward to 2017. We're already, I can't believe we're all the way through. What are some of your top priorities that you are working on? Some new exciting things that you can share. >> I think one of the things that we are very proud of is our work in the text analytics space and what I mean by that is we're ingesting about two years of speech data from our call center every day. And, we are mining that data for emergent trends. Sometimes you don't know what you don't know and it's those unknown unknowns that gets you. They are the things that creep up in your data and you don't really realize it until they are a big enough issue. And so, this really is helping us understand emerging trends, the emerging trend of millennials, the emerging trend of things like Apple Pay, and it also gives us insight as to how our own MSRs are interacting with our members in a very personal level. So, beyond words and language we're also getting into things like recognizing things like babies crying in the background, to be able to detect things like life events because a lot of your financial needs center around life events. >> Right, right. >> You know, getting a new home, having another child, getting a new car, those types of things. And so, that's really where we're trying to bring the computer more as an assistant to the human, as opposed to trying to replace the human. >> Right. >> But, it is a very exciting space for us and areas that we are actually able to scale about 100 times faster than we were fast before. >> Wow. That's awesome. We look forward to hearing more about that and thanks for taking a few minutes to stop by. Appreciated. >> Peter: Thanks, guys. >> Allen: Thank you. >> Alright. Thank you both. With Peter Burris, I'm Jeff Frick. You're watching the Cube from the IBM Chief Data Officer Strategy Summit, Spring 2017. Thanks for watching. We'll be back after the short break. (upbeat music)