User Tools

Site Tools


communicationsbestpractices

This is an old revision of the document!


penguicon communication best practices

  • (this is just a start, needs additions and to be cleaned up and improved, feel free to help)
announcements:
  1. having them in one place is good
  2. having each separate is good
  3. people like it when both are done and others hate it when both are done
long emails:
  1. highlighting main points is good
  2. 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

  • let the list who can outright ignore a long email as well up at the top or in the subject
Action items:
  1. it is good to remember to let it be known what if any action needs to be done
  2. who is expected to do each action needed
  3. if there is a due date.
  4. 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
communicationsbestpractices.1349976502.txt.gz · Last modified: 2017/01/14 14:24 (external edit)