<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Documentation&gt;Technical Writing&gt;Minimalism</title>	<link>http://tc.eserver.org/dir/Articles/Documentation/Technical-Writing/Minimalism</link>
	<description>A listing of the most recently indexed works about Articles and Documentation and Technical Writing and Minimalism in the field of technical communication (and technical writing).</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>Articles&gt;Documentation&gt;Technical Writing&gt;Minimalism</title>
		<link>http://tc.eserver.org/dir/Articles/Documentation/Technical-Writing/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>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>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>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>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>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>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>
	<atom:link href="http://tc.eserver.org/dir/Articles/Documentation/Technical-Writing/Minimalism.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>