Especialista at a tech vendor with 10,001+ employees
Real User
Top 20
Jul 16, 2026
WalkMe is primarily used through WalkMe in Workday, where I create Smart Walk-throughs, banners, and several other features to make employees' lives easier when using Workday for HR tasks.
My main use case for WalkMe is primarily for mock-ups for new products. A quick specific example of how I use WalkMe for mock-ups with new products is that sometimes users have to go through different platforms, meaning one platform and another one a partner's platform, so I ensure that customers are guided on which platform to go first and second, because eventually it becomes a kind of back-and-forth situation. I would also add that another use case, though not really relevant, is the use of data and analytics to understand user behavior.
My main use case for WalkMe is for businesses who are SAP Rise customers or those going through a transformation from ECC to S/4HANA, as well as certain greenfield implementations for ERP. I have one end-to-end experience of a project transforming from ECC to S/4HANA, and once the transformation was completed, the entire business moved from on-premise to cloud. That is when the user had to be trained for certain new aspects, and I helped the clients understand and adopt WalkMe, showing them how it is useful. WalkMe has positively impacted our organization, which is mostly an SAP partner organization that helps customers already using SAP software for their businesses. We have used WalkMe in that perspective, especially for SAP Rise and Grow customers when an implementation is done and the organization is ready to operate independently with the new software features. When employees need to be trained, that is when WalkMe has been used.
My main use case for WalkMe is helping people go through the software more easily, productively, and faster. A specific example of how I use WalkMe is with SAP, where I create walkthroughs for new joiners or even long-time employees. When there is a new process or the process changes in SAP, I create walkthroughs so people can simply type how to book a hotel and then they have a walkthrough from beginning to end.
My main use case for WalkMe was that there were a lot of apps rolling out on enterprise software for a financial firm, and they turned to WalkMe as a solution. I scrambled to go through a bunch of the courses that allowed me to implement it as a test run, and I did on a couple of projects, but I ended up finding out that it has flaws, and so that was part of my conclusion with it. A specific example of how I used WalkMe on one of those projects was that there was a lot of confusion over software being developed, and users were completely in the dark about many things that were really right in their face that they just didn't see. During some more complex interaction processes, it was important to put something like WalkMe in place so that people would know what to do, how to navigate the UI, and where to go for things. We used WalkMe in tandem with questionnaires and surveys. I had to actually lock senior VP people out of the sessions because they were glued to their participants, which kind of screwed around a little with their feedback; it is giving feedback with your boss breathing down your neck. That was challenging to get real answers, but WalkMe was definitely a great solution. I believe it has been a long time, and I'm sure they've fixed many problems since then, but for my specific purposes, my relationship with that project didn't go exactly as I would have liked, resulting in a strange feeling about WalkMe. I found a flaw, and nobody believed me. Aside from that, assuming the flaw's been fixed, I think it would be great for people to incorporate because there are countless times where users look at a screen and have no idea what to do, and WalkMe is a really great solution for something that. There were many courses I didn't take that were part of the package and would be beneficial for anyone really looking at it; it is a powerful solution for sure.
My most current project with Presbyterian Health Services involves a Workday implementation where we use WalkMe as what we call in-app guidance to guide users through processes from start to finish, making their job easier by providing terminology changes for comparisons to what was referenced in the previous system and automating processes to streamline those and make them quicker and more efficient. With my previous project, I worked heavily on the supply chain change management side, automating the inventory transfer process where users would have to click multiple times depending on the sites selected. I automated it so users just received a message indicating we were working on it while WalkMe processed the clicks in the background. That is just one example of automated processes, which is heavily useful for financial components in applications, where users often repeat entries during month-end processes or balancing books. Automating and autofilling those fields saves users a lot of time and mistakes.
My main use case for WalkMe is to support our employees, or our users, in using the SAP S/4HANA process, especially in the purchasing and financial areas. A specific example of how WalkMe helps users in those purchasing or financial areas is that our employees use WalkMe to support them in completing processes, such as filling a purchase requisition or finishing a payment. Besides that, WalkMe provides all the information that is useful for onboarding tasks, which is a very useful feature for this solution.
In large digital transformations, my main use case for WalkMe is adoption. We are implementing streamlined processes, but change management requires a significant amount of time. By using digital adoption tools like WalkMe, you cannot replace change management, of course, but you can definitely impact it positively to help users understand how the processes have been implemented in the cloud platforms that you have selected. In the context of supporting HR and using WalkMe within a Workday environment, I realized that we needed a more technically focused person within the HR function itself, not just to do WalkMe, but also to conduct walkthroughs, change management activities, and provide basic first-level IT support to the HR community. WalkMe best sits within HR, as they need to keep it up to date, understand why the process has been implemented that way, and communicate in a user's language rather than an IT person's language. This allows an HR specialist and WalkMe to provide a step-by-step explanation of processes and system implementations, which is a significant advance in any digital transformation context. In terms of how the field-level support and step-by-step guides have impacted users, we have a quite complex payroll process where we opened up self-service to end users to update some beneficiaries or denote that they now have a child or are entitled to a new benefit package. This process has complex implications regarding payroll, and without WalkMe, we realized very soon that it would be difficult to open this self-service effectively. WalkMe allowed us to ensure the user understood the implications of making those changes and prevented bad data from entering the payroll process, which drove compliance, data quality, and cost savings. WalkMe supports compliance and regulatory requirements by ensuring that processes are implemented correctly and understood, minimizing room for errors and ensuring legal compliance within HR and financial processes. WalkMe helps manage change during large-scale projects by covering key change management activities. We provide walkthroughs of the processes and recording sessions while also offering WalkMe at the system level to guide users through how processes work and evolve.
Onboarding and change management are my main use cases for WalkMe. I use WalkMe to support digital adoption post-go-live for onboarding and change management. This means supporting in the flow of work, providing both resources, support, and in-app guidance to ensure that people are using the system as intended, not only correctly, but within their business processes. The other main use case is onboarding, which includes helping new staff members learn all about the organization they've just joined, and that includes all of their systems.
My main use case for WalkMe is measuring the adoption of enterprise applications, user digital task completion rate and time, so in general, digital task performance, and of course, also contextual guidance. In order to measure the digital task performance, I set up the analytics that measure user interactions with individual UI elements of applications, as well as how users navigate across or through digital tasks, measuring completion of different milestones and key steps throughout the task, in order to understand at which stage of a process or a task users drop off, and how long it takes them to complete a task.
I don't personally use WalkMe in my company, but I already have clients that I support with WalkMe.The main use case for WalkMe that I see with my clients is user enablement. That is, using targeted information or automations to provide employees as quickly as possible with relevant information, help and guidance, as well as the possibility to fully automate certain process steps 100%. So ultimately, to save the end user significantly more time and to greatly simplify handling and working with, for example, ERP systems or other applications. A classic case would be travel expense reporting. WalkMe helps to make travel expense reporting easier or more efficient for end users because if the process is always the same for everyone, it can be automated. I could configure that. But if it's different, for example, if we have different cost centers and so on, then it would make sense to use, for example, ShoutOuts or Launchers or simply add small quick tips to help the user with a task that has to be 100% correctly completed and created but is often prone to errors. That is, to support them in performing a task that may not really be a central part of their core job field as quickly, simply, and also as reliably as possible. I would not like to add anything else about the use cases or the support provided by WalkMe.
WalkMe guides end users on how to use tools such as Salesforce when they are new to the platform. It functions as an extension running on top of Salesforce, helping end users understand how to navigate and use the platform. WalkMe provides step-by-step guidance by instructing end users on UI elements, available fields, and next steps in their workflow. It serves as a guiding tool for end users to understand how to use the product.
My main use case for WalkMe is that it has been helping us unlock huge value by bringing WalkMe to our many products for the past five years. We have been using WalkMe for many use cases and opportunities, such as training, onboarding new users, managing changes, and updates in those platforms, ensuring our users are entering correct data, and learning user behavior from analytics. For change management, it eases users through change with guidance and provides in-system surveys. For onboarding, it quickly brings new users up to speed with onboarding tasks. It also helps with automation, automating our regular processes and cutting system time, freeing users up for more important tasks. There is ease of use and getting up to speed in just a few days. There is a very friendly community of users who help each other all the time and structured upskilling programs. Weekly tips keep the learning going. There is great analytics on our platform usage and adoption by users and surveys. WalkMe is particularly good for onboarding new staff and being able to search over multiple apps instantly. From an IT training point of view, I would use WalkMe if I could on every piece of software in some form.
Our story at Fulcrum GT with WalkMe started back in 2019 when we wanted to introduce WalkMe into our Snap solution, which is built on top of SAP S/4HANA. This was one of the first implementations of WalkMe on top of SAP. Our main use case for WalkMe at Fulcrum GT is primarily for change management, training, and onboarding new users to the platform. It is also used for users who have been using the platform for some time but may be running into trouble on a particular process or workflow they are working on. Referring to a WalkMe guided walkthrough in those instances proved to be helpful. Inside of SAP, there are hundreds of different workflows that a user can take depending on their role, and there could be dozens of examples of where users have leveraged WalkMe guided walkthrough functionality to guide them through a particular SAP process or workflow.
WalkMe serves as my digital adoption platform that provides features where user friction is reduced, and you get different sorts of walkability and navigation. The navigation workflows help you understand the features and perform all necessary operations. WalkMe is adopted across different platforms and acts as simple in-app guidance that gives automated tools, automation, and analytics, providing whatever content is visible on the platform. WalkMe helps you over the context. A quick specific example of how I use WalkMe in my organization is mainly during VMware deployments when we deploy this VMware. My main use case for WalkMe involves internal IT applications that are generally available. I write those IT, ITAM, and supporting tools for troubleshooting monitoring dashboards and all that. WalkMe can be deployed there, reducing time for my team and all of the change management and feature releases. Majorly, for example, in the case of VMware, we use VM management tools, all the storage, and where you have all your compute storage and networking in place. WalkMe helps with the virtualization of the storage part and gets things sorted for us.
WalkMe optimizes onboarding and user engagement by integrating in-app navigation and analytics for improved user guidance and efficiency. Its intuitive interface minimizes support needs, streamlining processes for better user interaction.WalkMe's in-app features enhance data integrity and reduce support tickets through effective user guidance. Shoutouts and launchers increase user engagement, while custom tutorials offer flexibility in workflows. Integration with popular systems allows for a...
WalkMe is primarily used through WalkMe in Workday, where I create Smart Walk-throughs, banners, and several other features to make employees' lives easier when using Workday for HR tasks.
My main use case for WalkMe is primarily for mock-ups for new products. A quick specific example of how I use WalkMe for mock-ups with new products is that sometimes users have to go through different platforms, meaning one platform and another one a partner's platform, so I ensure that customers are guided on which platform to go first and second, because eventually it becomes a kind of back-and-forth situation. I would also add that another use case, though not really relevant, is the use of data and analytics to understand user behavior.
My main use case for WalkMe is for businesses who are SAP Rise customers or those going through a transformation from ECC to S/4HANA, as well as certain greenfield implementations for ERP. I have one end-to-end experience of a project transforming from ECC to S/4HANA, and once the transformation was completed, the entire business moved from on-premise to cloud. That is when the user had to be trained for certain new aspects, and I helped the clients understand and adopt WalkMe, showing them how it is useful. WalkMe has positively impacted our organization, which is mostly an SAP partner organization that helps customers already using SAP software for their businesses. We have used WalkMe in that perspective, especially for SAP Rise and Grow customers when an implementation is done and the organization is ready to operate independently with the new software features. When employees need to be trained, that is when WalkMe has been used.
My main use case for WalkMe is helping people go through the software more easily, productively, and faster. A specific example of how I use WalkMe is with SAP, where I create walkthroughs for new joiners or even long-time employees. When there is a new process or the process changes in SAP, I create walkthroughs so people can simply type how to book a hotel and then they have a walkthrough from beginning to end.
My main use case for WalkMe was that there were a lot of apps rolling out on enterprise software for a financial firm, and they turned to WalkMe as a solution. I scrambled to go through a bunch of the courses that allowed me to implement it as a test run, and I did on a couple of projects, but I ended up finding out that it has flaws, and so that was part of my conclusion with it. A specific example of how I used WalkMe on one of those projects was that there was a lot of confusion over software being developed, and users were completely in the dark about many things that were really right in their face that they just didn't see. During some more complex interaction processes, it was important to put something like WalkMe in place so that people would know what to do, how to navigate the UI, and where to go for things. We used WalkMe in tandem with questionnaires and surveys. I had to actually lock senior VP people out of the sessions because they were glued to their participants, which kind of screwed around a little with their feedback; it is giving feedback with your boss breathing down your neck. That was challenging to get real answers, but WalkMe was definitely a great solution. I believe it has been a long time, and I'm sure they've fixed many problems since then, but for my specific purposes, my relationship with that project didn't go exactly as I would have liked, resulting in a strange feeling about WalkMe. I found a flaw, and nobody believed me. Aside from that, assuming the flaw's been fixed, I think it would be great for people to incorporate because there are countless times where users look at a screen and have no idea what to do, and WalkMe is a really great solution for something that. There were many courses I didn't take that were part of the package and would be beneficial for anyone really looking at it; it is a powerful solution for sure.
My most current project with Presbyterian Health Services involves a Workday implementation where we use WalkMe as what we call in-app guidance to guide users through processes from start to finish, making their job easier by providing terminology changes for comparisons to what was referenced in the previous system and automating processes to streamline those and make them quicker and more efficient. With my previous project, I worked heavily on the supply chain change management side, automating the inventory transfer process where users would have to click multiple times depending on the sites selected. I automated it so users just received a message indicating we were working on it while WalkMe processed the clicks in the background. That is just one example of automated processes, which is heavily useful for financial components in applications, where users often repeat entries during month-end processes or balancing books. Automating and autofilling those fields saves users a lot of time and mistakes.
My main use case for WalkMe is to support our employees, or our users, in using the SAP S/4HANA process, especially in the purchasing and financial areas. A specific example of how WalkMe helps users in those purchasing or financial areas is that our employees use WalkMe to support them in completing processes, such as filling a purchase requisition or finishing a payment. Besides that, WalkMe provides all the information that is useful for onboarding tasks, which is a very useful feature for this solution.
In large digital transformations, my main use case for WalkMe is adoption. We are implementing streamlined processes, but change management requires a significant amount of time. By using digital adoption tools like WalkMe, you cannot replace change management, of course, but you can definitely impact it positively to help users understand how the processes have been implemented in the cloud platforms that you have selected. In the context of supporting HR and using WalkMe within a Workday environment, I realized that we needed a more technically focused person within the HR function itself, not just to do WalkMe, but also to conduct walkthroughs, change management activities, and provide basic first-level IT support to the HR community. WalkMe best sits within HR, as they need to keep it up to date, understand why the process has been implemented that way, and communicate in a user's language rather than an IT person's language. This allows an HR specialist and WalkMe to provide a step-by-step explanation of processes and system implementations, which is a significant advance in any digital transformation context. In terms of how the field-level support and step-by-step guides have impacted users, we have a quite complex payroll process where we opened up self-service to end users to update some beneficiaries or denote that they now have a child or are entitled to a new benefit package. This process has complex implications regarding payroll, and without WalkMe, we realized very soon that it would be difficult to open this self-service effectively. WalkMe allowed us to ensure the user understood the implications of making those changes and prevented bad data from entering the payroll process, which drove compliance, data quality, and cost savings. WalkMe supports compliance and regulatory requirements by ensuring that processes are implemented correctly and understood, minimizing room for errors and ensuring legal compliance within HR and financial processes. WalkMe helps manage change during large-scale projects by covering key change management activities. We provide walkthroughs of the processes and recording sessions while also offering WalkMe at the system level to guide users through how processes work and evolve.
Onboarding and change management are my main use cases for WalkMe. I use WalkMe to support digital adoption post-go-live for onboarding and change management. This means supporting in the flow of work, providing both resources, support, and in-app guidance to ensure that people are using the system as intended, not only correctly, but within their business processes. The other main use case is onboarding, which includes helping new staff members learn all about the organization they've just joined, and that includes all of their systems.
My main use case for WalkMe is measuring the adoption of enterprise applications, user digital task completion rate and time, so in general, digital task performance, and of course, also contextual guidance. In order to measure the digital task performance, I set up the analytics that measure user interactions with individual UI elements of applications, as well as how users navigate across or through digital tasks, measuring completion of different milestones and key steps throughout the task, in order to understand at which stage of a process or a task users drop off, and how long it takes them to complete a task.
I don't personally use WalkMe in my company, but I already have clients that I support with WalkMe.The main use case for WalkMe that I see with my clients is user enablement. That is, using targeted information or automations to provide employees as quickly as possible with relevant information, help and guidance, as well as the possibility to fully automate certain process steps 100%. So ultimately, to save the end user significantly more time and to greatly simplify handling and working with, for example, ERP systems or other applications. A classic case would be travel expense reporting. WalkMe helps to make travel expense reporting easier or more efficient for end users because if the process is always the same for everyone, it can be automated. I could configure that. But if it's different, for example, if we have different cost centers and so on, then it would make sense to use, for example, ShoutOuts or Launchers or simply add small quick tips to help the user with a task that has to be 100% correctly completed and created but is often prone to errors. That is, to support them in performing a task that may not really be a central part of their core job field as quickly, simply, and also as reliably as possible. I would not like to add anything else about the use cases or the support provided by WalkMe.
WalkMe guides end users on how to use tools such as Salesforce when they are new to the platform. It functions as an extension running on top of Salesforce, helping end users understand how to navigate and use the platform. WalkMe provides step-by-step guidance by instructing end users on UI elements, available fields, and next steps in their workflow. It serves as a guiding tool for end users to understand how to use the product.
My main use case for WalkMe is that it has been helping us unlock huge value by bringing WalkMe to our many products for the past five years. We have been using WalkMe for many use cases and opportunities, such as training, onboarding new users, managing changes, and updates in those platforms, ensuring our users are entering correct data, and learning user behavior from analytics. For change management, it eases users through change with guidance and provides in-system surveys. For onboarding, it quickly brings new users up to speed with onboarding tasks. It also helps with automation, automating our regular processes and cutting system time, freeing users up for more important tasks. There is ease of use and getting up to speed in just a few days. There is a very friendly community of users who help each other all the time and structured upskilling programs. Weekly tips keep the learning going. There is great analytics on our platform usage and adoption by users and surveys. WalkMe is particularly good for onboarding new staff and being able to search over multiple apps instantly. From an IT training point of view, I would use WalkMe if I could on every piece of software in some form.
Our story at Fulcrum GT with WalkMe started back in 2019 when we wanted to introduce WalkMe into our Snap solution, which is built on top of SAP S/4HANA. This was one of the first implementations of WalkMe on top of SAP. Our main use case for WalkMe at Fulcrum GT is primarily for change management, training, and onboarding new users to the platform. It is also used for users who have been using the platform for some time but may be running into trouble on a particular process or workflow they are working on. Referring to a WalkMe guided walkthrough in those instances proved to be helpful. Inside of SAP, there are hundreds of different workflows that a user can take depending on their role, and there could be dozens of examples of where users have leveraged WalkMe guided walkthrough functionality to guide them through a particular SAP process or workflow.
WalkMe serves as my digital adoption platform that provides features where user friction is reduced, and you get different sorts of walkability and navigation. The navigation workflows help you understand the features and perform all necessary operations. WalkMe is adopted across different platforms and acts as simple in-app guidance that gives automated tools, automation, and analytics, providing whatever content is visible on the platform. WalkMe helps you over the context. A quick specific example of how I use WalkMe in my organization is mainly during VMware deployments when we deploy this VMware. My main use case for WalkMe involves internal IT applications that are generally available. I write those IT, ITAM, and supporting tools for troubleshooting monitoring dashboards and all that. WalkMe can be deployed there, reducing time for my team and all of the change management and feature releases. Majorly, for example, in the case of VMware, we use VM management tools, all the storage, and where you have all your compute storage and networking in place. WalkMe helps with the virtualization of the storage part and gets things sorted for us.