This is just a simple tip. When providing email address think about what the purpose is. If it is to contact a specific person then an individual’s email address makes sense. But if you are really emailing the software testing manager then it may well make sense to provide people the email address software_testing_manager@
Essentially, I think it is often sensible to break out email addresses for specific functions or processes. Then the email address can just be routed to whoever is suppose to handle those emails. And as your responsibilities shift a bit, those you no longer do can be shifted to someone else and you start getting your new emails. Another nice (I think so anyway) side affect is your various roles are made more concrete. Often it seems who really is responsible is unclear, if you have 5 email address that Jane handled before she left it will be obvious if only 4 of them have been reassigned that 1 has not. Granted such a thing should be obvious without this email tip-off but given how many organizations really operate failing to assign all of someone’s responsibilities to someone when they leave is more common than you would hope.
It is also nice because, if their is a reason it is helpful, those emails can automatically go to as many people as desired. Also if the manager goes on vacation for 2 weeks, the emails can be sent also to the person filling in for them until they return.
Another benefit is a manager, or whoever, can take a quick dip into the email traffic to get a sense of what is being requested. Another benefit (depending on the way it is implemented) can be to have all the software_testing_manager@ emails and responses associated with that email so if you are given that responsibility you can view historical response.
If our knowledge management (wikis, or whatever) solutions were great this would be less important (though still probably valuable) but often the email history may have the best record of our organization knowledge on a topic. When it is spread about in a bunch of individuals mail boxes it is often essentially lost.
It is a small think but this bit of process thinking I have found helpful.
Related: Management By IT Crowd Bosses – Software Supporting Processes Not the Other Way Around – Encourage Improvement Action by Everyone – Delighting Customers
In my organisation we do just this, particularly for enquiries from members of the public. We can then route the enquiry to the right person, and, if necessary, reply as the organisation, rather than a person, if we need to protect someone’s personal privacy.