Mid-Term Evaluation  Course and Instructor evaluation  Jennie Dorman.

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

Management, Leadership, & Internal Organization………..
User problems, scenarios and storyboards
Components of a Product Vision/Strategy
Project leaders will keep track of team progress using an A3 Report.
SECOND MIDTERM REVIEW CS 580 Human Computer Interaction.
Experiential Learning Cycle
Web E’s goal is for you to understand how to create an initial interaction design and how to evaluate that design by studying a sample. Web F’s goal is.
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.
IS214 Recap. IS214 Understanding Users and Their Work –User and task analysis –Ethnographic methods –Site visits: observation, interviews –Contextual.
7 Chapter Management, Leadership, and the Internal Organization
IS 214 Needs Assessment and Evaluation of Information Systems Managing Usability © Copyright 2001 Kevin McBride.
Usability presented by the OSU Libraries’ u-team.
Administrivia  Review Deliverable 2 –Overview (audience) –Excellent additions  User Goals  Usability Goals  User Group (who are you designing for?)
Usability Inspection n Usability inspection is a generic name for a set of methods based on having evaluators inspect or examine usability-related issues.
Information & Interaction Design Fall 2005 Bill Hart-Davidson Session 6: analyzing work practices – rationale and challenges; the 5 Contextual Design work.
Midterm Exam Review IS 485, Professor Matt Thatcher.
Heuristics  Basis  Evaluators –Qualifications –Training  Preparation –Scenario  Results –List of problems –Severity –Group synthesis.
Project Sharing  Team discussions –Share results of heuristic evaluations –Discuss your choice of methods and results  Class-level discussion –Each spokesperson.
Administrivia  Feedback on first Deliverable –Audience: Management –Requirements  Description of the system (what it is, how it works)  Define user.
Administrivia EPost and Portfolio EPost and Portfolio Analysis of Design process Analysis of Design process.
Inspection Methods. Inspection methods Heuristic evaluation Guidelines review Consistency inspections Standards inspections Features inspection Cognitive.
Analysis of Design Process Lewis/Gould 1981 Study TC518 W ’06 Students Early Focus on Users 62%58% Empirical Measurement 40%69% Iterative Design 20%62%
Usability 2004 J T Burns1 Usability & Usability Engineering.
Oct. 30, 2003CS WPI1 CS 509 Design of Software Systems Lecture #9 Thursday, Oct. 30, 2003.
Administrivia Turn in ranking sheets, we’ll have group assignments to you as soon as possible Homeworks Programming Assignment 1 due next Tuesday Group.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 22, 2004.
Principles of High Quality Assessment
Feedback from Mid-term Evaluation  What could better help you learn –Assignments  Assignments are too vague (expectations are not clear)  Unsure about.
Elicitation Methods Information types Information types Information Information Internal Perspectives Internal Perspectives Behavior Behavior Facts Facts.
Research problem, Purpose, question
Understanding Task Orientation Guidelines for a Successful Manual & Help System.
Work Sample: Engineering Design Grades 3-5
User Centered Design April 1-3, 2009 Joshua Ganderson Laura Baalman Jay Trimble.
ZEIT2301- Design Studios and Design Critiques School of Engineering and Information Technology Dr Kathryn Merrick Bldg 16, Rm 212 (Thursdays.
William H. Bowers – Modeling Users: Personas and Goals Cooper 5.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
S556 SYSTEMS ANALYSIS & DESIGN Week 11. Creating a Vision (Solution) SLIS S556 2  Visioning:  Encourages you to think more systemically about your redesign.
Part 1-Intro; Part 2- Req; Part 3- Design  Chapter 20 Why evaluate the usability of user interface designs?  Chapter 21 Deciding on what you need to.
T 7.0 Chapter 7: Questioning for Inquiry Chapter 7: Questioning for Inquiry Central concepts:  Questioning stimulates and guides inquiry  Teachers use.
Ch.4 The UCSD Process.
What is Usability? Usability Is a measure of how easy it is to use something: –How easy will the use of the software be for a typical user to understand,
Chapter 12: Systems Investigation and Analysis. Agenda  How to Develop a CBIS?  Systems Development Life Cycle (SDLC)  Prototyping  Join Application.
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.
Chapter 6 Team Work Blueprint By Lec.Hadeel Qasaimeh.
Leading (and Assessing) a Learning Intervention IMPACT Lunch and Learn Session August 6, 2014 Facilitated By Ozgur Ekmekci, EdD Interim Chair, Department.
Exploratory Research and Proper Problem Definition Lecture 3.
The Major Steps of a Public Health Evaluation 1. Engage Stakeholders 2. Describe the program 3. Focus on the evaluation design 4. Gather credible evidence.
Human Computer Interaction
Project Sharing  Team discussions (15 minutes) –Share results of your work on the Project Scope Proposal –Discuss your choice of methods and results –Prepare.
Administrivia  Final Exam –Due Date – Thursday, March 17 –Q & A  Deliverable 2 –Q & A.
Module 4: Systems Development Chapter 13: Investigation and Analysis.
Content Vocabulary Word Documentation. Content Vocabulary 0 Teamwork: cooperative or coordinated effort on the part of a group of persons acting together.
Administrivia  Feedback from the mid-term evaluation  Insights from project proposal.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Putting it in Practice: CD Ch. 20 Monday Fun with Icons CS 321 Human-Computer.
Organizing Programs, Business Units and other Service Systems Diamond of Organization Credit function The concept of Flow Project Explorer.
User Interface Evaluation Introduction Lecture #15.
Reading Take-Aways 1.Which of the four C’s do you think is most critical for student preparation for PJL? Why? 2.How does a driving question facilitate.
Supporting the design of interactive systems a perspective on supporting people’s work Hans de Graaff 27 april 2000.
Overview of System or Process Design and Improvement 1.
Technical Report Writing Dr. Shelley Thomas. Overview Selecting effective report topics Using worksheets to plan projects Developing and proposing project.
Chapter 6 Assessing Science Learning Updated Spring 2012 – D. Fulton.
For more course tutorials visit
Data Synthesis and Analysis
Chapter 12 Instructional Project Management: Managing Instructional Design Projects on Site and at a Distance Brenda C Litchfield.
“It was years after we had taken usability to guide us that it was said by some other companies that they could not afford to employ a usability specialist.
Administrivia Final Exam Deliverable 3 Feedback on Heuristic Eval
Data Synthesis and Analysis
Administrivia Issues – EPost and Portfolio
A Fundamental Challenge
Presentation transcript:

Mid-Term Evaluation  Course and Instructor evaluation  Jennie Dorman

 “It was years after we had taken usability to guide us that it was said by some other companies that they could not afford to employ a usability specialist. Had they known the truth then, they would have known that they could not afford to be without one.” - Who said this?

 “It was years after we had taken chemistry to guide us that it was said by the proprietors of some other furnaces that they could not afford to employ a chemist. Had they known the truth then, they would have known that they could not afford to be without one.” - Andrew Carnegie, 1920 “Robber Baron” of steel mills “Robber Baron” of steel mills

Project Sharing  Team discussions –Share results of synthesis –Discuss your choice of methods and results  Class-level discussion –Each spokesperson share  One challenge  One surprise  One lesson learned

Administrivia  Example of the impact of Context  EPost participation impacts your grade  Exercises complete before class  Refrain from working on exercises and during class  Insights from exercises

Insight  … explore the differences between tasks we assumed users would be able to perform and what they actually performed. Participants struggled valiantly to perform what should have been easy tasks, if the interface had been designed with them in mind. As it was, yes, they performed some tasks, but at what cost in frustration and enmity for the company that designed such junk! A very real insight into a common problem.  --Mark Hoffman

Discussion of Readings  Insights from supplemental readings.  Facilitate class discussion of topics / ideas / themes garnered from the online discussion, related to assigned readings. –Discussion Leaders 1. Kelly Lillis 2. Angie Moulden 3. Mark Hoffman

Where are we in the UCD process?

Topic E: Moving toward problem definition Driving Questions:  How do designers use knowledge of users, tasks, and contexts to understand observed usability problems?  How does one set priorities for a UCD redesign? How does one constrain redesign?  How do designers manage the scope of a project? What are the challenges associated with managing scope (e.g., scope creep)?

Problem Definition  Beginning the process of translating robust (user) models into design solutions  Requirements Definition –Based directly on research and user models –Problem Statement (objective of the design)  A situation that needs changing for both: –Personas (users) –Business  Frame the design in terms of both user and business goals –Vision Statement (high level design mandate)  Start with user’s needs  Tie in with how business goals are met  Activity: create problem & vision statements for the Photo Book (Cooper)

Design Activity

 Usability Activity  Review Phase 1 design –Functionality problems –Usability problems (instructions)  Exercise: think, pair, share –How would you remedy the problems?  Discuss design ideas  Review Phase 2 design

Design Activity

 Usability Activity  Review Phase 1 design –Functionality problems –Usability problems (instructions)  Exercise: think, pair, share –How would you remedy the problems?  Discuss design ideas  Review Phase 2 design –Functionality –Usability problems  Exercise: think, pair, share –How would you remedy the problems?  Review Phase 3 design

Design Activity

Persona Expectations  Mental model of the persona should match the design model (how the design behaves and presents itself)  Car stereo anecdote (developing mental models)  Behaviors they expect from the product/system  Influences –Attitudes –Past experiences –Social and environmental factors –Cognitive factors

Context Scenario  Map out the big picture  Help people imagine  Focus on mental model, goals, activities  Only behaviors of the user and the system  Broad context, includes environment considerations  Illuminate frequent and regular use–describing an optimal, yet feasible experience  Key aspects –Setting –Complexity (related to persona skill and frequency of use) –Primary activities (to meet goals) –End result of using the product  Tool: pretend the product has magical powers to meet user goals (creative, outside the box)

Usability Goals  Measurable  Organizational goals  Format –A conditional statement –How many of what type of user will be able to perform what task within what measure –Establish the context in which a goal must be met –Conditions are generally quantitative (countable) or qualitative (subjective )

Usability Goals  Format –How many of what type of user will be able to perform what task within what measure  Examples –80% of managers are able to complete enrollment in the XYZ system without calling the Help Desk –90% of employees will be able to find their paycheck online within 30 seconds, beginning from the Home page of the intranet –80% of experienced users will rate their satisfaction with TME at least 5, on a scale of 1 to 7, where 1=Extremely dissatisfied, 7=Extremely satisfied  Activity –Write a measurable usability goal for selecting raters

Requirements  Balancing user, business and technology requirements  Fit criterion (success)… makes you THINK –Quantifiable & Measurable –How will you know if a solution satisfies the requirement? –Validate (test whether, or not, it truly is a requirement)  Skill: separating the real requirements from the solution ideas.  Within a business team –Get the conflicts out in the open, keep them visible –Conflict is a respectable form of creativity, of processing ideas  Waiting room (novel idea to deal with team/politics)  Consider non-user goals (corporate, technical, customer), but not at the expense of the user.  Successful products meet user goals first.  Good interaction design is devising interactions that achieve the business goals without violating the goals of users.

Rationale  Rationale for the problem –What evidence supports the conclusion that this is a problem to be solved by a design change?  Rationale for the solution –Why will this solution remedy the problem? –What design principles or patterns does the solution rely on? (rather than opinion) –Explain

Rationale  Example 1 –The middle area of the home page should be a portal to the different features and services available. Also, a portal gives users a context should they return to the site after taking their attention away for a period of time.  Example 2 –According to the practice of grouping related user interface elements together [3], the site needs to have a layout which more closely matches the customer’s work flow. Items which relate to a given task must be more closely situated. We will reposition components of the payment interface so that like items are in the same space. For instance, move the X and Y components within closer proximity of the payment area.

Business Case  Why should a business invest money in this solution?  Examples –Version Changes: The number one most common technical support inquiry is related to version changes (upgrades and bug fixes) to the program. A web-based interface would eliminate these inquiries as upgrades can be done centrally, behind the scenes, without knowledge of the user. –Using user-centered design methodologies, we found new users may not easily understand the site’s purpose, what the site can do for them, and how they would use it. Based on FY06 business goals of lowering user registration attrition rates and increasing net user base by 20%, we recommend home page and quick tour design changes to improve the user’s first experience.

Project Exercise Preliminary Design (first of 2 weeks)  For the first week of the two-week preliminary design effort, prepare a draft of key components of the project proposal in which you describe your analysis of the redesign situation and the problem that you wish the redesign to address: –Problem Statement  Clearly state what you think the problem is. –Rationale for Solution  Propose a solution that addresses the problem, justifying design decisions with user-centered analysis (i.e., using design principles as well as the information you have about your users, their tasks, and the context for their tasks. –Business Case  Provide justification for investing in moving the redesign forward.  This draft should be no more than one page in length.  Bring copies of the exercise to class (one copy for each member of the team, one copy for the instructor) and also post it to your design portfolio.  Due next Thursday

Looking back / Looking ahead Where we’ve been  Topics – Readings and discussion –What is UCD? –What to know about users? –Collecting information about users… –Doing contextual inquiry…  Project –Insights about users, tasks, and contextual issues –Actual data from observing real users –Sharing among team members –Resulting in… task information to analyze and synthesize Where we’re going  Project Deliverable: –Describe the problem –Propose a redesign –Justification  Readings: –On design: visual, navigation; heuristics, prototyping  Upcoming Exercises: –Design –Heuristic Evaluation –Usability Study  Issue Statement: A reminder 1. Steve Messerer 2. Laurent Gherardi 3. Maren Costa