ΕΠΛ 435: Αλληλεπίδραση Ανθρώπου Υπολογιστή. Personas, Σενάρια κ.α. Personas. Personas are a tool that Alan Cooper developed based on an old market research technique. To be better able to sell to people, advertisers would take their demographics and try to invent an archetypal human from it.
You can design interaction without personas. Plenty of designers do. But the capability to target a specific person makes your design more effective, and being able to prioritize features makes design faster.
Why give that up?
The data might include the following information:
Did you extrapolate any specific goals? Find any interesting facts about your users?
Specific: Each piece of information should be as precise as possible. Throw out information like, “Users like it to be easy,” and keep information like, “Users need to be able to complete a process in half an hour.”
Relevant: Relevant to your product, not to every site on the Web. Don’t report, “Users like free stuff,” but include, “Many users request free evaluation periods for software to know if paying will be worth it.”
Universal: Find things that are true for the entire site, not for a single item on a single page. Weed out things like, “Users couldn’t find the Submit button on the checkout page,” but leave in, “We have a type of user who knows what he wants already and needs a way to speed through finding and buying.”
2.Hold a work session with stakeholders and the development team to brainstorm personas.
Woman + 25-35 + East Coast, USA = 26-year-old woman from Washington, D.C.
3. Prioritize and cull personas; develop primary and supporting personas.
4. Make the personas into real people.
Sarah Carlson/ 26/ female/ married/ Washington, D.C.
“The Thomson family enjoy outdoor activities and want to try their hand at sailing this year. There are four family members: Sky (10 years old), Eamonn (15 years old), Claire (35), and Will (40). One evening after dinner they decide to start exploring the possibilities. They all gather around the travel organizer and enter their initial set of requirements – a sailing trip for four novices in the Mediterranean. The console is designed so that all members of the family can interact easily and comfortably with it. The system’s initial suggestion is a flotilla, where several crews (with various levels of experience) sail together on separate boats. Sky and Eamonn aren’t very happy at the idea of going on vacation with a group of other people, even though the Thomsons would have their own boat. The travel organizer shows them descriptions of flotillas from other children their ages and they are all very positive, so eventually, everyone agrees to explore flotilla opportunities. Will confirms this recommendation and asks for detailed options. As it’s getting late, he asks for the details to be printed so everyone can consider them tomorrow. The travel organizer prints out a summary of the different options available.”
1. The system displays options for investigating visa and vaccination requirements.
2. The user chooses the option to find out about visa requirements.
3. The system prompts user for the name of the destination country.
4. The user enters the country’s name.
5. The system checks that the country is valid.
6. The system prompts the user for her nationality.
7. The user enters her nationality.
8. The system checks the visa requirements of the entered country for a passport holder of her nationality.
9. The system displays the visa requirements.
10. The system displays the option to print out the visa requirements.
11. The user chooses to print the requirements.
Some alternative courses:
6. If the country name is invalid:
6.1 The system displays an error message.
6.2 The system returns to step 3.
8. If the nationality is invalid:
8.1 The system displays an error message.
8.2 The system returns to step 6.
9. If no information about visa requirements is found:
9.1 The system displays a suitable message.
9.2 The system returns to step 1.
USER INTENTION SYSTEM RESPONSIBILITYfind visa requirements request destination and nationalitysupply required information obtain appropriate visa infoobtain copy of visa info offer info in different formatschoose suitable format provide info in chosen format
you can also use scenarios to evaluate how well it meets your user needs
Pick a persona and role-play them through the system
Try to imagine what their experience will be
Although this isn’t as effective as usability testing, it can reveal flaws in the system while there’s still time to change the design.
A scenario can be used as a communication tool
A scenario can communicate the way a design will work
how a user will move through and interact with a system
because it uses a story format, you don’t become bogged down in the design details.
enables other members of the product team to understand how the Web site will work
Keep to the ideal experience:Your boss might insist that users sign in before using the system. It’s better to ignore constraints like this in the first version of the scenario. You can always go back and change the scenario to reflect business and technological constraints, but if you don’t aim for the ideal user experience, you don’t have any chance of achieving it. You can always scale back to reality, but once you’re there, it’s almost impossible to imagine something ideal.
Don’t talk about interface decisions: Save the decisions like how many pages it will be or whether you’ll use buttons or links for later. Answer those questions when you’re designing. You want to focus on how the persona moves through the system. It’s tough. It’s so easy to say, “On the next page,” or, “He clicks a link,” but if you can avoid this, do so. It keeps your mind open to new design possibilities.
Don’t get caught up in minutiae:If you get stuck, just keep telling the story. Keep it vague. It’s tempting to start answering little questions like, “How do they access movies they viewed in the past?” but just keep moving forward, staying with the intent, of the user in that particular scenario. You can always leave “bookmarks”—little notes to yoruself—to return to side-stories later.
Keep with your persona:Use the persona’s name as often as possible (at least once a paragraph). Remember, you’re telling the story of how the persona experiences the site, not how the site handles users. Write what you suspect the persona would say and do, not what your boss would say or what you wish the persona would do.
Sitepath diagramming is a sketching system in which you try to determine who the users of the site will be and what sorts of activities they’ll try to accomplish.
This allows you to decide what you need to design and determine what designs will be most crucial to the success of the Web site.
It is especially good for determining site flow, early interaction design, and workflow.
They’re also really good at showing similar processes you can design for one type of user and reuse for all of them.
It reveals places where your personas can use the same interface. In the end, this means you can design and develop fewer features while retaining the same great experience.
You can create sitepath diagrams by yourself, but they’re definitely fun with a group.
Now start thinking about your scenarios. If you’ve formally documented scenarios, you can return to those. If you haven’t, you can make them up as you go along.
An introduction to personas and how to create them
How To Create User Personas for Your Website