by Bill Pray | September 14, 2011 | Comments Off on
If you ask an IT professional to define presence, you may get something along the lines of:
The term “presence” is frequently associated with instant messaging (IM). The basic definition for presence is information that conveys the ability and interest of a user to communicate with another user (or users). For many people, the predominantly manual status settings included in popular consumer IM clients (e.g., Google Talk, Windows Messenger, and Yahoo! Messenger) are their first experience with presence.
However, if you ask the average information worker, you might be greeted with a blank look. What is really interesting is to ask them to find a co-worker’s availability or ask them how they would find out if they could contact a co-worker at this moment. Do they check an IM client to see a red or green button? Do they grab a mobile phone and call them? Do they SMS instead of call? Do they check their email client? Do they go to a social software web page and look at an activity stream?
Do these options (and many others) change the basic definition of presence? How does an enterprise glean value out of presence if the definition is changing? Does the introduction of contextual presence from social streams – e.g. a Facebook entry that says I am in my office today, working on a huge project, but I am looking forward to lunch with my family and will be taking the afternoon off to take them to a ballgame – change the landscape for presence?
Read Complimentary Relevant Research
Predicts 2017: Artificial Intelligence
Artificial intelligence is changing the way in which organizations innovate and communicate their processes, products and services. Practical...
View Relevant Webinars
The Education CIO Challenge: IT Is a Team Sport
This video will outline key Education CIO challenges and recommendations based on business and technology trends in education as well...
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.