Changes for document Accidentalbroadcast
From version 5.1
edited by Steven Warburton
on 2009/03/04 11:41
on 2009/03/04 11:41
To version 7.1
edited by Steven Warburton
on 2009/03/04 14:39
on 2009/03/04 14:39
Change comment: There is no comment for this version
| Object changes | ||
|---|---|---|
| Property | Previous value | New value |
| Object number 0 of type Scenarios.ScenarioClass modified | ||
| Situation | Email lists or any group email conversation: Often we find that email list conversations can become confused between sending to the list/group and sending replies to individual. The To: and Cc: fields can become a mess of individual email addresses mixed with the mailing list address as people hit the Reply to: button without really checking the recipient addresses. The danger is that off-list replies can be mistakenly sent to the whole list and can cause embarrassment or worse, have serious professional repercussions. Forces in play: Speed to get things done. Keep email under control. Deal with issues immediately. vs. behave professionally. Make each message of value. Thoughtfulness. | Email lists or any group email conversation: Often we find that email list conversations can become confused between sending to the list/group and sending replies to individual. The To: and Cc: fields can become a mess of individual email addresses mixed with the mailing list address as people hit the Reply to: button without really checking the recipient addresses. The danger is that off-list replies can be mistakenly sent to the whole list and can cause embarrassment or worse, have serious professional repercussions. Forces in play: Speed to get things done. Keep email under control. Deal with issues immediately. vs. behave professionally. Make each message of value. Thoughtfulness. |
| Patterns | Patterns: 1) Purposeful delay. 2) Standstill | Patterns: 1) Purposeful delay. 2) Standstill |
| Created | 03/09/2008 18:11:47 | 03/09/2008 18:11:47 |
| Modified | 03/09/2008 18:11:47 | 03/09/2008 18:11:47 |
| Task | Is there a way to mitigate or prevent this occurrence? | Is there a way to mitigate or prevent this occurrence? |
| Solution | If the list is moderated, talk to the moderator as quickly as possible. For large and potentially sensitive lists then perhaps this is something that needs to be invoked. The problem with human intervention in the form of moderation is that it slows the conversation down. So this is not at all practical for example with small project based lists where emails can pass back and forth at a rapid rate. The solution for small lists would be better found by acknowledging that some email usage is in fact “conversational” and perhaps better held outside of the email list using a different communication channel e.g. using IM chat in Skype … arguably more efficient and less dangerous. Whether it is suitable to shift conversations from asynchronous to synchronous mode is an issue to address in assessing the viability of this solution. | If the list is moderated, talk to the moderator as quickly as possible. For large and potentially sensitive lists then perhaps this is something that needs to be invoked. The problem with human intervention in the form of moderation is that it slows the conversation down. So this is not at all practical for example with small project based lists where emails can pass back and forth at a rapid rate. The solution for small lists would be better found by acknowledging that some email usage is in fact “conversational” and perhaps better held outside of the email list using a different communication channel e.g. using IM chat in Skype … arguably more efficient and less dangerous. Whether it is suitable to shift conversations from asynchronous to synchronous mode is an issue to address in assessing the viability of this solution. In summary: Lighten the mood. Try and recontextualise the message Delete the message if you can. Add a dealy before sending difficult messages |
