Six months in, my client's work has TOTALLY CHANGED. You can plan ahead, but WalkMe sneaks up on you...
Here's a typical case from a client engagement last year.
Implementing on two different systems, 1k users, both CORE to their business ops.
We start by handling the IT logistics. Extension, SSO, system config, analytics, segmentation.
Then we divide up the labor.
I've never used their app before and build in PARALLEL with folks who have never touched WalkMe before.
Announcements, data validation, help menu, overall Walk-Thrus, automation, etc.
Six month later, my SME is loving building WalkMe and her work has totally changed.
"This is fun!"
But also... "This could be my full-time job!"
She's no longer just "fighting fires". Now looking at every question, every error as a "symptom". What kinds of "Walks" can we put in place to prevent?
Because we've used WalkMe to make errors and phone calls go away, now we are able to be strategic.
And with the success on this app, we expanded to an adjacent HR function.
So now we get to WalkMe Program Management.
Yes, you can talk about these things ahead of time. Centralized, decentralized, hybrid models, who would do what, etc.
But until you have demand, there's really nothing to talk about. You're putting the cart before the horse.
That's why in my experience the A#1 determination of success with WalkMe is the quality of the first deployment.
If you knock it out of the park, your customers are engaged.
If they are engaged, they take an interest and promote it internally.
If your first build is "meh" then WalkMe gets a reputation as oversold, "too hard", etc.
But really, it's not the tool.
It's the quality of the implementation.
Aaaaaaand.... That's why you don't want to DIY this out of the gate.
That's why you want to go with a competent partner.
Here's a typical case from a client engagement last year.
Implementing on two different systems, 1k users, both CORE to their business ops.
We start by handling the IT logistics. Extension, SSO, system config, analytics, segmentation.
Then we divide up the labor.
I've never used their app before and build in PARALLEL with folks who have never touched WalkMe before.
Announcements, data validation, help menu, overall Walk-Thrus, automation, etc.
Six month later, my SME is loving building WalkMe and her work has totally changed.
"This is fun!"
But also... "This could be my full-time job!"
She's no longer just "fighting fires". Now looking at every question, every error as a "symptom". What kinds of "Walks" can we put in place to prevent?
Because we've used WalkMe to make errors and phone calls go away, now we are able to be strategic.
And with the success on this app, we expanded to an adjacent HR function.
So now we get to WalkMe Program Management.
Yes, you can talk about these things ahead of time. Centralized, decentralized, hybrid models, who would do what, etc.
But until you have demand, there's really nothing to talk about. You're putting the cart before the horse.
That's why in my experience the A#1 determination of success with WalkMe is the quality of the first deployment.
If you knock it out of the park, your customers are engaged.
If they are engaged, they take an interest and promote it internally.
If your first build is "meh" then WalkMe gets a reputation as oversold, "too hard", etc.
But really, it's not the tool.
It's the quality of the implementation.
Aaaaaaand.... That's why you don't want to DIY this out of the gate.
That's why you want to go with a competent partner.