| 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 opened. Very rare someone opens the PDF reader because they're just having a look around to see if there are any interesting new features. If someone opens my virtual whiteboard product, 95% chance they're in some sort of sprint review meeting and they want to write some virtual post-it notes right now. A tour isn't what they need. If someone opens the ticket management product, or the expense report filing product, or the music playing product... you get the picture. |
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 the "checklist" and "load sample data" approach better.
This is primary reason perhaps why my apps are growing fast.