Creating an Effective Smart Walk-Thru

Objective

After completing this lesson, you will be able to create an effective Smart Walk-Thru.

Smart Walk-Thru Best Practices

Building with WalkMe Best Practice

When we first start out building Smart Walk-Thrus, we may be inclined to point out every input field or element of a website. However, building more steps in our Smart Walk-Thrus to address every possible path and roadblock isn't necessarily a good thing.

In general, it is a WalkMe best practice to have our Smart Walk-Thrus consist of 10 visible steps that users interact with or fewer. This does not include Flow Steps since users do not see them. Why? We've found that users are more likely to exit out of longer Smart Walk-Thru flows. Think about it - who wants to finish a process that appears to have no end in sight?

How to Simplify WalkMe Implementations

If keeping Smart Walk-Thrus shorter sounds like a challenge, no fear! We have several best practices to keep in mind to accomplish this.

Consolidate Steps when Necessary

If a Smart Walk-Thru guides a user through completing a form on a site, we don't need to build a step for each and every input field they need to fill out.

Instead, make one step that instructs the user to fill out all the required fields before clicking Save or Submit.

Watch the video to know more. Note that the video doesn't support audio.

Use Automation Steps

Instead of instructing a user to click a button or fill in a field, why not have the Smart Walk-Thru do it for them instead?

Auto-Steps are a great way to increase efficiency by reducing redundant actions within processes. Some of the various automation steps we've learned so far include:

  • Auto Click Elements

  • Auto Fill Text

The figure shows the use of Automation Steps.

The image shows the use of Automation Steps.

Replace Steps with SmartTips

If you have a step within a Smart Walk-Thru that is more information-driven rather than action-oriented, consider removing that step and replacing it with a SmartTip instead.

Remember, SmartTips are there regardless of whether Smart Walk-Thrus is being played or not. They are there permanently and can assist ALL user personas (novice, veteran, etc). Having the information exist as a SmartTip instead will ensure that our end users can easily access the helpful tip.

The figure shows the use of SmartTips.

The image shows the use of SmartTips.

Use Linear Flows

While it's thoughtful to take into account every possible scenario that our users might go through to complete a process, we highly recommend streamlining Smart Walk-Thru flows so users are being guided through the preferred way to complete the process. This means limiting the number of paths a user can take by eliminating excessive Split steps.

The reason why we highly recommend building linear flows is to make it easier to maintain Smart Walk-Thrus in the long run. If you were to make a Smart Walk-Thru with multiple paths and Split steps within Split steps, it would be harder to test the process and fix every issue.

The figure shows the use of Linear Flows.

The image shows the use of Linear Flows.

Microcopy Best Practices

Microcopy is the words, sentences, phrases, and punctuation in your WalkMe content. These can have a big impact on the way users engage with our content!

  • Aim for no more than 12 words per sentence.
  • Try removing words as much as possible, without the message losing its meaning.
  • Avoid nominalization (verbs turned into nouns - "completion," "decision," "interference").
  • Avoid words that are too technical or complex.

The figure shows the Microcopy best practices.

The image shows the Microcopy best practices.

Great job! Now that we understand some best practices, let's check out a few ongoing resources and then put this all together with a build activity.

Hands-on Practice: Enhance the Request a Signature for Documentation Process

Disclaimer

Instructions

In this section, we will give you a scenario for the fictional organization KLAW. Watch the discovery call video to understand the business challenge they would like to address. Then using what you've learnt in this course, build a solution using your own Editor.

KLAW Login Credentials

URL: https://klawsign.com/app/

Username: training@walkme.com

Password: WalkMe123!

Be sure to write this login information down somewhere! Do not reset the password for this account.

Below is a guide on how to navigate to the relevant fields and more specifics on what the KLAW team wants in their Smart Walk-Thru.

Introduction

The KLAW team has tested your Smart Walk-Thru, and they are pretty happy with the current state. But they have some additional needs with this process.

Let's review the asks from the KLAW team.

Step 1: Requesting a Signature for Documentation

Watch the video to understand the process of requesting a signature for documentation.

Here are the list of asks that they would like added to the Smart Walk-Thru:

  • We find that users may not have a template to request a signature for, so we'd like to give them the option to add a document.

  • However, if the user clicks Request Sign, we'd like a template to auto-populate in the Message field with the following text:

    "You have requested a signature for this document.

    Please sign the attached document. You will be taken to a portal called Klaw E-Sign in order to complete."

Summary

Take your time to think through each of the KLAW asks.

Be sure to test and play your Smart Walk-Thru to get a sense of what the user experience might be like.

Answer Guide

This answer guide will go over the enhancement requests to the Requesting a Signature for Documentation process.

Step 1: Requesting a Signature For Documentation

Watch the video to understand the process of requesting a signature for documentation.

Summary

Flow Steps help redefine the user experience within the Smart Walk-Thru and can often lead to higher engagement!

Always take the time to review the user experience of your Smart Walk-Thrus to find areas for improvement.

Summary

Smart Walk-Thrus Flow Steps
  • Splits are a kind of Flow Step in Smart Walk-Thrus that allow us to build variations in your guidance.Splits can be built with any of the available Rule Types in the Condition Builder. A common Rule Type for creating Splits is Element On-Screen.
  • A Wait For Condition is a Flow Step that will cause the Smart Walk-Thrus to wait for a certain amount of time or until a certain condition is met before continuing. It's recommended to use URL and Element On-Screen rules for a Wait For Condition.
  • With Auto-Steps, automating multiple steps or an entire process is fast and easy to do. We can add Auto-Steps anywhere in a Smart Walk-Thrus. Auto-Steps complete actions on behalf of the user, like clicking on a link or button, typing into a field, or hovering over a menu.

Related Resources

Splits: Getting Started Guide

Deviate from the main path using Splits.

View Article

Wait For Conditions: Getting Started Guide

Pause WalkMe with Wait For Conditions

View Article

Auto-Steps: Getting Started Guide

Create Efficiency with Auto-Steps.

View Article

Smart Walk-Thru Best Practices

Use this helpful guide to build the best possible Smart Walk-Thru.

View Article

Log in to track your progress & complete quizzes