Building WalkMe can be like solving a puzzle. But it’s the most rewarding thing. Example from this week:
Building out some WalkMe content this week for a client on an HCM system.
Typical HCM stuff - Personal info, vacation, timecards, approvals, etc.
And this system is top 10 on G2, so what’s the problem?
Well, menus are not really intuitive, some gaps from the IT implementation, etc etc. No one is a fan.
Then we always have company-specific guidance around the way we want the system to be used that is not on-screen.
Plus we have a vendor-provided toggle for an “Old UI” or a “New UI”.
And here’s where the puzzle comes in.
If I build to new, WalkMe breaks if you’re in the old. And vice-versa.
Am I building two versions of user help for old and new? Don’t want to do that.
Is there something in the main portion of the screen I can rely on to designate old vs new? Not really...
Aah wait, there is! We can read the toggle (via jQuery, not on-screen element).
But this element is hidden in a sidebar..
Sometimes it takes a bit to figure out the “Design Pattern” if you will for a particular app. This is like wrestling the app to the ground.
Then the WalkMe building can come quickly.
Here’s what I ended up doing:
1. Autoplaying flow to expand the sidebar.
2. Read the state of the toggle via jQuery.
3. Split logic to set WalkMe Data for old vs. new.
4. Segment Walkthru content based on whether a user was in Old UI vs. New UI
Then some Walkthru content ended up being unique to Old vs. New UI like the sidebar navigation steps. But others worked regardless.
Starting a single Walkthru will just branch "Are we in Old or New?" and then do the right steps.
Getting this going took a few hours. But that was OK because I schedule client work in whole day increments in order to avoid cost of attention switching.
At the end of the day we have a handful of automated flows that work in both old in new UI. Accessible by our new WalkMe Action Bar.
And to top it off? We’re going to be able to put these items direct in WalkMe WorkStation (err, Desktop) so they’re accessible from a single enterprises search.
WalkMe is not something that you just plug in and turn it on. Sometimes it takes a bit to make WalkMe really jive with the underlying app and your business process.
But getting this sorted is one of the most rewarding things..
Building out some WalkMe content this week for a client on an HCM system.
Typical HCM stuff - Personal info, vacation, timecards, approvals, etc.
And this system is top 10 on G2, so what’s the problem?
Well, menus are not really intuitive, some gaps from the IT implementation, etc etc. No one is a fan.
Then we always have company-specific guidance around the way we want the system to be used that is not on-screen.
Plus we have a vendor-provided toggle for an “Old UI” or a “New UI”.
And here’s where the puzzle comes in.
If I build to new, WalkMe breaks if you’re in the old. And vice-versa.
Am I building two versions of user help for old and new? Don’t want to do that.
Is there something in the main portion of the screen I can rely on to designate old vs new? Not really...
Aah wait, there is! We can read the toggle (via jQuery, not on-screen element).
But this element is hidden in a sidebar..
Sometimes it takes a bit to figure out the “Design Pattern” if you will for a particular app. This is like wrestling the app to the ground.
Then the WalkMe building can come quickly.
Here’s what I ended up doing:
1. Autoplaying flow to expand the sidebar.
2. Read the state of the toggle via jQuery.
3. Split logic to set WalkMe Data for old vs. new.
4. Segment Walkthru content based on whether a user was in Old UI vs. New UI
Then some Walkthru content ended up being unique to Old vs. New UI like the sidebar navigation steps. But others worked regardless.
Starting a single Walkthru will just branch "Are we in Old or New?" and then do the right steps.
Getting this going took a few hours. But that was OK because I schedule client work in whole day increments in order to avoid cost of attention switching.
At the end of the day we have a handful of automated flows that work in both old in new UI. Accessible by our new WalkMe Action Bar.
And to top it off? We’re going to be able to put these items direct in WalkMe WorkStation (err, Desktop) so they’re accessible from a single enterprises search.
WalkMe is not something that you just plug in and turn it on. Sometimes it takes a bit to make WalkMe really jive with the underlying app and your business process.
But getting this sorted is one of the most rewarding things..