TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: What exactly is minimalist documentation? From:Scott Miller <smiller -at- CORP -dot- PORTAL -dot- COM> Date:Mon, 27 Oct 1997 09:29:50 -0800
>>>>>
>I have a vague sense of what minimalist documentation probably is, but I need
>to
>be able to define it by this evening. Can anyone help me out here? Does
>anyone
>do this kind of documentation? What is its advantage? Thanks!!
><<<<<<<
>Applied to software documentation, the goal of minimalist documentation is to
>provide just enough information that the user is able to find out just enough
>crucial information to get by with basic tasks. Enough information is
>provided to allow the user to figure out non-basic tasks on their own. By
>figuring things out on their own, the user learns how to use the software
>better, and has greater retention. In other words, the goal is not to just
>have fewer words, or kill fewer trees, but to enhance usability by providing
>a minimal safety net over which a user can explore and learn.
>
>The closest I've seen to minimalist documentation is the online help for
>Windows 95.
>
>- Scott Miller
>smiller -at- portal -dot- com
>