Mistake #2: Organizational Setup – Not Understanding Broader Context

Issues with WalkMe generally fall into two broad categories:  Technical and Organizational.  Or rather, Software and People.

One of the most common organizational-related issues I see WalkMe builders encounter is not understanding the broader organizational context.

Who originally brought WalkMe into your organization?

Who all was involved in the review?

How is WalkMe licensed?  Individual app, departmental DAP, Unlimited Enterprise License Agreement (ELA)?

When does your WalkMe license renew?

Who makes that decision?

When do the budget decisions get discussed?

Whose budget in your organization does it come out of?

When was the last time you presented to the executive champion?

What did they have in mind when first bringing in WalkMe?

Do they think WalkMe is delivering on the value or not yet?

Here’s the process I recommend:

If you are a new WalkMe builder, do not put on blinders and just build content.

• Start doing some digging and assembling your own answers to these questions.
• Ask your boss, ask your peers, ask IT.
• These are a critical piece of the foundation to your program.
• We must establish where it came from, who approved it, who pays for it.  Who are your allies and detractors?

When this is sorted, we can craft a way forward.  If it’s unknown, we may be in jeopardy.

Next Steps:

I hope you found this helpful.

Do you currently see any of these in your organization?

Or does this make you think of anything you need to check on?

Any corrective actions to put in place?

Let’s talk about what’s going on and try to find the best way to address it:

Schedule your free WalkMe help session here.