Why AI Agents Still Need Digital Adoption
From guidance to cross-application workflows
WalkMe began by guiding users through enterprise applications. Large companies may have thousands of people in a single role, so training and enablement can be harder than building the system itself. Over time, WalkMe added analytics on where people get stuck. It also added simple automations and workflows that start in a CRM and finish in an ERP.Why chatbots can’t replace digital adoption
A chatbot can explain how to use a common app. However, it has never seen a company’s own fields, logic and approval steps. Every enterprise system has been customized, Carmi says. As a result, an LLM can only solve a small part of the problem.AI agents need governance, not just APIs
AI agents face a similar gap. Many enterprise systems still lack APIs, and much of the guidance lives in the user interface. WalkMe works inside the application as the user, with the same permissions and an audit trail. Companies can also decide whether a human must approve every step or only the final one.Digital adoption for AI itself
Finally, Carmi notes that rolling out an LLM is itself an adoption challenge. People will not use it the same way unless someone shows them how. That makes digital adoption just as important for AI tools as for any other system.Transcript
Hey, everyone. Welcome back here to Techstrong TV. My next guest is Tal Carmi.
Tal is the CIO of a company called WalkMe. It's actually now WalkMe SAP. It's part of the SAP family.
WalkMe is not a stranger to my world. I've been following WalkMe for many, many years, prior to the SAP merger, and I think this might be my first or second interview since then. So if you're not familiar with WalkMe, though, don't worry, we're going to tell you all about it.
But first, let me introduce you to Tal Carmi, who's the CIO over at WalkMe. And Tal, welcome to Techstrong TV. It's great to have you on here.
Thank you. Thank you for having me. Before we get into WalkMe, let's hear a little bit about you.
Sure. So I'm Tal. I am CIO of WalkMe, as you mentioned.
I kind of grew up in, I guess, in business applications. I started as a Salesforce professional, and I grew up to that. I was a consultant, moved in-house for managing Salesforce for a company, and then did a little stint, a few years as a product manager, went back to information systems, and been at WalkMe, left for a while, came back prior to the IPO, and I've been with WalkMe now from the second run for about six years now.
And I stepped into the CIO position about half a year ago. I was the deputy CIO before, managing information systems, integration, BI, data, all of those worlds. So that's me.
And yeah. Very good. You want us to talk about WalkMe now at this point?
Yes, if that's okay. I think you were very humble, but it's an interesting path. Now, Tal, I mentioned I've covered WalkMe for a long time.
What I remember most about it was the first time I saw a demo of it. I think I mentioned I was at an Insight Ignite meeting, from Insight Partners. And I'm trying to remember the gentleman's name.
He was terrific. But basically, he was, I think, part of the founding team, and he spoke about the need for his mother to be able to use applications and how he was trying to explain to his mother how to use, I forgot what app it was. But it wasn't easy.
She wasn't a tech person, and he had to explain it to her, and he knew there had to be a better way. And then he realized, forget his mother, what about all of the many users out here who are using, in an enterprise, I forgot what the number was, how many different applications we have a typical enterprise user has to use. And how you may be an expert in Salesforce, let's say, but HubSpot, Slack, all of the other things you're using, how do we make sure you're getting the most out of them?
How do we make sure you really know how to use them? And that was kind of the WalkMe reason for being, if you will. That was the mission.
Am I off base? Am I right? How would you describe it?
It's a digital adoption platform, right? So it's definitely what you just said. I think that is the core.
And it's both for external use cases, like you mentioned, I have a website and I have customers and I want them to use it, so how do I help them use it in a better way? But of course, I think the bigger use case even, it might is internal. So I have so many systems, as you mentioned, and they're constantly changing because the business is evolving.
How do I get everybody to actually use the systems at all, and specifically the way I want them to? And if you are working at a small company, that sounds like, okay, I have 10 guys, AEs, or even 50, and I can train them. But as you go to real enterprise, like really big enterprises, you might have thousands or tens of thousands of employees in a specific role, right?
So now training and enablement become a probably much bigger challenge than actually developing whatever you need to develop. And I think that was where WalkMe traditionally started, and then we evolved around analytics around that, like what are people doing in the systems? Where do they get stuck?
How do we get better insights around do they do what we want them to do? Are they able to complete whatever processes we want them to complete? So it was an entire layer around that.
I think WalkMe's technology got to a point where it was also augmenting IT in a sense. So we would have people that, in some use case, you might say, "You know what? I can go through my traditional IT road and get them to add a button or an explanation or something, but it might take me six months to get it in the pipe.
" And then WalkMe started to be also cross-applications. So I would start a process in Salesforce or whatever my CRM is, and I would need it to end in my ERP. So, it evolved to something much more complex.
So you start here, and then it will take you to the right place in the ERP and will even fill in some of the details for you from the CRM. And now, with AI, there is even more. So that's where we were, that's the road we did, and that's where we are now, I guess.
Yeah. Some may look at AI, and if it's okay with you, I'd like to bifurcate AI into generative AI versus agentic. Some may look at generative AI chatbot and say, "Oh, who needs WalkMe?
" Like I ask it so many other things. But the fact of the matter is, having a chatbot is a long way from learning how to use a website or getting the most out of an application that your company has paid for. So let's confine right now, Tal, to that.
Is a chatbot friend or foe to WalkMe? Is it a tool that makes WalkMe better, or is it something that you could use in place of a WalkMe sometimes? It really depends.
I guess, everything has two sides of it. Yeah. And, I think that, as you mentioned, I can ask probably any LLM, hey, how do I, I don't know, use a government site, or submit my taxes, or anything that is very common and well-known.
And I can also use it, how do I use Salesforce, or whatever, or HubSpot, or whatever other CRM. And it will tell you how to do it. But that's a very small piece of it, because if any company builds a process specific for itself, this is how we close a deal at company X.
If you ask any LLM, what do I need to do to close a deal as an AE in a company? It has no idea because it has never seen that system. It doesn't know the fields.
It doesn't know the logic. It's probably going to fail. It's going to give you really high-level direction.
You should probably change it to closed one. Great, but I might have 100 fields that I need to fill in, in the process, or I need to do... So I think LLM, if you're, as you mentioned, separating it into two different areas, just an LLM wouldn't solve that use case.
It might solve some of the use case for if you have a bank and it's very common and it has been trained on it, then it might be able to guide you on where to click in order to do something. But if you need to do something in your internal systems- It can guess. If your system hasn't been modified at all, it can probably tell you.
The number of systems that haven't been heavily modified in any enterprise, I think are zero. So, in that sense, it solves maybe a subset of the problem. And more to somebody on the admin side, right?
So if I need to know how do I define or build something in CRM or ERP, probably an LLM can tell me what to do. But that's not the audience that we are aiming for. We are aiming for, once I build that process based on my knowledge or the LLM helped me, how do I now get everybody to use it in the way I want them to?
So I have an internal process. Take a bank, for example. So I have a new process for taking a loan.
And when the bank teller or the person you speak to at the bank, you need to fill in different fields, and now we have a new field, and it has five different values, and I need them to choose the right value. An LLM won't be able to tell them what the right value is because they don't know. Maybe it's around definitions, right?
And I think that's where WalkMe is very relevant. So that's one side of the problem, as you mentioned. Did that answer or that make sense?
Yeah, absolutely. Yeah. I think that answers that for sure.
Let us now, though, move over to the agentic- Yeah ... piece of this. Yeah, so agentic- To bypass the human, it seems.
How do you view that with WalkMe? Yeah. So agentic, again, is the other side of it.
I type to close. Oh, go to my CRM and close this deal for me or update these details or whatever we need to do. And again, if it doesn't have the knowledge of my CRM, it's just going to look at the screen.
Okay. And this is even a harder one because it might be able to, again, agentic is also complicated when you get a little bit technical. You can get agentic to do things for you behind the scenes through an API, in a sense.
Connect directly to the system. You don't need to go through any screens because it's a computer speaking to a computer, in a sense, right? But then it might miss a lot of things.
So it will try and update what it knows. It will say, "Oh, you want to close the deal? Great.
I know that I need to move this stage. I will look for a stage called whatever closed one. " Okay.
So, if it will get back to me, maybe it will iterate, and by itself, it'll be able to fill them and go through all the errors and eventually get it. But in many systems, you might have things that are built into the user interface. So when you want to close a deal, I will show you a lot of things.
I will walk you through a process, either with WalkMe or internally in the system, that walks you through whatever you need to do. And that is completely unavailable through the API. And that's where things start to get a little bit messy.
So me, as a company, I need to now sort of change my systems so they will allow you to do whatever you're trying to do via the API route and make the changes needed or provide you the tools or the APIs to support what you could have done as a human in the user interface. And that's a big challenge, and I think many companies are far, far away. We have a lot of enterprise, or in general, there are a lot of enterprise customers that don't have APIs to all of their systems.
I'm not even talking about MCP, which is the way agents speak to APIs. And I'm putting aside all the security questions and all that. I'm just looking at the functional side.
I'm not even looking now at the other levels of it, of complexity. So if I have a system and I don't even have an API, so this entire, "Oh, the LLM will do everything for me," sort of breaks. " Again, great.
" Once I learn it, I will do it in the exact same way because I don't need to discover the world every time. And if this is the first time I've seen the system, I will help you bake in governance and control steps and where do I get a human to approve? Does the human need to approve every step or just the final step, or what do I want to happen?
And again, that's very different for every company, for every process, for every system. " Maybe other systems or processes, you're like, "Oh, what? Okay, give me an approval in the end.
If you made a mistake, okay, it's not great, but it's not... " In an ideal world, you would. In reality, you have companies that have been still migrating to the cloud.
So having them saying, "Oh, now we are also fully agentic," it's a leap. So I think that gap is not yet there. Maybe someday it will be.
" And then if WalkMe works in the system as you, then it has your permission, it has the governance, everything is exactly the same from the IT governance security perspective of it. Mm-hmm. And that's where WalkMe is in the agentic side of things, as you called it.
I love it. You know what? I feel like we just scratched the surface.
We're already at 15 minutes. I still got important things I need to hit on, Tal. First of all, to start wrapping up, how can people get their hands on WalkMe?
How can they try it out? What's like the on-ramp? It's the same process it has always been.
You reach out to WalkMe. We have a website and somebody- And the website is? com, surprisingly.
Right. And somebody will get back to you. And yeah, and I think it's a transformation.
And again, we haven't even spoken about the digital adoption transformation side of things. If I give everybody an LLM, they will not use it the same way, and definitely many people will not use it as I would want them to. That's another area where WalkMe can help.
Because just like any other tool that you need to enable, WalkMe can help you enable that. So yeah, definitely reach out to WalkMe, and we'd love to show you when, you know. Absolutely.
I appreciate you coming on, Tal. The time goes so quick here. Yes, it does.
15 minutes, it's boom, before you know it, it's gone. com. They can check it out, and there's probably also a list of all the different applications and everything that- Yes, of course ...
WalkMe works with there. Continued success. Come back and visit us.
We'll continue the conversation. All right. Thank you very much.
All right. Tal Carmi, CIO WalkMe from SAP, here on TechStrata TV. We'll be back in a minute.
Thank you. Bye.