If you're getting ready to purchase or expand WalkMe, don't think you can rely on pre-built content templates.
Like other products, Digital Adoption Platforms have a general "time to value" challenge. How quickly will customers get results for their orgs after investing?
One thread to this is that for various Processes and Systems, there can be different pre-made "Kits", "Workflows", "Accelerators", etc.
In a pre-sale conversation: "Oh, you need help with Coupa? We have stuff already made for that!"
Don't want to offend here, just sharing my experience:
In six years of building WalkMe, I have gotten value from these exactly zero times.
Here's why..
Like other products, Digital Adoption Platforms have a general "time to value" challenge. How quickly will customers get results for their orgs after investing?
One thread to this is that for various Processes and Systems, there can be different pre-made "Kits", "Workflows", "Accelerators", etc.
In a pre-sale conversation: "Oh, you need help with Coupa? We have stuff already made for that!"
Don't want to offend here, just sharing my experience:
In six years of building WalkMe, I have gotten value from these exactly zero times.
Here's why..
- SaaS products are HIGHLY configurable company-to-company.
- When you're building WalkMe you need to go through a thought process in order to ARRIVE AT a solution.
You want to go from: Problem -> Impact -> Cause(s) -> WalkMe Solution
Let's take an example:
- Problem: Coupa users approve Invoices with incomplete data -->
- Impact: Company can lose money when improperly vetted invoices are approved -->
- Cause: Approve button on the homepage allows single-click approval without inspecting details -->
- WalkMe Solution: ShoutOut around policy, invisible launcher(s) on homepage to block instant approval, redirect flow to open invoice and inspect for complete data, etc.
How do templates play into this?
Templates shortcut the first three steps and give you "something" which may be interesting but not that useful in my experience.
"Home page tour", "Update Profile", "Create an Opportunity".
Templated content tries to anticipate what sorts of problems users might have on a given platform.
But here's the thing -- these are all "Solutions" to someone else's problem.
The way that product was configured in that org at that time.
But if you want your WalkMe solutions to really be effective? You're going to have to make them on your own.
What do you think?
Have you made use of templated content in WalkMe development?