along similar public-notification lines, I use the Twitter service www.twitter.com, and follow SFBART which sends out light rail timetable delay status reports that would be wholly ineffective if they were sent to me via email.
On Mon, Mar 30, 2009 at 4:52 PM, Mark Elliott <[email protected]> wrote: > Thanks Howard and Nancy! - from the article upon first scan: > > ...SMS and mobile IM messages seem to hold a much stricter timetable [than >> instant messaging]. Almost all participants indicated a punctual 5-15 >> minutes response time at replying to messages they receive. They expect >> similar response time for messages that they send out, so much so that most >> of them claimed that they would follow-up with a second message or phone >> call, if no response was given within 2 hours. >> > > Also of note: > > All participants responded that they almost always immediately notice the >> notification and immediately >> respond by reading the SMS/mobile IM message. In contrast, participants >> indicated they are more likely to negotiate their response time when dealing >> with desktop/laptop IM messages, leading to longer delays before reading the >> message. >> > > As many of you probably are aware of, here in Australia, in my state > Victoria, we had some pretty horrendous bushfires (forest fires) - many > lives lost, completely unprecedented fire dynamics etc. My > consultancy<http://collabforge.com>is providing advice and strategy to > emergency services bodies regarding > options for enabling smart mobs via social media, SMS and other distributed > communications which got me wondering about response time. > > It's interesting to think about the network effects of cascading responses, > each taking 5-15 minutes - which actually adds up to sizable delays. However > this doesn't take into consideration sending messages to groups, or even how > many individual messages might be sent out after receiving one high priority > / important message - which could create exponentially growing cascades of > recipents. > > Of course a major problem we had with the last fires was that mobile/cell > phone coverage went down in effected areas as cell towers were consumed in > the fires... > > On Tue, Mar 31, 2009 at 10:34 AM, Nancy McClure <[email protected]>wrote: > >> this study has a short section on the immediacy of recognition, and begins >> to allude to the impact upon social response. No hard metrics, but could >> lead you to more... >> >> http://www.cs.cmu.edu/~jasonh/publications/CHI2006-kptang-workshop-chi2006.pdf<http://www.cs.cmu.edu/%7Ejasonh/publications/CHI2006-kptang-workshop-chi2006.pdf> >> >> On Mon, Mar 30, 2009 at 3:56 PM, Mark Elliott <[email protected]>wrote: >> >>> Has anyone come across any research on average SMS text message response >>> time - that is, the average time it takes for someone to respond to an SMS >>> text message (not the technical potential speed, but the social speed)? >>> >>> Just curious as it seems like it would be an interesting indicator >>> regarding speed of potential cooperation via SMS smartmob networks... >>> >>> Thoughts? >>> Mark >>> >>> >>> -- >>> ----- >>> Mark Elliott, PhD >>> Director, CollabForge pty ltd >>> collaboration ~ mass collaboration ~ social software >>> http://Collabforge.com <http://collabforge.com/> ~ >>> http://Mark-Elliott.net <http://mark-elliott.net/> ~ >>> http://MetaCollab.net <http://metacollab.net/> >>> Phone: 0421 978 501 (international callers: +614 21 978 501) >>> >>> >>> >> >> >> >> >> > > > -- > ----- > Mark Elliott, PhD > Director, CollabForge pty ltd > collaboration ~ mass collaboration ~ social software > http://Collabforge.com ~ http://Mark-Elliott.net ~ http://MetaCollab.net > Phone: 0421 978 501 (international callers: +614 21 978 501) > > > > -- http://apertedesign.typepad.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CooperationCommons" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/CooperationCommons?hl=en -~----------~----~----~----~------~----~------~--~---
