Personas & Scenario Mapping This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License It was originally created by Apps for Good ( ) as S14 - Personas Slideshow & S15 - Scenario Mapping Slideshow. Modified here for Garfield HS’s Summer Apps Course, Summer

Objectives: Perfect your Personas creating typical user profiles with their specific Characteristics & Key goals for your App. Build Scenario Maps to assemble the Steps in using your App and gather Ideas and Questions to include.

Items Created so far: Problem Statement ◦ A clear, concise statement describing the problem your app will solve ◦ Brief, no more than two sentences Market Research ◦ Outline the key insights from your research ◦ Include alternatives are already out there (competing apps, non-app solutions) and research from users on why these alternatives are not good enough in addressing the problem ◦ Each insight should include: an assumption statement, research method, insight statement and corresponding data Personas – what are these? Note: Please add your Team Name at the top of all your documents

Personas

Goal of Personas A detailed summary of your main target user groups. How many are there? Niche audience or mass market? What are their key characteristics (age, lifestyle etc)? Create Personas to represent the variety of users. Include: ◦ Their Characteristics ◦ Key Goals in using the App ◦ Create a Label for them (i.e. “Student”) and give them a name for them! (makes it more fun)

Which of these samples are identifying user Characteristics? “The persons that will use our app will be the people who cannot locate…” “The audience we are targeting are boys between the ages of because guys are known to like…” “Our App is targeted towards anybody that has access to a credit card.” “This app is aimed towards adults, teen moms, single parents because adults always have stuff to do and they need time for themselves, they work and need a… ”

Examples Example Persona’s from Apps for Good winning project “Soundproof” Rachel Smith “College Student” o Aged 20 & is at college o Lives in Edinburgh o Into music o Enjoys live music o Likes social media Key goals- o Keep up to date with new music o Wants to know tour dates o Wants to be able to access all information the one place

Multiple Personas Jordan Bailey “Teen Student” o Aged 14 and goes to secondary school. o Lives in Glasgow with his parents. o Leads a life of going out with friends and school. o Is into music. o He likes social media. o Enjoys live music Key goals- o Keep up to date with music news. o Wants to know when tickets for concerts and gigs go on sale. o Doesn’t want to have to log onto several different websites to get information. o Wants all information in one place. Why? Now you can refer to Rachel & Jordan when you are thinking through your App’s design as if they are real people.

Another Good Example Persona

Perfect your Personas Create a few personas representing the likely users of your App – give them titles & actual names. Include them as your target users in your further design & development For each Persona users make sure your design meets their Key goals of the App Reminder: Please add your Team Name at the top of all your documents

Scenario Maps Scenario mapping helps a designer to describe very simply how the app will work. Select one of your Personas to start with Items on the Map: ◦ Steps – interactions a user must do to accomplish their goal (post along top) ◦ Questions – write them down, you can answer them later (don’t get bogged down, keep going) ◦ Ideas & Comments – details of the steps to include in your design (gather them all) Record each Item on a Post-It on a board…

Source: Uxforthemasses.com

From the diary page the user can input daily feelings and notes that they can look back on. They can also rate each day out of 10. The user will select the app form the screen. Here the user can select a page from 3 options. These are: Diary, Goals, and Tips. From the Goals page users can input a goal and when this is achieved it can be turned into some visual prompt – graph. Also they can view finished goals From the Tips page the user can receive a tip daily. Will our product name be memorable enough for people to find the app and download it? This will then be turned into a line graph that would give you tips on how to improve if you get a low score Within each of these pages there may be other pages. For example on the goals page we will have an achievement log with achieved goal and on-going goals This will most likely be a picture of our logo. It would make you enter something you have done to make you feel proud. We can have another aspect of this page that makes people want to come back. When you have reached a certain amount you could get a reward of some sort These could be picture buttons or buttons with text It could play a clip of a song every time you enter something. If you get a high score it will congratulate you. Maybe we could work with companies to get discounts or special offers for users. StepIdeaComment Question Key

Preview – what we do with our Scenario Maps… Build our Site Map

Let’s get Started Create a scenario map showing what should happen in the solution you have decided upon Get a Poster Board and some Post-It’s Write your Team/App Name at the top Start with Steps for your App (for a Persona) Add your Questions & Ideas as you go along Include a key at the bottom

Any Questions? Today’s Objectives: Perfect your Personas creating typical user profiles with their specific Characteristics & Key goals for your App. Build Scenario Maps to assemble the Steps in using your App and gather Ideas and Questions to include.