>>Good morning fellow nerds and welcome back to AWS Reinvent. We are live from the show floor here in Las Vegas, Nevada. My name is Savannah Peterson, joined with my fabulous co-host John Furrier. Day two keynotes are rolling. >>Yeah. What do you thinking this? This is the day where everything comes, so the core gets popped off the bottle, all the announcements start flowing out tomorrow. You hear machine learning from swee lot more in depth around AI probably. And then developers with Verner Vos, the CTO who wrote the seminal paper in in early two thousands around web service that becames. So again, just another great year of next level cloud. Big discussion of data in the keynote bulk of the time was talking about data and business intelligence, business transformation easier. Is that what people want? They want the easy button and we're gonna talk a lot about that in this segment. I'm really looking forward to this interview. >>Easy button. We all want the >>Easy, we want the easy button. >>I love that you brought up champagne. It really feels like a champagne moment for the AWS community as a whole. Being here on the floor feels a bit like the before times. I don't want to jinx it. Our next guest, Scott Castle, from Si Sense. Thank you so much for joining us. How are you feeling? How's the show for you going so far? Oh, >>This is exciting. It's really great to see the changes that are coming in aws. It's great to see the, the excitement and the activity around how we can do so much more with data, with compute, with visualization, with reporting. It's fun. >>It is very fun. I just got a note. I think you have the coolest last name of anyone we've had on the show so far, castle. Oh, thank you. I'm here for it. I'm sure no one's ever said that before, but I'm so just in case our audience isn't familiar, tell us about >>Soy Sense is an embedded analytics platform. So we're used to take the queries and the analysis that you can power off of Aurora and Redshift and everything else and bring it to the end user in the applications they already know how to use. So it's all about embedding insights into tools. >>Embedded has been a, a real theme. Nobody wants to, it's I, I keep using the analogy of multiple tabs. Nobody wants to have to leave where they are. They want it all to come in there. Yep. Now this space is older than I think everyone at this table bis been around since 1958. Yep. How do you see Siente playing a role in the evolution there of we're in a different generation of analytics? >>Yeah, I mean, BI started, as you said, 58 with Peter Lu's paper that he wrote for IBM kind of get became popular in the late eighties and early nineties. And that was Gen one bi, that was Cognos and Business Objects and Lotus 1 23 think like green and black screen days. And the way things worked back then is if you ran a business and you wanted to get insights about that business, you went to it with a big check in your hand and said, Hey, can I have a report? And they'd come back and here's a report. And it wasn't quite right. You'd go back and cycle, cycle, cycle and eventually you'd get something. And it wasn't great. It wasn't all that accurate, but it's what we had. And then that whole thing changed in about two, 2004 when self-service BI became a thing. And the whole idea was instead of going to it with a big check in your hand, how about you make your own charts? >>And that was totally transformative. Everybody started doing this and it was great. And it was all built on semantic modeling and having very fast databases and data warehouses. Here's the problem, the tools to get to those insights needed to serve both business users like you and me and also power users who could do a lot more complex analysis and transformation. And as the tools got more complicated, the barrier to entry for everyday users got higher and higher and higher to the point where now you look, look at Gartner and Forester and IDC this year. They're all reporting in the same statistic. Between 10 and 20% of knowledge workers have learned business intelligence and everybody else is just waiting in line for a data analyst or a BI analyst to get a report for them. And that's why the focus on embedded is suddenly showing up so strong because little startups have been putting analytics into their products. People are seeing, oh my, this doesn't have to be hard. It can be easy, it can be intuitive, it can be native. Well why don't I have that for my whole business? So suddenly there's a lot of focus on how do we embed analytics seamlessly? How do we embed the investments people make in machine learning in data science? How do we bring those back to the users who can actually operationalize that? Yeah. And that's what Tysons does. Yeah. >>Yeah. It's interesting. Savannah, you know, data processing used to be what the IT department used to be called back in the day data processing. Now data processing is what everyone wants to do. There's a ton of data we got, we saw the keynote this morning at Adam Lesky. There was almost a standing of vision, big applause for his announcement around ML powered forecasting with Quick Site Cube. My point is people want automation. They want to have this embedded semantic layer in where they are not having all the process of ETL or all the muck that goes on with aligning the data. All this like a lot of stuff that goes on. How do you make it easier? >>Well, to be honest, I, I would argue that they don't want that. I think they, they think they want that, cuz that feels easier. But what users actually want is they want the insight, right? When they are about to make a decision. If you have a, you have an ML powered forecast, Andy Sense has had that built in for years, now you have an ML powered forecast. You don't need it two weeks before or a week after in a report somewhere. You need it when you're about to decide do I hire more salespeople or do I put a hundred grand into a marketing program? It's putting that insight at the point of decision that's important. And you don't wanna be waiting to dig through a lot of infrastructure to find it. You just want it when you need it. What's >>The alternative from a time standpoint? So real time insight, which is what you're saying. Yep. What's the alternative? If they don't have that, what's >>The alternative? Is what we are currently seeing in the market. You hire a bunch of BI analysts and data analysts to do the work for you and you hire enough that your business users can ask questions and get answers in a timely fashion. And by the way, if you're paying attention, there's not enough data analysts in the whole world to do that. Good luck. I am >>Time to get it. I really empathize with when I, I used to work for a 3D printing startup and I can, I have just, I mean, I would call it PTSD flashbacks of standing behind our BI guy with my list of queries and things that I wanted to learn more about our e-commerce platform in our, in our marketplace and community. And it would take weeks and I mean this was only in 2012. We're not talking 1958 here. We're talking, we're talking, well, a decade in, in startup years is, is a hundred years in the rest of the world life. But I think it's really interesting. So talk to us a little bit about infused and composable analytics. Sure. And how does this relate to embedded? Yeah. >>So embedded analytics for a long time was I want to take a dashboard I built in a BI environment. I wanna lift it and shift it into some other application so it's close to the user and that is the right direction to go. But going back to that statistic about how, hey, 10 to 20% of users know how to do something with that dashboard. Well how do you reach the rest of users? Yeah. When you think about breaking that up and making it more personalized so that instead of getting a dashboard embedded in a tool, you get individual insights, you get data visualizations, you get controls, maybe it's not even actually a visualization at all. Maybe it's just a query result that influences the ordering of a list. So like if you're a csm, you have a list of accounts in your book of business, you wanna rank those by who's priorities the most likely to churn. >>Yeah. You get that. How do you get that most likely to churn? You get it from your BI system. So how, but then the question is, how do I insert that back into the application that CSM is using? So that's what we talk about when we talk about Infusion. And SI started the infusion term about two years ago and now it's being used everywhere. We see it in marketing from Click and Tableau and from Looker just recently did a whole launch on infusion. The idea is you break this up into very small digestible pieces. You put those pieces into user experiences where they're relevant and when you need them. And to do that, you need a set of APIs, SDKs, to program it. But you also need a lot of very solid building blocks so that you're not building this from scratch, you're, you're assembling it from big pieces. >>And so what we do aty sense is we've got machine learning built in. We have an LQ built in. We have a whole bunch of AI powered features, including a knowledge graph that helps users find what else they need to know. And we, we provide those to our customers as building blocks so that they can put those into their own products, make them look and feel native and get that experience. In fact, one of the things that was most interesting this last couple of couple of quarters is that we built a technology demo. We integrated SI sensee with Office 365 with Google apps for business with Slack and MS teams. We literally just threw an Nlq box into Excel and now users can go in and say, Hey, which of my sales people in the northwest region are on track to meet their quota? And they just get the table back in Excel. They can build charts of it and PowerPoint. And then when they go to their q do their QBR next week or week after that, they just hit refresh to get live data. It makes it so much more digestible. And that's the whole point of infusion. It's bigger than just, yeah. The iframe based embedding or the JavaScript embedding we used to talk about four or five years >>Ago. APIs are very key. You brought that up. That's gonna be more of the integration piece. How does embedable and composable work as more people start getting on board? It's kind of like a Yeah. A flywheel. Yes. What, how do you guys see that progression? Cause everyone's copying you. We see that, but this is a, this means it's standard. People want this. Yeah. What's next? What's the, what's that next flywheel benefit that you guys coming out with >>Composability, fundamentally, if you read the Gartner analysis, right, they, when they talk about composable, they're talking about building pre-built analytics pieces in different business units for, for different purposes. And being able to plug those together. Think of like containers and services that can, that can talk to each other. You have a composition platform that can pull it into a presentation layer. Well, the presentation layer is where I focus. And so the, so for us, composable means I'm gonna have formulas and queries and widgets and charts and everything else that my, that my end users are gonna wanna say almost minority report style. If I'm not dating myself with that, I can put this card here, I can put that chart here. I can set these filters here and I get my own personalized view. But based on all the investments my organization's made in data and governance and quality so that all that infrastructure is supporting me without me worrying much about it. >>Well that's productivity on the user side. Talk about the software angle development. Yeah. Is your low code, no code? Is there coding involved? APIs are certainly the connective tissue. What's the impact to Yeah, the >>Developer. Oh. So if you were working on a traditional legacy BI platform, it's virtually impossible because this is an architectural thing that you have to be able to do. Every single tool that can make a chart has an API to embed that chart somewhere. But that's not the point. You need the life cycle automation to create models, to modify models, to create new dashboards and charts and queries on the fly. And be able to manage the whole life cycle of that. So that in your composable application, when you say, well I want chart and I want it to go here and I want it to do this and I want it to be filtered this way you can interact with the underlying platform. And most importantly, when you want to use big pieces like, Hey, I wanna forecast revenue for the next six months. You don't want it popping down into Python and writing that yourself. >>You wanna be able to say, okay, here's my forecasting algorithm. Here are the inputs, here's the dimensions, and then go and just put it somewhere for me. And so that's what you get withy sense. And there aren't any other analytics platforms that were built to do that. We were built that way because of our architecture. We're an API first product. But more importantly, most of the legacy BI tools are legacy. They're coming from that desktop single user, self-service, BI environment. And it's a small use case for them to go embedding. And so composable is kind of out of reach without a complete rebuild. Right? But with SI senses, because our bread and butter has always been embedding, it's all architected to be API first. It's integrated for software developers with gi, but it also has all those low code and no code capabilities for business users to do the minority report style thing. And it's assemble endless components into a workable digital workspace application. >>Talk about the strategy with aws. You're here at the ecosystem, you're in the ecosystem, you're leading product and they have a strategy. We know their strategy, they have some stuff, but then the ecosystem goes faster and ends up making a better product in most of the cases. If you compare, I know they'll take me to school on that, but I, that's pretty much what we report on. Mongo's doing a great job. They have databases. So you kind of see this balance. How are you guys playing in the ecosystem? What's the, what's the feedback? What's it like? What's going on? >>AWS is actually really our best partner. And the reason why is because AWS has been clear for many, many years. They build componentry, they build services, they build infrastructure, they build Redshift, they build all these different things, but they need, they need vendors to pull it all together into something usable. And fundamentally, that's what Cient does. I mean, we didn't invent sequel, right? We didn't invent jackal or dle. These are not, these are underlying analytics technologies, but we're taking the bricks out of the briefcase. We're assembling it into something that users can actually deploy for their use cases. And so for us, AWS is perfect because they focus on the hard bits. The the underlying technologies we assemble those make them usable for customers. And we get the distribution. And of course AWS loves that. Cause it drives more compute and it drives more, more consumption. >>How much do they pay you to say that >>Keynote, >>That was a wonderful pitch. That's >>Absolutely, we always say, hey, they got a lot of, they got a lot of great goodness in the cloud, but they're not always the best at the solutions and that they're trying to bring out, and you guys are making these solutions for customers. Yeah. That resonates with what they got with Amazon. For >>Example, we, last year we did a, a technology demo with Comprehend where we put comprehend inside of a semantic model and we would compile it and then send it back to Redshift. And it takes comprehend, which is a very cool service, but you kind of gotta be a coder to use it. >>I've been hear a lot of hype about the semantic layer. What is, what is going on with that >>Semantec layer is what connects the actual data, the tables in your database with how they're connected and what they mean so that a user like you or me who's saying I wanna bar chart with revenue over time can just work with revenue and time. And the semantic layer translates between what we did and what the database knows >>About. So it speaks English and then they converts it to data language. It's >>Exactly >>Right. >>Yeah. It's facilitating the exchange of information. And, and I love this. So I like that you actually talked about it in the beginning, the knowledge map and helping people figure out what they might not know. Yeah. I, I am not a bi analyst by trade and I, I don't always know what's possible to know. Yeah. And I think it's really great that you're doing that education piece. I'm sure, especially working with AWS companies, depending on their scale, that's gotta be a big part of it. How much is the community play a role in your product development? >>It's huge because I'll tell you, one of the challenges in embedding is someone who sees an amazing experience in outreach or in seismic. And to say, I want that. And I want it to be exactly the way my product is built, but I don't wanna learn a lot. And so you, what you want do is you want to have a community of people who have already built things who can help lead the way. And our community, we launched a new version of the SES community in early 2022 and we've seen a 450% growth in the c in that community. And we've gone from an average of one response, >>450%. I just wanna put a little exclamation point on that. Yeah, yeah. That's awesome. We, >>We've tripled our organic activity. So now if you post this Tysons community, it used to be, you'd get one response maybe from us, maybe from from a customer. Now it's up to three. And it's continuing to trend up. So we're, it's >>Amazing how much people are willing to help each other. If you just get in the platform, >>Do it. It's great. I mean, business is so >>Competitive. I think it's time for the, it's time. I think it's time. Instagram challenge. The reels on John. So we have a new thing. We're gonna run by you. Okay. We just call it the bumper sticker for reinvent. Instead of calling it the Instagram reels. If we're gonna do an Instagram reel for 30 seconds, what would be your take on what's going on this year at Reinvent? What you guys are doing? What's the most important story that you would share with folks on Instagram? >>You know, I think it's really what, what's been interesting to me is the, the story with Redshift composable, sorry. No, composable, Redshift Serverless. Yeah. One of the things I've been >>Seeing, we know you're thinking about composable a lot. Yes. Right? It's, it's just, it's in there, it's in your mouth. Yeah. >>So the fact that Redshift Serverless is now kind becoming the defacto standard, it changes something for, for my customers. Cuz one of the challenges with Redshift that I've seen in, in production is if as people use it more, you gotta get more boxes. You have to manage that. The fact that serverless is now available, it's, it's the default means it now people are just seeing Redshift as a very fast, very responsive repository. And that plays right into the story I'm telling cuz I'm telling them it's not that hard to put some analysis on top of things. So for me it's, it's a, maybe it's a narrow Instagram reel, but it's an >>Important one. Yeah. And that makes it better for you because you get to embed that. Yeah. And you get access to better data. Faster data. Yeah. Higher quality, relevant, updated. >>Yep. Awesome. As it goes into that 80% of knowledge workers, they have a consumer great expectation of experience. They're expecting that five ms response time. They're not waiting 2, 3, 4, 5, 10 seconds. They're not trained on theola expectations. And so it's, it matters a lot. >>Final question for you. Five years out from now, if things progress the way they're going with more innovation around data, this front end being very usable, semantic layer kicks in, you got the Lambda and you got serverless kind of coming in, helping out along the way. What's the experience gonna look like for a user? What's it in your mind's eye? What's that user look like? What's their experience? >>I, I think it shifts almost every role in a business towards being a quantitative one. Talking about, Hey, this is what I saw. This is my hypothesis and this is what came out of it. So here's what we should do next. I, I'm really excited to see that sort of scientific method move into more functions in the business. Cuz for decades it's been the domain of a few people like me doing strategy, but now I'm seeing it in CSMs, in support people and sales engineers and line engineers. That's gonna be a big shift. Awesome. >>Thank >>You Scott. Thank you so much. This has been a fantastic session. We wish you the best at si sense. John, always pleasure to share the, the stage with you. Thank you to everybody who's attuning in, tell us your thoughts. We're always eager to hear what, what features have got you most excited. And as you know, we will be live here from Las Vegas at reinvent from the show floor 10 to six all week except for Friday. We'll give you Friday off with John Furrier. My name's Savannah Peterson. We're the cube, the the, the leader in high tech coverage.

hey welcome back to los angeles lisa martin here with the cube we are live at kubecon and cloudnativecon 21. it's been great to be here we've been broadcasting the last couple of days about 2 700 people joining us in person great buzz great energy i've got two guests here next joining me remotely please welcome it's reich the vp technologist at dell emc anivis iyer senior principal product manager at dell technologies gentlemen welcome to the program thanks for having us lisa thank you lisa and we're pleased that you're joining us today it's like let's go ahead and start with you let's talk we've seen a lot of of uptick and kubernetes it's been picking up a lot what are some of the things that you're seeing through your lens right that's a great question lisa so really we need to take a step back bobby into 2019 we just mentioned in-person conferences so back then we started to see a slow adoption of customers that are starting to play with kubernetes in their test environment maybe running some pocs but then the pandemic happened obviously and we started to see huge explosion in terms of adoption and accelerating the digital based projects for our customers so they're really starting to pick up kubernetes and use it heavily in their production and of course in addition to their test and dev environments as well and because of that adoption they started to think about other scenarios and other considerations that are relevant for their production environment which is based upon kubernetes things like disaster recovery availability all of those things that typically you don't worry about when you just run them in a small desk or a poc environment but are super critical for our customers and you know it's the largest storage company in the world we have the smallest company customers in the world but also the largest and the most demanding one it's a really huge adoption that needs to basically accelerate all of those aspects that belong to an enterprise environment that happens to run on kubernetes itself if ask do you see something similar yeah absolutely i agree with itzik and actually one of the brief stories actually i start out with is because a few years ago actually several years ago when i was taking a cab in new york remember the point-of-sale terminal was not working so you know you took my credit card just like use the magnetic spike so not having the technology access was like an inconvenience but it still could transact but now today's age when you look at digital transform trans digitally transformed companies starting with all these web companies like you know you've got like uber lyft and things like that but then you also have mainstream companies where the entire business is now taking over digital hence all these applications are the ones that are powering the entire business if you will and not having these applications available or these apps available uh will basically the business is gonna lose money and and that's and that's what is and the pandemic has only accelerated digital transformation right because everyone working from home and and also the customers are also remote so now you have the entire operation is just software is running the business pretty much every company is a technology company and then you have you know and then all these applications they are modernized so they are modernized in the way that they're not built to the traditional architectures they're now using you know microservices devops and agile these are three major aspects that kind of you know drove the new application modernized applications to build more complex applications and kubernetes has emerged as the sole platform that can you know kind of serve the underlying platform between all of these aspects and hence we see that you know kubernetes adoption has taken off a lot because pretty much every organization is running several projects within the enterprise including app modernization you know transformation of any kind of secondary kind of use cases iot you know the whole digital transformation story is kind of running on kubernetes and as sick was pointing out so now kubernetes are simmered as the key infrastructure as a service layer if you will or above the infrastructure service and it needs to consume storage and it needs to have you know all these traditional capabilities that were for uh for applications right i mean like uh disaster recovery uh having enterprise grade uh availability aspects like you know for this uh data protection things like that and that's sort of is and the enterprise capabilities are relatively i would say uh accelerating a lot earlier kubernetes was more on the non-enterprise aspects of the journey now we are seeing a lot more enterprise growth are you seeing your conversations within organizations elevate up the chain where kubernetes is concerned is this a c-level conversation or the understanding that from a competitive differentiation perspective from a modernization perspective it's the direction they need to go in yeah absolutely and for them you know vmware ran itself a couple of months ago about the reasons that are important for customers to run containers in production there were like ten tens of them but the number one reason is to accelerate software adoption and to basically write codes faster that's like the number one reason it's not about the technology itself you know technology is just an enabler and the enabler is to write the code as quickly as you could deploy it in test and dev quickly as you could run some qa cycles on it and release release release the code that's at the end of the day that's the main difference between the old way of the waterfall approach to the new way of agile approach which eventually got translated into the infrastructure layer itself it needs to accommodate those changes if you will well releasing code faster is going to enable organizations presumably in any industry to be able to develop and release products and services faster to the demanding consumer market i imagine that's absolutely correct we've all got spoiled by the smartphone industry we'll just expect a new version to be just deployed to your device almost every day now it's exactly the same it is we i think we carry that i think it's i think it's impossible not to carry that consumer expectation from our consumer life into our business life and we just expect that things are going to work that way because in our consumer lives they do i want to ask you guys about is that this question is directly for you talk to me about csi what is it besides a tv show i know you have a great answer for this and many spin-offs by the way right not just a single one csi right so let's take a step back into 2015. docker rebecca dockercon they sit on the stage and during the keynote and they explain that you should write your code in the 12 factor way resiliency should be built in into the containers themselves and you shouldn't care about storage persistency now we're in the storage industry for the best part of my life right now and storage persistence is important if a customer lose data that's a very bad day for the customer and possibly a very bad day for me as well so it's all about the data nothing else really matters the data itself is the goal and so there was no data persistency back then you go here and we actually work with the startup that did just storage consistency for containers basically meaning the ability to provision a volume from storage array into kubernetes and kubernetes will know about this that style tab went busted but the need still existed and so into that need google came and they come up with this api called container storage interface short for csi that does exactly that it allows kubernetes administrator of the kubernetes api to consume storage from the underlying storage array so provision volumes map mapping volumes taking a snapshot of the volume and mapping those from those very basic capabilities now those capabilities are very basic and we now have customers that are telling us i need far more than just the ability to provision a volume for my kubernetes environments i need this volume to be protected i need this volume to be replicated and it is volume to be protected into a backup device all of those things that csi doesn't know to do today no we didn't know to do in the near future so what we did is we said right we're not going to reinvent the wheel that's csi we're not just going to repeat csi all over again we're going to extend csi with open source tools that will enable our customers to do all of those things that are just mentioned before so csm is container storage modules which is what we announced today and it's very high level it provides you i provided the capabilities to do the following the first one is the observability module so if you're monitoring your open source environments you are very very likely to use open source tools like graphing and commit use so we have this plugin that allows you to monitor your storage array with gofundme and prometus and really uh becomes the liaison point between the storage admin the kubernetes admin they can connect both to the console and each really understand the the entity that is not aware of i call it the two-way mirror base second module is the resiliency module kubernetes is very infant in terms of understanding storage it doesn't understand storage failure conditions and so our resiliency module run as the k3s is like a minimum version of kubernetes if you will which keeps monitoring both the storage array and the host and in case of a storage arrow it knows to act upon it and do things like volume unmapping and map those volumes to other surviving servers in the product center etc the other module is the replication module so back into 2015 uh customers are basically telling us today i want to use kubernetes but i also want to replicate the data to either a passive site or an active site and in case of a failure if my primary site goes down i want to fail over this kubernetes volumes and data to a remote site so literally within a click of a button you can fail over your kubernetes environment from site a to site b using the underlying storage array capabilities replication etc etc and the other module that we've also announced is the volume group snapshots so instead of just taking a single volume which is what csr is all about you can actually take multiple volume that belong to multiple micro services that at the end of the day running within those containers in order to really back up a service and not just the micro service itself so all of these modules and future modules that will come in the future as well belong to csm and csm for us is just the beginning it's everything that our most most the demanding customers want us to provide today and they are not willing to wait for csi to catch up base got it so we you've done a great job of explaining what csi is what it isn't what csm is and all the great things that were announced today let's talk about the data protection the security angle we've seen so much change in the security the threat landscape in the last 18 months we've seen ransomware become a household word the proliferation of ddos attacks and of course there's this scattered workforce that is still scattered talk to me about why data protection for kubernetes and what are some of the unique needs that that presents uh sure uh thanks lisa so um so when you look at the kubernetes landscape it originally started out with mostly the front-end aspects multi like you know like web tier type applications but as the landscape has evolved now we are seeing actually in the kubernetes community also there has been newer concepts like stateful sets for example which allows you to have more persistent type uh or basically they you know the application that have retained state and data uh in the kubernetes cluster and we are seeing a huge proliferation and that is also increasing you know across the board on uh for example everything from experimentation or like any kind of user experience kind of data the understanding about sessions you know what users like what they don't like to all critical operational aspects to transactional elements too all of them being brought into the kubernetes we are seeing organizations in various stages of the journey and then add on to the additional uh capabilities on the storage side as she was mentioning about csi and csm and are basically the ways for the kubernetes layer to consume these storage services so when you're building these modern applications uh the state is now preserved as part of the kubernetes and actually recently we had a case with one of the customers we've had and uh so they did not have data protection as part of their kubernetes and uh and you know and we are seeing this in several organizations where you have an it ops kind of a team and there is a devops team there's a two-speed it concept so devops teams a lot of time they do not take into consideration a lot of these uh you know disaster recovery and uh you know the data protection aspects as part of the design and then one of the customers just what happened and they lost you know data because the you know their systems crashed and it was not through ransomware luckily but it was through uh you know a general logical you know failure of hardware things like that and so they could not recover that so they had to go back and they had to like rest all the whole thing so they started investing in saying oh we need a ways to protect the data so that i can recover so data is all about recovery it's about you know making sure you can record to a certain point in time and also recovering in the minimal amount of time and the challenges that kubernetes adds on top of traditional application that you know the entire application definition in kubernetes is split across multiple of these smaller metadata aspects like the application itself will have labels they will have uh you know they'll have secrets they'll have config maps they'll have custom resource definitions they have all this additional metadata that make up the entire application not just the data so you need to have all of that captured in context in a cloud native fashion if you if you're trying to protect that kubernetes environment and that's kind of a little bit of a unique challenge and then from a security aspect that you alluded to from kubernetes yes there are been you know multiple security challenges that we see although we don't directly work on the front end on the uh on the prevention side but on the cure side data protection is an important aspect right i mean if you look at the open source community there is so much open source today and how do you know that the open source and the api that you're consuming is is coming from a valid source you need so there is all kinds of like different security solutions that kubernetes community offers to validate making sure the source code is good the apis are authenticated and you know authorized things like that so there is a lot of these but even despite that you know there is always ability for some attacks to sneak in and that's where data protection is providing that cure so in case something does happen and you have a ransomware attack i have a cyber security vault or i have data stored in a secure fashion in a panic room if you will that i can so my business like i was alluding to my earlier example the business depends on that data and that operational transactional customer data and you need to recover that and you need to store it in a secure place and that's sort of the whole aspect of that it's got to be recoverable that's the whole point guys thank you so much for joining me talking to me about what you're seeing from a kubernetes adoption acceleration perspective thank you for helping me learn a new definition of csi not a show or a spin-off and talk to us about what csm is and the things that you are the modules that you're announcing today we appreciate your candor and your time thank you lisa thanks for having us my pleasure for my guests i'm lisa martin coming to you live from los angeles at kubecon cloudbanditcon21 be right back dave nicholson will rejoin me with our next guest stay tuned you

>> Man: Live from Atlanta, Georgia. It's theCUBE. Covering Citrix Synergy Atlanta 2019. Brought to you by Citrix. >> Hey welcome back to theCUBE, Lisa Martin with Keith Townsend live from Atlanta, Georgia. We're at Citrix Synergy 2019, the first time theCUBE has been back here in eight years and I'm geakin out even more, yes, I know it's early, two man hand CMO and EBP of Strodigy CIRTIX TIBB, it's great to have you back on theCUBE. >> Well thanks for joining us here. >> The Keno was awesome this morning, Keith and I were both tweeting like crazy and like and we were like, Wow, we're going to have a great couple of days. >> Thank you. >> You can hear all of the networking and the innovation and the conversations going on behind us here in the Solutions EXPO. I think record number of people attending live, as well as watching the live stream today. There was at least one round of applause, standing here all night. Citrix, a lot of transformation in the last year alone. Really talking about the employee experience as a critical enabler of digital business transformation. Talk to us about that. Yeah, absolutely I mean, with all the technology, technology choices we've had with Cloud and Sass and Mobile. We've created a lot of opportunity but we've also created a lot of complexity. Both through IT and especially for the employee who now needs no navigate across all of this different environment to try get a bit of information or to get their key work done. And so, Citrix and our Customers were saying: Hey look, employee experience has become a sea level and board level imperative. So what we've done is, we've unveiled and continued to extend upon our digital work space. Not just a place where we've unified access to everything an employee needs to be productive. All their Sass Apps, Web Apps, Mobile Apps and content, wrapper that in a layer of security so that IT and the company are confident that Applications and information is more secure in the workspace than now. But now we're infusing intelligence into the workspace. Machine learning and simplified work flows, in order to guide an employee through their day, so they don't need to spend all their time navigating multiple apps, but the tasks and insides that they need to get done are presented to them veery quickly, they can move on and get to perform their best work. >> So Tim, you're literally preaching to the choir. Me and Lisa, we get it, we understand it and then even at they key note, David was preaching to all the major announcements, big claps. Thousands of people clapping. The innovation and ideal of extending the workspace to the intelligent experience, I think the Citrix faithful today, get that. But a seven trillion Dollar problem that you guys are addressing, you just mentioned, but now we're talking about talking to the CEO, the CIO, the CMO, the COO. Talk about expanding message beyond the faithful into the sea squeed. How's that impacting your jobs and how are you getting that message out there? >> Yeah, that's a great question. You're absolutely right. Employee experience is something that is shared. In fact, we've just done a considerable amount of research into that with the Economist on a global basis. What we were finding is IT and HR are sharing this problem together. The rethinking, not just the digital environment of how they're delivering technology to the employee but the physical space and the culture and how it all weaves together. And how we're engaging within Citrix at a much higher level with not just the CIO but with the Chief Human Resources officer, the CEO, the CFO, is because employee experience and how well an employee feels when they have access to the information and tools they need to get their job done, is directly related to the business outcomes the company is trying to achieve. You know, its proven to deliver greater customer satisfaction, increase revenues, greater profitability, all the metrics that really move a business. >> And you know, this is pervasive across any industry and every roll in every organization. I mean, the cool video that David showed this morning, show an example of a Senior Marketing Manager who wants to deliver Rock Star campaigns for her company, but she's got before Citrix workspace and intelligent experience. All these different apps and all this distraction, every couple of minutes distraction. And you think about how that impacts that Marketing Manager's role even all the way to like a call center. And how a call center employee is in the front lines with the customer, whether it's your ISP or something who has so much choice. If that call center person doesn't have access to all the apps and the information that they need, not only are you effecting the employee experience and potentially causing attrition, but the end user customer that service might say, forget it, I'm going to go somewhere else. >> Yeah, absolutely. I mean, if you think about it, we all have that experience where you call a call center and they might not have the answer for you or in some cases the connection might be poor. So really what we're trying to do with the digital workspace is eliminate that. We talk about experiences, it's not just unifying and infusing intelligence into it, but we also leverage our networking portfolio to ensure reliable connectivity. So that employee has access to the applications they need, they can reliably access the information they need and any kind of their telephony or your voiceover IP is consistent. So you or I think they're on a landline in a big call center and they might be working from home but still have access to everything they need through the Citrix Workspace. >> So just a couple of weeks ago, I was at SAP Sapphire, we're talking about customer experience, employee experience. Kind of the ex-data versus the old-data, operational data. And Citrix in the past has been about operational data. You have to share stuff with your warehouse about improving analytics so administrators and engineers can deliver applications and experiences better. Lets talk about the user experience in this new, or the employee experience in this future of work. I have this SAP green screen and man, would my job be so much easier if I could just push a button and get that data into Salesforce, but I have to engage IT for that. I have to open the ticket and we have to take it through project, 6 months later we abandon it because the industry has moved on. How's Citrix going to make that faster for the employee and improving my employee experience? >> Well fist of all, coming from an Enterprise application background, myself, including SAP, I know the depth of functionality of those applications. And for specialized roles, whether you're in supply chain or finance or alike, they spend their day in that core application. However, the rest of us, we're hired for a specific purpose. Whether its the example we gave onstage today about Maria, the Senior Marketing Director, or whether its an engineer who wants to spend their time building product. We were at hight to spend our day navigating, expense reporting apps or performance review apps or other types of applications that we're all exposed to. They're not our primary application, we have to learn a new interphase, we have to manage different authentication. And what the workspace does is in the words of one of our customers, is by unifying is all and being able to reach into those applications and extract out the information and task that's very personal to you. One customer says to their employees, you may never need to log into an enterprise application again, but you'll still get all the utilities, all the value because you have all the insides you need and you can get them quickly without needing to navigate or search across multiple applications. So you can get that task, approve that expense report like that. Without needing to go through 4 screens to do it and take you away from your core job. So really what this is all about, is removing the noise from an employees day so they can perform at their very best. >> So critical because, Sorry Keith, one of the stats aslo I think David shared this morning, was that enterprise software is designed for power users. Which is 1% of the population. So for those folks who need to get their job done as effectively as possible, so that their delivering what they need to and the big end users experience is what it should be. That's to be able to say, you don't ever have to log into an enterprise application again and making that experience personalized, Game changers. >> Absolutely, I mean we think about the frustration that employees have today and that they would share the findings today from the Gallops study but 80% of employees are disengaged at work. The number one reason happens to be around their level of their manager, but the number two one is they don't feel they have access to the right information tools to do their job. They want to get that noise out of their day so they can do what they were hired to do and what they're passionate about. >> So we talked a lot today about the familiarization of enterprise tech. We love these things. We don't love these things because the hardware is great, we love these things because we're able to do our jobs. So whether I'm downloading a app or Angry Birds or whatever experience that I'm having on it is, I get instant gratification from this devise. Talk to us about the overall potential of speed to value in a repeatable process that Enterprises can enjoy around digital transformation based on Citrix versus you know, I've heard similar things from ISV's. They can come in and write a customization from an Enterprise app into another solution, simplify a specific job, but if I have to do that for every application, one I don have the money, bandwidth, time and the industry will pass me up. How are you guys bringing this consumerized experience to the future world. >> Yeah, that's a great illustration is our mobile devices. We live on our mobile devices. A lot of Enterprise application have created really good mobile applications. You know, concur from SAP where I came from, that's a great experience. Very quick to go in. Salesforce, an awesome tool, their mobile experience is different from their regular experience so you have to relearn and navigate. And then there's others that never really created a mobile experience so we're all doing this on our phone and trying to get that done. And even if every, to your point, if every individual enterprise app had a great mobile experience, that still means we need to navigate a whole bunch of interfaces. What we're doing by unifying this into a single digital workspace by curating and personalizing your workday and creating a work stream very similar to what Facebook and others have done for our personal screen and how we get information through that feed, how we get news through that feed. We're doing the same for work. So on a mobile device that experience is so much richer than we've seen since almost the invention of the smart phone. >> So as we talk about the consumerization of Tech, big announcements with Azure and Google. How does that impact that new audience when you go talk to another CMO at a big Car Manufacturer? Why should they get excited about Azure or Google compute? They really don't see that. >> There's no doubt that the world is moving to the cloud, but everyone's moving at their own pace right? Companies has invested decades in some cases of infrastructure and I promise they're not going to move that to the cloud over night, but they are beginning to move certain workloads, certain styles and, by the way, they want to choice of multiple clouds. Which is why Citrix has invested to partner with all the major cloud providers to allow our customers to have that choice. So if they want to leverage some aspects of Azure, they want to move some of the Citrix workloads there, they can do that. If they want to virtualize, as you heard today, the announcement with Google, if they want to take some of their Citrix virtualization, virtual apps or virtual desktops and move that to Google cloud, that's available to them. Including now, as we announced today, with automated provisioning. So IT can quickly set up a desktop, maybe its for a new hire, maybe its for a contractor to come in and give him the tools they need to be productive. So if companies want choice across those clouds, they don't want to have locked in, and they're going to move at their own pace. As we heard today from Partner's Healthcare for example, security first, cloud considered. Their considering aspect is to move to the cloud when it makes sense and they want to have that flexibility to allow them to move at their own pace and make it seamless with their on-premises infrastructure. And that's what we provide. >> That flexibility is key and you brought up, every business today lives in a hybrid multi cloud world. So employees, with that employee experience, needs to deliver access to Sass apps, mobile apps, web apps. To deliver that great employee experience, but I want to turn the times a little bit and take a look at what you guys are doing with marketing and on the business strategy side of Citrix to help deliver that outstanding employee experience to your customers. By way of you CSM team and you even have a relatively new adoption marketing team. I'd love to know how that ladder fits into your business strategy. >> Right, so I'll come to the adoption marketing team in a moment, but the first thing we're doing is, as illustrated here earlier, is that this discussion around employee experience, as it becomes a sea level and board level imperative, it's become a company wide initiative. And so, from a marketing perspective, we have not only gone higher up in the organization having a much more strategic discussion around how we can drive the business outcomes of the companies want to achieve. But also making sure we're putting it in the language of these other roles. All right, HR wants to talk about employee engagement and how we can demonstrate through the work space of how we're doing that. IT wants to talk about adoption of their technologies in the like. So getting to the customer adoption component, so within, as you move to the cloud, it's no longer, I'll sell you a product, good luck. When you engage with a customer, once you get that agreement, that's when the real work starts, right. You're in a long term service agreement and the value they extract from your application, the adoption they get, is going to determine their level of success and their level to renew with you at the end of the term. So we've put a lot of investment as a company into what we call our customer success team. Folks that are 'view them as the coach at the gym'. That's the difference between you buy a treadmill at home, you might use it for a while and it becomes a towel rack. Or you join the gym and your trainers there telling you how to get the best performance. That's what our customer success team does, but top do that at scale and to engage on a real time basis, we've paralleled that with the customer adoption marketing team. And really, we're providing both out-of-product and in-product marketing queue to the customer, to the user of how best to take advantage of the product they've already subscribed to. >> That's exciting, Tim. Speaking of customers' success, the last question as we wrap here. You guys kind of have the American Idol of Customer Awards, The Innovation Awards, there are down to three finalists. We will get to speak to all three of them over the next two days. But something that I mentioned to you that really peaked my interest is, is this is an Awards opportunity for other folks to vote on. And then the winner, all our Ryan Seacrests' are going to be here to announce it on Thursday. Tell us a little bit about the Customer Innovation Awards and how these customers are really articulating the value prop of Citrix. >> Yeah the Citrix Customer Innovation Award's one of my favorite times of the year. The program's been around for a number of years and its really grown a cold following within the Citrix community as customers get nominated based on their deployment and the business outcomes they're driving. We have an, initially an individual panel that widows all those nominations down so that panel consist of former winners as well as analysts and other influencers in the community. And then to your point, the three finalists that we have right now, we expose their stories to the world to everyone here at Synergy and beyond. And they get to vote. So the votes are going to be tallied, I believe the voting polls close on Wednesday night and then we'll announce the winner on Thursday and the customers love it. Not only do they get the recognition, but the other customers love it because I have those same problems. I want to be able to solve it and I want to understand how Citrix can help me. >> And that is as a marketer you know, I know I'm preaching to the choir, but there's no better brand validation than the voice of your customer articulating how their business is benefiting significantly and giving them the opportunity to talk to peers and in the industry. >> Absolutely, that's why we're in it, for the customer's success. >> Well, we'll be anxiously awaiting to hear the results on Thursday Tim, I'm already excited for next year. So, thank you so much for having theCUBE, Keith and me >> Great >> At Synergy 2019 >> Thank you for being here. Thank you for having me. Our pleasure, for Keith Townsend and I'm Lisa Martin, live from Citrix Synergy 2019 from Atlanta. Thanks for watching. (upbeat music)

>> Announcer: Live, from Las Vegas, it's theCUBE, covering ServiceNow Knowledge 2018. Brought to you by ServiceNow. >> Welcome back, everyone, to theCUBE's live coverage of ServiceNow Knowledge18. I'm your host, Rebecca Knight. We are theCUBE. We are the leader in live tech coverage. I'm joined by Landon Cook. He is a director of Customer Service for the State of Tennessee. It's your first time on theCUBE. You're going to live it. >> Okay, great, I hope so. Brand new. >> So, you're a director of Customer Service, before the cameras were rolling, we were talking. Does every state have such a department? >> Not exactly, and even in our department, the idea of customer service being a focal point and the creation of an office for us, it's all brand new. So, my office of customer service didn't even exist until five years ago, and I've had one predecessor in that time. And this all came from a new focus and state government on the Customer Service Delivery Model. And usually we had been focused on federal rules and regulations, audit findings, always being good stewards of taxpayers dollars, but service delivery hadn't come from the mouth of the governor, usually itself. So, this is all pretty new for us, and from peers I talk with in other areas, I may have a contact who is maybe the lead of customer service in their area, but the idea of an office that exclusively exists to improve customer service throughout our department, and eventually throughout the state, I believe we're in new territory here. >> So this is really the baby of your governor, Bill Haslam, who has really said he wanted, what was it, Customer Focus Government. So what does that mean? >> So, Customer Focus Government started right after Governor Haslam came to office, in 2011. The idea behind it, he created an initiative, and he stated that our goal was to provide the best possible customer service, at the lowest possible cost. And again, that may not seem that new in many industries, but in state government, state operations, that was kind of ground breaking. And that's what's led to us talking, actually, about the customer experience, the agent experience, and how can we actually redefine customer service in government? And my department, we are one of 47 state agencies. In my department, I talked just briefly about the history, going back there five years, and you see this slowly popping up in all these different departments, and the idea is that we're all going to, at some point, be able to come together and deliver customer service as a state, instead of as each individual department. We're actually going to be able to share the scope of services, and really tailor service delivery to each citizen's need through a log in portal, there's all sorts of stuff we talk about now that's brand new, I'm sorry. >> So it's helping citizens do their citizenship duties. So this is helping them register to vote, registering at the DMV, getting fishing licenses, building permits, that kinds of thing. So, how do you do it? How do you service now? >> So, we're babies, here. So ServiceNow is, the new CSM solution, for the entire enterprise, for the state of Tennessee. My department, the Department of Human Services, we are the pilot agency for all those 47 I described. And we're about seven months in, so it's all been pretty fresh for us. But how this works right now, is we're using it primarily for inquiry management, phone calls, emails, web forms and chat, things people typically think of as customer service. And so, what we're doing with service now, and we started very carefully, very small, we had a very tiny pilot to start with, but once we launched, after October, we very quickly realized that ServiceNow was so collaborative and cooperative with us, and they were just as engaged in our success as we were, that we were building a partnership with CSM. It's kind of new to ServiceNow, too, right? So, it was new to us, new to them, and we're really kind of intertwining and growing together here. Even though we're using it, just now, for inquiry management and typical customer service delivery, once our department has it fully integrated through all of our various, we have 12 divisions just within our department, once we have it integrated there, we're going to take that model, and we're going to go to other state agencies. We've actually already had, there are three other state agencies that are probably going to be joining on board, if they haven't already. This has been a very fast standup for us. And we're going to, eventually it's going to go from, "Well, wow, DHS delivers great customer service," and then instead, DHS is partnering with the Department of Health to deliver customer service to people who need it. And we'll start, slowly, just putting everyone together so in the future citizens of Tennessee can just ask for assistance with something, and the state knows what they need, and the state knows how to deliver it, and can do all that assignment and sharing in the responsibilities behind the scenes, through ServiceNow. >> Anything you can do to improve the DMV experience. So, I mean, that is the thing. You're trying to make people's lives easier, better, simpler, more streamlined, but what was Haslam's goal? What was his impetus for starting this? >> You know, that's actually a hard one for me to say. I've gathered that, you know, he came from a corporate background. I think he had a different perspective on customer service than what is typical of state government. So he brought something new along with all of his prior experience. And I think he was the first who really made it a priority, because I think he understood that the expectation of the customer is different nowadays, and it's different today than it was yesterday and last year, and it's always growing and changing. And people of my generation, and the generation following me, they're always expecting something to be simpler, faster, and more based on their needs, right? And we, state agencies, have been so slow to react, we still use a log of legacy systems, before we launched with ServiceNow, all of our inquiry management was through Excel spreadsheets and Outlook emails. Those are great tools, but their not designed for CSM. And so, we had done a really deep dive within DHS and within state government, to look at okay, where does customer service need to be focused on? Is it the people? It's not the people, we found out very quickly we have passionate people in the state of Tennessee. It's not the processes, because people are doing what they can, but we needed a tool. So, with Governor Haslam's initiative, and our understanding that we had to find a tool to better deliver service, we came on to ServiceNow, just a year ago. So, I've been smiling ever since. I feel it in my face. >> You're a good advertisement. So, what are some of the improvements that you have seen? >> Even when we were doing just our pilot phase, we launched on October 2nd, and I was talking with a lot of people from ServiceNow then, and from the governor's office, and they said, "Try "to get a snapshot of the before, "and be sure to compare it with the snapshot of afterwards." So I figured two months would be actually sufficient, and we were still in our kind of test and pilot stages, but we knew pretty quickly we wanted to continue on with ServiceNow. So, the two months prior, we were averaging inquiry assignment time, so if you filled out an application or you submitted an inquiry to my unit, the Office of Customer Service, the amount of time it would take to get from the time you submitted it, to a person in the field, or in program, who could actually help with it, that was taking about 36 hours average. Some were faster, some were slower, some reached up to three days, and that's not even a resolution. Sometimes that's just for us to even acknowledge that we got it, that someone's working on it. Afterwards, I looked at those two months following, so October and November, and we were at like eight or nine minute average. And it's because, we knew we wanted something enterprise wide, but we didn't quite anticipate the difference that workflow management would provide us. So all the parts that normally were all these handoffs, and I looked at it last Friday, it was 100 seconds. You know, we've entered new measurement criteria, every time I go back and look at it. >> So it's lightening speed, lightening fast changes. >> Yes, and our resolution time on this has come right on board along side that. We've cut it down to about 30% of what it used to be. We're able to just do our jobs faster, so we can get back to what people coming to DHS to do is, they come here to serve, they come here to try to help people, and this has taken away all that administrative responsibility, so we can do what we're actually good at. >> Well, we're going to look forward to hearing what it is, next year at Knowledge19. Thanks so much for joining us, Landon it was great having you on theCUBE >> I appreciate it >> I'm Rebecca Knight. We'll have more from ServiceNow Knowledge18, and theCUBE's live coverage just after this. (electronic music)

>> Announcer: Live from Las Vegas, it's the Cube. Covering ServiceNow Knowledge 2018. Brought to you by ServiceNow. >> Welcome to day three of Knowledge18. You're watching the Cube, the leader in live tech coverage. Day three is when ServiceNow brings together its audience and talks about its platform, the creators, the developers, the doers get together in the room. Jeff Frick and I, my co-host, we've seen this show now, Jeff, for many, many years. I joked on Twitter today, it's not often you see a full room and this room was packed on day three. Unless Larry Ellison is speaking. Well, Larry Ellison is not here, but Pat Casey is. He's the Senior Vice President of DevOps at ServiceNow and a Cube alum, Pat, great to see you again. >> Absolutely, just glad to be back. >> So, my head is exploding. With all the innovation that's comin' out. I feel like I'm at a AWS re:Invent with Andy Jassy up on stage with all these features that are coming out. But wow, you guys are on it. And part of that is because of the platform. You're able to put out new features, but how's the week going? >> So far it's been great. But you're sort of right, we are super proud of this year. I think there's more new stuff that's valuable for our customers coming out this year than probably the three years prior to this. I mean you got the chat bot designer, and you got some great application innovation, you got Flow Designer, you've got the entire integration suite coming online, and then in addition to that you've got a whole new mobile experience coming out. Just all stuff that our customers can touch. You can go downstairs and see all that and they can get their hands on it. Super exciting. >> So consistent too with the messaging. We've been coming here, I this is our sixth year, with kind of the low-code and no-code vision that Fred had way at the beginning. To let lots of people build great workflows and then to start taking some of these crazy new applications like chat bots and integration platform, pretty innovative. >> Yeah, I think it's a mindset when you get down to it. I mean we, the weird failure mode of technology is technology tends to get built by by technologists. And I do this for a living. There's a failure mode where you design the tool you want to use. And those tend to be programmer tools 'cause they tend to get designed by programmers. It does take an extra mental shift to say no, my user is not me. My user is a different person. I want to build the tool that they want to use. And that sort of user empathy, you know Fred had that in spades. That was his huge, huge, huge strength. Among other things. One of his huge strengths. It's something that we're really trying to keep foreground in the company. And you see that in some of the new products we released as well. It's really aimed at our customers not at our developers. >> The other thing I think that's been consistent in all the interviews we've done, and John talked on the day one keynote one of his kind of three keys to success was try to stay with out of the box as much as you can as a rule, and we've had all the GMs of the various application stacks that you guys have, they've all talked consistently we really try to drive, even as a group our specific requests back into development on the platform level so we can all leverage it. So even though then the vertical applications you guys are building, it's still this drive towards leverage the common platform. >> Yeah, absolutely. And there is, what's the word I'm looking for? There's a lot of value in using the product the way it was shipped. For easiest thing is when it advances or when we ship you new features you can just turn 'em on, and it doesn't conflict with anything else you got going in there. There's always an element of, you know, this is enterprise software. Every customer's a little bit different. GE does not work the same way as Bank of America. So you probably never get away entirely from configuring, but doing the minimum that you can get away with, the minimum that'll let you put your business-specific needs in there, and being really sure of it, you need to do it, it's the right approach to take. The failure mode of technologists, the other one, is we like writing technology. So give me a platform and I'm going to just write stuff. Applying that only when it makes sense to the business is where you really need to be. Especially in this day and age. >> Well I wanted to ask you about that 'cause you guys talk about many applications one platform. But you used to be one platform one app. >> Pat: Yep. >> So as you have more, and more, and more apps, how are you finding it regarding prioritization of features, and capabilities? I imagine the GMs like any company are saying, hey, this is a priority. >> Sure. >> And because you have a platform there's I'm sure a lot more overlap than if you're a stovepipe development organization. But nonetheless you still got to prioritize. Maybe talk about that a little bit. >> Sure, you end up with two different levels of it though. At one level, you tend to want to pick businesses to go into, which you're aligned with the technology stack you have. I don't think we're going to go into video streaming business. It's a good business, but it's not our business. >> Too bad, we could use some of that actually. >> Well, maybe next year. (laughs) But when you get down to it we mostly write enterprise business apps. So HR is an enterprise business app, CSM, SecOps, ITSM, they're all kind of the same general application area. So we don't tend to have something which is totally out to lunch. But you're right in the sense that A, what's important to CSM might be less important to ITSM. And so we do prioritize. And we prioritize partly based on what the perceived benefit across the product line is. If something that a particular BU wants that five other BUs are going to benefit from that's pretty valuable. If only them, not so much. And part of it too is based on how big the BUs are. You know if you're an emerging product line you probably get few less features than like Feryl Huff. Like she has a very big product line. Or Pabla, he has a very big product line. But there's also an over-investment in the emerging stuff. Because you have to invest to build the product lines out. >> The other thing I think is you guys have been such a great opportunity is I just go back to those early Fred interviews with the copy room and the color paper 'cause nobody knows what that is anymore. >> Pat: Yep. >> But workflow just by its very nature lends itself so much to leveraging, AI, and ML, so you've already kind of approached it while trying to make work easier with these great workflow tools, but what an opportunity now to apply AI and machine learning to those things over time. So I don't even have to write the rules and even a big chunk of that workflow that I built will eventually go away for me actually having to interact with it. >> Yeah, there's a second layer to it too, which I'll call out. The workflows between businesses are different. But we have the advantage that we have the data for each of the businesses. So we can train AI on this is the way this particular workflow works at General Electric and use that bot at GE and train a different bot at maybe at Siemens. You know it's still a big industrial firm. It's a different way of doing it. That gives us a really big advantage over people who commingle the data together. Because of our architecture, we can treat every customer uniquely and we can train the automation for the unique workflows for that particular customer. It gives a much more accurate result. >> So thinking about, staying on the theme of machine intelligence for a moment, you're not a household name in the world of AI, so you've done some acquisitions and-- >> Pat: Yep. >> But it's really becoming a fundamental part of your next wave of innovation. As a technologist, and you look out at the landscape, you obviously you see Google, Apple, Facebook, IBM, with Watson, et cetera, et cetera, as sort of the perceived leaders, do you guys aspire to be at that level? Do you need to be? What's the philosophy and strategy with regard to implementing AI in the road map? >> Well if you cast your eyes forward to where we think the future's going to be, I do think there are going to be certain core AI services that they're going to call their volume plays. You need a lot of engineers, a lot of resources, a lot of time to execute them. Really good voice-to-text is an example. And that's getting pretty good. It's almost solved at this point. A general case conversational agent, not solved yet. Even the stuff you see at Google I/O, it's very specialized. It does one thing really well and it's a great demo, but ask it about Russian history, no idea what to talk about. Whereas, maybe you don't know a lot about Russian history, you as a human would at least have something interesting to say. We expect that we will be leveraging other people's core AI services for a lot of stuff out there. Voice-to-text is a good example. There may well be some language parsing that we can do out there. There may be other things we never even thought of. Maybe stuff that'll read text for you and give you back summaries. Those are the kinds of things that we probably won't implement internally. Where you never know, but that's my guess, where you look at where we think we need to write our own code or own our own IP, it's where the domain is specific to our customers. So when I talked about General Electric having a specific workflow, I need to be able to train something specific for that. And if you look at some other things like language processing, there's a grammar problem. Which is a fancy way of saying that the words that you use describing a Cube show are different than the words that I would use describing a trade show. So if I teach a bot to talk about the Cube, it can't talk about trade shows. If you're Amazon, you train your bot to talk in generic language. When you want to actually speak in domain-specific language, it gets a lot harder. It's not good at talking about your show. We think we're going to have value to provide domain-specific language for our customers' individualized domains. I think that's a big investment. >> But you don't have to do it all as well. We saw two actually interesting use cases talking to some of your customers this week. One was the hospital in Australia, I don't know if you're familiar with this, where they're using Alexa as the interface, and everything goes into the ServiceNow platform for the nurses. >> Yep. >> And so that's not really your AI, it's kind of Amazon's AI, that's fine. And the other was Siemens taking some of your data and then doing some stuff in Azure and Watson, although the Watson piece was, my take away was it was kind of a fail, so there's some work to be done there, but customers are going to use different technologies. >> Pat: Oh, they will. >> You have to pick your spots. >> You know we're, as a vendor, we're pretty customer-centric. We love it when you use our technology and we think it's awesome, otherwise we wouldn't sell it. But fundamentally we don't expect to be the only person in the universe. And we're also not, like you've seen us with our chat bot, our chat bot, you can use somebody else's chat client. You can use Slack, you can use Teams, you can use our client, we can use Jabber. It's great. If you were a customer and want to use it, use it. Same thing on the AI front. Even if you look at our chat bot right now, there's the ability to plug in third-party AIs for certain things even today. You can plug it in for language processing. I think out of box is configured for Google, but you can use Amazon, you can use Microsoft if you want to. And it'll parse your language for you at certain steps in there. We're pretty open to partnering on that stuff. >> But you're also adding value on top of those platforms, and that's the key point, right? >> The operating model we have is we want it to be transparent to our customers as to what's going on in the back end. We will make their life easy. And if we're going to make their life easy by behind the scenes, integrating somebody else's technology in there, that's what we're going to do. And for things like language processing, our customers never need to know about that. We know. And the customers might care if they asked because we're not hiding it. But we're not going to make them do that integration. We're going to do it for them, and just they click to turn it on. >> Pat, I want to shift gears a little bit in terms of the human factors point of all this. I laugh, I have an Alexa at home, I have a Google at home, and they send me emails suggesting ways that I should interact with these things that I've never thought of. So as you see kind of an increase in chat bots and you see it increase in things like voice-to-text and these kind of automated systems in the background, how are you finding people's adoption of it? Do they get it? Do the younger folks just get it automatically? Are you able to bury it such where it's just served up without much thought in their proc, 'cause it's really the behavior thing I think's probably a bigger challenge than the technology. >> It is and frankly it's varied by domain. If you look at something like Voice that's getting pretty ubiquitous in the home, it's not that common in a business world. And partly there frankly is just you've got a background noise problem. Engineering-wise, crowded office, someone's going to say Alexa and like nobody even knows what they're talking about. >> Jeff: And then 50 of 'em all-- >> Exactly. There's ways to solve that, but this is actual challenge. >> Right. >> If you look at how people like to interact with technologies, I would argue we've already gone through a paradigm shift that's generational. My generation by default is I get out a laptop. If you're a millennial your default is you get out your phone. You will go to a laptop and the same says I will go to a phone, but that's your default. You see the same thing with how you want to interact. Chat is a very natural thing on the phone. It's something you might do on a full screen, but it's a less common. So you're definitely seeing people shifting over to chat as their preferred interaction paradigm especially as they move onto the phones. Nobody wants to fill out a form on a phone. It's miserable. >> Jeff: Right. >> I wonder if we could, so when Jeff and I have Fred on, we always ask him to break out his telescope. So as the resident technologist, we're going to ask you. And I'm going to ask a bunch of open-ended questions and you can pick whatever ones you want to answer, so the questions are, how far can we take machine intelligence and how far should we take machine intelligence? What are the things that machines can do that humans really can't and vice versa? How will humans and machines come together in the future? >> That's a broad question. I'll say right now that AI is probably a little over-marketed. In that you can build really awesome demos that make it seem like it's thinking. But we're a lot further away from an actual thinking machine, which is aware of itself than I think it would seem from the demos. My kids think Alexa's alive, but my son's nine, right? There's no actual Alexa at the end of it. I doubt that one's going to get solved in my lifetime. I think what we're going to get is a lot better at faking it. So there's the classical the Turing test. The Turing test doesn't require that you be self-aware. The Turing test says that my AI passes the Turing test if you can't tell the difference. And you can do that by faking it really well. So I do think there's going to be a big push there. First level you're seeing it is really in the voice-to-text and the voice assistance. And you're seeing it move from the Alexas into the call centers into the customer service into a lot of those rote interactions. When it's positive it's usually replacing one of those horrible telephone mazes that everybody hates. It gets replaced by a voice assist, and as a customer you're like that is better. My life is better. When it's negative, it might replace a human with a not-so-good chat. The good news on that front is our society seems to have a pretty good immune system on that. When companies have tried to roll out less good experiences that are based on less good AI, we tend to rebel, and go no, no, we don't want that. And so I haven't seen that been all that successful. You could imagine a model where people were like, I'm going to roll out something that's worse but cheaper. And I haven't seen that happening. Usually when the AI rolls out it's doing it to be better at something for the consumer perspective. >> That's great. I mean we were talking earlier, it's very hard to predict. >> Pat: Of course. >> I mean who would have predicted that Alexa would have emerged as a leader in NLP or that, and we said this yesterday, that the images of cats on the internet would lead to facial recognition. >> I think Alexa is one example though. The thing I think's even more amazing is the Comcast Voice Remote. Because I used to be in that business. I'm like, how could you ever have a voice remote while you're watching a TV and watching a movie with the sound interaction? And the fact that now they've got the integration as a real nice consumer experience with YouTube and Netflix, if I want to watch a show, and I don't know where it is, HBO, Netflix, Comcast, YouTube, I just tell that Comcast remote find me Chris Rock the Tamborine man was his latest one, and boom there it comes. >> There's a school of thought out there, which is actually pretty widespread that feels like the voice technologies have actually been a bit of a fail from a pure technologies standpoint. In that for all the energy that we've spent on them, they're sort of stuck as a niche application. There's like Alexa, my kids talk to Alexa at home, you can talk to Siri, but when these technologies were coming online, I think we thought that they would replace hard keyboard interactions to a greater degree than they have. I think there's actually a bit of a learning in there that people are not as, we don't mandatorily, I'm not sure if that's a real word, but we don't need to go oral. There's actually a need for non-oral interfaces. And I do think that's a big learning for a lot of the technology is that there's a variety of interface paradigms that actual humans want to use, and forcing people into any one of them is just not the right approach. You have to, right now I want to talk, tomorrow I want to text, I might want to make hand gestures another time. You're mostly a visual media, obviously there's talking too, but it's not radio, right? >> You're absolutely right. That's a great point because when you're on a plane, you don't want to be interacting in a voice. And other times that there's background noise that will screw up the voice reactions, but clearly there's been a lot of work in Silicon Valley and other places on a different interface and it needs to be there. I don't know if neural will happen in our lifetime. I wanted to give you some props on the DevOps announcement that you sort of pre-announced. >> We did. >> It's, you know CJ looked like he was a little upset there. Was that supposed to be his announcement? >> In my version of the script, I announced it and he commented on my announcement. >> It's your baby, come on. So I love the way you kind of laid out the DevOps and kind of DevOps 101 for the audience. Bringing together the plan, dev, test, deploy, and operate. And explaining the DevOps problem. You really didn't go into the dev versus the ops, throwing it over the wall, but people I think generally understand that. But you announced solving a different problem. 500 DevOps tools out there and it gets confusing. We've talked to a bunch of customers about that. They're super excited to get that capability. >> Well, we're super, it's one of those cases where you have an epiphany, 'cause we solved it internally. >> Dave: Right. >> And we just ran it for like three years, and we kept hearing customers say, hey, what are you guys going to do about DevOps? And we're never like quite sure what they mean, 'cause you're like, well what do you mean? Do you want like a planning tool? And then probably about a year ago we sort of had this epiphany of, oh, our customers have exactly the same problem we do. Duh. And so from that it kind of led us to go down the product road of how can we build this kind of management layer? But if you look across our customer base and the industry, DevOps is almost a rebellion. It's a rebellion against the waterfall development model which has dominated things. It's a rebellion against that centralized control. And in a sense it's good because there's a lot of silliness that comes out of those formal development methodologies. Slow everybody down, stupid bureaucracy in there. But when you apply it in an enterprise, okay some of the stuff in there, you actually did need that. And you kind of throw the baby out with the bathwater. So adding that kind of enterprise DevOps layer back in, you still do get that speed. Your developers get to iterate, you get the automated tests, you get the operating model, but you still don't lose those kind of key things you need at the top enterprise levels. >> And most of the customers we've talked to this week have straight up said, look, we do waterfall for certain things, and we're not going to stop doing waterfall, but some of the new cool stuff, you know. (laughs) >> Well if you look at us, it's at the, if you take the microscope far enough away from ServiceNow, we're waterfall in that every six months we release. >> Dave: Yeah, right. >> But if you're an engineer, we're iterating in 24-hour cycles for you. 24-hour cycles, two-week sprints. It's a very different model when you're in the trenches than from the customer perspective. >> And then I think that's the more important part of the DevOps story. Again, there's the technology and the execution detail which you outlined, but it's really more the attitudinal way that you approach problems. We don't try to solve the big problems. We try to keep moving down the road, moving down the road. We have a vision of where we want to get, but let's just keep moving down the road, moving down the road. So it's a very, like you said, cumbersome MRD and PRD and all those kind of classic things that were just too slow for 2018. >> Nobody goes into technology to do paperwork. You go into technology to build things to create, it's a creative outlet. So the more time you can spend doing that, and the less time you're spending on overhead, the happier you're going to be. And if you fundamentally like doing administration, you should move into management. That's great. That's the right job for you. But if you're a hands on the keyboard engineer, you probably want to have your hands on the keyboard, engineering. That's what you do. >> Let's leave on a last thought around the platform. I mentioned Andy Jassy before and AWS. He talks about the flywheel effect. Clearly we're seeing the power of the platform and it feels like there's the developer analog to operating leverage. And that flywheel effect going from your perspective. What can we expect going forward? >> Well, I mean for us there's two parallel big investment vectors. One is clearly we want to make the platform better for our apps. And you asked earlier about how do we prioritize from our various BUs, and that is driving platform enhancements. But the second layer is, this is the platform our customers are using to automate their entire workflow across their whole organization. So there's a series of stuff we're doing there to make that easier for them. In a lot of cases, less about new capabilities. You look at a lot of our investments, it's more about taking something that previously was hard, but possible, and making it easier and still possible. And in doing that, that's been my experience, is Fred Luddy's experience, the easier you can make something, the more successful people will be with it. And Fred had an insight that you could almost over-simplify it sometimes. You could take something which had 10 features and was hard to use, and replace with something that had seven features and was easy to use, everyone would be super happy. At some level, that's the iPhone story, right? I could do more on my Blackberry, it just took me an hour of reading the documentation to figure out how. >> Both: Right, right. >> But I still miss the little side wheel. (laughs) >> Love that side wheel. All right, Pat, listen thanks very much for coming. We are humbled by your humility. You are like a rock star in this community, and congratulations on all this success and really thanks for coming back on the Cube. >> Thank you very much. It's been a pleasure meeting you guys again. >> All right, great. Okay, keep it right there, everybody. We'll be back with our next guest. You're watching the Cube live from ServiceNow Knowledge K18, #know18. We'll be right back. (upbeat music)

(techy music) >> Announcer: Live from Las Vegas, it's theCUBE, covering ServiceNow Knowledge 2018. Brought to you by ServiceNow. >> Welcome back, everyone, to theCUBE's live coverage of ServiceNow Knowledge 18 here in Las Vegas, Nevada. I'm your host, Rebecca Knight, along with my cohost, Dave Vellante. We're joined by CJ Desai. He is the Chief Product Officer for ServiceNow. Thanks so much for coming on theCUBE again, CJ. >> Thank you, it's great to be here. First time I came was last Knowledge, which was my first Knowledge, so I'm a lot more educated and equipped this time as compared to firing round of questions from Dave last time. >> We will pick your brain, exactly. So you were up on the stage this morning, a great keynote, and you said, "Welcome to the era of great experiences." Unpack that a little bit. What do you mean by that? >> First of all, thank you for remembering that. That was supposed to be the idea. But on a serious note, we feel, if you think about even our company name is ServiceNow, so you provide service, and when you provide service, that's not a technology you provide, you provide an experience, whether it's IT service, customer service, employee, whatever the case might be. And, if you are not delivering experiences, then you are not that relevant. So we are trying to truly, and we are in the beginning of this journey, truly internalize that, that if people are using us, they call themselves service desk, insider organization, IT service desk, customer service desk, whatever the terms you want to use, there is about experiences. Rather than focusing on bits and bytes, we want to focus on experiences, deliver those experiences via our platform. It's not software as a service, it's software as an experience. It's software as an experience, that's the idea, correct. Thank you for-- >> You also talked about the eras. You know, we went back to the industrial era and then went through the ages of computing. Yeah, I was not sure if that was going to work or not, but the point I was trying to make, Dave, was just around the quality of work and how work has evolved. That's it, that was the idea. >> But I think my takeaway was even more than that, because we are entering, in my view, anyway, a new era, and I'd love to get your comments. We're moving from what is real tailwind for you, which is the Cloud era, and obviously, Cloud is an important part of the new era where you have a remote set of services to one where you have this ubiquitous set of digital services that do things like sense, hear, read, act, respond. That's a different world, and it's all about the experience, and I don't know how to define that yet. Digital, I guess, is how we define it. But what are your thoughts? >> The one thing, even simple things, and these are not simple things to understand. When I look at things like even genomic sequencing, that's so different. They are using technology to figure out how to sequence the human genome so that it can help you with your health, live longer, even things like knowing that somebody rings a doorbell at my home and I can see on my phone. Everything is connected, humans are connected, when mobile came and computer came and internet came. But things being connected is pretty exciting for me. That just transforms our lives and how we work, and I really like that it is all about us, and other than us being focusing on the technology itself. So that's the point. It's that we're humans, and let's focus on humans and experience, rather than worry about, oh, this runs two times faster than the other thing, or this thing is smaller than other thing. That's interesting, but not that interesting. >> At this conference, this is really the message that you're getting across. It's the new tag line, we are making the world of work work better for people. How does the Now platform really deliver on that promise? How does it make the employees life easier? I would say we have a bunch of use cases, but as you know, we started out early on with IT service management, and the whole idea was can we provide, as long as computers are there, as long as software is there, password reset is going to be there for a very, very long time. So, my point is that that's when it started. Okay, I need to do password reset, I want to upgrade my laptop. Every year there is a new laptop, every year there is a new phone, and that cycle will continue, and as long as we are using technology for our knowledge workers, IT help desk will be there, right? And where we are evolving is enterprise service management, because you don't, as an employee, you may deal with IT, you may deal with HR, you may have a contractual issue with legal, you may need something related to your payroll from finance. People think payroll is HR, but payroll is finance. And as you try to go across in a day in a life of an employee, you need to make it as easy as possible. So that's what we are focused on, deliver better experiences. You know, artificial intelligence that listen today, I believe, is more about optimization, rather than intelligence. Yeah, we want to use your data to be able to predict, like if you see in Gmail, I don't know if you use Gmail, but if you have Gmail, you get an email, it'll suggest auto-responses. Those auto-responses are almost positive. Have you noticed that? They are never negative. >> Yeah. >> Oh, of course. >> They're like, no, I don't want to come to your meeting. (laughing) It's kind of like trying to predict most likely what you would want to say, and I think if we can use intelligence to make people more productive, that's what we want. >> I mean, I use that function. I actually like it. >> CJ: Yeah, exactly. >> You know, it gives you three choices, and one of 'em is pretty close to what I would normally, and if I'm busy, I'm done. >> Yeah, right, exactly. >> I like that. This is the other thing we've talked about. We've talked about this with Farrel this morning. Try to anticipate my needs, right? So that means you've got to infuse AI into the application and identify specific use cases. You guys have done some M&A there, you talked to the financial analysts meeting, obviously, not disclosing anything, but watch for us to do some more M&A. You got to believe that that machine intelligence space is really ripe for innovation. >> And what we believe is if I look at the big Cloud providers, like Google, are investing a lot in deep learning and many, many other technologies, so whenever they expose it, and some of them do a really good job, we will just leverage their libraries. But there are things specific to enterprise, because there are things specific to enterprise, like if you use the word network at a hardware company, that's always in context of compute network and storage. If you use the word network at a healthcare company, that's a network of physicians, networks of hospitals, networks of whatever. And if you use the word network at a Telco company, that is a whole different network. My point is we want to understand those pieces, and if we can make it easier based on your data, so if all your cases, which are, Oh, part of your network is down. Ah, that's what you mean from the context end point, so we want to use wherever folks like Google are investing, we will leverage that, but if we need to leverage, we'll do that too. >> It's interesting, we were talking to a customer today, it might have been Worldpay, and they took the CMDV language and transformed it into the language of the business. What a rare and powerful concept for somebody from IT to do that, because if the lingua franca is business, then the adoption's going to go through the roof. >> So does that make sense? >> Yeah, it makes a lot of sense. Well, I appreciate you talking about the value and the customer experience versus the technology. Certainly, it speeds and feeds you right. Boring. But the platform is important. Many products, one platform, that's unique for an enterprise software company, and you guys aspire to be the next great enterprise software company. Talk about how the platform enables you to get there. >> So I will tell you simple. You know our founder, Fred Luddy, started with the platform in 2004, so that was 14 years ago now, and his idea was you should be able to route work through the enterprise using our platform, and then we started with the IT service management and use case. The biggest advantage we have is that we are a very customer-driven organization. Many companies say that, but you see it here. Dave, you have been coming to Knowledge for a long time, I don't know about you. >> This is my first rodeo, but it's cool. >> It's the first thing you see. >> These are 80-plus person sessions, are customer sessions. They're not our sessions, where they are sharing best practices with them. So we get all these requests, CJ, we have built emergency response system using ServiceNow, CJ, we have built financial close using ServiceNow. Can you productize it? And we say, okay, thank you for the idea, which is great, thank you for the idea. How do I prioritize all of that? And, Dave, where platform comes in, because all the services I talked about today, service intelligence, service experience, user experience, they're all built in the platform, and I'm trying to be cautious, but if I want to create a brand new product on our platform, a brand new product on our platform, 40-use case, a 1.0 product where I feel comfortable the customers can use it, I would say 12 to 18 engineers. That's it. >> Rebecca: Wow. >> If I want to create one product, it's 12 to 18 engineers. So the R&D leverage, and that's the point I was trying to get across, that whether it's my own team creating product or whether our customer building apps on our product, because on platform, because we provide all the common services integration, the incremental cost to create something, now sales marketing, with my close friend, Dave Schneider, is much harder, because he has to scale it, build specialty in it and all that, but to create the product is not an issue for us on the platform. >> But this is where Cloud economics are so important, because at volume, your marginal costs go to practically zero. >> CJ: That's exactly right. >> But people may say, oh, 12 to 18, that sounds like a lot, but we're talking about an enterprise class software product here, and Fred Luddy, in the 2004 time frame, I mean, the state of enterprise software then, frankly, and now, was terrible. The guys at 37signals, I don't know if you know Jason, they made valid attempts, but it wasn't enterprise class software, it wasn't a platform. I've said, a number of times this week, the reference model for enterprise software is painfully mediocre, so you guys have done a great job, and now you've really got to take the next step and stay ahead on innovation. >> Correct on innovation card, that's what I said, innovation should be my top priority. You heard me at the Financial Analysts Day. Customer Service Management, brand new product, we actually launched it at Knowledge 16. Okay, that's when we launched it. It was engineers and teens who created that product, so many teens, the 1.0, now we have evolved quite a bit, 500 customers two weeks ago, 500 enterprise customers. You guys know that we don't go to the small line of the business. 500 in two years, eight quarters. >> And I found out last night, I think it was 75, or it might even be higher, reference customers. >> CJ: Yeah, already, using CSM. >> That's the difference. I do, we do, a lot of these shows. >> That's the platform impact. >> And you're talking about the customer focus. You do a lot of these shows. The customers talk about the impact on their business. They don't talk about how they installed some box, or like you say, runs faster. It's the business impact that really makes a difference, and that's why we're excited to be here. >> You saw today when I talked about Flow Designer and Integration Hub. IT wants to provide software so that business analysts can model business processes in a Cloud way with whoever you need to integrate with, so we are really keeping that as the north star for our customers, and how can we make their life easier, whatever they want to automate, some manual processes, all of manual processes. I remember speaking to Fred when I joined initially, and I said, "Fred, how did you think about TAM?" He said, "What do you mean, TAM?" You know, he's a funny guy, and he was serious. His point was there are so many manual workflows, how do you put a TAM around it? Every business is unique, their processes are complex, so don't box yourself and say, Oh, this is a $4 billion TAM and I'm going to get 20% of it. Every enterprise, as long as they exist, they will have manual workflows, you go and give it our platform so they can automate however they want. >> Well, I'm going to make you laugh about TAM. I'm a former industry analyst, so when you guys did the IPO way back when, well before your time-- >> CJ: 2012. >> when Frank was here, there was a research company saying this is small market, maybe it's a billion dollars and it's shrinking, so I, with some of my colleagues, developed a TAM analysis, and it was more than 30 billion. I published 30 billion, you can go on our old Wiki and see that, and the guy said to me, "Dave, you can't publish more than 30 billion. You'll look like a fool." The TAM is much, much bigger than 30 billion. You can't even quantify it, it's so large when you start looking at it. >> And now, because people are recognizing that we automate all the manual workflows in a enterprise on a Cloud platform, last week somebody published a report and I just saw the headlines, I didn't go through the details, 126 billion. So from in 2012 to that small number, and we don't know what the number is. >> Could it be bigger? >> I would have no idea. I would be completely disingenuous if I told you I know what my TAM is, but I don't think that way. I say what customer problems can I solve? >> Well, that's what I wanted to ask you. So you're here with so many different customers. Just on the show, we've had ones in payments, in insurance, in health care. What are you hearing from customers, and what are sort of your favorite applications of what you're doing? What makes you the proudest? >> Yeah, so I would say the proudest moments for me are when I'm like, wow, you do that with ServiceNow? I would have never thought that. So when I didn't expect, when I expect something, Oh, I had this routine email, text collaboration, and I switched it to ServiceNow, get it, like not a big aha moment. I had this one customer who said he has a big distribution network, all these partners, and those guys have ServiceNow, he has ServiceNow, and when they have problem with the product, their product, my customer's product, they all communicate via ServiceNow to each other. So they have created a whole ServiceNow network, truly a B2B kind of exchange, kind of, using ServiceNow. One of our median and entertainment customers who owns a bunch of parks, they refill the popcorn machine using ServiceNow. When the popcorn levels dip, they have those people who carry around the cart, Oh! The popcorn level dip, it marks the sensor, it routines the workflow, goes to the corporate, Ah, we need to fill up popcorn on by this particular ride. For me-- >> And even at my house, I love it. >> Yeah, so that's exciting to me. >> We talked to Siemens today. >> Yes, great customer. >> Awesome, and I want to run a line by you. We talk about AI a lot, machine intelligence. I wrote down during, you know, data is the fuel for AI. Well, you know we love data here at theCUBE, and he was describing that, he said, you know, even though CJ was not prescribing taking the data out, we could leave it in so it learns, right now, we take some of the data out. Well, you described that. Well, we put it to SAP HANA, we throw a little Watson in there, we do some Azure, machine learning, we use Tableau for visualization, he's probably got some Hadoop and Kafka in there, a very complicated, big data pipeline. And I said to him, Okay, in two years, do you want to do that inside of ServiceNow? He goes, "Absolutely. That would be my dream come true." So, I guess I'm laying down the gauntlet. Do you see that as a reality? >> So, we are talk to Siemens, great customer, they keep us honest, so I love that and I did actually meet the team who was in charge of their BI and reporting and they did share the same story a few months ago when I met them. And we are trying to figure out, Dave, if I knew the answer, I would have told you, but you know my style. I don't know the answer. We are seriously trying to figure out, Do we become an analytics hub? We are really good with ServiceNow data, we can build connectors with other data, but do I want to be in the BI and reporting market? Absolutely not. Do I want to help customers as their processes span across and provide them more visual credit tools than others, text-based searches, whatever they need, the answer is yes. Performance analytics, as you know, we have been moving along really at a good pace, and now we have what every single product, but this is something that Eric Miller, who runs that business, we talk about it all the time, because currently our analytics is building the platform, and now you know that data has a Cloud issue, so if you have data here, you have data there, you have data there, we are in our own Cloud. Can we build a connector, potentially, to OnPrem? Don't know the answer, but this is something, it's a fair gauntlet having to solve. >> Humbly, I'd like to give you my input, if I may. >> Yes. >> We see innovation, as I said before, it's data, applying machine learning to that data, and then leveraging Cloud economics. The project with big data projects, as you well know, is the complexity has killed them. Now you see the Cloud guys, whether it's Amazon or Microsoft, and that's where the data pipelines are being simplified and built. Now, I don't know if it's the right business decision for you guys, but wow, wouldn't that be powerful if you guys could do that, certainly, for your customers. >> And, truly, that is, as you heard me on Financial Analysts Day, I'm a huge fan of Geoffrey Moore's work, and he defines system of record, ERP CRM, system of action where we fall in, and then he has System of Intelligence, which is all the things around data and how do you harness the power of data. And that's something that I really, in our product teams, we talk about all the time, if I can solve Siemens problem with everything in ServiceNow, that'd be awesome, but is that something I want to prioritize right now, or is there something, we should give them the flexibility. I don't know. >> Well, you're one of the top product guys in our industry. It's why they found you. No, seriously, I put you up there with the greats. >> You're kind, thank you. >> It's true. You've got an incredible future ahead of you. But as a lead product person, you have to make those decisions, and you have to be very circumspect about where you put your resources. You can't just run to every customer requirement, right? >> And I tell, coincidentally, my wife asks me What's your job, by the way? I said, that's a good question. >> I'm married to a product officer, too, I feel the same way. What do you do all day? You do a lot of meetings. >> Yeah, exactly. So I said that I do a lot of meetings, and she said why do you do a lot of meetings? And I said I'm making a some decision or help my team make a decision because they already analyze a bunch of things. And I said, my hope is, as long as I can make more good decisions than bad decisions, specifically about product strategy, because you never know unless you make the chess pieces move and think of two or three steps ahead, and some things could be right and some things could be wrong. I have a simple framework on my whiteboard for every meeting. No jokes, right? So, my framework is very simple. Question number one, What customer problems we are trying to solve. If you cannot articulate that, for any new product idea you have, I don't go past that question, What customer problem we are trying to solve? Second is Why now? Why do we need to solve this problem now? Like you said, there are many problems, which one are you prioritize? And then, third, Why us? Why should we solve that problem? So, if you can articulate the problem, which always is a challenge because you kind of know what problems you have, but unless you really, really understand the customer pain point, you cannot articulate it. Then you say, why now? Like why is the time right now for us to invest in this, say, analytics, as a service? Why right now? And, third, why you, as in why us? Why is ServiceNow should solve it? That, at least, gives me a guiding compass to say because I have many products, as you know, I am very protective of our platform, and all these use cases come in, every product line wants to go deeper, rightfully so, because they are trying to solve for customers, and the new products want to be built on this platform. Sometimes I say maybe a partner should build it, so we made a decision, facilities product, Should our ISB partner build it? And that's the right place because we feel they are more suited, they have the skill set, all of that. But that's it, what problem, why now, why you? >> Rebecca: Really, I love it. >> Well, the Why you? it's a great framework. The why you is unclear for the Siemens problem, and I can understand that. You take the DemOps announcement that Pat stole from you today-- >> I know, that's not cool, man. >> But that's a problem that you guys solved internally, clear problem. >> He did a nice job of articulating it, very nice job. >> Yeah, definitely. >> But we feel that there always is a process when you need a workflow across, because in planning there are a bunch of companies, as the patch, or in build there are a bunch of companies in develop there are a bunch of companies. That's fine. They could be the system of records for those chevrons and we are the workflow that cuts across. So we feel loved. We showed our value to our customers by doing that. >> Rebecca: That's great. >> I know we've got to go, but lastly, it's roadmap. Last year, you talked about how you guys do releases by alphabet, twice a year. You were really transparent today, laid out the room and talked a lot about Madrid, you laid out well into the future what you guys are doing so, as an analyst, I love that. I'm sure you're customers love it, so-- >> A lot of people to picture, so that's nice. And Twitter, a lot of people posted on social media as well, so clearly there was a customer pain point, as we call it, that they needed a roadmap. In speaking to customers last one year, number one thing, if you tell us what you're building, then we don't have to build it. If you tell us when you're shipping, then we can plan around it, and then we will set aside resources to do testing. Any Cloud software company, whether it's us, CRM software or HR software, people still test, because you cannot mess up your employee experience or customer experience, and they just said give us a predictable schedule, please, so that we know. We did say two times a year, but we were not prescriptive which quarter. It could be four months and eight months, it could be six and six, it could be seven and five. I'm currently going with the quarterly-level fidelity, and eventually, I want to get to a month-level fidelity, where I say March and September, once our internal processes are organized. >> So the other subtlety there, and I know we got to go, is the ecosystem, because you're giving visibility, they have to make bets. They're making a bet on service, but then where's the white space? They're betting on white space. If you're exposing that to them, they can say, Oh, not going to solve that problem. ServiceNow's going to solve it in two quarters. >> I agree. >> Huge difference for them. >> You guys are wonderful. Thank you so much for inviting me. >> Rebecca: Thank you for coming on the show. We appreciate it. >> No, that's awesome, thank you, thank you. >> Dave: Great to have you. >> Rebecca: Great to have you. I'm Rebecca Knight, for Dave Vellante. We'll have more from ServiceNow Knowledge 18 just after this. (techy music)

>> Announcer: Live from Las Vegas, it's theCUBE, covering ServiceNow Knowledge 2018. Brought to you by ServiceNow. >> Welcome back everyone to theCUBE's live coverage of ServiceNow Knowledge18. We are wrapping up day one of coverage. I'm Rebecca Knight, your host, along with my co-host, Dave Vellante. We're joined by Bipin Paracha. He is the co-founder and principal consultant of IntegRhythm. Thanks so much for coming on the show, Bipin. >> Thank you for having us. >> So let's just lay the scene for our viewers. Tell our viewers a little bit about what IntegRhythm does. >> So IntegRhythm started as a management advisory firm. We were teaching clients how to transform, fell in love with ServiceNow platform back in 2012, and since then, we love leaving behind working systems that drive outcomes for our clients. So we do a lot of transformative process organization, shared service transformations, things that leave behind business value for our clients. >> So a combination of tip of the spear consulting, and also implementation, is that correct or? >> So we change the tip of the spear, we kind of have tip of the spear in the implementation phase. So it is kind of baked into our methodology on how we drive outcomes for our clients. >> Dave: Oh, okay. >> So we don't charge our clients extra for consulting because we believe we get paid when we drive outcomes. >> Outcome-based incentives. >> Bipin: Yep, exactly. >> So your growth has been phenomenal, really, in recent years. So what's the magic? What are you doing? How has it been achievable? >> So one of the fundamental things that you've heard all along here, but what we also believe, is customer success. If you drive value for your customers, if you drive great value, they come back. Lot of people say that. Lot of people believe that. But we were fortunate enough to latch on to the comet's tail with ServiceNow early on. We were one of the few early partners. We saw the platform is amazing. It can do terrific things. And we've been able to drive the platform to do things for our customers, and that's helped propel our growth. As long as we stay true to that mission, we are keeping to grow. >> I want to ask you a question as a practitioner, somebody who really knows this space. ServiceNow obviously great for mid to large-size companies, trying to do anything related to a service request, customer service management, obviously ITSM, change management, problem management, et cetera, et cetera, et cetera. What's it not good at? It's not for small business. It's not CRM. It's not an HR app. So what's the profile of a company that you typically work with? >> So it is great for small businesses. We are a small business. We own ServiceNow. >> Dave: Really? We run our business on ServiceNow. >> Dave: Get out of here. >> For the right profile of a customer, it is beautiful. >> How many employees are you? >> We have 70 today. >> Dave: 70? >> 70. >> Dave: Oh, you really are a small business. >> And we are pretty small, but we still run our business on ServiceNow. It does more things than any other project management tool. It does more things than any other content management tool. We use CSM, we use PPM, we use everything. It drives value. >> Dave: Do you run your CRM at ServiceNow? >> We integrate with CRM. >> Dave: Okay. >> So we use the same CRM that ServiceNow uses, Hubspot. Our marketing, our website. >> Which is really marketing, I mean, ServiceNow is your backend CRM platform essentially. >> Yep. So our single view of our customer is ServiceNow. Anytime anybody touches us across a project, across an incident, across, we see them in ServiceNow. >> Wow, that's, I didn't realize that. I mean, is that common that a company of your size? >> It's actually not, so one of the big leg-ups we have is we are an implementation company, we are passionate, so we kind of get the free implementation. So our team goes gangbusters. >> Yeah, you're ServiceNow alpha geeks. You guys are really deep into this stuff. >> Yeah, they love what they're doing. We have to kind of slow them down sometimes. We got customers to deal with, go focus on customers. >> You are a passionate evangelist for ServiceNow. >> Oh yeah. >> What are you learning here at Knowledge? And this is not your first Knowledge, not your first rodeo. But are you talking with other customers and learning how they're using it, the platform? And then also being able to come back and take those best practices home? >> So we are a business, right, end of the day. So we get our clients here to ServiceNow, and when clients talk to the product company, product team, they learn a lot. When the product team talks with the clients, they learn a lot. But when clients talk to clients, magic happens. We've been a partner for other technologies, I won't name them, but ServiceNow is truly a customer-driven organization. I have never in my 20 plus years of experience run into a passionate customer base. Sometimes customers know how to sell ServiceNow better than ServiceNow themselves. So get a bunch of customers together, we win. >> In the early days when we started covering ServiceNow you would hear stories about making custom mods, making modifications, how that slowed people down, going into subsequent releases. I hear more often now, no custom mods, we avoid custom mods. What are you seeing? What are you preaching in the marketplace? >> So ServiceNow today is different from ServiceNow five years ago. >> Yeah, for sure. >> So we strongly believe you can go live out of the box. We actually had two presentations, a 2.5 billion dollar company, top 20 exporter in the U.S. Took them live in ServiceNow with zero customizations. Straight out of the box. Schooler, American Greetings, CSM out of the box. Our story is you're buying a Ferrari. Drive it around the block. Use what you use, and then figure out how you transform the organization. When you're buying ServiceNow, you get best practices. ServiceNow's already baked in industry best practices. If you are doing something, figure out where you're special, and pay attention to where you're special. >> When you think back to those customers five years ago that did a lot of custom modifications, how do you help them get off that technical debt? >> So we have a couple of programs that we run. So we've done back in the box for a couple of our accounts. Stand up a new ServiceNow instance, build up from scratch, migrate. Sounds easy, but we've done it a few times, so we know we can, we do. The other thing is, you can move in a phased approach. So HR has come up with a scoped app. It was two years. Move off the custom HR into scoped app. GRC, move into the scoped app. So you can migrate in phases. We've had like six major conversations today around how you roll back the stuff. So what customers built six years ago, ServiceNow delivers out of the box. >> Rebecca: Bipin, thanks so much for coming on theCUBE. It's been a pleasure having you. >> So thanks for having me here. It was fun hanging out. >> Dave: You're welcome. Good to meet you. >> The party is getting started, so, I think we've got to join them. It's our time now, exactly. >> Bipin: Alright, thank you. >> Yes, thank you, thank you. We will come back tomorrow with more from ServiceNow Knowledge18. I'm Rebecca Knight for Dave Vellante. We'll see you back here tomorrow. (upbeat music)

(exciting, upbeat music) >> (Announcer) Live from Orlando, Florida. It's theCUBE, covering ServiceNow Knowledge '17. Brought to you by ServiceNow. >> We're back. Dave Vellante with Jeff Frick. This is theCube and we're here at ServiceNow Knowledge '17. Stanley Toh is here, he's the Global IT Director at semiconductor manufacturer Broadcom. Stanley, thanks for coming to theCUBE. >> Nice to be here. >> So, semiconductor, hot space right now. Things are going crazy and it's a good market, booming. That's good, it's always good to be in a hot space. But we're here at Knowledge. Maybe talk a little bit about your role, and then we'll get into what you're doing with ServiceNow. >> Sure. You're right. Semiconductor is booming. But we don't do anything sexy. Everything is components that go into your iPhones and stuff like that. They do the sexy stuff. We do the thing that make it work. So, I'm the what we call the Enterprise and User Services Director, so basically anything that touches the end user, from the help desk to collaboration to your PC support desk, everything is under. Basically anything that touches the end user, even onboarding, and then, now with the latest, we actually moved our old customer support portal to even ServiceNow CSM. >> Okay, so what led you to ServiceNow? Maybe take us back, and take us through the before and the after. >> Okay. Broadcom Limited, before we changed our name to Broadcom, we were Avago Technologies. We are very cloud centric. Anything that we can move to the cloud, we moved to the cloud. So we were the first multi-billion dollar company to move to Google, back in 2007. That was 10 years ago. And then we never stopped since. We have Opta, we have Workday. And if you look at it, all this cloud technology works so well with ServiceNow. And ServiceNow is a platform that has all the API and connectors to all these other cloud platforms. So, when we were looking and evaluating, first as just the ITSM replacement, we selected ServiceNow because of the ease of integration. But as we get into ServiceNow, and as we learn ServiceNow, we found that it's not just an ITSM platform. You can use it for HR, for finance, for legal, for facilities. Recently, probably about six months ago, we launched the HR module. And then three weeks ago, we went live with a CSM portal for the external customer. >> When you say you go back to 2007 with Google, you're talking about what, Google Docs? >> Everything. >> Dave: Everything. >> Email, calendar, docs, sites, Drive, but it was unknown. >> Dave: All the productivity stuff. >> Everything. >> Dave: Outsourced stuff. >> They were unknown then, >> Jeff: Right, right, right. >> And it's a risk. >> So what was the conversation to take that risk? Because obviously there was a lot of concern at the enterprise level on some of these cloud services beyond test/dev in the early days. Obviously you made the right bet, it worked out pretty well. (Stanley laughing) But I'm curious, what were the conversations and why did you ultimately decide to make that bet? >> Okay. So 2007 was just after the downturn. >> Jeff: Right. >> So everyone was looking at cost, at supportability. But at the same time, the mobile phone, the smart phone is just exploding in the market. So we want something that is very flexible, very scalable, and very easy to integrate, plus also give you mobility. So that's why we went with Google as the first cloud platform, but then we started adding. So right now, we can basically do everything on your smart phone. We have Opta as our single sign-on. From one portal, I go everywhere. >> Dave: Okay, so that's good. So you talked about some of the criteria for the platform. How has that affected how you do business, how you do IT business? >> See, IT has always been looked upon as a cost center. And we are always slow, legacy system, hard to use, we don't listen to you. (Jeff laughing) >> Dave: What do those guys do? >> You know, why are we paying those guys, right? And then you look at all the consumer stuff. They are sexy, they are mobile, they have pretty pictures. Now all your internal users want the same experience. So, the experience has changed. The old UNIX command key doesn't work anymore. They want something touch, GUI, mobile. They want the feel, the color, you know. >> That might be the best description (Stanley laughing) of the consumerization of IT, Dave, that we've ever had on theCUBE. >> It's really honest. Coming from an IT person, it is, it is honest. And now you've driven ServiceNow into other areas beyond IT. >> Stanley: Yes. >> You mentioned HR. >> HR. We went live six months ago. >> Okay. And these other areas, are you thinking about it, looking at it, or? >> So we are also looking with legal, because they have a lot of legal documents and NDAs and stuff like that. And ServiceNow have a very nice integration to DocuSign and Vox. So we are looking at that. But the latest one, we went live three weeks ago, is the CSM, the customer support management portal. And that one actually replaced one of our legacy system that has a stack of sixteen application running. And we collapsed that, and went live on ServiceNow CSM three weeks ago. >> And what has been, two impacts - the business impact, and, I'm curious, is it the culture impact. You sort of set it up as the attitude. We had fun with it, but it's true. What's the business impact? And what has the cultural impact been? >> The last few years, we have been doing a lot of acquisition. So we have been bringing in a lot of new BU's. Business units. And they want things to move fast, and we want to integrate them into one brand. So speed and agility is key when you do acquisitions. So that's why we are moving into a platform where we can integrate all these new companies easily. We found that in ServiceNow and we can integrate them. So for example, when we acquired Broadcom Corporation, they have 18,000 employees. We onboarded them on day one, and usually when you do an acquisition, they don't give you the employee information until the last minute. Two days, all I need, is to bring them all on, onboarded into my collaboration suite. I only need two days of the information, and on day one, Turn it on, they are live. Their information is in, they have an email account. All their information is in ServiceNow. They call one help desk, they call our help desk, they get all the help and services. So it's fully integrated on day one itself. >> And you guys also own LSI now, right? >> Yes, LSI. >> Emulex? >> Emulex, PLX. >> PLX. >> The latest acquisition is Brocade, which we will close in the summer. And then, the rumored Toshiba NAND business. So, yeah, we are doing a lot of acquisitions. >> Yeah, quite a roll-up there. >> Correct. So as you can see, they are all very different companies. So when they come in, they have different culture. They have different workflow, they have different processes. But if you integrate them into a platform that we are very familiar right now, it's the consumerized look and feel, it's very easy to bring them in. >> And that is the cultural change that has occurred. >> Yes, it's a huge, >> So do people love IT now? >> They still hate IT. (Jeff and Dave laughing) They still say iT is a cost center. But right now, they are coming around. They see that we are bringing value to them. So right now, IT is just not to provide you the basic. IT is to enable the business to be better and more competitive. >> A true partner for the business. >> Yes, correct. >> Stanley, thanks very much for coming to theCUBE. It was great to hear your story, we appreciate it. >> Stanley: Thanks for having me. >> You're welcome. All right, keep it right there, buddy. We'll be back with our next guest. This is theCUBE, we're live from ServiceNow Knowledge '17. We'll be right back. (upbeat music)

>> Announcer: Live from Orlando, Florida, it's theCUBE. Covering ServiceNow Knowledge '17. Brought to you by ServiceNow. >> Welcome back to Orlando, everybody. This is theCUBE, the leader in live tech coverage, and we are covering three days wall to wall coverage of ServiceNow Knowledge 2017. I'm Dave Volante with my co-host Jeff Frick. When we first started doing Knowledge in 2013, you'd walk around the show floor, and the names that you'd see weren't the brand names. Well, Infosys is here and Gaurav Uniyal, who's the industry principal of North America for the practice lead at ITSM for the ServiceNow practice with Infosys, you're seeing the big SIs join the community and really start to add value. Gaurav, welcome to theCUBE, thanks so much. >> Thank you. >> How'd you guys get into this? Like you say, four or five years ago, you guys might have been kicking the can, and now, you're all in. What's the journey been like? >> Sure, sure. We have been a partner with ServiceNow for almost last eight years, and as I look back to the journey, I can categorize the journey into four parts. Initially we saw 2010 to 2012 is basically about ITSM, how do you get the foundation capabilities in? Once that was there, we saw for the next couple of years it was all about how do you integrate services together, the service integration management as a concept. The third wave we saw is where concepts like ITOM, mobility, there's a lot of focus on user experience. And now, here we are in 2017, and as we look at the trends, what we are anticipating for the next two to three years, on a very high level, there are three trends which we believe are going to shape the journey of ServiceNow. First one is AI, obviously, how do you bring in concepts of machine learning, chat bars, predictive analytics, and how would that help organization do things faster, more efficiently, and in a cost-optimizing manner? AI is definitely one. Second trend that we are seeing is now organizations are looking for solutions that are relevant to their business. Solutions which are specific to retail industry, to CBGs, to finance, to healthcare, and so on, so forth. We are seeing a lot of traction there. And third is the natural expansion of ServiceNow into newer areas like obviously CSM, HR and so on, so forth. These are the three trends on the high level that we see, AI, going vertical, and on going horizontal by expanding these capabilities. >> Big factor when you talk to customers is sometimes it's not simple to implement ServiceNow. They need a partner like yours, so where do you start? I mean, when we first started following ServiceNow, a lot of folks weren't adopting CMDB and going too hard on the service catalog. To take advantage of these trends, the AI and other things that you talked about, do they need to be there on the majority curve? I wonder if you could talk about that a little bit. >> Sure, sure. What we see is that obviously there are a set of foundational capabilities that are required. There's definitely a push required from the management to be able to drive the initiator. But more and more we are seeing our clients implementing the solution in a standardized manner. If I look back four or five years back, a lot of customization, everybody have their own processes. But when I talk with clients now, they're looking for something which is ready-made, which can be deployed in a very, very faster manner. >> Gaurav, why Infosys? Talk about what you bring to the table versus maybe some of the other suppliers out there, and what do you consider your sweet spot? >> I think I would, a couple of things. One is Infosys we do a lot of work outside of ServiceNow. We have our practices for cloud, we have practices for HR, and so on, so forth. One thing that have been to our table is the domain expertise. If you're implementing HR, it requires not only ServiceNow skills, but as well as domain skills to be able to configure the processes. That's one differentiator that we have. The second differentiator we have is delivering ServiceNow as a service, so clients are also looking for turnkey projects where one render can bring in the platform, bring in consulting, implementation services, and also be able to manage the platform end-to-end, so that's the second thing. And third thing is basically being ahead of the curve. What we have done, we have invested last, I would say, last eight to 10 months in building a product that we brand as ESM Cafe, Enterprise Service Management Cafe, and it's what we call as a gold image of ServiceNow, and that helps you deploy ServiceNow faster and in efficient manner. >> So, Gaurav, what did you see eight years ago, 'cause clearly ServiceNow isn't where it is today, that gave you guys the confidence to make the investment? >> And before ServiceNow, we used to work with other products as well. What we saw new with ServiceNow was a huge focus on user experience. How do you make it easy for the users, how do you deploy an intuitive solution? And in our view, that has been the key, a focus on user experience, bring simplistic workflows, and be able to drive user behavior. >> Maybe some of those other domains, you mentioned HR, where else do you see Infosys as really strong? >> What we are seeing is ITOM is definitely one area that we are focusing on. HR, CSM, these are two big stack we have. And then, we are also focusing a lot on building vertical solutions. As I said, having specific solutions for retail industry, for our healthcare clients, or manufacturing clients. That has been a focus for us. >> We're out of time, Gaurav, but I'd like to leave you with the last word. Knowledge 2017, what does it mean to you, your customers, and Infosys and your presence here? Give us the bumper sticker. >> So I think, if I have to summarize everything in one word, I will say it's all about diversity. We see so many partners, so many clients, everybody they have their own perspective. But how do you bring in all that diverse experience and gel it together to be able to deliver the experience for the users? >> Great, well, Gaurav, thanks very much for coming on theCUBE, we appreciate it. >> Yep, it has been pleasure. >> Okay, well, keep it right there, everybody. We'll be back with our next guest right after this short break. This is theCUBE, we're live from ServiceNow Knowledge '17. Be right back. (electronic keyboard music)