Journals by RSS
Journals by EmailA while back, I wrote a couple of posts called “Seven Reasons Your Company Needs a Technical Communicator” and “Four More Reasons Your Company Needs Technical Communicators.”
I recently decided that combining these posts would make a good cohesive document—with some tweaking, of course. So in the near future, I’ll be posting a PDF version of this combined document. As time goes on and I discover more supporting examples and additional points, I’ll add them to the paper. It will be something of an ongoing project. I hope that it will be useful to technical communicators looking for ways to explain and demonstrate their contributions to their employers.
Related posts (auto-generated):
- Four More Reasons Your Company Needs Technical Communicators
- Technical Communicators as a Point of Contact between Users and Project Teams
- Seven Reasons Your Company Needs a Technical Communicator
- The Technical Communicator as Project Manager
- Two Thoughts for Unemployed or Underemployed Technical Communicators
1 Comment to 'Project: Reasons for Technical Communicators'
August 18, 2009
Sounds cool. I look forward to reading it — and saving the PDF on my desktop. Never know if I might need it, given our economic climate. If you remember, drop me a line when it is ready. Come to think of it, I will probably see it via my Google Reader. I have Gryphon Mountain plugged in. Keep up the great work.