It's pretty simple to understand - when a user opens a tool, it's because they want to do the thing that tool does, now. If someone opens my videoconferencing product 98% of the time it's they've got a scheduled call to join within the next 20 seconds . They're not going to be late for their meeting so they can read my release notes. If someone opens my PDF viewer, 99.9% chance they want to view the PDF they just ope…
New users are probably the only ones who really need guided product tours. If I'm a longtime existing user I'm far less likely to be interested in a guided tour.
Why most product tours get skipped
71–80 of 185 posts
Re: Why most product tours get skipped
#72Earlier quoted context omitted.
That works if you know the feature exists.
The best software help used to have a complete list of all features, with comprehensive explanations of all of them.
The other side though is sometimes even more important it's what this thing does as a high-level introduction so you can understand all the things you're supposed to be able to do depending on the software this is some sometimes not obvious and that explanation can be really helpful to understand all the things you're supposed to be able to do and thus plan to use all those features.
Re: Why most product tours get skipped
#73In some countries engineers wear a ring on their pinky to remind them of their obligation to ethics, safety and humility in engineering practice. In the US engineers don't get that ring and they implement product tours.
Re: Why most product tours get skipped
#74It's a writing reviewer app, and the landing page is the product. It's literally a document with a critique. You can write in it, use the editor, even delete the whole page.
I always skip tours, but I think this kind of thing (if your product can support it) is much better. Then again, this isn't so much a "you've logged in, now let us teach you how to use this product" as a "welcome, here's what this product does".
Re: Why most product tours get skipped
#75Re: Why most product tours get skipped
#76In some countries engineers wear a ring on their pinky to remind them of their obligation to ethics, safety and humility in engineering practice. In the US engineers don't get that ring and they implement product tours.
(FWIW, I'm not aware of any country where it's common for software folks to wear one)
Re: Why most product tours get skipped
#77It's pretty simple to understand - when a user opens a tool, it's because they want to do the thing that tool does, now. If someone opens my videoconferencing product 98% of the time it's they've got a scheduled call to join within the next 20 seconds . They're not going to be late for their meeting so they can read my release notes. If someone opens my PDF viewer, 99.9% chance they want to view the PDF they just ope…
I've never liked those "focus hijacking guided tours" and never really followed through any such onboarding process. But they are so common, i don't know who designs them and makes me feel like 5yo. You gotta understand, people will use the product you made, in a way that makes sense to them, not according to your devised "one way". And that's fine because it allows user to own his workflow using your product. I like…
Re: Why most product tours get skipped
#78Re: Why most product tours get skipped
#79Sorry but in many startup cases it's by design. See: got a KPI increase (email is collected), but as the user left there's no AWS resource usage! Profit!