3/30/2007
Is presence simply an interruption in flow?
Cross-posted here from the Realtime Unified Communications Community
Recently my friend Alec Saunders posted a piece, Couldn’t have said it better myself!, triggered by another post, Mobile Presence: The Essential Attributes from Jared Benson. Since then, Jim Courtney posted a follow up,Getting Presence Right II - A More Comprehensive Perspective, on Skype Journal.
Each piece is really emphasizing some thoughts on ten basic points. Each piece is noteworthy, readable and quite valid. It’s not my intent to detract in any way from the points that Alec, Jared and Jim make. I agree with all of them.
Here are the ten basic points:
- Presence should not be interruptive.
- Users must set/maintain their own presence information.
- Setting presence should be quick, simple, and easy.
- Presence should accommodate for a contact’s different phones.
- Presence should allow users to display different statuses to different groups.
- Mobile presence should include communication preference.
- Presence should include a universal visual/icon system for quick reference.
- Presence should allow connections to other mobile services.
- Presence information should be seen anywhere a contact is referenced in the mobile UI.
- Presence should be maintained by a non-carrier third party.
I count Alec as both a personal friend and a master of presence (along with Howard). But over the past few months, I’ve spoken to a number of people about presence, ranging from home users, to enterprise business people to industry players to investors. And I’ve got some differing thoughts. They aren’t fully developed, but they carry some very consistent observations from my conversations.
Presence isn’t understood or appreciated. For most of people, talking in these terms and has no relevance worth speaking of. It isn’t sexy. It isn’t a feature or a function. Presence is, at best, a state attribute with multiple dynamics.
When I look at the list above, it carries some connotations that are for me, and many people, problematic.
One theme that’s clear above is that presence, as we talk about it today, is disruptive. Not a distruptive technology, but an interruptive one. It disrupts my work flow because it requires constant attention from me. It’s analogous to a mood indicator, and for it to have any value, I must continually tweak it.
If I follow Stowe Boyd’s thought on information flows and continuous partial attention, it’s another interruption flow that I must constantly monitor and alter. And while this conversation focuses on presence as it relates to mobile devices, that too is problematic. I’d perhaps argue that Twitter is a presence engine, requiring continuous partial attention to be effective, always asking “What are you doing?” In a recent presentation, Stowe asked the question “Is attention a resource?” I don’t think it is. I think attention’s simply an attribute of where I am in a given current (what Stowe calls a flow).
I see the problem, if we think of it as a problem, not to be one of presence, and not to be one of continuous partial attention and multiple information flows. The root problem we’re addressing is interruption management. Presence, as described above, is just a small facet of that.
The dichotomy is that when we think of presence this way, we use presence as yet another interruptor. It’s another item requiring attention. And while these are leading edge thoughts on presence management. I think it’s important to recognize that if presence has a maturity model, it’s in its infancy and these are very raw, very immature aspects of the role presence will play in the larger need for interruption management.
When I look at the current state of what we call presence, and compare it with the current state of VoIP, my fear is that we’ll spend too much time on presence and not evolve quickly enough to the larger need of interruption management.
I’m going to pay very close attention to Stowe and what he’s thinking because I think he’s on the right path for where we’re headed in the next generation.
Technorati Tags: presence, attention, interruption management
Filed by Ken at 7:29 pm under Unified Communications
Ken, you know that I am never really “up” to a conversation that gets going between you and your fellow thinkers on the topic of presence, but I’m honored by the fact that you let me play along now and then. Here is one of those times: you got me thinking along with you about presence and the frames you discuss here for (present)ing the ideas of resource. I might counter “interruption management” with an idea framed more along the lines of “attention (or presence) distribution” and in this way answer Boyd’s question with “yes,” attention is a resource. I wonder if the difference is more a rhetorical “high ground” than a real difference in function or fact. By this I mean it seems to me that interruption management gives the interruption (and therefore the interrupter) the edge of control, but framing the same phenomenon as “attention distribution” give the consumer/individual the experience of control - even if only the experience - and creates an opening in the market for meeting more a need fashioned in “cause” than one fashioned in response to an outside force needing to be controlled. I don’t know … really, I’m coming through a fourth day of being very sick with the flu that all of Minnesota seems to have caught. Let me know if any of this rambling sparks a thought or if I’m just plain over my head in this conversation. Either way, fun… and thanks again for letting me play. -mg
Mary, you’re more up for diving into the conversations that you ever give yourself credit for. You should play along more often. Truly.
Your comment really made me step back and think because I realized how every different our days must be, As an educator, you have lesson plans, class schedules, a routine that is followed. I open email first thing in the morning and compare with my calendar to see which scheduled meetings and such have to be deferred or cancelled. My day, and that of a huge number of colleagues is, in essence, interrupt driven. Without constant interruption, there would be no schedule. The day is that fluid.
I agree that interruption management could be argued as presence distribution, but I still think presence is a bad word and minor concept. Presence and availablity are different. Context is another aspect. I know friends who work in presence management think of it as layers of presence, but that doesn’t work for me.
I actually have a visual, well sketch in a journal at this point, driven from some other techniques I used often that lead me toward a new set of conclusions. I just haven’t fully fleshed it out yet. It puts more definition to the set of characteristics that defined our “link state.”
I’ll be watching for the continuation of this conversation, Ken, but when you get the visual up, please do send a copy to my email address so that I don’t miss it, ok? And thanks… I caught the encouragement in the compliment. -mg