How to Staff WalkMe
What's the best way to "resource" WalkMe™ in my company? Oof, big topic...
I usually get this question from folks who are trying to take someone with an existing job (Salesforce Admin, IT Dev, Marketing, etc) and add WalkMe to their list.
So let's step back a bit, maybe come at this from another angle.
("Resourcing" here is not my favorite term but that's for another time).
Here are your options:
1. Outsource to Partner
2. Hire New Employee
3. Assign / Train Existing Employee
#1 - Outsourcing to Partner
This is great for first in the company deployments. There's a lot of excitement, a lot of work to do (Extension, IDP, etc), you want it to go well, you want to get it done quickly, etc.
Until it's up and running all the way in your ecosystem at least once, you don't know what you don't know and you broader org hasn't really seen it.
So if you go with a partner who has been doing WalkMe for a while, you should get good results.
And the next question becomes where do we go from here? Continue to outsource or build capability in-house?
#2 - Hire Dedicated WalkMe Builder
This is IDEAL if your company can add the headcount. We're getting someone in with the experience and the explicit assignment. That's great.
Often this is not going to work with your timeline for new system introduction.
Say you have a system timeline that's launching in 3 months, you're going to have a hard time HIRING someone, getting them all the access they need, getting them up to speed on the business problems AND then having them build the WalkMe content in that timeline.
Hence outsourcing that first deployment.
And sometimes it's a big ask to just do the big WalkMe project and implementation. So with only one system under your belt, some companies can be reluctant to then go hire someone to advance it.
OK so we had a partner help us for the initial deployment.
But I don't have the juice to go open a job rec. Now what?
#3 - Assign / Train Existing Employee
It's ideal if the WalkMe Champion / SME can also be initial builder. That's how it was for me many years ago.
But that person can then leave or take another job. Or you want to expand to a new department.
Then what do we do?
Well, we should have cross-trained a backup WalkMe builder so we could avoid a single point of failure. But suppose we didn't do that either?
First off, don't just PICK someone and tell them they have a new assignment. That usually does not go well.
You want to have people VOLUNTEER for the assignment.
The thing I've found to be the greatest predictor of success is MOTIVATION.
If the person is building and maintaining on a single app, I've found that WalkMe can be a part-time assignment (depending on skill level, content to be built, and 10 other factors).
And after you've found that person?
Send them to my DAP Academy program. I'll be happy to get you going.
