http://tc.eserver.org/dir/Articles/Project-Management/Writing A listing of the most recently indexed works about Articles and Project Management and Writing in the field of technical communication (and technical writing). en-us Copyright (c) 2005-08 by the EServer. All rights reserved. tclib-editorial@eserver.org (TC Library Editorial Board) webmaster@eserver.org (Geoffrey Sauer) http://tc.eserver.org/images/newlogo.gif http://tc.eserver.org/dir/Articles/Project-Management/Writing http://tc.eserver.org/35586.html http://tc.eserver.org/35586.html One common complaint a lot of technical writers have is that they aren’t included early enough in lifecycle of a project. The downsides are that by the time work hits your desk you don’t have a full picture of who the customer is, why they want whatever it is you are building, and how they want it provided to them. All of which directly impacts the information being created. http://tc.eserver.org/35208.html http://tc.eserver.org/35208.html In such a scenario, this article presents some of the practices that have helped me track and address inputs effectively – regardless of their volume and importance. http://tc.eserver.org/35078.html http://tc.eserver.org/35078.html It is our position that use of PowerPoint for document planning negatively impacts all potential collaborative authoring and review outcomes. Though PowerPoint is commonly used because it is a familiar tool, it is not the most effective tool for managing knowledge either intellectually or financially. http://tc.eserver.org/34890.html http://tc.eserver.org/34890.html When you live in the moment, completing the activity itself is the success. And because writing is so multifaceted in effect — the effect both on me and others — having an open purpose doesn’t limit the results. I’m not narrow-mindedly searching for a specific achievement to happen. Instead, I’m open to unconsidered possibilities, if any of those possibilities decide to unravel. http://tc.eserver.org/33551.html http://tc.eserver.org/33551.html As hard as it may seem, lesson one of technical writing is to break the rules and contact the end user. Conduct a mini-ethnography. Sit with the users. Call them on the phone. Send them emails. Do not let it get to the point where you feel you must go through the PM to communicate with the end user. As hard and uncomfortable as it may be, the consequences of not talking to the end user can be crippling to your help. http://tc.eserver.org/31902.html http://tc.eserver.org/31902.html As much as we all like and/or need money, getting paid may not be enough to keep a writer motivated. Deadlines often are just as important. Although some of us fear — or even hate — them, the truth is that without them many of us simply wouldn’t write anything. And you can count me among those many. http://tc.eserver.org/30546.html http://tc.eserver.org/30546.html Project management skills are part of every writer's life, in some form or another. However, the more you use these skills to manage your daily work, the more you will grow as a writer. Estimating, controlling scope, and tracking your progress are all part of delivering the product that your "customer" wants. Your primary tool is your documentation plan. In this workshop, we will discuss why these processes are important to you and how to implement them on your job. http://tc.eserver.org/29426.html http://tc.eserver.org/29426.html Pragmatism is the necessary first step: do the best job you can do under the conditions. Nobody's going to benefit if you do a superb job on half the manual, then die of stress before you can document the important parts in the second half. http://tc.eserver.org/29336.html http://tc.eserver.org/29336.html Want to know the secret to better quality documentation and improved software design? Will Kelly outlines how the key is an effective relationship between project managers and technical writers. http://tc.eserver.org/28603.html http://tc.eserver.org/28603.html Sometimes considered an afterthought in the product development lifecycle, technical writers often struggle to become part of a performing Agile team. http://tc.eserver.org/28193.html http://tc.eserver.org/28193.html What does it take to get a newsletter out each month? Well, I spend about 16-20 hours a month on the newsletter at home, which doesn't include copying. http://tc.eserver.org/27887.html http://tc.eserver.org/27887.html It is my firm belief that every technical writer is passionate about her work and would put in her best efforts to deliver high quality. If you are a manager or an editor and are shaking your head in disagreement, think again. Why would someone want to submit a work of poor quality? http://tc.eserver.org/27462.html http://tc.eserver.org/27462.html This workshop shows a technical publication manager or rising professional how to work in the following technical publishing/financial areas: project management, operating budget preparation and management, and quality control. http://tc.eserver.org/26726.html http://tc.eserver.org/26726.html Hiring the right freelancer to do the job correctly the first time around could save you hundreds or thousands in help desk calls, service calls, document revision, and distribution. Here's why. http://tc.eserver.org/25950.html http://tc.eserver.org/25950.html Does your job involve writing? Here's a surefire recipe for bringing on writer's block and making the whole process seem so onerous that you'll vow never to put pen to paper again. http://tc.eserver.org/22051.html http://tc.eserver.org/22051.html Between 25-30 percent of the overall writing time is typically devoted to developing the document specification, meaning how the document will be formatted and actually present the information. This is true even when the organization has a style guide with a prescribed format, but no “standard” for documentation overall. Although this may seem an inordinate amount of time and effort on the front end, before getting any information onto the paper, it is far more cost-effective than spending unplanned time rewriting and reformatting the document late in the production process.