Here's something I'm going to tell you that no one else will.  WalkMe needs more technical precision than traditional L&D software.

This has happened to me a few times. 

Company buys WalkMe, starts to get it going. Looks around at their staff to see who could be a WalkMe builder.

Finds someone who has been doing L&D for the last 20 years, has them try to build WalkMe, person struggles to adapt.

Hey, this is just another "training" tool, right?

Not knocking Articulate or any of the tools out there.

It's one thing to make a video with animated cartoons characters saying "Hey, here's how this process works".

When you're creating a course or an explainer video, it's entirely self-contained.

It needs to be correct, to flow, to look good, etc.

But it's something else entirely to break that down into appropriate pieces and use WalkMe to overlay it on your app.

This requires a detailed understanding of the process at the individual field-level and an integration with the underlying application.

1. Do we really know where the friction is in this process? This guides what we even build to address.

2. What downstream risk of inappropriate data entry? This gets to how assertive the DAP content is going to be.

3/ Who needs to see this? Segmentation. 

Wait, what segmentation options are even available? IPD, Variable, etc? OK, you'll need a test user account who has those same permissions. 

Or wait, do we even need to segment if the permissions in the underlying app handle that for us?

4. On what pages? Display conditions. Wait, it's in an iframe. We can still do this...

5. Do we have one monolithic process or components? Connect-to Walk-thrus.

6. How do we announce this new DAP content? ShoutOuts.

7. How do we measure success? Engaged Elements vs. Tracked Events. 

Wait, what analytics level is the customer using? Or is there a "Goal" for the Walk-thru? Or some downstream metric from the app or process we're ultimately trying to influence? 

8. How do we allow for re-engagement halfway through the process if a user drops out?

ETC and so on.

This is why our traditional L&D person may be tempted to throw some screenshots in a PPT and call it a day.

But like a lot of things in life, you get out what you put in.

And if you want to get the value that WalkMe brings, it's important to keep in mind that building WalkMe well requires more technical precision than traditional L&D software.

What do you think, am I off base here?