<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Communication&gt;Technical Writing</title>	<link>http://tc.eserver.org/dir/Articles/Communication/Technical-Writing</link>
	<description>A listing of the most recently indexed works about Articles and Communication and Technical Writing in the field of technical communication (and technical writing).</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-10 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>Articles&gt;Communication&gt;Technical Writing</title>
		<link>http://tc.eserver.org/dir/Articles/Communication/Technical-Writing</link>
	</image>
	<item>
		<title>The Effect of the Organization’s Culture on Conversational Technical Writing</title>
		<link>http://tc.eserver.org/36759.html</link>
		<guid>http://tc.eserver.org/36759.html</guid>
		<description>Lately, when I’m writing for training, I’m thinking of actually having a conversation, of talking to a real person. When I write other documents, for some reason I’m not thinking this way. It’s a problem because my user assistance content probably comes out dry as a desert in summer. In addition to not being as conscious of users as I should, perhaps there are a couple of organizational factors affecting my mindset.</description>
	</item>
	<item>
		<title>The Importance of Communication Skills over Technical Skills</title>
		<link>http://tc.eserver.org/36431.html</link>
		<guid>http://tc.eserver.org/36431.html</guid>
		<description>A developer who does some tech writing gets paid more than the full-time tech writer is because the first guy is still a developer. Developers get paid more than technical communicators most of the time (or all the time, most likely). I think a programmer with some interest or a bit of practice in technical writing getting a job ahead of experienced technical writers may be a signal that management (or HR) doesn’t know what they’re supposed to be looking for in a technical writer.</description>
	</item>
	<item>
		<title>Addressing Resistance to Change in Policy and Procedure Writing</title>
		<link>http://tc.eserver.org/36295.html</link>
		<guid>http://tc.eserver.org/36295.html</guid>
		<description>Policy writing and procedure writing is challenging because of the mechanics involved. Words must be carefully chosen; nuances must be considered. Understanding the mechanics of writing these documents is critical; however, an often overlooked aspect should be dealt with before the first word is written. How can policy and procedure writing tiptoe around the elephant in the room that everyone is trying to ignore?</description>
	</item>
	<item>
		<title>Safety Warnings in Tractor Operation Manuals, 1920-1980: Manuals and Warnings Don&apos;t Always Work</title>
		<link>http://tc.eserver.org/36262.html</link>
		<guid>http://tc.eserver.org/36262.html</guid>
		<description>This article studies the history of one of the most critical, unresolved problems in mechanized agriculture: Tractor operators do not read the operation manuals, particularly the safety warnings. The result: sustained death and injury of these operators for well over a century. The article tracks the emergence of warnings in tractor operator manuals found in the archives of the University of Nebraska Tractor Test Museum (1919-2007), describes efforts of manufacturers during this time to alert operators to dangers associated with tractors, and concludes with a summary of current research on tractor safety and the problem that remains unresolved: how to change the culture of farmers who use these implements, critical to agriculture production, to encourage them to read and follow safety practices.</description>
	</item>
	<item>
		<title>White Paper Writing: Strategies for Success</title>
		<link>http://tc.eserver.org/35472.html</link>
		<guid>http://tc.eserver.org/35472.html</guid>
		<description>White papers are a fundamental part of your marketing arsenal. And if you think technical writers don&apos;t need to worry about marketing, read on to see why white paper writing is an essential skill, and how to turn a ho-hum paper into a killer communications tool.</description>
	</item>
	<item>
		<title>Why Tech Writers Need To Understand Business: Yet Another Example...</title>
		<link>http://tc.eserver.org/34802.html</link>
		<guid>http://tc.eserver.org/34802.html</guid>
		<description>For some years, people, myself included, have noted the lack of interest, even disdain, that many tech writers have for business issues. This reduces these writers&apos; ability to affect company decisions, including decisions that may affect them. Writers from fine arts or English backgrounds can rarely discuss cost-justification in finance terms, so they have little input on buying decisions.</description>
	</item>
	<item>
		<title>Writing For the Market</title>
		<link>http://tc.eserver.org/34403.html</link>
		<guid>http://tc.eserver.org/34403.html</guid>
		<description>If you’re a generalist, as most tech writers are, you write about many things in a variety of media with a number of objectives. Each new job involves determining who your audience is, what their needs are, and how your product or service can satisfy those needs. Then you need to recognize, understand, and adjust your writing so one time it appeals to the camper and the next time to the business owner.</description>
	</item>
	<item>
		<title>Toward a Post-Technê: Or, Inventing Pedagogies for Professional Writing</title>
		<link>http://tc.eserver.org/33621.html</link>
		<guid>http://tc.eserver.org/33621.html</guid>
		<description>This article examines the concept of technê in relation to situatedness. Technê is conceived as techniques for situating bodies in contexts. Although many theorists and practitioners in technical communication are working from ecological and posthuman perspectives with regard to interface designs, this article argues for extending those perspectives to workplace and classroom situations. Starting from a &#xD;Heideggerian reading of technê, the article moves toward the concept of post-technê, which remakes pedagogical techniques for writing and inventing in institutional contexts.</description>
	</item>
	<item>
		<title>An Ergonomic Format for Short Reporting in Scientific Journals Using Nested Tables and the Deming&apos;s Cycle</title>
		<link>http://tc.eserver.org/32328.html</link>
		<guid>http://tc.eserver.org/32328.html</guid>
		<description>The typical structure of a scientific report involves highly standardized sections. The key concept of a scientific report is the reproducibility of results. Because not only clarity but also conciseness is a tool for the advancement of science, a new format using nested tables is proposed with the aim of improving the design of short reports in scientific journals, namely short communications, short technical reports, case reports, etc. This format is based on the ergonomic philosophy of visual encyclopaedias (one topic, one page) and on the quality system of the Deming&apos;s cycle (plan--do--check--act) for continuous improvement. This new editing tool has several advantages over existing forms, because it provides quick and ergonomic, reader-friendly research reports that, at the same time, would render a saving in terms of available space and publishing costs of the printed version of scientific journals.</description>
	</item>
	<item>
		<title>Writing in the Corporate Workplace: How to Keep Your Writing Healthy at Work</title>
		<link>http://tc.eserver.org/31776.html</link>
		<guid>http://tc.eserver.org/31776.html</guid>
		<description>Make sure you know what you&apos;re talking about. This means understanding the big picture as well as sweating the small stuff. When interviewing subject matter experts, don&apos;t accept high-level answers to questions. Drill down to the details.</description>
	</item>
	<item>
		<title>Modeling Rhetoric in Scientific Publications</title>
		<link>http://tc.eserver.org/31700.html</link>
		<guid>http://tc.eserver.org/31700.html</guid>
		<description>Despite the advent of computer-centered ways of creating and accessing scientific knowledge, the format of the scientific research article has remained basically unchanged. We have developed a model of a more appropriate form for research publications to structure scientific articles, based on a rhetorical structure which is ubiquitous in (natural) science papers. The model has three components: defining rhetorical elements inside the documents, the identification of the argumentational relationships between these elements; and the connection of data elements and entities to external sources.</description>
	</item>
	<item>
		<title>They&apos;ll Thank You for Sharing: Make Those Reports, Memos and White Papers Clear and Readable</title>
		<link>http://tc.eserver.org/31284.html</link>
		<guid>http://tc.eserver.org/31284.html</guid>
		<description>Words, words, words. It seems as if we&apos;re being asked to write something every minute for every need and occasion. Your boss wants a report; your colleagues need a memo explaining a procedure; your clients send e-mails that need to be considered and answered; your company&apos;s products or services should be described in a descriptive white paper, and on and on.&#xD;&#xD;How can you deal with all that? Are there any general writing rules that apply to business writing of all sorts?</description>
	</item>
	<item>
		<title>Marketing Writing for Technical Products</title>
		<link>http://tc.eserver.org/30522.html</link>
		<guid>http://tc.eserver.org/30522.html</guid>
		<description>This workshop will examine the types of marketing materials that can give you creative experience. You&apos;ll learn how to adapt your skills and subject matter knowledge to these projects, how to plan and develop different types of materials, and how to identify opportunities for new types of communication.</description>
	</item>
	<item>
		<title>Writing for Technical and Business Decision-Maker Audiences</title>
		<link>http://tc.eserver.org/29728.html</link>
		<guid>http://tc.eserver.org/29728.html</guid>
		<description>The impact of any technical writing depends on the ability of the writer to understand and address the readers&apos; concern, and to deliver highly usable documents that are relevant to the audience. Especially when readers make business decisions about technology, based on technical communication, writers need to develop best practices for conducting their own audience analysis and writing with audience needs in mind. This paper introduces several likely audiences a technical writer is likely to encounter and makes a few practical recommendations for communicating to them with the intended impact.</description>
	</item>
	<item>
		<title>The Presentation of Safety Information in Product Manuals</title>
		<link>http://tc.eserver.org/29695.html</link>
		<guid>http://tc.eserver.org/29695.html</guid>
		<description>Technical communicators may be asked to design and develop safety information for a product manual. During this process, technical communicators can add value to the presentation of safety information. In addition to adhering to a manufacturer’s internal guideline for the content and formatting of safety information, other factors can be considered as well. This paper presents the following factors: (1) an overview of common failure-to-warn allegations, (2) an analysis of current practices in automotive owner’s manuals for presenting safety information, and (3) an update on a new ANSI Z535 consensus standard for the presentation of safety information in product manuals.</description>
	</item>
	<item>
		<title>The Art and Science of Policy and Procedure Writing and Publishing</title>
		<link>http://tc.eserver.org/29272.html</link>
		<guid>http://tc.eserver.org/29272.html</guid>
		<description>This is an informational site dedicated to topics relevant to writing and publishing business process knowledge, especially policies and procedures. The objective of this site is to openly share information about writing and publishing policies and procedures and other forms of business knowledge.</description>
	</item>
	<item>
		<title>Communication in Technology Transfer and Diffusion: Defining the Field</title>
		<link>http://tc.eserver.org/28418.html</link>
		<guid>http://tc.eserver.org/28418.html</guid>
		<description>Provides an introduction to our field’s connections with technology transfer and diffusion. Technology transfer, the complex social process that moves technology from bench to market, drives global economic growth; technology diffusion, the market-driven process by which innovations are adopted and implemented, follows similar patterns. Indeed, technology transfer and diffusion may be considered synonymous with the phenomenon of growth in a global economy.</description>
	</item>
	<item>
		<title>WhitePaperSource</title>
		<link>http://tc.eserver.org/27770.html</link>
		<guid>http://tc.eserver.org/27770.html</guid>
		<description>WhitePaperSource is a rich information source for white paper enthusiasts. It contains  news about the industry and a forum for discussing everything and anything about writing and marketing white papers.</description>
	</item>
	<item>
		<title>Course Design and Content Organization: A Psychological Perspective</title>
		<link>http://tc.eserver.org/27594.html</link>
		<guid>http://tc.eserver.org/27594.html</guid>
		<description>While a lot of effort is spent on designing an effective structure of the course, individual memory is seemingly the more untouched and somehow neglected aspect of our efforts to develop effective learning solutions. There is a need to add a psychological perspective of memory and retention/recollection to the way we design learning solutions.</description>
	</item>
	<item>
		<title>Issues in Technical Writing</title>
		<link>http://tc.eserver.org/26474.html</link>
		<guid>http://tc.eserver.org/26474.html</guid>
		<description>Now it is very important to recognize the vital role of a technical writer and services expected to provide to justify the requirements of this profession. Since technical writer is a sub category of technical communication, that involves other categories involved in documentation, like content writer, software configuration manager, technical editor, information designer and many more.</description>
	</item>
	<item>
		<title>Technical Writing vs. Science Communication: What is the Difference, and Why Should We Care?</title>
		<link>http://tc.eserver.org/24793.html</link>
		<guid>http://tc.eserver.org/24793.html</guid>
		<description>Many technical writer/editors at Los Alamos National Laboratory feel that we (and our colleagues at other institutions) do a good job of helping scientists communicate with each other, but we do not do so well in communicating with the general public. We have done a literature search and interviewed target audience members to learn how to better communicate science. Our research falls into the four following areas: the need for this special knowledge, characterization of audiences, communications strategies, and evaluation of the resulting communication products.</description>
	</item>
	<item>
		<title>Memos</title>
		<link>http://tc.eserver.org/23535.html</link>
		<guid>http://tc.eserver.org/23535.html</guid>
		<description>A memo is a concise document that conveys essential information about your accomplishment(s). All memos at Ohio University should be written in third person.</description>
	</item>
	<item>
		<title>Current Status Of Business And Technical Writing Courses In English Departments</title>
		<link>http://tc.eserver.org/23313.html</link>
		<guid>http://tc.eserver.org/23313.html</guid>
		<description>We have heard a great deal of talk in recent years about the growth of business and technical writing courses in English departments. But very little, if any, factual information exists on how much enrollments have grown and whether they are expected to grow in the near future. Furthermore, no study has attempted to assess the impact these relatively new, rapidly expanding courses are having and will continue to have on English departments and their faculty members.</description>
	</item>
	<item>
		<title>Testing the Role of Technical Information in Public Risk Perception</title>
		<link>http://tc.eserver.org/22281.html</link>
		<guid>http://tc.eserver.org/22281.html</guid>
		<description>Through experiments with simulated news stories about hazardous materials release, this study finds that providing technical detail about health effects may be less useful than keeping citizens current on the agency&apos;s strategies for dealing with problems and other behaviors by officials.</description>
	</item>
	<item>
		<title>A Virtual Conversation on Bernadette Longo&apos;s Spurious Coin: A History of Science, Management, and Technical Writing</title>
		<link>http://tc.eserver.org/22140.html</link>
		<guid>http://tc.eserver.org/22140.html</guid>
		<description>A collection of responses to Bernadette Longo&apos;s &lt;i&gt;Spurious Coin&lt;/i&gt;.</description>
	</item>
	<item>
		<title>Legal Communication in Technical Communication Programs: Worth Thinking About?</title>
		<link>http://tc.eserver.org/21549.html</link>
		<guid>http://tc.eserver.org/21549.html</guid>
		<description>What, if anything, should technical communication programs teach their students about the nature of law and the production of legal discourse? When is technical writing also legal writing, and vice versa; when is legal writing (really) technical? Are there distinctions worth maintaining and dissolving here? Do lawyers&apos; relationships to, and problems with, legal writing contexts and processes parallel in important ways technical writers&apos; relationships to, and problems with, technical writing contexts and processes? If they do, is a conversation between the disciplines worth institutionalizing, at least experimentally, in each other&apos;s programs?</description>
	</item>
	<item>
		<title>Contracting and Consulting for Policies and Procedures Engagements</title>
		<link>http://tc.eserver.org/20760.html</link>
		<guid>http://tc.eserver.org/20760.html</guid>
		<description>As the number of persons employed by some U.S. organizations declined since the late 1980s, so have employment opportunities for Policies &amp; Procedures (P&amp;P) practitioners. During this period, the number of contractors and consultants has increased to meet the needs of newly changed organizations. A useful way for P&amp;P practitioners to learn how they can provide&#xD;contracting and consulting services is to understand three&#xD;roles in leveraging such services: an extra pair of hands,&#xD;expert, and collaborator.</description>
	</item>
	<item>
		<title>Expand Your Income by Writing for Magazines</title>
		<link>http://tc.eserver.org/20323.html</link>
		<guid>http://tc.eserver.org/20323.html</guid>
		<description>Technical writers are well-equipped to write how-to articles for magazines. There are many markets for&#xD;informational articles, and by creating a well-crafted&#xD;query, a competent technical writer can get an&#xD;assignment. This work is ideal for generating part-time&#xD;income and it provides a more creative outlet for writers..&#xD;Getting ideas for good articles is as simple as following&#xD;oneâ*™s own interests. Writing for magazines can become a&#xD;lucrative â*œsecondâ** career for technical writers.</description>
	</item>
	<item>
		<title>Medical Technical Writing</title>
		<link>http://tc.eserver.org/19639.html</link>
		<guid>http://tc.eserver.org/19639.html</guid>
		<description>In a multibillion-dollar-per-yearcindustry, medical technical writers&#xD;are well situated between companies that manufacture drugs and&#xD;medical equipment and the federal government, which regulates&#xD;the manufacture of drugs and medical equipment. The government requires that these companies produce specific&#xD;types of documents, which must be of a&#xD;very high standard. This situation creates&#xD;lucrative opportunities for technical&#xD;writers.</description>
	</item>
	<item>
		<title>Nuclear Information: One Rhetorical Moment in the Construction of the Information Age</title>
		<link>http://tc.eserver.org/14053.html</link>
		<guid>http://tc.eserver.org/14053.html</guid>
		<description>Since the late 1970&apos;s we have been said to be living in the information age, and that name has stuck, with the phrase increasingly appearing throughout the closing decades of the millennium. The slogan, like all slogans, attempts to assert unity in the face of complexity; nonetheless, it captures, better than most such slogans, a dominant theme of almost all aspects of our everyday life. The slogan has its visual icons in advertising and journalism: binary bits flashing down wires and across the sky, tied to no location and independent of the humans who may need or use that information. Information has become an abstract universal, like atoms and electrons, to create or serve any entity, in no particular configuration, serving no particular purpose, gathered and used by no particular people (but of course provided or facilitated by specific companies who make this information their business). Information, however, is a human creation for human purposes, even if our devices now produce terrabytes of signals that travel only to other devices, never to be seen or touched by humans. This essay recovers a small piece of the history by which we constructed our understandings and uses of information, so that information has become pervasive in everyday life, needs, and action. It considers how information came to have major governmental and military meanings to the U.S. public during World War Two and after, and how an anti-nuclear test activist group asserted an alternative understanding of information to foster public opposition to government policy. This rhetorical reconstruction of information advanced a culture of citizen information, validated by citizen scientists to serve the needs and concerns of citizens, which pervaded the anti-war, environmental, and consumer movements that became our everyday reality in the second half of the century. Such citizen information embodies multiple assumptions about threats to everyday life, the necessity of reliable and up-to-date information for action to oppose the threats, large institutions whose interests are served by the threatening situation and which limit access to relevant information, science as an independent and objective source of information, and the responsibilities of a citizen to be informed.</description>
	</item>
	<item>
		<title>Writing Material Safety Data Sheets Using the American National Standard for Hazardous Industrial Chemicals-MSDS Preparation</title>
		<link>http://tc.eserver.org/10281.html</link>
		<guid>http://tc.eserver.org/10281.html</guid>
		<description>This article presents the history of the ANSI standard for preparation of Material Safety Data Sheets, and then provides a section-by-section guide to preparing MSDSs that comply with the standard.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Communication/Technical-Writing.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>