Demo Day Presentation

59
Improved Awareness Systems in Unified Communications Software William Kennedy 0726885

Transcript of Demo Day Presentation

Page 1: Demo Day Presentation

Improved Awareness Systems in Unified Communications

Software

William Kennedy

0726885

Page 2: Demo Day Presentation

Contents

• Introduction

• Initial Research

• First Site Visit

• Persona Generation

• Initial design phase

• Second design phase

• Second Site Visit

Page 3: Demo Day Presentation

Introduction

Page 4: Demo Day Presentation

General Information

• Overall exploration of awareness technologies within unified

communications.

• Methods through which these systems can be improved.

• Unified Communications (or UC) Clients are not a single product,

"but rather a solution made up of a variety of communication tools

and components" Pleasant (2008)

• Core to most UC clients: • Audio

• Video

• Text

• Presence Tech

• Examples include Skype, Google Talk, Microsoft Lync, CUPC (Cisco

Unified Personal Communicator) and now even Facebook.

Page 5: Demo Day Presentation

A note on "Presence"

• Presence is a common industry term, used by Skype, Cisco,

Microsoft et al to describe what would by known to many,

academically, as awareness technologies within Unified

Communications. (Emacs-Jabber Project, 2011)

• "Presence services, in particular, are expanding to enable the aggregation and publication of presence and location information from and to multiple sources. This enhanced functionality is sometimes called "rich presence"." - Elliot and Blood (2011)

Page 6: Demo Day Presentation

Motivating Factors

• Work at Cisco Galway

• Cisco Jabber UI Design

• Problems with the Presence Model

o Are they busy?

o Are they working from home?

• Saunders (2006) describes the Skype presence model as a "broken idea", going on to explain that it "tells you nothing about the person using the PC at the other end".

• The author at the blog 'Steve's Tech Journal' (2006) goes so far as to say that "presence no longer has meaning" due to the problem of people setting their status to 'Available' at all times even when they are too busy to talk.

Page 7: Demo Day Presentation

Objectives

• To gain an understanding of current literature in regard to

presence and awareness models.

• To gain a deep understanding of the needs of real world

users in regard to presence in unified communications.

• To design a more useful model of presence for unified

communications.

• To create an Adobe Flash based prototype which will

accurately and easily convey this improved presence model.

Page 8: Demo Day Presentation

Design Assumptions

• Good awareness is peripheral in that it does not require the

users attention or focus in order to be effective.

• Schmidt (2002) shows that users are capable of taking

peripheral information use this to create useful meaning

effortlessly.

• Awareness information must be useful outside of a

traditional desk based environment.

• Even people who consider themselves as ‘desk workers’

actually spend less than 50% of their working time at a desk

(Bjerrum and Bodker, 2003).

Page 9: Demo Day Presentation

Design Assumptions

• It is important for geographically removed workers to be able

to communicate informally, spontaneously, and to feel

comfortable in doing so. (Bly et al, 1993)

• While current awareness technologies allow for informality

and spontaneity, they fail to encourage it by giving none of

the social cues we would get by walking through any office.

E.g. Mood of other workers, how busy they are and the

feeling of a ‘shared culture’ (Dourish and Bly, 1992)

Page 10: Demo Day Presentation

Initial Research

Page 11: Demo Day Presentation

Literature Review

There are a number of core design issues presented within the

literature for producing a coherent, useful and usable system

of awareness. These are:

• Social Awareness

• Translucence

• Serendipity

• Geographical Dispersion

Page 12: Demo Day Presentation

Social Awareness and Translucence • Bardram and Hansen (2010), citing Schmist (2002) and numerous others,

argue that social awareness "fosters efficient coordination and

collaborating".

• Social awareness helps to reduce the amount of interruption and

disturbance which occurs when people are engaged in cooperative work.

Bardram and Hansen (2010)

• Bardrem and Hansen define four key areas in which contextual workplace

awareness can be fostered:

o Social

o Temporal

o Spatial

o Activity

• They call these the "'who', 'when', 'where' and 'what' in a shared work

environment."

Page 13: Demo Day Presentation

Geographical Dispersion

• Maintenance of "mutual knowledge" (Crampton, 2001) is one of the main problems for geographically dispersed groups who wish to communicate.

• As humans we give on another strong nonverbal cues that show that we are listening and understand one another (Hogan and Stubbs, 2003). Distances destroy our ability to adequately do so.

• Distance may cause us to make incorrect assumptions about dispersed team mates, and Crampton advises that this must be avoided.

Page 14: Demo Day Presentation

Serendipity

• Kraut et al (1990) claim that there are four main types of interpersonal interactions.

• They define these as:

o Scheduled interactions

o Intended interactions

o Opportunistic interactions

o Spontaneous interactions.

• While it is obviously important to design for all of these while designing a communications system, it is spontaneous interactions which are of particular interest when we speak of designing an awareness system.

Page 15: Demo Day Presentation

Software Research

• Elliot & Blood (2011) identify a number of existing integrated unified communications suites including: o Alcatel-Lucent (OpenTouch Communication Suite)

o Avaya (Aura)

o Cisco (CUPC, Jabber, WebEx Connect)

o Digium (Switchvox)

o Huawei (SoftCo)

o IBM (UC2)

o Microsoft (Lync, Skype)

o Mittel (MAS)

o NEC (Univerge Sphericall)

o Siemens (OpenScape UC)

Page 16: Demo Day Presentation

First Site Visit

Page 17: Demo Day Presentation

Preparation

• Cisco Galway were contacted as it fulfilled the criteria of:

o Being a large Enterprise

o Being a consumate user of UC software

o Being able to provide a broad variety of users

o Being open to research visits

• Cisco Galway are also the developers of the Cisco Jabber client and I felt this would provide valuable insight.

• Cisco were particularly open to me visiting the site due to my prior experience in working there.

Page 18: Demo Day Presentation

Preparation

• Documents prepared:

o E-mail survey

o Interview Recruitment E-mail

o Research questionnaire

o Declaration of Informed Consent

o Information Sheet

• Equipment:

o Handheld Recorder

o Notepad and Paper

Page 19: Demo Day Presentation
Page 20: Demo Day Presentation

Site Visit

• Organized with Mark Congiusta, User Experience Manager at the Cisco Galway site.

• Took place on October 27th 2011 from 10am to 3pm.

• Met and interviewed seven members of the Cisco Jabber team, including designers, engineers, qa and management.

• Involved a semi-structured interview and discussion of issues in UC including Geographical Dispersion, Mood and Awareness.

Page 21: Demo Day Presentation

Data Analysis

• Interviews were transcribed manually.

• In line with Saffer (2010) I made the data physical by highlighting key and repeating terms in the transcript and transferring them to post-it notes.

• I then combined, clustered, juxtaposed and named the resulting clusters to produce new and meaningful insights. (Saffer, 2010)

• Arranged core terms and important quotes into a spider diagram.

Page 22: Demo Day Presentation
Page 23: Demo Day Presentation
Page 24: Demo Day Presentation
Page 25: Demo Day Presentation

Findings

• Users are unsure of the usefulness of sharing their mood with their workmates.

• Some also showed a level of discomfort in sharing this level of personal information with their workmates.

• Many users would be dishonest in sharing their mood with workmates, and would prefer to show themselves as always in a good mood, or to put on a "brave face".

• There is a pressure to be 'Available despite how busy they may be.

• Users feel that emoticons are an extremely effective method for sharing emotion through text, and would be happy and comfortable to use them.

Page 26: Demo Day Presentation

Findings

• Users feel that their level of activity, or how busy they are, is far more important to convey than what mood they are in.

• Rennecker (2005) describes this as the "what I need to know to do my job" ethos.

• Users would be extremely interested in being able to show different status messages to different groups of people, for example showing a different status message to teammates than other work colleagues.

• One users describes this as "show[ing] different people different faces".

• Many feel that this would be in keeping with how they currently use 'groups' in their unified communication client.

Page 27: Demo Day Presentation

Findings

• Many users use their co-workers presence indicators as a method of knowing if that person is in the office or at their desk.

• While many would like to know where their coworkers are, they would also be uncomfortable with sharing this information themselves. A sliding level of accuracy was suggested by a number of users.

• Users would like to be able to specify their preferred method of being contacted, for example "IM only", "Phone only" or "Video Preferred".

• Physical distance are not a huge factor in being able to contact someone, however time differences are.

Page 28: Demo Day Presentation

Persona Generation

Page 29: Demo Day Presentation

Creating Personas

• The personas are generic users of unified communications within a corporate environment as these are the primary users for whom I am designing.

• The scenarios are based on scenarios mentioned during the interviews conducted at the Galway site, as well as my own experiences with using unified communications in that environment.

Page 30: Demo Day Presentation

Personas

Robert:

• 35 Years Old

• Mid-Level Manager

• 10 team members

• Managers geographically dispersed

• Team can work from home

• Uses UC for work mostly.

Amanda:

• 24 Year old

• Software Engineer

• Many managers

• Member of Roberts team

• Uses UC for work and social life

Jeremy:

• 30 Year old

• Designer

• Works with many teams including Roberts

• Based in Ireland, but largely works with American teams.

Page 31: Demo Day Presentation

Initial Design Phase

Page 32: Demo Day Presentation
Page 33: Demo Day Presentation

Sketching

Page 34: Demo Day Presentation
Page 35: Demo Day Presentation
Page 36: Demo Day Presentation
Page 37: Demo Day Presentation
Page 38: Demo Day Presentation

Second Design Phase

Page 39: Demo Day Presentation
Page 40: Demo Day Presentation
Page 41: Demo Day Presentation
Page 42: Demo Day Presentation
Page 43: Demo Day Presentation
Page 44: Demo Day Presentation
Page 45: Demo Day Presentation
Page 46: Demo Day Presentation
Page 47: Demo Day Presentation
Page 48: Demo Day Presentation
Page 49: Demo Day Presentation
Page 50: Demo Day Presentation

Second Site Visit

Page 51: Demo Day Presentation

Preparation

• Cisco Galway agreed to a second visit for the purpose of testing my Flash UI prototype.

• Testing was pushed back for various reasons, including time constraints.

• Eventually took place on March 21st.

Page 52: Demo Day Presentation

Site Visit

• Took place March 21st

• Asked 6 people to complete a guided walkthrough of the prototype

• Users were asked to run through a set of predefined tasks on the prototype and "think aloud" as they did so.

• This interaction was guided by myself, and recorded using both video and audio.

Page 53: Demo Day Presentation

Preliminary Findings

• Users were concerned as to whether people affected by colour-blindness would be able to use the application.

• Users found it difficult disliked the concept of averaging the presence of a group of people. People are either available individually or not.

• Users in general found the user interface clean and easy to navigate.

Page 54: Demo Day Presentation

Preliminary Findings

• Some users found the grey text difficult to read on some backgrounds.

• Users were concerned that they might not always recognise a user by their profile picture alone.

• Users found the menu system and call transfer system relatively straightforward.

• Some confusion arose due to a flaw in the

prototype to do with MouseOver events.

Page 55: Demo Day Presentation

Future Directions • Scalability

o Search

o Large numbers of users

o Visibility

• Mobile o Apps

o GPS

• Platform Independence o PC

o Mac

o Linux

• Social Media Integration o Facebook

Page 56: Demo Day Presentation

Questions?

Page 57: Demo Day Presentation

References

Armstrong, D., Cole, P. B (1995) Managing distances and differences in geographically distributed work groups. Diversity in Work Teams,

American Psychological Association, Washington, DC, pp 187-216

Bardram, J.E. and Hansen T.R. (2010) Context-based workplace awareness concepts and technologies for supporting distributed awareness in

a hospital environment. Computer Supported Cooperative Work, 19, pp. 105–138.

Biehl, J et al. (2010) “MyUnity: Building awareness and fostering community in the workplace,” FXPAL-TR-09-21 and arXiv:1006.5024

Bødker, S. and Christiansen, E. (2006) Computer Support for Social Awareness in Flexible Work, Computer Supported Cooperative Woek,

15(1), p.1-28.

Bødker, S. and Christiansen, E. (2004). Designing for ephemerality and prototypicality, In DIS '04: Proceedings of the 2004 conference on

Designing interactive systems, p. 255-260. ACM Press.

Crampton, C.D. (2001) The Mutual Knowledge Problem and Its Consequences for Dispersed Collaboration. Organization Science, 12, 3, 346-

371.

DeGuzzman, E., Yau, M., Gagliano, A. et al. (2004) Exploring the Design and Use of Peripheral Displays of Awareness Information. CHI2004,

Vienna, 1247-1250.

Dourish, P., & Bly, S. (1992). Portholes: Supporting awareness in a distributed group. Proceedings of the 1992 Conference on Computer–

Human Interaction, p. 541– 547. New York: ACM.

Elliot, B. and Blood, S. (2011) Magic Quadrant for Unified Communications. Gartner Research. Note G00214025

Emacs-Jabber Project (2011) Presence, http://emacs-jabber.sourceforge.net/

manual-0.8.0/Presence.html, 16/12/11

Fuchs, L., Pankoke-Babatz, U. and Prinz, W. (1995), Supporting cooperative awareness with local event mechanisms: The GroupDesk system,

in Proceedings of ECSCW’95, Stockholm, Sweden, 11-15 September, Kluwer Academic Publishers, p. 247-262.

Gaver, B. (2002) Provocative Awareness, Computer Supported Cooperative Work, 11(3-4), p.475-493. Greenberg, S. (1996) Peepholes: Low

Cost Awareness of One’s Community. Short paper, CHI’96 Companion, Vancouver, 206, 207.

Page 58: Demo Day Presentation

References

Healey, P. et al. (2007) Communication Spaces, Computer Supported Cooperative Work, 17(2-3), p.169-193.

Heath, C.C. and Luff, P. (1992) Collaboration and control: Crisis management and multimedia technology in London Underground control

rooms. Computer Supported Cooperative Work. An international journal. 1(1-2), pp 69-94.

Hogan, K., Stubbs, R. (2003). Can’t get Through 8 Barriers to Communication. Grenta, LA: Pelican Publishing Company.

Kraut, R., Fish, R., Root, B., Chalfonte, B. (1990) Informal communication in organisation: Form function and technology. People's reaction to

technology in factories, offices and aerospace. The Claremont Symposium on applied social psychology, Sage, 145-199

Redström, J., Ljungstrand, P. and Jaksetic, P. (2000) The ChatterBox; Using Text Manipulation in an Entertaining Information Display.

Proceedings of Graphics Interface 2000, Montréal, Canada. Proceedings of Graphics Interface 2000, Montréal, Canada

Rennecker, J. (2005) “Promoting Awareness in Distributed Mobile Organizations: A cultural and technological challenge.” GROUP'05, Sanibel,

Florida, USA, November 6-9, 2005.

Robertson, T. (2002) The Public Availability of Actions and Artefacts, Computer Supported Cooperative Work, 11(3-4), p.299-316.

Pallot, M., Bergmann, U., Kuhnle, H., Pawar, K.S., Riedel, J. CKH. (2010) “Collaborative Working Environments: Distance Factors Affecting

Collaboration”, Proceedings of the 16th International Conference on Concurrent Enterprising, ICE'2010, 2010.

Phillip, J. and McGrath, A. (2000) “Sharing Serendipity in the Workplace”, Proceedings of the Conference on Collaborative Virtual

Environments (CVE), San Francisco, pp. 173-179.

Saffer, D (2010). Designing for Interaction. Berkeley: New Riders.

Schmidt, K. (2002) The Problem with Awareness: Introductory Remarks on Awareness in CSCW , Computer Supported Cooperative Work,

11(3-4), p.285-298.

Skype identity crisis?

Wiese, J. et al. (2011) Beyond ‘yesterday’s tomorrow’: Towards the design ofawareness technologies for the contemporary worker. [ONLINE]

Available at: http://www.cs.cmu.edu/~jwwiese/publications/wiese-myUnity.pdf. [Accessed 23 September 11].

Pleasant, B (2008) What UC is and isn't, http://

searchunifiedcommunications.techtarget.com/feature/What-UC-is-and-isnt, 16/12/11

Page 59: Demo Day Presentation

References

Saunders, A. (2006) SaundersLog.com, http://www.saunderslog.com/2006/05/23/the-

value-of-presence/, 17/12/11

Skype (2011) Status and Mood, http://www.skype.com/intl/en/business-user-guide/

pc/essentials/status-mood/, 16/12/11

Steve's Tech Journal (2006)

2006/05/22/skype-identity-crisis/, 16/12/11

, http://www.ampersand.com/blog/

Wolff, P. (2011) SkypeJournal.com, http://skypejournal.com/blog/2011/06/28/new-

skype-beta-uses-im-interop-code/, 17/12/11