How Do We Get Started? Keep it Simple!

When folks ask how they get started with WalkMe, there are two different topics to distinguish:

1. How do we pick the very first IT system within our organization?

This is usually less of a concern.?Most of the time people come to Digital Adoption with a system in mind.?It could be you have strong / forward-thinking subject matter experts.?Or a new system you’re going to roll-out.?Or a system you have rolled out but have a lot of problems with.??

2. We’ve picked an IT system, how do we bundle / package / scope the first solutions?

This issue takes a bit more discussion and how you handle it depends on your answer to the first question.

If you’re building WalkMe in parallel with a new system launch, here are a few things to consider.??

1. How will you know what WalkMe content should be built in the new system??Do you have an older or existing system / processes to reference??If so, you’ll want to emphasize the before and after effects of each process change.??
2. Do you know where users will struggle in the new system??If possible, consider setting up Tracked Events / Funnels during your early UAT so you have some data around this.
3. Are you implementing the new system in phases??If so your WalkMe content can be built in phases as well.
4. Are the two systems going to run in parallel for any length of time as you transition??Depending on how old the incumbent system is, you may be able to build WalkMe within it to communicate or shuttle to the new system.

On the other hand, let’s say we’re not building to address a system migration but rather to alleviate issues with a current application.

1. Do you have vocal stakeholders in the organization?
2. Do you have a rank-ordered list of tickets / incidents / ideas associated with the site?
3. What if you just have a lot of complaints and still don’t know where to begin to build your first piece of content.

You may have certain detail-oriented team members who want to apply a categorization framework like Agile WSJF.?Everything should have an explicit criterion, how many people will benefit, how bad is the current pain, how difficult or involved is the WalkMe implementation, etc.

This sort of methodology is more appropriate where you have a more mature implementation, and you have a ton of different requests from users across the organization.

But I don’t recommend doing this before you even get any WalkMe content out there.?There is the real potential of analysis paralysis.

Just Pick Something

Your team could be overwhelmed at the thought of learning WalkMe, incorporating work and routines into their schedule, etc.

If we’re talking about the very first WalkMe deployment, very first system, very first problem to address…? A valid option is to just pick something!

Pick a single set of SmartTips for a single page.? Build it, QA it and Deploy it in one afternoon.

Don’t make perfection the enemy of progress.? This is not rocket science.? This approach lets your team get over the hurdle of their first WalkMe deployment.

If you have strong internal UI design teams who need to be involved, that’s a different story.? But in general, don’t put in pomp and circumstance where you don’t need it.? And don’t seek everyone’s permission before you make things incrementally better.

I hope this helps.? If you’d like to get in touch, here are three ways:

• Call or text me: 203-915-5267
• Send me an email: [email protected]
• Or just pick a time that works for you: https://calendly.com/jmayhugh-consulting/30min

#WalkMe #DigitalAdoption