| |||||||||
|
1. #28188 Developing Technical Curiosity: A Marketable Skill Every technical writer should have strong writing skills. Just as important, in my judgment, is a keen sense of technical curiosity. As a hiring manager, I look for it in every job applicant I interview. If you do not have this sense naturally, you can develop it. Harvey, Michael. Carolina Communique (2003). Careers>TC>Collaboration 2. #30779 Don't Let Your Work Become a Commodity Learn specific steps technical communicators can take to respond to the commoditization of technical tasks. Harvey, Michael. Intercom (2008). Careers>TC>Workplace 3. #13199 How We Developed an Intranet: Using the Web to Inform Employees, Manage Projects, and Save Money Data General’s R&D organization had developed disparate web sites. It was hard to find relevant information and difficult to know what others were doing. We volunteered to create a unified web presence to solve these problems. Taking initiative while building consensus, we crafted a highly used and highly useful intranet. This paper describes how we did it. Our success allowed us to broaden our department’s scope and change its name from “Documentation” to “Documentation and Web Services.” Our experience shows that documentation departments are well suited to create and maintain intranets, and that documentation professionals have the skills to become content developers or information architects. Harvey, Michael. STC Proceedings (2001). Presentations>Web Design>Intranets 4. #28958 Is Technical Writing Your Calling? An essay exploring whether technical writing is a 'calling.' Harvey, Michael. Carolina Communique (2007). Articles>Writing>Technical Writing>Community 5. #23716 It's a Marathon, not a Sprint: Managing Your Technical Writing Career I've trained for and run three marathons. My marathon experiences taught me lessons that can be applied to going the distance in a technical communication career. Going the distance requires a willingness to “get going,” continually work on the basics, cross- train, avoid being distracted by what was and what could be, and learn from experience. Harvey, Michael. STC Proceedings (2003). Careers>Advice>Writing>Technical Writing 6. #29789 Pith and Vinegar: What Do You Do for a Living? Rather than authoring printed manuals and on-line help panels, technical communicators should be involved in or leading projects that make them unnecessary. Harvey, Michael. Carolina Communique (2006). Articles>TC 7. #28166 Usability Testing and Research The more intuitive a product's interfaces and procedures become, the more usable it becomes. Thus, the less formal documentation it requires. To do our part, we can strive to reduce the number of words a customer needs to read. Focusing on clarity and concision, we can take pride that of the words that remain, every word will count. Working with usability experts, our fellow customer advocates, we can transmute unwieldy products into easily used ones. To me, that's a compelling reason to remain a technical communicator, regardless of why we became one. Harvey, Michael. Carolina Communique (2005). Articles>Usability>Testing 8. #30056 We need to revise our job descriptions. Rather than authoring printed manuals and on-line help panels, we should be involved in or leading projects that make them unnecessary. Why? Because consumers increasingly demand intuitive interfaces to the products they use. Users and administrators of more complex products expect interfaces that guide them through decisions rather than require them to read details. We must stay ahead of this trend, rather allow ourselves to be flattened by it. Harvey, Michael. STC Puget Sound (2006). Careers>TC 9. #28169 When you scan job postings for technical communicators, you'll find prospective employers seeking candidates who have an understanding of current technology, working knowledge of publishing tools, and time management skills. A bullet may ask for 'excellent writing and editing skills,' but that bullet rarely appears at the top of the list. Not for me. Harvey, Michael. Carolina Communique (2005). Articles>Writing>Grammar
| |||||||||
| |||||||||
Click here to learn how to embed the RSS feed by this author in your website.