<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Minimalism</title>	<link>http://tc.eserver.org/dir/Minimalism</link>
	<description>A listing of the most recently indexed works about Minimalism 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>Minimalism</title>
		<link>http://tc.eserver.org/dir/Minimalism</link>
	</image>
	<item>
		<title>Quick-Start Guides Require a Minimalist Mindset</title>
		<link>http://tc.eserver.org/35714.html</link>
		<guid>http://tc.eserver.org/35714.html</guid>
		<description>The point of a quick-start guide is, as the name says, to help the users get on their feet as fast as possible. This requires the writer to ask, “What is the absolute minimum that someone needs in order to get started?” The next best question is “What is the user going to do the most often?”</description>
	</item>
	<item>
		<title>Minimal Procedure Content: Reasoning</title>
		<link>http://tc.eserver.org/35634.html</link>
		<guid>http://tc.eserver.org/35634.html</guid>
		<description>The procedure I wrote about creating a Twitter list uses abbreviated content. This post describes the reasoning behind and decisions made in writing the topic.</description>
	</item>
	<item>
		<title>The RoboColum(n)</title>
		<link>http://tc.eserver.org/35588.html</link>
		<guid>http://tc.eserver.org/35588.html</guid>
		<description>With in excess of ten years front line authoring experience and many more producing training documentation, I have a passion for language, its use and its odities. I was an Account Manager for a computer bureau providing a service to the advertising industry prior to taking the plunge into technical authoring. A large part of this was the production of technical training material for the ad-hoc customer training and classroom led courses held in the company’s training suite.</description>
	</item>
	<item>
		<title>Minimizing Documentation</title>
		<link>http://tc.eserver.org/35535.html</link>
		<guid>http://tc.eserver.org/35535.html</guid>
		<description>Is less always more? I’m not sure. But if Apple’s minimalistic designs are any indicator of trends, minimalism in documentation is something to pay attention to. Here are five ideas for minimizing documentation.</description>
	</item>
	<item>
		<title>Minimizing Complexity In User Interfaces</title>
		<link>http://tc.eserver.org/35459.html</link>
		<guid>http://tc.eserver.org/35459.html</guid>
		<description>Clean. Easy to use. User-friendly. Intuitive. This mantra is proclaimed by many but often gets lost in translation. The culprit: complexity. How one deals with complexity can make or break an application. A complex interface can disorient the user in a mild case and completely alienate them in an extreme case. But if you take measures first to reduce actual complexity and then to minimize perceived complexity, the user will be rewarded with a gratifying experience.</description>
	</item>
	<item>
		<title>Keep It Simple: Streamline Your Documentation to Make it More Effective</title>
		<link>http://tc.eserver.org/35468.html</link>
		<guid>http://tc.eserver.org/35468.html</guid>
		<description>Are we giving users the help they need, in the way they need it? Go minimal.</description>
	</item>
	<item>
		<title>Three Tweets for the Web</title>
		<link>http://tc.eserver.org/35441.html</link>
		<guid>http://tc.eserver.org/35441.html</guid>
		<description>The relative decline of the book is part of a broader shift toward short and to the point. Small cultural bits—written words, music, video—have never been easier to record, store, organize, and search, and thus they are a growing part of our enjoyment and education. The new brevity has many virtues.</description>
	</item>
	<item>
		<title>A Strident Defense of Mediocre Formatting</title>
		<link>http://tc.eserver.org/35218.html</link>
		<guid>http://tc.eserver.org/35218.html</guid>
		<description>Formatting automation removes cost from the process of creating and delivering content. For technical documents that change often and are perhaps delivered in multiple languages, it removes a lot of cost. Essentially, we can produce documents inexpensively and give more people access to them as a direct result of lower cost, or we can climb on our typographic high horse and whine about word spacing. I’m with the noisome fanboys.</description>
	</item>
	<item>
		<title>Duct Tape Technical Writers</title>
		<link>http://tc.eserver.org/35219.html</link>
		<guid>http://tc.eserver.org/35219.html</guid>
		<description>In reality, the user just wants a brief, clear explanation of a concept or task. The user will glance and skim — reading behaviors hardly worthy of the elitist grammarian who argues the finer points of “which” versus “that” in restrictive clauses.</description>
	</item>
	<item>
		<title>Can You Design Your Way to a “No User Documentation” Approach?</title>
		<link>http://tc.eserver.org/35195.html</link>
		<guid>http://tc.eserver.org/35195.html</guid>
		<description>For simple, commonly known actions in a closed environment, you probably can design your way to a “no user documentation” approach. Good design can also lead to less documentation. However, customers may expect to do more than that with a product and, in those situations, documentation can play a key role in meeting those expectations.</description>
	</item>
	<item>
		<title>Simplicity Trumps Complexity….Mostly!</title>
		<link>http://tc.eserver.org/35203.html</link>
		<guid>http://tc.eserver.org/35203.html</guid>
		<description>One of the tips for creating a help project is to keeps things simple. This applies as much to the content as it does to the manner in which it is produced. The tool used to produce it has a big bearing on how simple the documentation process is of course but sometimes you just have to bend the rules.</description>
	</item>
	<item>
		<title>Sometimes, Simple is the Way to Go</title>
		<link>http://tc.eserver.org/35125.html</link>
		<guid>http://tc.eserver.org/35125.html</guid>
		<description>I’m advocating boiling the documentation down to the essentials. Remove any superfluous material. Tell the user how to do things with a piece of software or a gadget, not what that something can do. You might wind up with documentation that’s just a set of procedures connected together by linking material and cross references. Don’t bog them down with what’s not necessary for them to get things done in a fast and efficient way.</description>
	</item>
	<item>
		<title>More Tips for Writing Well</title>
		<link>http://tc.eserver.org/35090.html</link>
		<guid>http://tc.eserver.org/35090.html</guid>
		<description>Be vicious when you edit. Vicious. Follow these recommendations with zealous fervor. They help your writing say what it should in a way we’ll understand.</description>
	</item>
	<item>
		<title>Plain English Is the Best Policy</title>
		<link>http://tc.eserver.org/35026.html</link>
		<guid>http://tc.eserver.org/35026.html</guid>
		<description>The health care reform bill now under consideration in the House of Representatives includes a proposal that certain disclosures in insurance policies be made in “plain language.” Another piece of legislation now being considered by both houses of Congress would likewise require uniform and simplified coverage information, much like what’s required on nutritional labels. These are excellent proposals, but they do not go far enough. Plain-language disclosures of some policy information and consumer-friendly labels are no substitutes for making an entire policy readable.</description>
	</item>
	<item>
		<title>The Minimalist Principle: Omit Needless Things</title>
		<link>http://tc.eserver.org/35024.html</link>
		<guid>http://tc.eserver.org/35024.html</guid>
		<description>Minimalism is something people might strive for, but they don’t know where to start.</description>
	</item>
	<item>
		<title>Write Everything as if Writing for the Web</title>
		<link>http://tc.eserver.org/34978.html</link>
		<guid>http://tc.eserver.org/34978.html</guid>
		<description>Writing tightly means packing the most information into the least amount of space. It&apos;s not easy, but when you do it, the result is like magic. The key to being an effective writer is to keep what you’re writing short, to the point, and easy to read. Like the best writing on the Web.&#xD;</description>
	</item>
	<item>
		<title>Cut, Cut, Cut your Content and Procedures</title>
		<link>http://tc.eserver.org/34804.html</link>
		<guid>http://tc.eserver.org/34804.html</guid>
		<description>Sure. We’ve been reducing word count in procedures for some time. It’s time to do more, however. As noted in an earlier post, we have to think mobile. Think small screens and small devices. Screen real estate will be at a premium.</description>
	</item>
	<item>
		<title>The Myth of Simplicity and Complexity in Help Authoring</title>
		<link>http://tc.eserver.org/34577.html</link>
		<guid>http://tc.eserver.org/34577.html</guid>
		<description>Although simplicity is a noble ideal, and something like “simplify complexity” could be the mission statement of any technical writer, simplicity is in fact a complex undertaking. The interplay between simplicity and complexity is what technical writing is all about.</description>
	</item>
	<item>
		<title>Making Content Understandable: Inherent Usability in Plain Language</title>
		<link>http://tc.eserver.org/34510.html</link>
		<guid>http://tc.eserver.org/34510.html</guid>
		<description>Using an example from his personal life, Haller shows how government writing should be simplified to ensure that a reader can understand government documents. He also discusses the importance of passing the Brayley Bill, the plain language bill.</description>
	</item>
	<item>
		<title>Seven Interface Design Techniques to Simplify and De-Clutter Your Interfaces</title>
		<link>http://tc.eserver.org/34321.html</link>
		<guid>http://tc.eserver.org/34321.html</guid>
		<description>What is simplicity? Simplicity is the quality of being natural, plain and easy to understand. It is not surprising then that simplicity is often thrived for in user interface design. Most people naturally dislike complexity in devices and software. Yes, some people find joy in figuring out how something works, but for most of us, being unable to operate a device leads to wasted time and frustration, and that’s not a good thing.&#xD;&#xD;If you can take a complex device or a piece of software and somehow rearrange, reorganize and redesign the interface to make it easy to use and understand, then you’re well on the way to delivering a better user experience.&#xD;&#xD;In this article I’m going to talk about 7 practical techniques that you can utilize in web design to make your websites or web applications simpler and less cluttered.</description>
	</item>
	<item>
		<title>Writing Global English</title>
		<link>http://tc.eserver.org/34123.html</link>
		<guid>http://tc.eserver.org/34123.html</guid>
		<description>Unfortunately, there seems to be no such thing as simplicity-checking software - even remotely like the description above. Audience Dialogue tried to persuade a few software developers to make their fortunes by writing this software, but with no success so far. In the meantime, there are a few widely available tools to use.</description>
	</item>
	<item>
		<title>Speed Up Your Web Pages</title>
		<link>http://tc.eserver.org/34125.html</link>
		<guid>http://tc.eserver.org/34125.html</guid>
		<description>Do you want faster-loading Web pages? Learn how you can make the browsing experience better for dial-up users by reducing loading times by as much as 80 percent, in some cases.</description>
	</item>
	<item>
		<title>Professionalizing Plain Language: A Postcard on Current Developments</title>
		<link>http://tc.eserver.org/34130.html</link>
		<guid>http://tc.eserver.org/34130.html</guid>
		<description>With the passing of the Brayley Bill in Congress, the significance of plain language has become even more apparent to technical communicators. The author lays out a step-by-step plan to maintain the relevance of plain language as an important and necessary profession.</description>
	</item>
	<item>
		<title>Short and Simple Sentences</title>
		<link>http://tc.eserver.org/33961.html</link>
		<guid>http://tc.eserver.org/33961.html</guid>
		<description>When you’re writing for the web, try to keep your sentences under 20 words in length. Your content will be easier to read this way. This is because it’s easier to read a few short sentences than it is to read one big one.</description>
	</item>
	<item>
		<title>Hyped Web Stories Are Irrelevant</title>
		<link>http://tc.eserver.org/33448.html</link>
		<guid>http://tc.eserver.org/33448.html</guid>
		<description>The fads and big deals that get the press coverage are not important for running a workhorse website. To serve your customers, it&apos;s far better to emphasize simplicity and quality than to chase buzzwords.</description>
	</item>
	<item>
		<title>Plain English</title>
		<link>http://tc.eserver.org/33329.html</link>
		<guid>http://tc.eserver.org/33329.html</guid>
		<description>According to Plain English Campaign (www.plainenglish.co.uk), plain English is &quot;… something that the intended audience can read, understand and act upon the first time they read it. Plain English takes into account design and layout as well as language.&quot; Many organisations have found that plain English brings commercial advantages.</description>
	</item>
	<item>
		<title>Beyond Plain English</title>
		<link>http://tc.eserver.org/33333.html</link>
		<guid>http://tc.eserver.org/33333.html</guid>
		<description>Plain English is good for increasing the quality of written documents. Unfortunately, it has limits in many technical situations. We need a special form of language, known as a controlled language, to overcome those limits. One particular controlled language is ASD Simplified Technical English.</description>
	</item>
	<item>
		<title>Tools and Techniques for Working with Subject-Matter Experts to Create Plain Language Manuals</title>
		<link>http://tc.eserver.org/32694.html</link>
		<guid>http://tc.eserver.org/32694.html</guid>
		<description>This paper discusses tools and techniques for editors and writers who need to work with subject matter experts (i.e., engineers, programmers, accountants, etc.) to create plain language manuals.</description>
	</item>
	<item>
		<title>The Almighty Thud</title>
		<link>http://tc.eserver.org/32171.html</link>
		<guid>http://tc.eserver.org/32171.html</guid>
		<description>If you document everything, you are giving everything an equal weight. Do that for a complex system, and you are buried in detail. In any system there are some aspects that are more important than the others, key aspects of the system that once understood, will help someone to learn more. The art in documentation is to find how to document these aspects as clearly as possible. In this you emphasize these areas, and leave the details for the code.</description>
	</item>
	<item>
		<title>Clear, Brief and Bold: Will Strunk’s Legacy</title>
		<link>http://tc.eserver.org/32097.html</link>
		<guid>http://tc.eserver.org/32097.html</guid>
		<description>A masterpiece of concision so tightly written that you almost don&apos;t need to read past the table of contents.</description>
	</item>
	<item>
		<title>Fixing the Flaws in the Ten Principles of Clear Writing</title>
		<link>http://tc.eserver.org/31672.html</link>
		<guid>http://tc.eserver.org/31672.html</guid>
		<description>More importantly, most lists of ten principles of clear writing are not really principles at all, but rather tips and technique. Understanding why you are doing something, i.e., the benefit you will gain, helps ensure that you will actually do it and do it consistently. Too often, when we are told only what to do, we follow the instruction half-heartedly, inconsistently, or not at all.</description>
	</item>
	<item>
		<title>The Basics of Plain Language </title>
		<link>http://tc.eserver.org/31613.html</link>
		<guid>http://tc.eserver.org/31613.html</guid>
		<description>The purpose of this lesson is to introduce the basic concepts of plain language.</description>
	</item>
	<item>
		<title>Overcoming Word Inflation: The Benefits of Minimalist Design</title>
		<link>http://tc.eserver.org/31609.html</link>
		<guid>http://tc.eserver.org/31609.html</guid>
		<description>Writers are great inflators. We can take a simple half page describing a computer interface and in a few hours transform it into a 35-page document complete with glossaries, type conventions, overviews, introductions, mission statements, charts, clip art, and copyright pages full of disclaimers, trademark acknowledgements, and credits. The results will make the people in marketing and sales simply glow.</description>
	</item>
	<item>
		<title>The Plain Language Process: Steps for Effective Writing</title>
		<link>http://tc.eserver.org/31607.html</link>
		<guid>http://tc.eserver.org/31607.html</guid>
		<description>Effective writing does not come by chance. The creation of all documents, including forms, labels, websites, business letters, legal notices, manuals, procedures, reports, and proposals, usually involves the following key steps.</description>
	</item>
	<item>
		<title>Politics and the English Language</title>
		<link>http://tc.eserver.org/31610.html</link>
		<guid>http://tc.eserver.org/31610.html</guid>
		<description>If thought corrupts language, language can also corrupt thought. A bad usage can spread by tradition and imitation, even among people who should and do know better.</description>
	</item>
	<item>
		<title>Writing for Dollars, Writing to Please</title>
		<link>http://tc.eserver.org/31612.html</link>
		<guid>http://tc.eserver.org/31612.html</guid>
		<description>Call it the benefits of plain language. The literature contains studies about these benefits, but no one has ever collected and summarized the studies in a way that makes their full force apparent. As you read the summaries in this article, try to imagine the costs of poor writing — typified by officialese and legalese — in business, government, and law. The costs are almost beyond imagining, and certainly beyond calculating. If this evidence doesn&apos;t convince organizations and individual writers that plain language can change their fortunes, probably nothing will.</description>
	</item>
	<item>
		<title>Simplicity in Your Mind</title>
		<link>http://tc.eserver.org/31602.html</link>
		<guid>http://tc.eserver.org/31602.html</guid>
		<description>This article postulates that we cannot address the issue of simplification exclusively by analyzing the physical and computational parameters of technology. Instead, we must understand the goal of simplification in light of the knowledge, tasks, and processing-load demands on its users. We can approach simplicity as an engineering endeavor by controlling the impact on these three usage dimensions.</description>
	</item>
	<item>
		<title>Strunk and White Were Wrong: In Speechwriting, Personality Should Not Remain in the Background</title>
		<link>http://tc.eserver.org/31448.html</link>
		<guid>http://tc.eserver.org/31448.html</guid>
		<description>A speech generally needs personal language because it is delivered by a live human being whose words should not sound, as Wabash College Professor William Norwood Brigance put it, &quot;like an essay standing on its hind legs.&quot;</description>
	</item>
	<item>
		<title>Writing Government Policies and Procedures in Plain Language</title>
		<link>http://tc.eserver.org/30853.html</link>
		<guid>http://tc.eserver.org/30853.html</guid>
		<description>Ask ordinary citizens for an example of unreadable prose, and half of them will show you a government document; the other half will point to something written by a lawyer. As a government lawyer for more than 30 years, I wrote and reviewed safety regulations and technical policies and procedures for a major federal agency and eventually supervised other lawyers who did the same. Although I never met a technical document I didn&apos;t have the urge to rewrite, I always thought that what my fellow lawyers wrote was pretty clear. Then the plain-language movement came along, and I found I had a lot of room for improvement.</description>
	</item>
	<item>
		<title>AECMA Simplified English</title>
		<link>http://tc.eserver.org/30788.html</link>
		<guid>http://tc.eserver.org/30788.html</guid>
		<description>ASD-STE100 Simplified Technical English (formerly AECMA Simplified English) is a specification for writing aircraft documentation. The principles can be applied to all industry sectors. &#xD;&#xD;ASD-STE100 provides a set of writing rules and a dictionary of words and their meanings. It has a limited number of words; a limited number of clearly defined meanings for each word; a limited number of parts of speech for each word; a set of rules for writing text.&#xD;&#xD;This article outlines the standard, and shows how it helps to prevent ambiguity in text.</description>
	</item>
	<item>
		<title>To Draw and Hold Readers&apos; Attention, Apply a Hollywood Technique</title>
		<link>http://tc.eserver.org/30734.html</link>
		<guid>http://tc.eserver.org/30734.html</guid>
		<description>Find the one thing you want people to remember as you write a posting for a Web page, a subject line for an e-mail or a headline for a newsletter.</description>
	</item>
	<item>
		<title>To Be or Not To Be</title>
		<link>http://tc.eserver.org/30600.html</link>
		<guid>http://tc.eserver.org/30600.html</guid>
		<description>During this workshop, To Be or Not To Be, the workshop presenters demonstrate how getting rid of the verb &apos;to be&apos; increases accuracy, clarity and effectiveness in verbal communication. E-Prime originated in the field of general semantics; it consists of the English language, but excludes all forms of the verb &apos;to be.&apos; Practitioners in the field of general semantics have developed a number of techniques that promote clear understanding of communication in the world around us. The workshop presenters strive to create an environment for participants to learn the philosophical background and practical application of the English language subset known as E-Prime.</description>
	</item>
	<item>
		<title>Design Critique: On Plain Language</title>
		<link>http://tc.eserver.org/30579.html</link>
		<guid>http://tc.eserver.org/30579.html</guid>
		<description>An interview with Whitney Quesenbery about minimalism and plain language in user experience design.</description>
	</item>
	<item>
		<title>Reducing Complexity in Documentation</title>
		<link>http://tc.eserver.org/30561.html</link>
		<guid>http://tc.eserver.org/30561.html</guid>
		<description>With more emphasis being placed on customer satisfaction, technical writers need to focus on information strategies that will lead to happier customers. The complexity of the information is one common complaint of customers. Writers need to understand what customers think is complex. Then, writers need to develop strategies to combat these complexities.</description>
	</item>
	<item>
		<title>Minimalist Strategies for Improving User Documentation</title>
		<link>http://tc.eserver.org/30523.html</link>
		<guid>http://tc.eserver.org/30523.html</guid>
		<description>Those who use our products often ignore our best efforts at good documentation because they prefer to explore and learn by trial and error. Several researchers have developed document strategies that might help our users explore, learn, and recover from their errors. In order to use these strategies, however, technical communicators must get to know their users better, prototype their documentation, and test it on their users. Researchers need to tell us more about active learners and strategies for meeting their needs.</description>
	</item>
	<item>
		<title>A Study of Instructions for Information Systems: Variations on a Minimalist Theme</title>
		<link>http://tc.eserver.org/30377.html</link>
		<guid>http://tc.eserver.org/30377.html</guid>
		<description>To perform complex tasks, workplace computer users have to know how to control their programs and adapt program capabilities to the needs of their job goals and methods. I inquired into the instructional information that will help users learn such adaptive computing for complex data processing tasks by interviewing twelve experienced database users and analyzing twenty-five exchanges between experts and users on a database helpline network. Findings show that instructions may help users emulate expert approaches to adaptive computing for complex tasks by providing enough substantial technical information to help clarify task problems, goals, methods and analogies and presenting it in the form of rules of thumb, general procedures, and task-to-program explanations.</description>
	</item>
	<item>
		<title>Get Rid of the Babble</title>
		<link>http://tc.eserver.org/30362.html</link>
		<guid>http://tc.eserver.org/30362.html</guid>
		<description>Try to rid your writing, especially business writing, of unnecessary words. They take up space, look impressive only to naive readers, and say nothing.</description>
	</item>
	<item>
		<title>Advocating Plain Language: Thom Haller Discusses The Need For Clarity</title>
		<link>http://tc.eserver.org/30200.html</link>
		<guid>http://tc.eserver.org/30200.html</guid>
		<description>Plain language is clear, concise, and straightforward presentation of information. It is professional content structured to eliminate ambiguity and confusion in technical, government, and legal documents. Plain language allows readers to fully comprehend complex regulations, practices and instructions by requiring the language of bureaucracy to reflect the language of everyday speech.</description>
	</item>
	<item>
		<title>Style That Economizes Mental Energy</title>
		<link>http://tc.eserver.org/29888.html</link>
		<guid>http://tc.eserver.org/29888.html</guid>
		<description>Perhaps the most important feature of good writing style for scientific and technical communication is economy: writing that reduces the mental labor of the reader or user. I describe the principle of &quot;conservation of mental energy&quot; as developed by Herbert Spencer and extended by later studies in readability and psycholinguistics. Stylistic techniques that make reading easier have powerful application to the prose crafting that sci/tech communicators do every day. The idea of conserving mental energy, or being &quot;efficient&quot; in communication, gives us a touchstone for thinking about good style and a rationale for explaining why it&apos;s valuable.</description>
	</item>
	<item>
		<title>Achieving Minimalism through Interactive Multimedia</title>
		<link>http://tc.eserver.org/29734.html</link>
		<guid>http://tc.eserver.org/29734.html</guid>
		<description>Use interactive multimedia with text-based online documentation to achieve the minimalist model pioneered by instructional design guru John Carroll. Non-linear modules of &apos;real&apos; tasks help users get started fast, and quickly learn from any errors.</description>
	</item>
	<item>
		<title>How Important Is It To Streamline Communication</title>
		<link>http://tc.eserver.org/29546.html</link>
		<guid>http://tc.eserver.org/29546.html</guid>
		<description>Today&apos;s organizations must contend with increasingly complex communications environments that feature a wide array of communications methods. Employees, business partners, and customers communicate with one another through infinite combinations of phones, voice messaging, e-mail, fax, mobile clients, rich-media conferencing and other communication gadgets. One thing that is very important is proper communication. Whether you use the age-old snail mail or an email, the key to success lies in effective communication. One should get clear message as to what exactly is required or told by you. It is very important to streamline communication whether you are conversing in person or through an age-old snail mail, email or over the phone.</description>
	</item>
	<item>
		<title>The Nurnberg Funnel by John M. Carroll</title>
		<link>http://tc.eserver.org/29396.html</link>
		<guid>http://tc.eserver.org/29396.html</guid>
		<description>In the Nurnberg Funnel: Designing Minimalist Instruction, John Carroll presents some helpful ideas based on some useful research on how the initial self-instruction (often called &apos;tutorials&apos;) should be developed and written.</description>
	</item>
	<item>
		<title>Calculating Documentation Cruft</title>
		<link>http://tc.eserver.org/29359.html</link>
		<guid>http://tc.eserver.org/29359.html</guid>
		<description>It&apos;s easy to describe documentation cruft, and often easy to identify it once you see it, but it&apos;s hard to estimate how &apos;crufty&apos; a document actually is. Furthermore, it&apos;s often hard to convince the creators of a document that &apos;their baby&apos; isn&apos;t as beatiful as they believe it to be.</description>
	</item>
	<item>
		<title>Plain Language in Science: Signs of Intelligible Life in the Scientific Community?</title>
		<link>http://tc.eserver.org/29255.html</link>
		<guid>http://tc.eserver.org/29255.html</guid>
		<description>&apos;The importance of the work is inversely proportional to the number of people who can understand it&apos; is an outdated attitude in today&apos;s scientific arena. The trend toward plain language is gathering force in government, academe, and scientific journals.</description>
	</item>
	<item>
		<title>The Passive Voice and Social Values in Science</title>
		<link>http://tc.eserver.org/29077.html</link>
		<guid>http://tc.eserver.org/29077.html</guid>
		<description>This article claims that two social values in science--falsifiability of science and cooperation among scientists--determine use of passives in scientific communication. Scientists do not always develop valid theories, so scientific experiments must be amenable to being repeated and found invalid. This requires that the experiments must not be discrete events. Science is also a cooperative enterprise. As an integral part of science, scientific writing employs more passives than actives to focus on materials, methods, figures, processes, tables, concepts, etc. Use of passives to focus on the physical world helps de-emphasize discreteness of scientific experiments. Besides, it also helps remove personal qualifications of observing experimental results. Finally, it enhances cooperation among working scientists by providing a common knowledge base of scientific work--things and objects. Looked at in this way, the passive voice in scientific writing represents professional practices of science instead of personal stylistic choices of individual scientists.</description>
	</item>
	<item>
		<title>Plain English in Corporate Disclosures: Review and Implications for Consumers, Producers, and the Free-Market System</title>
		<link>http://tc.eserver.org/29040.html</link>
		<guid>http://tc.eserver.org/29040.html</guid>
		<description>The Internet is revolutionizing the investment world. There are clear benefits to these changes, including lower costs and faster access to the market for investors. There also are consequences to these changes when investors take risks without having access to clear, accurate, and full disclosures. In a free-market system, investors must have access to information they can understand and use autonomously to have full and equal access to the investment market. The Securities and Exchange Commission (SEC) recently passed a rule requiring businesses to use plain English to try and rid disclosures of their traditionally complex and ambiguous language. However, SEC&apos;s rule only addresses the front and back sides of prospectus disclosures. Consequently, the success of plain English will depend on the writer and business using it. Public corporations committed to using plain English will empower investors with the information they need to participate in the market freely and safely. In return, businesses will create a more effective and efficient free-market system by maximizing utility, benefiting producers, consumers, and the market as a whole.</description>
	</item>
	<item>
		<title>The Plain Style in the Seventeenth Century: Gender and the History of Scientific Discourse</title>
		<link>http://tc.eserver.org/29129.html</link>
		<guid>http://tc.eserver.org/29129.html</guid>
		<description>This article analyzes the statements on plain style made by Royal Society writers and seventeenth-century women writers. Using scholarship in feminist rhetorical theory, the article concludes that Royal Society plain stylists constructed scientific discourse as a masculine form of discourse by purging elements that were associated with femininity, such as emotional appeals. The article also discusses how women writers, particularly Margaret Cavendish, embraced a plain style more out of concern for their audience than out of a desire to eliminate undesirable feminine attributes. The implications of this historical study for understanding of current practice are noted.</description>
	</item>
	<item>
		<title>Simplicity Is Highly Overrated</title>
		<link>http://tc.eserver.org/28956.html</link>
		<guid>http://tc.eserver.org/28956.html</guid>
		<description>I am in favor of good design and attractive products. Easy to use products. But when it comes time to purchase, people tend to go for the more powerful products, and they judge the power by the apparent complexity of the controls. If that is what people use as a purchasing choice, we must provide it for them. While making the actual complexity low, the real simplicity high. That&apos;s an exciting design challenge: make it look powerful while also making it easy to use. And attractive. And affordable. And functional. And environmentally appropriate. Accessible to all. That&apos;s why I like design: it presents wonderful challenges.</description>
	</item>
	<item>
		<title>Simplicity: The Distribution of Complexity</title>
		<link>http://tc.eserver.org/28936.html</link>
		<guid>http://tc.eserver.org/28936.html</guid>
		<description>Achieving simplicity is not that simple when you are dealing with complex modern device design. Rob Tannen mused on lazy shortcuts, artificial constraints and Maeda&apos;s crusade on the complex.</description>
	</item>
	<item>
		<title>A Mathematical Theory of Communication</title>
		<link>http://tc.eserver.org/28868.html</link>
		<guid>http://tc.eserver.org/28868.html</guid>
		<description>The article entitled &apos;A Mathematical Theory of Communication&apos;, published in 1948 by mathematician Claude E. Shannon, was one of the founding works of the field of information theory. Shannon&apos;s paper laid out the basic elements of any digital communication.</description>
	</item>
	<item>
		<title>How to Create a Site Where Users Can Actually Find Information: Interview with Thom Haller</title>
		<link>http://tc.eserver.org/28792.html</link>
		<guid>http://tc.eserver.org/28792.html</guid>
		<description>Thom Haller, information architect and director of the Center for Plain Language, talks about how to create a site where users can actually find the information they&apos;re looking for.</description>
	</item>
	<item>
		<title>The Complexity of Simplicity</title>
		<link>http://tc.eserver.org/28671.html</link>
		<guid>http://tc.eserver.org/28671.html</guid>
		<description>Though many business strategies and publications continue to trumpet the power of simplicity in the design of digital products, for lots of companies and product teams, simplicity doesn&apos;t come easy.</description>
	</item>
	<item>
		<title>The Golden Rule</title>
		<link>http://tc.eserver.org/28407.html</link>
		<guid>http://tc.eserver.org/28407.html</guid>
		<description>Everything that goes into your web site must have a purpose. Every single element and decision must help users achieve their goals and support the site&apos;s goals.</description>
	</item>
	<item>
		<title>Simplicity</title>
		<link>http://tc.eserver.org/28409.html</link>
		<guid>http://tc.eserver.org/28409.html</guid>
		<description>Simple web design delivers huge benefits to designer, client and user. When a design doesn&apos;t seem to work, ask what should be taken away before asking what&apos;s missing.</description>
	</item>
	<item>
		<title>Simplicity</title>
		<link>http://tc.eserver.org/28213.html</link>
		<guid>http://tc.eserver.org/28213.html</guid>
		<description>Simplicity as a result of a creative process is &apos;the ultimate sophistication,&apos; as Leonardo da Vinci (1452-1519) said. Achieving simplicity is a difficult task not only in web-design but in every discipline (art, business, sports, science), yet simplicity for websites is a particular challenge as paper derived graphic design and usability on one side, marketing language and user expectations on the other side are in constant struggle with each-other.</description>
	</item>
	<item>
		<title>Keep your Web Pages Simple</title>
		<link>http://tc.eserver.org/28142.html</link>
		<guid>http://tc.eserver.org/28142.html</guid>
		<description>Simplicity is probably the most important underlying factor when it comes to the performance of any web page...whether it be your home page, an interior page, a sales page or a landing page. Here are six ways to keep your pages simple, and increase conversions.</description>
	</item>
	<item>
		<title>Dogmas Are Meant to be Broken: An Interview with Eric Reiss</title>
		<link>http://tc.eserver.org/28012.html</link>
		<guid>http://tc.eserver.org/28012.html</guid>
		<description>With training in everything from stage design to Egyptology to hypertext games to web projects, Reiss has had extensive practice in finding out what makes an experience work. Could these be the principles I&apos;ve been waiting for? I tracked down Reiss in Vancouver to find out.</description>
	</item>
	<item>
		<title>Putting the White Back in Strunk and White</title>
		<link>http://tc.eserver.org/28008.html</link>
		<guid>http://tc.eserver.org/28008.html</guid>
		<description>In web design screeds, the most commonly cited book is not what you might expect. It is not by Jakob Nielsen or Jeffrey Zeldman or Edward Tufte. It&apos;s not even on design or typography or code. It is a thin volume of guidelines on writing by a professor &apos;at the closing of the first world war&apos; and treasured by one student enough to put it into print. William Strunk was the professor, and E.B. White, author of Charlotte&apos;s Web, was that grateful student. White took the master&apos;s set of laws, removed some &apos;bewhiskered entries,&apos; corrected some errors, and added his own chapter at the end for &apos;those who feel English prose composition is not only a necessary skill but a sensible pursuit as well.&apos;</description>
	</item>
	<item>
		<title>The Elements of Style for Designers</title>
		<link>http://tc.eserver.org/27994.html</link>
		<guid>http://tc.eserver.org/27994.html</guid>
		<description>What if E.B. White had written &apos;Hanging Commas 99% Bad&apos; instead of a gentle list of reminders for young writers? Wodtke outlines how White&apos;s list of 22 reminders for writing can be just what young designers need.</description>
	</item>
	<item>
		<title>Simplified Technical English: STC Should Take the Lead</title>
		<link>http://tc.eserver.org/27986.html</link>
		<guid>http://tc.eserver.org/27986.html</guid>
		<description>Proposes that STC become involved in brainstorming ideas about Simplified Technical English, thus leading the way for clear, correct documentation.</description>
	</item>
	<item>
		<title>Write English the Way You Write Code</title>
		<link>http://tc.eserver.org/27754.html</link>
		<guid>http://tc.eserver.org/27754.html</guid>
		<description>For a profession full of sharp people, software engineering produces some hideous prose. How many times have you tried to read a technical document and failed because it was, in a very real sense, unreadable? It doesn&apos;t have to be this way. We technical types can improve our writing simply by applying some of those hard won coding skills to to those other, human, languages. I may be grammar challenged and spelling incapable, but writing code has taught me a few things about writing for people.</description>
	</item>
	<item>
		<title>Clear as Mud: The Plot Thickens</title>
		<link>http://tc.eserver.org/27733.html</link>
		<guid>http://tc.eserver.org/27733.html</guid>
		<description>A lot of the time, management-speak simply seems ridiculous. But campaigners for plain English say there is a more serious side to the issue.</description>
	</item>
	<item>
		<title>What is Plain English?</title>
		<link>http://tc.eserver.org/27739.html</link>
		<guid>http://tc.eserver.org/27739.html</guid>
		<description>Over the last two decades, a â€˜culture of clarityâ€™ has been gaining ground in many large organisations around the English-speaking world. In the United Kingdom, government departments, banks, insurance companies, local councils and others have come to realise that clear communication is actually a good idea. Instead of writing to impress or confuse, they are now writing to inform and explain. They are using plain English to do this.</description>
	</item>
	<item>
		<title>Conciseness is Key to Good Technical Documentation</title>
		<link>http://tc.eserver.org/27488.html</link>
		<guid>http://tc.eserver.org/27488.html</guid>
		<description>One of the most important and difficult parts of technical documentation concerns writing in a concise manner. Technical writing is different than writing fiction or magazine articles, where a mood may be set or--in some cases--where space must be filled. (People seldom buy thin books.)</description>
	</item>
	<item>
		<title>Usability Professionals’ Association Urges Consideration of Plain Language</title>
		<link>http://tc.eserver.org/27398.html</link>
		<guid>http://tc.eserver.org/27398.html</guid>
		<description>The Usability Professionals’ Association (UPA) wishes to express its support for plain language.</description>
	</item>
	<item>
		<title>&quot;More is Less&quot; for Many Home Entertainment System Users</title>
		<link>http://tc.eserver.org/27319.html</link>
		<guid>http://tc.eserver.org/27319.html</guid>
		<description>The days of a single remote for the TV or cable box are long gone. Like ants at a picnic, the control pads have invaded the nation&apos;s coffee tables.&#xD;&#xD;But unlike ants, remotes evolve rapidly. Not only are there more, but many sport added buttons and complexity added each time a model is upgraded with new features.</description>
	</item>
	<item>
		<title>But, Having Said That, ...</title>
		<link>http://tc.eserver.org/27212.html</link>
		<guid>http://tc.eserver.org/27212.html</guid>
		<description>A persistent rule of thumb in the programming trade is the 80/20 rule: &apos;80 percent of the useful work is performed by 20 percent of the code.&apos; As with gas mileage, your performance statistics may vary, and given the mensurational vagaries of body parts such as thumbs (unless you take the French pouce as an exact nonmetric inch), you may prefer a 90/10 partition of labor. With some of the bloated code-generating meta-frameworks floating around, cynics have suggested a 99/1 rule—if you can locate that frantic 1 percent. Whatever the ratio, the concept has proved useful in performance tuning.</description>
	</item>
	<item>
		<title>Usable Regulations: Legislation Pending in U.S. Congress</title>
		<link>http://tc.eserver.org/27056.html</link>
		<guid>http://tc.eserver.org/27056.html</guid>
		<description>On March 1, 2006, witnesses testified before the House Government Reform Committee’s Subcommittee on Regulatory Affairs. Their testimony supported what plain language and usability experts have long known: Clear, concise, easy to understand regulations will save the government (and taxpayers) time and money.</description>
	</item>
	<item>
		<title>Text Clarity Blog</title>
		<link>http://tc.eserver.org/26934.html</link>
		<guid>http://tc.eserver.org/26934.html</guid>
		<description>A blog about clearly communicating your message.</description>
	</item>
	<item>
		<title>The Paper Mountain Goes Online</title>
		<link>http://tc.eserver.org/26158.html</link>
		<guid>http://tc.eserver.org/26158.html</guid>
		<description>Ample research has proved that companies can save many thousands of dollars by rewriting key documents in plain English. Poor communication on the Web and intranet are squandering the time and money of many an organisation.</description>
	</item>
	<item>
		<title>Engineering Terms in Plain English</title>
		<link>http://tc.eserver.org/25999.html</link>
		<guid>http://tc.eserver.org/25999.html</guid>
		<description>Twenty terms from engineering writiting translated into the vernacular.</description>
	</item>
	<item>
		<title>The Great Myth That Plain Language Is Not Precise</title>
		<link>http://tc.eserver.org/25992.html</link>
		<guid>http://tc.eserver.org/25992.html</guid>
		<description>Occasionally, when you try to convert from legalese to plain language, someone will come forward and assert that you made a mistake. You missed something in the translation. You inadvertently changed the substance.</description>
	</item>
	<item>
		<title>High Tech Humor</title>
		<link>http://tc.eserver.org/25990.html</link>
		<guid>http://tc.eserver.org/25990.html</guid>
		<description>The remarkable growth of the information technology industry has created a tremendous opportunity for people with skill putting words on paper. Technical writers, once a rare and highly skilled position, are now as common as fruit flies—though they take up a lot more space. Yet the pay is pretty good considering how little work they actually do, so young English-major weenies desperate for employment continue to swarm around IT companies, hoping for a bit of rotting fru—er, looking for a plum position.</description>
	</item>
	<item>
		<title>A History of Plain Language in the United States Government</title>
		<link>http://tc.eserver.org/25991.html</link>
		<guid>http://tc.eserver.org/25991.html</guid>
		<description>Awareness of the need for clear language isn&apos;t new in the US government.</description>
	</item>
	<item>
		<title>Nine Easy Steps to Longer Sentences</title>
		<link>http://tc.eserver.org/26001.html</link>
		<guid>http://tc.eserver.org/26001.html</guid>
		<description>Are you tired of short, direct, and simple sentences that seem to take forever to fill up a page? Are you paid by the word? In either case you can benefit by increasing the number of words in your sentences and the bulk of your writing. And it&apos;s easy if you just follow nine simple steps, many of which you may already know and practice.</description>
	</item>
	<item>
		<title>Scientists Need Plain Language</title>
		<link>http://tc.eserver.org/25994.html</link>
		<guid>http://tc.eserver.org/25994.html</guid>
		<description>Expresses concisely why scientists need to use plain language when they write for the public.</description>
	</item>
	<item>
		<title>Signs of Intelligible Life</title>
		<link>http://tc.eserver.org/25996.html</link>
		<guid>http://tc.eserver.org/25996.html</guid>
		<description>Looks at a number of institutions that are finding ways to insert plain English into communication between scientists and the public, as well as among scientists of different disciplines.</description>
	</item>
	<item>
		<title>Wanted: Articulate Scientists</title>
		<link>http://tc.eserver.org/25997.html</link>
		<guid>http://tc.eserver.org/25997.html</guid>
		<description>This article outlines the benefits you can realize by articulating your science clearly and succinctly; next time, we&apos;ll look at how and why several academic and government institutions as well as some publications are encouraging this trend.</description>
	</item>
	<item>
		<title>Writing Effective Letters</title>
		<link>http://tc.eserver.org/26003.html</link>
		<guid>http://tc.eserver.org/26003.html</guid>
		<description>Always start by putting your main message up front. Some people feel that bad news should be buried. But research shows that readers will always look for the bottom line.</description>
	</item>
	<item>
		<title>Writing Reader-Friendly Documents</title>
		<link>http://tc.eserver.org/26002.html</link>
		<guid>http://tc.eserver.org/26002.html</guid>
		<description>The traditional way of writing government documents has not worked well.  Too often, complicated and jargon filled documents have resulted in frustration, lawsuits, and a lack of trust between citizens and their government. To overcome this legacy, we have a great responsibility to communicate clearly.</description>
	</item>
	<item>
		<title>So You Want a Website: Tips for Diving into the Internet Ocean Without Getting Drowned</title>
		<link>http://tc.eserver.org/25957.html</link>
		<guid>http://tc.eserver.org/25957.html</guid>
		<description>Practical advice for anyone trying to find a good web designer. A few semi-technical topics, but mostly plain English pointers.</description>
	</item>
	<item>
		<title>Minimalism</title>
		<link>http://tc.eserver.org/25847.html</link>
		<guid>http://tc.eserver.org/25847.html</guid>
		<description>Links to resources about the Minimalist Model applied to documentation and training.</description>
	</item>
	<item>
		<title>Minimalism and Documentation</title>
		<link>http://tc.eserver.org/25848.html</link>
		<guid>http://tc.eserver.org/25848.html</guid>
		<description>What is minimalism? Is minimalist documentation &apos;risky,&apos; and if so, what can be done to mitgate the risk? Was the structure of Windows 95&apos;s Help based on John Carroll&apos;s Minimalist Model or was &apos;the result&apos; more a Microsoft business decision -- or a bit of both?</description>
	</item>
	<item>
		<title>Plain English Campaign</title>
		<link>http://tc.eserver.org/25845.html</link>
		<guid>http://tc.eserver.org/25845.html</guid>
		<description>Plain English Campaign is an independent pressure group fighting for public information to be written in plain English.</description>
	</item>
	<item>
		<title>Adopting Minimalism in a Corporate Environment</title>
		<link>http://tc.eserver.org/25126.html</link>
		<guid>http://tc.eserver.org/25126.html</guid>
		<description>Minimalism is more a methodology or set of principles than a set of measurable qualities. In order for your writers to move to a minimalist approach to documentation, you must be able to explain what you mean by the term and what you expect from your writers.</description>
	</item>
	<item>
		<title>Designing Minimalist Principles Into User Interfaces</title>
		<link>http://tc.eserver.org/25061.html</link>
		<guid>http://tc.eserver.org/25061.html</guid>
		<description>Designing a user interface using minimalist principles for guided exploration can reduce the amount of paper and text necessary to document the system. Graphics in the interface can help the user grasp the concepts of the system, while dialog boxes, status information, and error messages can aid in recognition of success and recovery from errors. Online help can then be used as a backup for users if they get stuck. Reducing text and paper can reduce translation and printing costs, making this process very attractive.</description>
	</item>
	<item>
		<title>Good Legal Writing: of Orwell and Window Panes</title>
		<link>http://tc.eserver.org/25004.html</link>
		<guid>http://tc.eserver.org/25004.html</guid>
		<description>George Orwell once wrote that `[g]ood prose is like a window pane.&apos; What I take Orwell to have meant by that remark is that when people read good prose, it makes them feel as if they&apos;ve `seen&apos; something more clearly.</description>
	</item>
	<item>
		<title>Downsizing Documentation: Meeting the Challenge</title>
		<link>http://tc.eserver.org/24890.html</link>
		<guid>http://tc.eserver.org/24890.html</guid>
		<description>The redesign of the Microsoft Windows operating system along with a shrinking page count and Help file-size allocation, presented Windows User Education with a unique opportunity. We not only redesigned our entire documentation model, we also changed and improved our authoring tools. And, along the way, we changed how we did our work.</description>
	</item>
	<item>
		<title>Using a Plain Language Assessment Tool to Improve Business Communication</title>
		<link>http://tc.eserver.org/24276.html</link>
		<guid>http://tc.eserver.org/24276.html</guid>
		<description>Our company has been involved in a joint public/private sector initiative to bring the benefits of plain language campaigns to business communication. For the project we developed a plain language assessment tool that identifies problem documents, estimates costs associated with poor documents, analyzes their usability, profiles their authors and readers, and helps create action plans for improvement. Two organizations have run pilot projects with the assessment tool, and we did follow up research on them and on some organizations that  were exposed to the tool in a workshop setting. The tool is an effective vehicle for improving business documents and performance.</description>
	</item>
	<item>
		<title>The Zen of Minimalism: Designing a Top-of-Class Manual for Beginners and Advanced Users</title>
		<link>http://tc.eserver.org/24120.html</link>
		<guid>http://tc.eserver.org/24120.html</guid>
		<description>Can using minimalist documentation improve accuracy and learning speed for beginners as well as for advanced users? I tested this question using Microsoft Access for Windows 95 ® and three different third-party manuals explaining this product. Then I set up three main tasks for the user in a usability test. For each task, I provided the task description in blue type, and then copied the appropriate documentation in black. Documentation for each of the three tasks was reprinted from a different book.</description>
	</item>
	<item>
		<title>A Critical Assessment of the Minimalist Approach to Documentation</title>
		<link>http://tc.eserver.org/24090.html</link>
		<guid>http://tc.eserver.org/24090.html</guid>
		<description>Carroll&apos;s (1991) minimal manual has been considered an important advance in teaching first-time users the basics of computer programs. Unfortunately, it is not very clear what minimalism really means. Practitioners, for example, will find it difficult to create their own minimal manual because the principles of minimalism have not been described in enough detail (see Horn, 1992; Tripp, 1990). It is also not yet settled that a minimalist approach is the most effective one because critical experiments have hardly been conducted. This study therefore closely examines the minimalist principles and claims. This paper describes the basic ideas of minimalism, its design principles and how they can be operationalized. A parallel is drawn between a minimalist and constructivist perspective on learning and instruction. Like minimalism, constructivism places a high value on experience-based learning in context-rich environments. Like minimalism, it stresses the need to capitalize on the learner&apos;s prior knowledge as much as possible. And like minimalism, constructivists urge learners to follow their own plans and goals, to make inferences, and to abstract principles from what they experience (see Duffy &amp; Jonassen, 1991, 1992). An experiment is reported that examines the claims of minimalism. Strong and significant gains on several factors were found, all favoring the minimal manual over a control (conventional) manual. The discussion points to several issues that minimalism has yet to address.</description>
	</item>
	<item>
		<title>From Plain English to Global English</title>
		<link>http://tc.eserver.org/23941.html</link>
		<guid>http://tc.eserver.org/23941.html</guid>
		<description>Make your documents easy for EFL users to read and understand, and communicate successfully with people all over the world.&#xD;&#xD;About one billion people use English as a foreign language (EFL). You can avoid most pitfalls of cross-cultural communication by using global English.</description>
	</item>
	<item>
		<title>Answering the Critics of Plain Language</title>
		<link>http://tc.eserver.org/23903.html</link>
		<guid>http://tc.eserver.org/23903.html</guid>
		<description>Plain language has to do with clear and effective communication -- nothing more or less. It does, though, signify a new attitude and a fundamental change from past practices.</description>
	</item>
	<item>
		<title>How To Write Well</title>
		<link>http://tc.eserver.org/23917.html</link>
		<guid>http://tc.eserver.org/23917.html</guid>
		<description>The phrase &apos;Plain English&apos; (although widely used) is a little misleading. It is nothing to do with the English language as such. The principles outlined here apply to writing in any language. A more accurate expression is &apos;plain language&apos;.</description>
	</item>
	<item>
		<title>How You Can Make Plain English Work for You</title>
		<link>http://tc.eserver.org/23918.html</link>
		<guid>http://tc.eserver.org/23918.html</guid>
		<description>Plain English is good, clear writing which  communicates as simply and effectively as possible. But  it is not a childish or simplistic form of English.</description>
	</item>
	<item>
		<title>Plain Language: What Is It?</title>
		<link>http://tc.eserver.org/23916.html</link>
		<guid>http://tc.eserver.org/23916.html</guid>
		<description>When you reach out to your readers, you show that you have considered who they are and what they need to know. Communicate a concern for your readers&apos; needs so they will be receptive to your message.</description>
	</item>
	<item>
		<title>Speaking in Tongues</title>
		<link>http://tc.eserver.org/23756.html</link>
		<guid>http://tc.eserver.org/23756.html</guid>
		<description>Last month I stated this is not a place for jargon. I felt that was important enough to call out. I certainly am being called to task for that.</description>
	</item>
	<item>
		<title>Effective Writing, or Tips on How to Write English &apos;Gooder&apos;</title>
		<link>http://tc.eserver.org/23672.html</link>
		<guid>http://tc.eserver.org/23672.html</guid>
		<description>Some quick tips toward a clearer, more lucid, meaningful,…well, you know what I mean.</description>
	</item>
	<item>
		<title>An Application of the Principles of Minimalism to the Design of Human-Computer Interfaces</title>
		<link>http://tc.eserver.org/22147.html</link>
		<guid>http://tc.eserver.org/22147.html</guid>
		<description>Minimalism in information design, specifically as applied to user tutorials and manuals, was introduced in the early 1980s through the work of Dr. John M. Carroll, then a cognitive psychologist at the IBM Watson Research Center. Since that time, theorists and practitioners have further elucidated the principles of minimalism and have attempted to apply it to a variety of situations in which people attempt to learn how to use a software application. Most recently, a new exposition of minimalist principles and practices was published by MIT Press. This work, &lt;i&gt;Minimalism Beyond the Nurnberg Funnel,&lt;/i&gt; represents the work of leading theorists and practitioners in the field.</description>
	</item>
	<item>
		<title>Deadwood  Phrases</title>
		<link>http://tc.eserver.org/21682.html</link>
		<guid>http://tc.eserver.org/21682.html</guid>
		<description>Deadwood phrases are found in all types of writing. In technical writing they are to be avoided at all costs as documentation needs to be  crisp, concise and accurate.</description>
	</item>
	<item>
		<title>Writing to Reduce Information</title>
		<link>http://tc.eserver.org/21517.html</link>
		<guid>http://tc.eserver.org/21517.html</guid>
		<description>When creating online and hardcopy information for software, technical writers tend to be prolific. Every piece of information is important, isn&apos;t it? And more information means happier users, right?&#xD;Not every piece of information is necessary,&#xD;however, and users don&apos;t want more information.&#xD;Instead, they want the right information with easy&#xD;access to it. This panel discussion describes why&#xD;you, as a technical writer, need to reduce information&#xD;and how you can reduce it by incorporating&#xD;the following techniques and activities into the&#xD;writing process.</description>
	</item>
	<item>
		<title>Removing Unnecessary Words</title>
		<link>http://tc.eserver.org/21389.html</link>
		<guid>http://tc.eserver.org/21389.html</guid>
		<description>Using an extended example, this article shows how it is possible to reduce the number of words in a text and at the same time increase readability.</description>
	</item>
	<item>
		<title>Making the Invisible Visible: Process, Inspiration and Practice for the New Media Designer</title>
		<link>http://tc.eserver.org/21295.html</link>
		<guid>http://tc.eserver.org/21295.html</guid>
		<description>Hillman Curtis&apos; minimalist approach to design also appears to be his approach to writing. In just a few words he captures the essence of what it means to be a New Media designer and what it takes to push into unknown territory.</description>
	</item>
	<item>
		<title>Clear Writing: Ten Principles of Clear Statement</title>
		<link>http://tc.eserver.org/20916.html</link>
		<guid>http://tc.eserver.org/20916.html</guid>
		<description>If you want to test the clearness of your writing, you may wish to consider using a &apos;fog index.&apos; Fog indexes measure the complexity of writing samples, and often provide a means of calculating the reading or educational level required to understand a particular passage. Some fog indexes are available as computer software programs, or you may do the calculations yourself.</description>
	</item>
	<item>
		<title>Apple Help and John Carroll&apos;s Minimalism</title>
		<link>http://tc.eserver.org/20391.html</link>
		<guid>http://tc.eserver.org/20391.html</guid>
		<description>This report gives a brief overview of minimalism, a description of an Apple Computer documentation project, and a summary of my findings. It also provides some of my and my Apple colleagues&apos; recommendations to improve both the user&apos;s experience and that of the instructional designers working to write Apple Help content. Through the course of this report, I will provide support for my hypotheses that (1) the current Apple Help model is not a minimalist help system, but that (2) users of most Apple software would not be well served by such a system anyway.</description>
	</item>
	<item>
		<title>Participles Becoming Prepositions--Some Arcane Information for Editors</title>
		<link>http://tc.eserver.org/20151.html</link>
		<guid>http://tc.eserver.org/20151.html</guid>
		<description>A presentation that accompanies &lt;A HREF=&quot;http://tc.eserver.org/20150.html&quot;&gt;the paper of the same name&lt;/A&gt; at http://webhome.crk.umn.edu/~mpringle/UsingPaper.rtf.</description>
	</item>
	<item>
		<title>Participles Becoming Prepositions--Some Arcane Information for Editors</title>
		<link>http://tc.eserver.org/20150.html</link>
		<guid>http://tc.eserver.org/20150.html</guid>
		<description>In English, some participles have already become prepositions. The author noticed in her work as a technical editor that most of her writers seemed to perceive the participle &apos;using&apos; as a preposition already although it is not listed as such in the dictionary. The paper gives the evidence and rationale for making such a claim. It offers a window on written language change in progress and celebrates the language user’s ability to make the stolid dialect we call technical writing more vigorous and efficient by turning a participle into a preposition.</description>
	</item>
	<item>
		<title>Applying Minimalist Principles, Strategies, and Techniques</title>
		<link>http://tc.eserver.org/19839.html</link>
		<guid>http://tc.eserver.org/19839.html</guid>
		<description>People use documentation differently from what we might expect. They don’t like to read; instead they jump to a&#xD;task with prior knowledge, and sometimes don’t realize&#xD;they’ve made an error. Understanding how users learn&#xD;and applying John Carroll’s minimalist principles will&#xD;help provide solutions to this problem.&#xD;Documentation that has been successfully planned and&#xD;designed for minimalism may take longer to create than&#xD;other manuals, but reaps the benefits of making users&#xD;more productive and happy, while reducing support calls,&#xD;maintenance, translation, and publishing costs. The key&#xD;factors to a successful minimalist approach (or any good&#xD;documentation design) are a keen understanding of your&#xD;users, prototypes designed to match tasks relevant to&#xD;users, and iterative testing to improve each draft.</description>
	</item>
	<item>
		<title>Needless to Say</title>
		<link>http://tc.eserver.org/19731.html</link>
		<guid>http://tc.eserver.org/19731.html</guid>
		<description>The needless repetition of words and the repeating of ideas is everywhere - in newspapers, books, magazines, e-mails, television, and even in conversation. They’re called redundancies and the English language is full of them. In fact, research shows that about 50 percent of English is redundant.</description>
	</item>
	<item>
		<title>Editing to Help Students&apos; Backs</title>
		<link>http://tc.eserver.org/19703.html</link>
		<guid>http://tc.eserver.org/19703.html</guid>
		<description>Perhaps the worst way to condense a book is by using smaller or condensed type; you want to be especially careful that all fonts are legible. Neither should you save space by tossing out pictures or diagrams that clarify subjects. Some engineers cram paragraphs together, but paragraphs are valuable structural devices that can make subjects more clear. So the clue to successful condensation of text is not mechanical miniaturization but literary efficiency.</description>
	</item>
	<item>
		<title>Plain Language Writing: From a Good Idea Emerges Good Public Policy</title>
		<link>http://tc.eserver.org/19587.html</link>
		<guid>http://tc.eserver.org/19587.html</guid>
		<description>Peter Zvalo looks at the plain language movement, its promoters and its critics.</description>
	</item>
	<item>
		<title>From Gobbledygook to Plain English: How a Large State Agency Took on the Bureaucratic Form Letter</title>
		<link>http://tc.eserver.org/19052.html</link>
		<guid>http://tc.eserver.org/19052.html</guid>
		<description>In an effort to reduce phone calls and improve customer service, the Washington State Department of Labor and Industries(L&amp;I), in July 2001, launched &apos;Plain Talk&apos; – a year-long project to rewrite 100 bureaucratic form letters into plain English. Hundreds of thousands of form letters are used each year by L&amp;I to process claims, to issue workplace safety and health citations, and to handle&#xD;many other workplace issues. As the Plain Talk project manager, I decided to focus on the department’s highest-frequency form letters and now work with 12 programs to rewrite them into clear and simple language. The effort is backed by a strong message from the governor and agency director, high-quality training, ongoing mentoring, and “reality check” usability testing. The project is due to be completed by the end of June 2002.</description>
	</item>
	<item>
		<title>Arthur Levitt and the SEC: Promoting Plain English</title>
		<link>http://tc.eserver.org/14665.html</link>
		<guid>http://tc.eserver.org/14665.html</guid>
		<description>&lt;i&gt;Intercom&lt;/i&gt;&apos;s assistant editor profiles a recent recipient of STC&apos;s President&apos;s Award. The Securities and Exchange Commission was honored for requiring plain English in all disclosure statements filed with the SEC.</description>
	</item>
	<item>
		<title>Sentence-Style Revision</title>
		<link>http://tc.eserver.org/14332.html</link>
		<guid>http://tc.eserver.org/14332.html</guid>
		<description>Problems involving sentence-style cause writing to be unclear, wordy, unemphatic, and difficult to read. But sentences with these kinds of style problems are not necessarily grammatically incorrect—--nor do they violate any of the commonly accepted standards of usage. Yes, perfectly wretched, unreadable writing can be perfectly error-free! &#xD;&#xD;Federal, state, and local government—as well as academicians and lawyers in general—have long been the primary resource for wordy, pompous, and just plain bad writing. However, with the Plain English Movement, William Clinton&apos;s 1998 Presidential Memorandum on Plain Language, and similar events in state and local governments— government writing is becoming less and less an easy target. This chapter reviews some of the most common sentence-style problems, showing how to recognize them and how to fix them. Surely many others exist —we&apos;ve just not trapped and labeled them yet. But in the wilds of bad writing, being able to recognize and revise sentence-style problems covered in this chapter will take you a long way—and enable you to recognize other types of problems as well.</description>
	</item>
	<item>
		<title>A Humanistic Rationale for Technical Writing</title>
		<link>http://tc.eserver.org/13987.html</link>
		<guid>http://tc.eserver.org/13987.html</guid>
		<description>A discussion of how to argue that technical writing has humanistic value. Reviewing the common belief (at least in 1979) that tech writing was of necessity a &apos;skills&apos; course, this article counters the traditional &apos;plain style&apos; rhetorical theory by suggesting possibilities for professional and theoretical alternatives for the field.</description>
	</item>
	<item>
		<title>Simplified English Roundup: Fait Accompli or Impossible Dream?</title>
		<link>http://tc.eserver.org/13452.html</link>
		<guid>http://tc.eserver.org/13452.html</guid>
		<description>The increase in the number of products with&#xD;accompanying documentation sold around the world has shown the need to develop some form of controlled English guideline. Simplified English is just one type of controlled English. The apparent benefits of writing in controlled fashion has led some to consider it a panacea. Others, however, have urged caution in&#xD;accepting controlled English as the solution to all&#xD;problems in the comprehension of documents. All&#xD;forms of controlled English have certain essential&#xD;features that any technical writer can accept.</description>
	</item>
	<item>
		<title>Focus on Simplicity</title>
		<link>http://tc.eserver.org/10636.html</link>
		<guid>http://tc.eserver.org/10636.html</guid>
		<description>An IBM Ease of Use poster with the message &apos;Focus on Simplicity.&apos;</description>
	</item>
	<item>
		<title>Keep It Simple</title>
		<link>http://tc.eserver.org/10635.html</link>
		<guid>http://tc.eserver.org/10635.html</guid>
		<description>An IBM Ease of Use poster with the message Keep it Simple.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Minimalism.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>