A directory of resources inthe field of technical communication (and technical writing).

Articles>Writing>Technical Writing>Minimalism

16 found.

About this Site | Advanced Search | Localization | Site Maps



Conciseness is Key to Good Technical Documentation

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.)

Kurtus, Ron. School for Champions (2005). Articles>Document Design>Technical Writing>Minimalism


Cut, Cut, Cut your Content and Procedures

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.

Norris, Julie. 2moro Docs (2009). Articles>Documentation>Technical Writing>Minimalism


Deadwood Phrases

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.

Klariti. Articles>Writing>Technical Writing>Minimalism


Duct Tape Technical Writers

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.

Johnson, Tom H. I'd Rather Be Writing (2009). Articles>Document Design>Technical Writing>Minimalism


Get Rid of the Babble

Try to rid your writing, especially business writing, of unnecessary words. They take up space, look impressive only to naive readers, and say nothing.

Leigh, Heather. Crazy for Words (2007). Articles>Writing>Technical Writing>Minimalism


Going a Bit Too Minimal

Aaron and I advocate minimalism in documentation. Our definition of minimalism differs slightly from how some people may define the term, and we take some heat for it. But no matter how you define it, the aim of minimalist doucmentation is always the same. To give user the information they need in the most concise, readable, and accessible way.

Nesbitt, Scott. Communications from DMN (2010). Articles>Documentation>Technical Writing>Minimalism


High Tech Humor

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.

PlainLanguage.gov (2005). Articles>Writing>Technical Writing>Minimalism


Minimal Procedure Content: Reasoning

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.

Norris, Julie. 2moroDocs (2009). Articles>Documentation>Technical Writing>Minimalism


Minimizing Documentation

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.

Johnson, Tom H. I'd Rather Be Writing (2009). Articles>Documentation>Technical Writing>Minimalism


Needless to Say

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.

Dowling, Dave. Indus (2003). Articles>Writing>Technical Writing>Minimalism


Review: The Nurnberg Funnel by John M. Carroll

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 'tutorials') should be developed and written.

Horn, Robert E. DITA Users (1999). Articles>Reviews>Technical Writing>Minimalism


Plain English

According to Plain English Campaign (www.plainenglish.co.uk), plain English is "… 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." Many organisations have found that plain English brings commercial advantages.

Unwalla, Mike. TechScribe (2008). Articles>Writing>Technical Writing>Minimalism


Removing Unnecessary Words

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.

Unwalla, Mike. TechScribe (2003). Articles>Writing>Technical Writing>Minimalism


Simplified Technical English: STC Should Take the Lead   (PDF)

Proposes that STC become involved in brainstorming ideas about Simplified Technical English, thus leading the way for clear, correct documentation.

Lester, Larry. Intercom (2006). Articles>Writing>Technical Writing>Minimalism


Sometimes, Simple is the Way to Go

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.

Nesbitt, Scott. Communications from DMN (2009). Articles>Documentation>Technical Writing>Minimalism


The Zen of Minimalism: Designing a Top-of-Class Manual for Beginners and Advanced Users

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.

Stieren, Carl. Simware (1998). Articles>Documentation>Technical Writing>Minimalism

Follow us on: TwitterFacebookRSSPost about us on: TwitterFacebookDeliciousRSSStumbleUpon