Collaboration with Google Drive

Slides:



Advertisements
Similar presentations
By: Edith Leticia Cerda
Advertisements

Project Management Concepts
User Studies With Camtasia Internet Librarian, Monterey, California.
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.
Using to Collaborate and to Facilitate Collaboration Amongst Your Students Shmuel Fink Touro College.
Formative and Summative Evaluations
Usable Privacy and Security Carnegie Mellon University Spring 2008 Lorrie Cranor 1 Designing user studies February.
Feedback from Usability Evaluation to User Interface Design: Are Usability Reports Any Good? Christian M. Nielsen 1 Michael Overgaard 2 Michael B. Pedersen.
Extremely Rapid Usability Testing (ERUT) When you can’t do anything do something… its better than nothing (K. Holtzblatt)
ICS 463, Intro to Human Computer Interaction Design: 8. Evaluation and Data Dan Suthers.
“COMPUTER-MEDIATED COMMUNICATION IS NOT JUST A TOOL; IT IS AT ONCE TECHNOLOGY, MEDIUM AND ENGINE OF SOCIAL RELATIONS. STEVEN G. JONES, CYBERSOCIETY Interviewing.
Damian Gordon.  Summary and Relevance of topic paper  Definition of Usability Testing ◦ Formal vs. Informal methods of testing  Testing Basics ◦ Five.
Conducting Usability Tests ITSW 1410 Presentation Media Software Instructor: Glenda H. Easter.
Chapter 11: An Evaluation Framework Group 4: Tony Masi, Sam Esswein, Brian Rood, & Chris Troisi.
Interim Presentation Group 4 - May 14th, 2012 Langson Library Redesign.
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.
AGENDA Introduction to Virtual Mechanic Demo Architectural diagram and summary QA steps and user acceptance testing Bugs in the software Feedback from.
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.
Gathering User Data IS 588 Dr. Dania Bilal Spring 2008.
Multimedia Specification Design and Production 2013 / Semester 1 / week 9 Lecturer: Dr. Nikos Gazepidis
Usability testing. Goals & questions focus on how well users perform tasks with the product. – typical users – doing typical tasks. Comparison of products.
Usability Evaluation June 8, Why do we need to do usability evaluation?
Copyright © 2008 Pearson Education, Inc. Publishing as Pearson Addison-Wesley The Resonant Interface HCI Foundations for Interaction Design First Edition.
Project 3 Cookie Cutters Kevin Huynh Sean Tsusaki Jordaniel Wolk.
Hana Lab Reservax System. Introduction——HanaLab Behavioral Lab (DBH 6F) A place to run o Systematic behavioral experiments o Usability studies o Focus.
1 ISE 412 Usability Testing Purpose of usability testing:  evaluate users’ experience with the interface  identify specific problems in the interface.
COMP5047 Pervasive Computing: 2012 Think-aloud usability experiments or concurrent verbal accounts Judy Kay CHAI: Computer human adapted interaction research.
Usability Assessment Methods beyond Testing Chapter 7 Evaluating without users.
Chapter 8 Usability Specification Techniques Hix & Hartson.
Usability Evaluation, part 2. REVIEW: A Test Plan Checklist, 1 Goal of the test? Specific questions you want to answer? Who will be the experimenter?
June 5, 2007Mohamad Eid Usability Testing Chapter 8.
UCI Library Website Chris Lee Archana Vaidyanathan Duncan Tsai Karen Quan.
KIMBERLY BABCOCK MASHEK INFORMATION LITERACY LIBRARIAN WARTBURG COLLEGE Library Technology Conference March 17 th, 2010 Getting Your Library Users Involved.
S T A T I S T I C SD E N M A R KS T A T I S T I C SD E N M A R K Test of reporting forms Ashu Conrad Statistics Denmark March 21, 2011.
Project Breakdowns HCDE 492/592 Winter 2014.
Investigating System Requirements
WP8: Demonstrators (UniCam – Regione Marche)
User Interface Evaluation
02086 Writing Inspirations Aalto University
DATA COLLECTION METHODS IN NURSING RESEARCH
Bell Ringer List five reasons why you think that some new businesses have almost immediate success while others fail miserably.
Document Development Cycle
Asking Users and Experts
Managing the Project Lifecycle
02086 Writing Inspirations Aalto University
Data Architecture World Class Operations - Impact Workshop.
Working in Groups in Canvas
Thinking with Technology Course Module 9
Developing a Methodology
Usability Evaluation, part 2
IENG 451 / 452 Voice of the Customer: Analysis (KANO, CTQ)
Awatef Ahmed Ben Ramadan
Usability Testing T/TAC Online Project Design Team
Evaluation of Google Docs as a collaborative tool among UCI graduate students Group 2 INF /2/2015.
Business and Management Research
The Marketing Research Process
Information Seeking Behavior of Scientists
Initial Presentation Group 4
Saad Ahmad Jola Bolaji Melvin Chien Maxwell Taylor
Youngwummin: Ethics and Data Collection Methods
RACIAL VIOLENCE ARCHIVE
Group: Chris, Daniel, Jeff, Kathy, Shirelle, Vincent
INF 132: Project 2B Course Management System for Students
Team 2+ Luke Fiji, Daniel Yang, Jasmine Fortich, Charles Yan
How do I know if my project is working?
Keeping Students on Track Using Technological Retention Tools
Qualtrics for data collection
Trimester 3 Week 3 Final Major Project.
Presentation transcript:

Collaboration with Google Drive Group 2 INF 231 10/19/2015

Primary Research Questions What problems do small groups of college students (4-5 users) have while using Google Docs for collaborative writing? How can we improve the functions and design associated with these problems? Why is this research question relevant? Collaborative writing is a core feature of Google Docs, so discovering which functions and design elements cause our target population problems is essential for its success among college users mention something about why looking at small groups is important for us -- feasible, allows for closer look at behaviors/social interactions, etc.

Proposed User Research Methods Open-Ended Survey Focus Group Usability Test

Survey Determine what collaborative writing scenarios (academic/non-academic) Google docs is used for in the target population List three most common scenarios (open ended) How long and with how many people do they collaborate Determine which functions and design elements these users like and do not like “What are the top 3 functions you like best about Google Docs?” “What are the top 3 functions you least about Google Docs?” Additional comments box for “Anything we missed?” Recruit interested users for secondary methods (focus groups, usability test) Goal is at least 20+ online survey responses We conducted a pilot survey using Qualtrics to inform the design of this survey (n = 11)

Focus Groups Conduct semi-structured in-person interviews with samples of the target population learn more about group workflow in Google Docs Skype can be used if groups cannot meet face-to-face Identify collaborative writing scenarios that are problematic for these groups issues of group dynamics (sharing, editing control, change tracking) “Do you find it easy or difficult to share your document with others?” formatting functions and design “How do you feel about the design of the editing interface?” Goal is 2-3 ~30min focus groups of 3-5 students Team includes two interviewers and one notetaker (with audio recording)

Usability Test Real time measures of the functions and design elements that were discovered to be problematic Tests will include scenarios identified by the survey data and focus groups Test groups of 3-4 people Subjects will collaborate on an example document with scripted scenarios for ~15min followed by a quick exit interview about their experience Setting up a shared document, controlling privacy settings, accepting and rejecting comments, revision navigation, using text formatting functions, multi-user editing at the same time We will conduct the usability tests in person using laptop computers running Morae Allowing subjects to sit with each-other or be separated will be decided after we analyze our scenario data from the surveys and focus groups Moderator to ensure group remains on task

Expected Results Open-Ended Survey Focus Groups Usability Test Most groups in our target population use Google Docs for academic writing, such as group projects for a class Based on pilot data, we expect problems with control of doc sharing/privacy and doc formatting during group editing Open-Ended Survey More information regarding the issues discovered from our survey Specifics about group-level interactions occurring in the most frequent collaborative writing scenarios from the survey Expanded details about the functions users like and do not like Focus Groups Step by step problems with the functions that are causing the problems discussed in the focus groups Quantitative metrics: time spent on each task, number of times users expressed confusion, post-task difficulty questionnaire (SUS questionnaire is an option) Qualitative metrics: subject feedback about their experience Usability Test

Plans for the Redesign of Google Docs The redesign will take into account our three sources of data (survey, focus groups, usability study) to ensure our proposed changes are consistent with what users want We plan to do a mockup of each redesigned function or design element we discover needs to be changed (frame by frame pictures) Keep in mind the current Google Docs aesthetics and interface

Procedures used for evaluation of the redesign Additional groups from the target population would need to be brought in to do the same usability test but with the redesigned Google Docs We could then compare directly difficulty metrics (quantitative) between the old and redesigned software and user feedback (qualitative) via follow-up questionnaire or interview

Expected Improvements to Google Docs We anticipate that through the survey, focus groups, and usability tests we will be able to create a redesign that successfully addresses all problematic functions of a specific, common scenario This project will provide multiple sources of data for a specific user group which may prove useful for comparison to other target populations Google may have interest in at a later time

Estimated Timeline Team 1: Veronica, Mark, Sierra, Abhijith Team 2: Saurebh, Urjit, Kasey, Zhe Time: Deliverables: Team Week 2 Initial planning meeting and survey pilot launch Team 1 & 2 Week 3 Survey Design - Refinement based on pilot data, presentation draft Week 4 Milestone Presentation (Monday) Collect and analyze survey data Schedule participants immediately after surveys start to come back Pilot test focus group questions and equipment Milestone Powerpoint - Team1 (Mark) Online survey setup - Team 1 (Veronica) Survey distribution - Team 1 & 2 Focus Group Scheduling - Team 1 Survey Data Analysis - Team 2 Week 5 Run focus groups Pilot usability test and recruit subjects for usability test Run Focus Groups - Team 1 Usability Test Pilot - Team 2 Week 6 Run usability tests, organize and transcribe data, analyze data Week 7 Week 8 Create mockup Presentation and Final Report preparation Mockup - Team 2 Presentation and Report -Team 1 & 2 Week 9 Finalize report, presentation and mockup (buffer week) Week 10 Final presentation