<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Knowles, Michael</title>	<link>http://tc.eserver.org/authors/Knowles,_Michael</link>
	<description>A bibliography of works by Knowles, Michael in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Knowles, Michael</title>
		<link>http://tc.eserver.org/dir/Knowles,_Michael</link>
	</image>
	<item>
		<title>Succeeding as a Technical Writer</title>
		<link>http://tc.eserver.org/26029.html</link>
		<guid>http://tc.eserver.org/26029.html</guid>
		<description>A list of rules that have served me in good stead over my entire career.</description>
	</item>
	<item>
		<title>How to Write a Competitive Analysis</title>
		<link>http://tc.eserver.org/26023.html</link>
		<guid>http://tc.eserver.org/26023.html</guid>
		<description>There are few documents that get the attention of product planners and marketers the way that a competitive analysis does. A good competitive analysis is a scouting report of the actual market terrain that your company must navigate in order to be successful. And there is no person better equipped to write one than a market-savvy technical writer.</description>
	</item>
	<item>
		<title>How to Write a White Paper</title>
		<link>http://tc.eserver.org/26024.html</link>
		<guid>http://tc.eserver.org/26024.html</guid>
		<description>A white paper in the high-tech industry is a technical document that describes how a technology or product solves a particular problem. It&apos;s a marketing document and a technical document, yet it doesn&apos;t go too far in either direction. A good white paper is informative and is designed to show off the advantages of a product or technology.</description>
	</item>
	<item>
		<title>Marketing the Wily Technical Writer</title>
		<link>http://tc.eserver.org/26027.html</link>
		<guid>http://tc.eserver.org/26027.html</guid>
		<description>If the world really is run by C students, then you have to ask yourself a question: How do I market myself in an ocean of average? Today&apos;s competitive job market can be a hard nut to crack. How do you stand out in that crowd?</description>
	</item>
	<item>
		<title>Sean Hower&apos;s Notes from the Cubicle: Getting the Most Out of the Web</title>
		<link>http://tc.eserver.org/21729.html</link>
		<guid>http://tc.eserver.org/21729.html</guid>
		<description>As long as you&apos;re careful about evaluating the information you find, the Web is the perfect place to start any project. It&apos;s easy and cheap to find information on a variety of subjects in just a few minutes, depending on the search engine you use and your research skills. With so much on the Web, though, it&apos;s may be hard to find good information.</description>
	</item>
	<item>
		<title>Guerilla WriteFare™: Nice Work If You Can Get it -- Here&apos;s How</title>
		<link>http://tc.eserver.org/18649.html</link>
		<guid>http://tc.eserver.org/18649.html</guid>
		<description>My experience in the corporate environment has been that larger companies don&apos;t go out of their way to hire home-based freelancers. That&apos;s not to say that they never do -- it simply hasn&apos;t been my experience with them. I run into this problem all the time. Finding off-site work is a challenge. I scour the top 20 or so job search engines and other places for work and, while there really are quite a few contract positions out there, nearly all of them require on-site work. &#xD;&#xD; That&apos;s the bad news. &#xD;&#xD;Here&apos;s the good news: I have figured this thing out, believe it or not. In fact, I&apos;m working on a book and a seminar about it. To locate good work that allows you to work out of the home office, you must know three things: How to look. Where to look. Hw to build trusting relationships with your customers.</description>
	</item>
	<item>
		<title>The Business of Writing: How Do I Set My Rates?</title>
		<link>http://tc.eserver.org/13574.html</link>
		<guid>http://tc.eserver.org/13574.html</guid>
		<description>Do you know how much what you do is worth? Very likely a lot more than you think. But how do you figure out how much to charge for a given job?</description>
	</item>
	<item>
		<title>How to Write a White Paper</title>
		<link>http://tc.eserver.org/13576.html</link>
		<guid>http://tc.eserver.org/13576.html</guid>
		<description>A white paper in the high-tech industry is a technical document that describes how a technology or product solves a particular problem. It&apos;s a marketing document and a technical document, yet it doesn&apos;t go too far in either direction. A good white paper is informative and is designed to show off the advantages of a product or technology.</description>
	</item>
	<item>
		<title>Brokedown Palace Part 2: Workflows for Fun and Profit</title>
		<link>http://tc.eserver.org/13567.html</link>
		<guid>http://tc.eserver.org/13567.html</guid>
		<description>If you&apos;re going to toss out your user guides, you&apos;d better have a good user interface and concise supporting materials. Workflows can help you both in the design of the user interface and in the creation of job aids for the people who use your product. A workflow is a compact and effective way to describe the flow of any procedure. How many times have you grumbled about the design of a piece of software or Web site that you&apos;ve been trying to use? Chances are that no one ever sat down to model it using the workflow technique.</description>
	</item>
	<item>
		<title>Brokedown Palace, Part 1: Why User Guides Don&apos;t Work</title>
		<link>http://tc.eserver.org/13566.html</link>
		<guid>http://tc.eserver.org/13566.html</guid>
		<description>Software user guides use up an awful lot of space with screen shots. But I know what the screen looks like -- it&apos;s right in front of me. Any decent GUI design is self-documenting to some extent, at least. No matter how much we complain about them, GUIs have gotten pretty good. Children have them figured out in minutes. And then they start asking questions like, &apos;How do I make my stick man move around?&apos; Computers are toasters or drawing pads to them. That&apos;s another reason user guides don&apos;t work: the average user doesn&apos;t need one anymore.</description>
	</item>
	<item>
		<title>The Four-Point Writing Project Success Guide</title>
		<link>http://tc.eserver.org/13571.html</link>
		<guid>http://tc.eserver.org/13571.html</guid>
		<description>Have you ever worked on a truly awful writing project? Maybe you&apos;re working on one right now. Too often, what could be a simple project becomes a morass of shifting requirements, last-minute changes, and expanding scope. In almost one-hundred percent of such cases, however, a well-run writing project can negotiate the most challenging terrain.&#xD;</description>
	</item>
	<item>
		<title>Guerilla WriteFare: When Clients Don&apos;t Listen</title>
		<link>http://tc.eserver.org/13563.html</link>
		<guid>http://tc.eserver.org/13563.html</guid>
		<description>What do you do with a perfectly good client who, despite your recommendations, embarks on a course of action you believe to be wrong or even disastrous? I know of only one answer to that question: let it go. After you&apos;ve given it the old college try, of course. I never did let go easily. There are few things more disturbing than watching a client jump off a cliff. You just know they&apos;re going to crash onto the rocks below, because you&apos;ve seen it happen so many times before. Is there anything you can do? Yes, and here&apos;s my list of things to do when clients don&apos;t listen.</description>
	</item>
	<item>
		<title>Marketing the Wily Technical Writer</title>
		<link>http://tc.eserver.org/13568.html</link>
		<guid>http://tc.eserver.org/13568.html</guid>
		<description>If the world really is run by C students, then you have to ask yourself a question: How do I market myself in an ocean of average? Today&apos;s competitive job market can be a hard nut to crack. How do you stand out in that crowd?</description>
	</item>
	<item>
		<title>Nice Work If You Can Get it -- Here&apos;s How</title>
		<link>http://tc.eserver.org/13572.html</link>
		<guid>http://tc.eserver.org/13572.html</guid>
		<description>The secret to finding off-site work is to change the way you think about work. You must first and foremost be doing a type of writing that lends itself well to off-site work. It&apos;s easy to say that all writing can be done off-site. But you&apos;d be wrong.</description>
	</item>
	<item>
		<title>The Shifting Technical Writing Market</title>
		<link>http://tc.eserver.org/13570.html</link>
		<guid>http://tc.eserver.org/13570.html</guid>
		<description>I believe that technical writers, by and large, do a poor job of marketing themselves in a competitive business. We cannot simply send resumes out anymore and expect the employers to come to us. The market moves too quickly for that. And business is changing: We&apos;re about to start moving even faster.</description>
	</item>
	<item>
		<title>Succeeding as a Technical Writer</title>
		<link>http://tc.eserver.org/13565.html</link>
		<guid>http://tc.eserver.org/13565.html</guid>
		<description>I&apos;ll start with a list of rules that have served me in good stead over my entire career. Some are common sense, and others may sound a little extreme or radical to your ears. That&apos;s okay. They&apos;ve worked for me.</description>
	</item>
	<item>
		<title>Where Can You Go from Here?</title>
		<link>http://tc.eserver.org/13569.html</link>
		<guid>http://tc.eserver.org/13569.html</guid>
		<description>Where can you go from technical writing? Someone once told me that once you&apos;re a tech writer, you&apos;re always a tech writer. I think that&apos;s a load of hooey.</description>
	</item>
	<item>
		<title>The WriteThinking Newsletter</title>
		<link>http://tc.eserver.org/13396.html</link>
		<guid>http://tc.eserver.org/13396.html</guid>
		<description>A free weekly e-mail newsletter for the practical technical writer. Contains articles, book and software reviews, links to resources, and a large weekly jobs list. Published every Monday.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Knowles,_Michael.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>