Tester skill: Influential writing
Pradeep brings up the skill of writing influential emails as a tester. I cannot agree more on the need for it. Here is what I wrote as a comment to his post. Please feel free to add more comments and give me some suggestions on rules for improvements.
Hi Pradeep! I like the way you bring out the need for good writing skills as tester. However, I am not very sure you showed us the very best answer to your own question. Actually, I think Sreenurajs last one was better. Why?
The planned readers of the email was the test team itself, not the management nor test management. For me this means sharing your thoughts from the testers perspective. Your example is really more of something to send to business people of management, but for the same reason. This because you talk about budgeting for testing etc.
Also, I have to add the cultural aspect to it. Always remember to whom you write, not only the role but also culture, experience and situation in project. Of course you have the humble approach, but in environments I work in, that was overdoing it.
What rules do you use when writing influential email? Examples are good, but do you keep a cheat sheet for it?
Thank you for sharing, and I would really look forward to an update on this./Sigge
As a side note, I actually think that the ability to clearly communicate in writing is a key skill as a tester, not only for emails. Bug reporting, notetaking and status reporting are other examples. And while I think I have some of the skills needed, knowing about my problems with conciseness helps me by knowing what to practice. Twitter is actually one of my ways to practice just that.