Your SlideShare is downloading. ×
Power to the People!
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Power to the People!


Published on

Extracts from a workshop at GOVIS 2007 ( …

Extracts from a workshop at GOVIS 2007 (

This one-day intensive workshop taught attendees how to incorporate user goals and agency needs into the web design process.

Workshop presenters: Zef Fugaz, Bob Medcalf, Elyssa Timmer

Feedback from the workshop attendees:

Published in: Technology, Design

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide
  • Transcript

    • 2. Agenda
      • 10:00AM MORNING TEA (30min)
      • 12:30PM LUNCH (60min)
      • 3:30PM AFTERNOON TEA (30min)
      • 4:00PM THE PANEL
      • 5:00PM ENDS
    • 3.
      • CONSUMER MARKET RESEARCH Making an Emotional Connection with your Audience
      • Elyssa Timmer
    • 4.
      • PERSONAS
      • Zef Fugaz
    • 5. Why do personas?
    • 6. In this session
      • Who are your users?
      • Where do they fit into the UCD process?
      • How to create a persona
      • How to utilise the persona(s) you’ve created
    • 7. Exercise
      • “ Our site needs to cater for EVERY New Zealander”
      • Using the identikit create your own ‘typical New Zealander’
    • 8. Personas in the UCD Process User Research & Task Analysis Information Architecture & Interaction Design Prototyping Usability Testing Visual Design Build Test ANALYSIS DESIGN IMPLEMENTATION CONCEPTUAL MODEL
    • 9. The ‘POV Persona’ who they are what they do contextual needs site features usage environ-ment attributes & general needs
    • 10.
      • Identify the users
      • Profile the users
      • Understand their behaviours
      • Describe common usage scenarios
      • Discuss their needs
      • Identify features to support scenarios and needs
      • Role-play each persona during design, development and testing
      The ‘POV Persona’
    • 11. POV Personas in 4 Stages Explore (Who Are Your Users?) Research People Model Your Persona(s) Utilise Your Persona(s) 1 2 3 4
    • 12. STEP 1: Explore
    • 13. So, who are they?
      • Who has direct contact with your users?
      • Talk to them!
      • Emails
      • Feedback, complaints, questions
      • Web usage statistics
      • Most popular content, repeat visitors, location
      • Online questionnaire
      • Limited value on it’s own, but a good starting point!
    • 14. So, who are they?
      • Heading
      • Content
      • “ Researchers”
      • Students
      • Librarians
      • Journalists
      • Academics
    • 15. Personas
    • 16. A hypothesis
      • Jill is an Intranet Content Manager working for Govt and living in Petone.
      • She’s a regular visitor to the Internet, where she buys books and 2 nd -hand goods online, uploads photos to Flickr and reads the news.
      • She likes to read - prefers to print out any articles she finds online.
      • Her work is fast-paced with a lot of meetings - requiring a mixture of people management and technical know-how.
      Background 34-years old Doing a degree in Information Management Experienced Internet user Windows XP, 19” LCD monitor, LAN Network Attributes Fast learner Cautious but early adopter of new technology Never learnt to touch type – mouse dominant Needs Ability to work independently Advice from other content managers To share her experiences and frustrations Goals Ensure uptake of the new intranet Leverage staff off email and into online tools Become a collaboration guru Learn about Information Architecture Jill
    • 17. A persona set
    • 18.
      • YOUR TURN!
    • 19. Activity
      • Create a persona hypothesis for your own site
      • Who are your users?
      • Choose one user-cluster and create a persona hypothesis for this cluster
    • 20. STEP 2: Research
    • 21. Meet your users - observe
    • 22. Meet your users – talk!
    • 23. What to look for...
      • Demographic Profile
      • Gender, Age group, Family situation, Income, Housing, Where living, Occupation, Education, Religion, Race/Ethnicity, Nationality, Language skills
      • Psychographics
      • Social networks , Lifestyle traits, Interests/Hobbies, Media read/watched/listened to
      • [Your Orgs] Relation to Person
      • Relationship (i.e. Employee) , Job title , Time in job , Previous jobs , Percentage of overall users, Importance of person relative to [Your Org]
      • Person’s Relation to [Your Org]
      • Usage rate of [Your Org], Attitude towards [Your Org], Frustrations, Hours of work, Place of work, Work environment, Computer reliance
      Specific Goals/Needs from [Your Site] Reliance on [Your Site], Intensity of use, Emotional goals, Needs, Frustrations, Attitude to [Your Site], Valued Context of use for [Your Site] Users role, People interactions, Surrounding environment, Traceability, Accuracy, Confidentiality, Flexibility, Operational risk, Assistance, Legal, Standards Webographics Type of usage, Connection speed, Browser setup, Operating System, Screen Resolution, Monitor Hardware, Input Devices, Base Computer, Other Devices , Accessibility, Software Workplace Scenarios “ From start-to-finish describe the main tasks you do on [Your Site]” (and get user to show you)
    • 24. STEP 3: Model Persona(s)
    • 25. Personas
    • 26. Mapping user behaviour Uses Occasionally Uses Frequently
    • 27. Audience Activity (Mapping)
      • 5 volunteers who have used Trade Me in last 6 months
      • Place yourself on the polar graph
      North South
    • 28. Audience Activity (Mapping)
      • Freq of use? Every day Several times a month
      • Doing what? Buying stuff Selling stuff
      • If buying? Know what I want Random browsing
      • If selling? One thing at a time Several at a time
      • Usage? Keyboard Mouse clicker
      North South
    • 29. Real Example
    • 30. Personas
    • 31. Scenarios
      • A ‘short story’ from start to finish describing what happens
      • Motivator / trigger for action
      • Steps and activities along the way
      • Outcome / next steps
        • Online Registration
        • Mira does a search in Google for “student jobs Dunedin” and SJS comes up top of the list. She visits to the SJS website and decides she wants to register, (which will then give her the ability to create a personal profile).
        • She selects ‘Register’ and is presented with a number of questions and options. To ensure she has a strong chance of getting a job she is prepared to spend time getting it right.
        • Once the registration/profile is entered and saved, the SJS website presents Mira with instructions to visit or phone a SJS Office. She is also sent an email with the same information.
        • She is asked if he would like to browse the available jobs. If “yes” goto Scenario.03
      SEO register path save option map
    • 32. A persona set
    • 33.
      • YOUR TURN!
    • 34. Activity
      • Describe some common usage scenarios for your persona
      • Identify some website features to support these usage scenarios
    • 35. STEP 4: Utilise Your Persona(s)!
    • 36. POV personas
      • Enacting the users point of view is one technique to better enable user centred design.
      • It is not intended to replace observational usability testing, but it can (and should) work in unison.
      • When to enact your persona(s):
      • Designing Taskflows and Sitemaps
      • Designing Information Architecture
      • Meetings – idea generation, problem solving
      • Usability (Heuristic) Reviews
    • 37. POV personas
    • 38. POV Personas - Task Analysis Use persona POV to model flowcharts showing complex scenarios. E.g. website registration Flow charts can be used to identify core screens for prototype development. Task flows can be used as a collaborative tool to clarify requirements and refine the designs.
    • 39. Task Analysis
    • 40. POV Personas – Task Accomplishment (POV Usability Review)
    • 41. POV Personas – Task Accomplishment (POV Usability Review)
    • 42. POV Personas – Information Architecture
    • 43. POV Personas – Tagging Metadata Element Element Definition Possible Attributes (Default is underlined ) Topic The topic of the content of the resource or keywords related to the resource that might be used by customers when performing a search (e.g. alternative spellings, acronyms). Examples: Administration, Communication, Government, Law, Money, People, Projects, Property, Publications, Research, Risk & Insurance, Safety, Security, Technology, Travel, Other Note: No default – user must make a selection. Transport Mode Identifies the transport type associated with the resource Air, Land, Sea, Rail, Multimodal, All Origin Resources can be identified by the government department concerned Ministry of Transport , Transit New Zealand, Land Transport New Zealand, Maritime Safety Authority, Civil Aviation Authority, Aviation Security Service of New Zealand, New Zealand Police, Ministers Offices, Transport Accident Investigation Commission, Ontrack, Other Govt, Non-Government Ministerial Portfolio Resources can be identified by a ministerial department Minister of Transport , Associate Minister of Transport, Minister for Transport Safety, Other
    • 44. Question| What is this? iPod MP3 Music Shuffle Portable Device Digital Player
    • 45. Question | What is this? Radio Funky Retro Appliance Transistor
    • 46. Question | What is this? Agreement Tenancy Form Document
    • 47. How BIG is your persona? several hours about a week several weeks Interview 5 users Basic personas Brainstorm with user/usage experts Interview 20+ users Advanced personas
    • 48.
      • Bob Medcalf + Zef Fugaz
    • 49. Why do personas?
      • [diagram!]
    • 50. Exercise
      • It’s all in your head...
    • 51. In this session
      • What’s a conceptual model?
      • Where do they fit into the UCD process?
      • Different types of models
      • How to utilise the models you’ve created
    • 52. What’s a Conceptual Model ?
      • Many interpretations!
        • Collaborative ‘conceptual design’ sessions
        • Fresh perspective on challenges
        • Break assumptions about constraints
        • Suggest new design approaches for reaching solutions
        • Learn from each other
    • 53. What’s a Conceptual Model ?
    • 54. What’s a Conceptual Model ?
    • 55. What’s a Conceptual Model ?
    • 56. What’s a Conceptual Model ?
    • 57. Conceptual Models in the UCD Process User Research & Task Analysis Information Architecture & Interaction Design Prototyping Usability Testing Visual Design Build Test ANALYSIS DESIGN IMPLEMENTATION CONCEPTUAL MODEL
    • 58. Conceptual Model | Uber Chart
    • 59. Conceptual Model | Uber Chart
    • 60. Conceptual Model | Mystery Client Size matches for Charlotte Sizes for the family 6 monthly reminders
    • 61. Conceptual Model | Biz
    • 62. Conceptual Model | Biz Scenario Doug has been an independent plumber and gasfitter for the past year following on from his apprenticeship. He’s managed to finally gain enough regular contacts to think about getting a firmer understanding of developing better business principles. Doug wants to hire a part time employee. He visits biz get information on the steps required to employ someone.
    • 63. Conceptual Model | Biz
    • 64. Conceptual Model | Biz
    • 65. Conceptual Model | Biz
    • 66. Conceptual Model | Biz
    • 67. Wireframes| Walk the landscape
    • 68. Paper Prototypes| Imagine...
    • 69. Decorating| Play with the test pots...
    • 70. Conceptual Model | Visual Design
    • 71. Conceptual Model | Visual Design
    • 72. Colours
    • 73. Conceptual Model | Visual Design
    • 74. Imagery
    • 75.
      • YOUR TURN!
    • 76. Activity
      • Create a hand-drawn conceptual model!
      • Refer to your persona and sketch a prototype for:
        • The homepage for your website or intranet.
        • And (if you have time), one other feature (or screen) you’ve identified for your persona.
      • Describe how your design will meet the goals of your persona
    • 77.
      • Bob Medcalf
    • 78. Overview CARS Image taken from Formway’s Life Brochure
    • 79.  
    • 80. User Centred Design Process User Research & Task Analysis Information Architecture & Interaction Design Prototyping Usability Testing Visual Design Build Test ANALYSIS DESIGN IMPLEMENTATION CONCEPTUAL MODEL
    • 81.  
    • 82. Cost Benefits of Early Testing
    • 83. Activity – Quick test of your prototype
      • Take a prototype (not your own) and try to answer these questions:
        • What site is it?
        • Who is it for?
        • What will you find or do on this site?
        • How do you navigate?
        • How do you search?
        • Initial impressions?
    • 84. HEURISTIC REVIEW EXPERT REVIEW AD-HOC TEST Types of Usability Test an hour several days a week several weeks OBSERVATIONAL USER TEST
    • 85. Ad-hoc review
    • 86. Ad-hoc review
    • 87. Activity - Expert Review
    • 88. Expert Review
    • 89. Heuristic Evaluation
    • 90. HIGH FIDELITY Observe 20 users over several rounds. Deliver in-depth report detailing findings, quick fixes and long term solutions. LOW FIDIELITY Observe 5 users. One round of testing. Deliver a short report of recommendations. AD-HOC Grab somebody who has little knowledge of your project Observational User Testing An hour Several days Several weeks
    • 91. Observational User Testing Overview Plan Identify Participants Prepare Observe Report PRE-TEST TEST POST-TEST Analysis
    • 92.
      • Scope and purpose of test
      • Types of participants
      • Tasks & questionnaires
      • Data / Defined Usability Goals
      • Test location and schedule
      • Equipment requirements
      • Confirmation email template
      • Reimbursements
    • 93. Plan
    • 94.
      • YOUR TURN!
    • 95. Activity
      • Create a task which can be used in a user test.
        • How does the task relate to the purpose as defined in the test of plan?
        • Choose tasks which are important or common to users of your site?
        • Focus on areas of the site where difficulties may arise.
    • 96.  
    • 97. Identify
    • 98. Identify
    • 99.
      • ISO defines usability as:
      • “ The effectiveness , efficiency , and satisfaction with which specified users achieve specified goals in particular environments”
      Effectiveness Number of tasks completed successfully. Optimal pathway followed? Efficiency Time taken or number of clicks. Number of back buttons. Number of pages viewed to find information. Satisfaction Comments, body language. Post-test questionnaire findings. Observe
    • 100.  
    • 101.
      • See each candidate individually.
      • Complete the forms and questionnaire.
      • Conduct the test and ask the participants to ‘Think aloud’
      • Focus on what people do, not what they say.
    • 102.
      • YOUR TURN!
    • 103. Activity
      • Perform a mock user test
    • 104. Analysis
    • 105. Report
    • 106. Report
    • 107. Report
    • 108. Report
    • 109.
      • THE PANEL
    • 110. [email_address] [email_address] [email_address] blog