Penguicon.info

User Tools

Site Tools

You are here: start » communicationsbestpractices
Trace:
communicationsbestpractices

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
communicationsbestpractices [2015/03/27 20:41] – waldocommunicationsbestpractices [2015/03/27 20:44] (current) – waldo
Line 14: Line 14:
  
 ==Announcements: == ==Announcements: ==
-  - should be made as soon as the information is known and can be made public+  * should be made as soon as the information is known and can be made public
      * for meetings sometimes time and date are known first.       * for meetings sometimes time and date are known first. 
        * It is important to get the date and time out        * It is important to get the date and time out
        * Then update as soon as possible when a location is found.        * Then update as soon as possible when a location is found.
-  - having them in one place is good  +  * having them in one place is good  
-  - having each separate is good +  * having each separate is good 
-  - people like it when both are done and others hate it when both are done+  * people like it when both are done and others hate it when both are done
  
 ==Long Emails: == ==Long Emails: ==
-  - highlighting main points is good +  * highlighting main points is good 
-  - **Drawing attention to the main point helps** those of us **on phone** or who **have ADD like me**+  * **Drawing attention to the main point helps** those of us **on phone** or who **have ADD like me**
  
-this also **helps when you are skimming** an email after a first read to **find the main points that you read before, adding particular strings to this could help with search-ability** as well this would take some discussion to find a good string+  * this also **helps when you are skimming** an email after a first read to **find the main points that you read before, adding particular strings to this could help with search-ability** as well this would take some discussion to find a good string
  
   * let the list know who can outright ignore a long email up at the top or in the subject   * let the list know who can outright ignore a long email up at the top or in the subject
Line 32: Line 32:
  
 ==Action Items: == ==Action Items: ==
-  - it is good to remember to let it be known what if any action needs to be done +  * it is good to remember to let it be known what if any action needs to be done 
-  - who is expected to do each action needed +  * who is expected to do each action needed 
-  - if there is a due date. +  * if there is a due date. 
-  - have a backup line of communications for more urgent items, like a second contact or request for feedback or receipt of message to make sure they got it with enough time to respond to any due date+  * have a backup line of communications for more urgent items, like a second contact or request for feedback or receipt of message to make sure they got it with enough time to respond to any due date
       * with unknowns in everyone's schedules such as travel, work, family events, sickness, dead batteries etc this could help out quite a bit       * with unknowns in everyone's schedules such as travel, work, family events, sickness, dead batteries etc this could help out quite a bit
communicationsbestpractices.1427488910.txt.gz · Last modified: (external edit)