The design of your app provides the foundation for working out the Aha! moments. You designed an app for sharing images, so you know your users need to know how to upload and edit images, connect with their friends, and share their work. How many types of workflow are there? Do you need an onboarding process which can target different users with different use-cases?.Which parts of the workflow in your design are necessary to your user's success? That is, which parts will cause a user to fail if they get stuck?.What did you build it to do for your users?.You made an app for analyzing data, so you know people need to know how to get their data in, how to set it up, how to do analysis, and how to share their results. You probably already know all this stuff. The important part is to make sure you that can reveal the intended workflow elements to your users. This is a great place to start designing your onboarding journey. When I first started training customers on how to use our desktop data analysis product, Q, I was not prepared for the kind of reactions I would get. I already knew people were getting great benefit from using Q through my interactions with them in customer support. However, until I stood in a room full of researchers and started taking them through things step-by-step, I never glimpsed the light that went on when people really "got it". Perhaps most surprisingly, some of the Aha! moments were coming from really simple things. These were things I took for granted as a daily user of the software.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |