Onboarding

Monday, February 11, 2019
3:30-5:00
Hawes 203

Guest: Jeremy Kriegel

Assignment

By 10:00am Monday Feb 11, share a link to the first draft of your application’s onboarding process and test plan in the Assignment Master for this session (Feb 11 - Onboarding). This is typically a google doc or slide presentation that outlines the key path for onboarding a new user. As you have done for key path scenarios, narrate the process that a first time user will follow to start using your product and include screenshots (scans or photos of paper wireframes are ok). Include a short script of the task you'll assign your test subject. If the onboarding process is already up and running on your app/site, please be sure to provide download instructions and any user names/passwords (if applicable) that we'll need to try it out.

Required Reading

  1. Onboarding New Users is Harder Than You Think by Nate Munger

  2. UserOnboard.com teardowns by Samuel Hulick. Focus on a few teardowns that address issues pertinent to your app.

  3. Seven Onboarding Mistakes You Don't Want to Make by Bayram Annakov

Session Prep

We will use the first hour of the session for an onboarding test workshop. The final 30 minutes will be critiques of two projects to be selected by Prof. Austin by this Friday, Feb 8 at 5pm.

  • Your team should be prepared to conduct, during class, a test of your app's onboarding experience, with classmates as test subjects.

  • Depending on your app's development status, you can conduct the test using working software, an interactive prototype built with Invision, Proto.io etc., or paper prototypes.

  • Whatever medium you use, structure your test for a new user who has never before experienced your app. Assume that the new user will navigate to your app through whatever marketing channel you think is likely to be your dominant one for customer acquisition (e.g., searching the iOS App Store; clicking on a Google AdWords ad; etc.). Give your test subject a single, specific task to complete that is representative of what a typical first-time user would do with your app.

  • If you want a refresher on how to structure and conduct a usability test, refer to the readings and assignment from our October 29, 2018 session (Students who didn't take PM101, please take note!)

  • Plan to spend 10 minutes in total on your test, with no more than half the time observing the test subject(s) complete the assigned task and the balance debriefing and getting feedback. We will do two tests for each team, rotating testers for the second test.

  • Each team will volunteer a team member to another team as a tester.

  • Please bring your laptop, along with whatever materials you'll need to administer your test. If you are testing software that can be run in a browser, you should plan to provide a link to your test subjects so they can use their own computers.

Mobile app teams: it is assumed you do not have an app ready for download yet (including via TestFlight, therefore this will be a low-fi test. Please contact Julia if otherwise. If testing an online interactive prototype on a mobile device, be prepared with a link to share with testers so they can use their own mobile device.

Julia Austin, Senior Lecturer

Harvard Business School

Rock Center 115