
- Image by Getty Images via Daylife
Most teams in business today rely on email. Though imperfect it is ubiquitous for electronic communication. It has proven the lowest-common denominator for communication between team members.
The question of how to organize email is often left to each team member. I think this approach is lacking – it leaves folks with good organization skills at an advantage to keeping up with information. As a team we should all be committed to keeping everyone in the loop. A little effort up front can pay big dividends in team productivity.
Mailing lists allow team members to easily filter email and keep track of emails as appropriate to their role on the team. In larger teams they also allow for managers in the team to manage the email lists appropriate for their team members.
From my experience (which is assisted by my last team at Microsoft – the former Max team) the following list of mailing lists should be created for a product team. Assume each one is started with a short description of the product/team (for example: gizmo-dev is the developer mailing list).
-dev: developer mailing list. Only developers on this list.
-test: test mailing list. Only testers on this list.
-bus: business analyst, program manager mailing list.
-team (aggregate of -dev, -test, -bus): entire team, sometimes includes upper management
-commit (aggregates team): all checkin emails related to software development
-deploy (aggregate of team): deployment announcements for software deployments
-chat (aggregate of team): non-work related chatter – like new joke site, xkcd comic, etc
-oof (aggregate of team): out of facility announcements – like at the dentist for the next two hours, out for a week next week etc
Continue reading ‘Engineering Team Communication: Using Mailing Lists Effectively’



I have recently been using 
