Skip to content

The three levels of technical documentation

Compare the three maturity levels of technical documentation - from informal notes to modular structured content - and see what sets each stage apart.

, 2 min read

View as Markdown

Picture technical documentation as a garden. Seen that way, it falls into three stages, depending on how it is tended.

The metaphor turns on a point of garden design: an English garden looks natural but is still deliberately planned, while a French garden imposes a visible, geometric order - much like the difference between unstructured and structured documentation.

The three maturity levels of technical documentationLevel 1 – The wasteland– No documentation process– No dedicated team– Unsuitable formats or inconsistent useLevel 2 – The English garden– Reliable documentation process– Dedicated team– Suitable but unstructured formatsLevel 3 – The French garden– Reliable documentation process– Dedicated team– Structured formats

The three maturity levels of technical documentation.

Three components set the levels apart: the documentation process, the team, and the formats.

Level 1: the wastelandLevel 2: the English gardenLevel 3: the French garden
ProcessNoneReliableReliable
TeamWhoever happens to be availableDedicatedDedicated
FormatsUnsuitable, or suitable but used inconsistentlySuitable but unstructured, used consistentlyStructured, used consistently
Format examplesWord processingFrameMaker typeDocBookA semantic XML markup language for technical documentation, organized in books, chapters, and sections rather than typed topics. It predates DITA XML and is the usual point of comparison when choosing a structured format.View in glossary →, DITA XMLA structured, modular XML authoring architecture built around the concept/task/reference typology and content reuse via conrefs and ditamaps.View in glossary →
Content model-Topic-based documentationStructured DITA XML

A word on the formats themselves. Word-processing formats are unsuitable for technical writing: they don’t separate content from layout cleanly enough. FrameMaker-type formats are suitable - they separate layout from content, more or less - but they are not semantic. The structured formats are the semantic ones, such as DocBook and DITA XML.

From the wasteland to the English garden
A reliable process, a dedicated team, and suitable formats used consistently. The English garden - cultivated but informal - is already a fine place to be: it guarantees quality information for the user.
From the English garden to the French garden
Structured formats. The French garden - formal, deliberate, every element in its place - goes further, giving a company tighter control over its content and lower production costs. That second step is the move from mere technical writing to true technical communication.

Ask the three questions the levels are built on:

  1. Process. Is there a reliable documentation process?
  2. Team. Is documentation produced by a dedicated team, or by whoever happens to be available?
  3. Formats. Are your formats suitable and used consistently? Are they structured?

If the answer to any of the first two questions is no, or your formats are unsuitable or used inconsistently, you are in the wasteland. With a process, a team, and suitable but unstructured formats, you are in the English garden. Structured formats on top of both make it the French garden.