Sequencing tasks together using guides
Hello,
We are focused on using Pendo as a training tool to help a user understand how to complete tasks within our application. Having used simulation tools in the past for this purpose, it was much easier as the simulations were essentially interactive movies :). They didn't do anything in the actual application. Since Pendo guides work in a 'live' application, we need to think differently.
Generically speaking a typical learning task would be to "Build a document" using these steps:
- Go to 'this directory'
- Create a folder in the directory
- Create a new document in the folder
- Add some Structure to your document
- Add some Media to your document
Initially, we thought of using different guides(1 for each step) and sequencing them together in a checklist. Since the outcome of each step is the creation of a 'real object' in our application, how would we help the user start the 'next step'. For example, how would the guide for step 3 know that the user created a new document and that the new document is the starting point for step 4.?
It is perfectly logical that I am overthinking this, but I also believe this training context can't be unique and the Pendo community has already solved this 10x over :).
We could create larger multi-step guides, but we also want to build guides at a size that bodes well for re-use.
0
Comments
Hey Jim!
We have a lot of examples of possible guides you can create in Pendo on this page. I think the 'Walk-through' might be what you're looking for.
It would just be a single guide with multiple steps and you would add the "Advance on Element Click" behavior for your guides so that when they complete a step it moves onto the next guide step. (This is all assuming that clicking on these buttons like, "Create a Folder" is a good enough indicator of a user creating a 'real object').
Thanks Angus,
The problem with the general "Advance on Element Click" is that the next step(in our case) is arbitrary. We are asking the user to pick their document from a list. So user A will have a different target than User B.
We think we have solved this using a code block that allows us to set the target for this step to 'any document' on the page. In this way, the user opens their document and that action triggers the next step.
Pendo flexibility in action!
Hi Jim Waschbusch could you please share the code block to enable this as I am also trying to achieve something similar.
Please sign in to leave a comment.