How to Self-QA your WalkMe content

1. Assessing the battlefield

• The first thing that you should do, even before building, is make sure you understand both the process and the site. Navigate to different pages, click on dropdowns, refresh the page mid-process, etc. What will happen if users do X while Y is happening? Are there shortcuts? Are there site issues that we need to build content to address? Will this process be different for some users? These are questions that you should continue asking yourself throughout the building process. 

2. Play Mode

• After you've built your skeleton and after you've added your logic you will need to run through the content from start to finish in play mode. The most important thing to remember about testing your content is to be as realistic as possible. Is this how a brand new user would do this? Can we expect that they'll know enough to do this correctly? What happens if they don't fill out that field? Make sure your content is thorough enough to act as guide but brief enough that users will continue to engage with it. Make sure the triggers and startpoints create an intuitive experience, we want our WalkMe content to make processes quicker and easier for our users. As you're playing the content, be sure to look out for design issues (z-index, scrolling, LTE, etc). 

3. Preview Mode

• Preview mode allows you to see the full experience of your WalkMe content (you can click here to learn more). This will be the first time you engage with your content as a user would. You'll be able to select content from the menu and spot any design/functionality issues. This part of the process is crucial for any holistic build (a build that includes more than just SWTs). If you have any aspect of engagement logic in your implementation (Launchers/ Smarttips/ Shoutouts/ Autoplay/ etc) this is the only way to assure that your functionality/display rules are set up correctly and will deliver a good experience.

4. Get a second opinion

• This article is about self-QA but the most important part of self-QA is recognizing that you will not be able to find everything by yourself. As a builder you will always be looking for specific problems but your users may think about the process differently. You need a second pair of eyes, someone unfamiliar with the process, to mimic the user's experience and find issues that that escape you.

I hope this helps! Feel free to let me know any questions you have about WalkMe in the comments.