WRIT 3152 | Communication and Collaboration Protocols

Photo by “My Life Through A Lens” on Unsplash

Communication Protocols (on Discord)

  1. Reactions/emojis for “I saw this” or “yes/no” voting.
  2. Use polls for standardized data collection that leads to decision making (picking times to meet, for example).
  3. Use threads when you’re looking to share resources or for more involved conversation.
  4. Remember @name usage; use replies when applicable. One or the other will alert the user (you don’t need both).
  5. Use pins (and turn them off when finished with them); look for pins if you’re uncertain/lost.
  6. Voice channels are useful; I’ve made three of them that any group can use at any time.
  7. Don’t forget the #help channel (both to ask and answer questions).
  8. Turn on notifications for at least: #announcements, @everyone, and your @ mentions
  9. If you get involved in a synchronous conversation (of more than a couple of real-time exchanges), avoid ghosting (leaving the conversation without an explanation).
  10. Thank people for help they provide.

Collaboration Protocols (during activities)

  1. Give team members at least 24 hours to respond for short or expected requests.
  2. Give team members at least 48 hours for questions that are unexpected or require more thought.
  3. Ask directed questions instead of open ended questions (not: “when is everyone free?”, but: “what is your availability between 8a-12p on Friday, Sept. 12”).
  4. Provided requested answers instead of meandering feedback.
  5. Of course emergencies and unexpected events happen, but plan ahead, not behind by being clear and realistic about your schedule and boundaries.
  6. Don’t let something that is slowing you down slow down your team; briefly explain your situation and empower the team to move on without you.
  7. If you are falling behind in collaboration, reach out to notify me if you decide that you should not be evaluated the same as your team members; this may result in your being pulled from a team and/or given a different assignment, but it’s better for me to know this from you than from your team evaluation.
  8. Make an agenda for a meeting (even if it’s just three short bullet points) and share it; when there is time, it’s usually best to collaborate on an agenda (to invite others to add things).
  9. Identify a note taker for every meeting and post notes
  10. Do not count a meeting if more than one team member is absent.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

css.php