Boot Camp: Creating Personas & Scenarios Carla Merrill, Ph.D. Chatham Design Consultants © Carla Merrill, Ph.D. Chatham Design Consultants, 2013.

Slides:



Advertisements
Similar presentations
User Experience Krista Van Laan. Agenda What is User Experience? How does a User Experience team support the rest of the organization? What processes.
Advertisements

FT228/4 Knowledge Based Decision Support Systems Knowledge Engineering Ref: Artificial Intelligence A Guide to Intelligent Systems, Michael Negnevitsky.
User Research Findings. 1 Overview Background Study goals Methodology Participants Findings Recommendations.
NML/436/L1-1 Nazareth Northwestern Mutual Life Participants in IS Development l A team of people comprising: l Project Manager l Systems Analysts l Specialists.
Components of a Product Vision/Strategy
Workbook 1: Crafting Your Value Proposition Workbook Template
Each individual person is working on a GUI subset. The goal is for you to create screens for three specific tasks your user will do from your GUI Project.
UI Standards & Tools Khushroo Shaikh.
Documenting Requirements using Use Case Diagrams
Scenario Assignment IS 485, Professor Matt Thatcher.
Designing a System 4 October Beyond the Technology What will be implemented – external view –“glossy” brochure –Use cases and user types Translation.
IIBA Denver | may 20, 2015 | Kym Byron , MBA, CBAP, PMP, CSM, CSPO
Requirements Gathering : Determining the scope of the system 1. Elicitiation – fact finding 2. Specification 3. Validation.
User Interface Design Process Gabriel Spitz. User-Interface design Steps/Goals Understand who are the users and what do they do Articulate how will users.
Slide 1 Requirements Workflow. Slide 2 The Phases/Workflows of the Unified Process Figure 3.1 l Phase is Business context of a step Workflow is Technical.
Domain Modelling the upper levels of the eframework Yvonne Howard Hilary Dexter David Millard Learning Societies LabDistributed Learning, University of.
User Centered Design April 1-3, 2009 Joshua Ganderson Laura Baalman Jay Trimble.
Buyer Personas About This Document This document describes the personas that are involved in purchasing and using your products. A persona is a typical.
User Interface Design Process Gabriel Spitz. User-Interface design Steps/Goals.
User Modeling Lecture # 5 Gabriel Spitz 1. User-Interface design - Steps/Goals.
Requirements II: Task Analysis. Objectives By the end of the class, you will be able to… Write detailed task descriptions to inform design. Create scenarios.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Incorporating Pragmatic Usability Testing Into a Software Test Plan Carla Merrill, Ph.D. Focused Design focuseddesign.com
BMAN Integrative Team Project Week 2 Professor Linda A Macaulay.
Market Research Lesson 6. Objectives Outline the five major steps in the market research process Describe how surveys can be used to learn about customer.
INFO3315 Week 4 Personas, Tasks Guidelines, Heuristic Evaluation.
What about Chapter 7?. What is the usability process? Tyldesley’s 22 possible Measurement Criteria Let’s focus on usability–A usability initiative needs.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Domain Modeling In FREMA David Millard Yvonne Howard Hugh Davis Gary Wills Lester Gilbert Learning Societies Lab University of Southampton, UK.
Objectives By the end of the class, you will be able to… Describe typical users by using “personas” Write detailed task descriptions to inform design.
Strategic Planning: Developing Strategic Initiatives 1.
1 Knowledge & Knowledge Management “Knowledge is power” to “Sharing K is power” Yaseen Hayajneh, PhD.
Introducing Unit Specifications and Unit Assessment Support Packs MUSIC TECHNOLOGY National 3 to 5.
Kendall & KendallCopyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall4-1 Interactive Methods to collect Information Requirements Interviewing.
Information Systems Analysis and Management Modeling Sys. Requirements with Use Cases Arnie Lund, Jeffrey Kim May 5, 2009 INFO380.
(SRS) SOFTWARE REQUIREMENT SPECIFICATION(SRS) 1. Topics to be discussed.. What is an SRS? Purpose of an SRS Who reads the SRS? Who writes the SRS? Characteristics.
User Modeling Lecture # 7 Gabriel Spitz 1. User Interface Design Process Gabriel Spitz 2 Needs Assessment Competitive Analysis Persona Develop Task Analysis/
Domain Modeling In FREMA Yvonne Howard David Millard Hugh Davis Gary Wills Lester Gilbert Learning Societies Lab University of Southampton, UK.
CSE 403, Software Engineering Lecture 3 Requirements.
User Modeling Lecture # 7 Gabriel Spitz 1. User Interface Design Process Gabriel Spitz 2 Needs Assessment Competitive Analysis Persona Develop Task Analysis/
Task Analysis Lecture # 8 Gabriel Spitz 1. Key Points  Task Analysis is a critical element of UI Design  It describes what is a user doing or will.
Task Analysis Lecture # 8 Gabriel Spitz 1. Key Points  Task Analysis is a critical element of UI Design  It specifies what functions the user will need.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 Click to edit Master title style What is Business Analysis Body of Knowledge?
How to Build Test Inventory Test inventory is built and updated as the software project moves from phase to phase –Start with Requirements List the actual.
ERA/LVA/R-00:000 Experience with qualitative methods Using Cooper’s Personas in System Development.
Main tasks of system analysis ? 1-study exit=sting information system 2-identify problem 3-spelify system requirement 4-asalysis decision ========= How.
William H. Bowers – Requirements Torres 9.
Requirements Engineering Determining and Defining the Requirements for the Project.
The Technical Communicator As User Interface Designer Carla MerrillDiane Feldman Focused Design AuthorCraft Services focuseddesign.comauthorcraft.net.
Copyright © 2007, Oracle. All rights reserved. Managing Items and Item Catalogs.
Prepared by Amira Selim 31 st October 2009 Revised by Dahlia Biazid Requirements Analysis.
Computer/Human Interaction Fall 2015 Northeastern University1 Name of Interface Tagline if you have one Team member names and schools/years Team member.
Designing User Experience (UX) This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.Creative Commons.
1 Requirements Determination (Analysis) Lecture 3 Courtesy to Dr.Subhasish Dasgupta.
Audience Profiling with Personae and Use-Case Scenarios User Scenarios combine User Personas/Personae with User Tasks remember.
NECC ForumJune, 2008 © Chris Stephenson Teaching Problem Solving and Design Chris Stephenson Computer Science Teachers Association.

Userinter14 1 User Interface Design – part 2 Pressman, chapter 12 pp Merrill and Feldman, “Rethinking the Path to Usability” IT Pro, May/June 2004.
1 Week 5 Software Engineering Spring Term 2016 Marymount University School of Business Administration Professor Suydam.
1 Testing—tuning and monitoring © 2013 by Larson Technical Services.
Crafting Your Offer & Market Value Proposition By Ed Downes.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
 Programming methodology: ◦ is a process of developing programs that involves strategically dividing important tasks into functions to be utilized by.
Client communication.
How does a Requirements Package Vary from Project to Project?
Incepting Enterprise Applications
8 Step Problem Solving Step 1: Clarify the Problem
Use Case Modeling.
Requirements “Content Guide”
Scenario Analysis Table
Presentation transcript:

Boot Camp: Creating Personas & Scenarios Carla Merrill, Ph.D. Chatham Design Consultants © Carla Merrill, Ph.D. Chatham Design Consultants, 2013

2 Satisfying Your Customers: The Three Design Challenges 1. What do we need to know about customers / users? 2. How do we gather the information we need? 3. How do we make effective use of the information?

3 3-Step UI design methodology © Carla Merrill, Ph.D. Chatham Design Consultants, 2013

4 Design method: Step 1 © Carla Merrill, Ph.D. Chatham Design Consultants, 2013

5 Design method Step 1: Get Key Facts about Users What do we need to know about users? © Carla Merrill, Ph.D. Chatham Design Consultants, 2013

6 Design method Step 1: Get Key Facts about Users How do we get the user information? Gain access to users Meet users in the right environment Prepare for the meetings Practice Guided Listening™ Create user reports Create a matrix of key user characteristics and needs © Carla Merrill, Ph.D. Chatham Design Consultants, 2013

7 Design method Step 1: Get Key Facts about Users How do we make effective use of the information we’ve gathered? The major problems of UI design “Many users — one user interface” Feature-creep and elastic users Who’s to say what users want? A persona* with scenarios can help solve the problems of UI design * Based on the usage of the term coined by Alan Cooper © Carla Merrill, Ph.D. Chatham Design Consultants, 2013

8 Persona Step A. Analyze your matrix of key user needs & characteristics Persona Step B. Create a hypothetical person who has the common and most important set of needs and characteristics in the matrix Design method Step 1: Get Key Facts about Users How do we create a persona? © Carla Merrill, Ph.D. Chatham Design Consultants, 2013

9 Design method Step 1: Get Key Facts about Users Persona Step A. Analyze the Matrix Assign weights to key users Make a master list of key needs © Carla Merrill, Ph.D. Chatham Design Consultants, 2013

10 Design method Step 1: Get Key Facts about Users Persona Step B. Create a Persona “Users” are Elastic Both average and edge-case Often interchangeable with “programmer” Personas are Specific Detailed Named Hypothetical © Carla Merrill, Ph.D. Chatham Design Consultants, 2013 Make up a person who has the master list of key needs Remember:

11 Design method: Step 2 © Carla Merrill, Ph.D. Chatham Design Consultants, 2013

12 Design method Step 2: Describe the Tasks the Persona Needs to Perform Create scenarios Tasks that your persona wants to accomplish The main tasks that he or she wants to accomplish Detailed, step-by-step descriptions © Carla Merrill, Ph.D. Chatham Design Consultants, 2013

13 Design method Step 2: Describe the Tasks the Persona Needs to Perform Required Format for User Scenarios 1. Pragmatic: only scenarios that capture the primary tasks of your target users (contrast with use cases). 2. Created from the user’s perspective with user-based vocabulary that is implementation free. 3. Step-by-step format, limited to 10 steps per scenario. 4. Long tasks are chunked into a series of scenarios that are prioritized by importance to target users. 5. Scenarios are validated with users before testing begins. © Carla Merrill, Ph.D. Chatham Design Consultants, 2013

14 Design method: Step 3 © Carla Merrill, Ph.D. Chatham Design Consultants, 2013

15 Design method Step 3: Create a UI that enables tasks in the Scenarios Design the UI from the Top Down 1. Start by designing the screen that the user sees first 2. Individuate the tasks in the scenarios by mutual exclusivity 3. Design the main navigation for accessing the tasks from any screen 4. Design the screens for performing each task © Carla Merrill, Ph.D. Chatham Design Consultants, 2013

16 The Goal-Oriented Design Lifecycle © Carla Merrill, Ph.D. Chatham Design Consultants, 2013