Make it easy for knowledge workers to focus on content and remove the need to define the document structure and formatting on a ad-hoc basis.

To store information in documents for further access, providing the content is often not the problem. Much work is required by the formatting details and figuring out a basic structure for the document.

How can we reduce the work for knowledge workers to provide information for the documentation?

Structure

Formatting issues are well known in the context of word processors. You won't define the template for business letters for your customers on a letter-by-letter basis. While the formatting may support the content, creating a specialized version does not rectify the investment.

It makes sense to have a common structure for specific types of documents. It is easier to deal with meeting minutes if they have the same basic structure. The same goes with decisions, use cases, user characters, and so on. An individual structure of a document may support the content better as a generic one. So if the gain is big in relation to the investment, authors need the freedom to do so. But keep in mind that readers have an easier time if similar content is presented in a similar structure.

A stylesheet and a template to covers the best practices to structure a given type of document supports authors to provide their information for the documentation more quickly. The template works also as guiding tool to reference aspects that have been relevant for the team in the past. It must not be required to fill out the template completely! Authors are encouraged to provided information only for those parts of the template that do actually apply.

Advantages

  • Focusing on the content saves time, since authors do no have to reinvent the wheel in form of formatting and structure.

Disadvantages

  • Authors may not be confident enough to break the structure provided by the form or change the stylesheet. In this case the document may be less readable than if the author had changed the structure and formatting according to the specific requirements.
  • Authors may fill out the template without applying thought. This will produce documents without value. It should be made clear at every possible occasion that the template is simply a suggestion for what has worked in the past.

Related Practices

The following practices are related to this practice.

Physical Location
Store information physically only by properties that are invariant.
Use Templates
Define a basic structure for all artifacts of a given type. Readers will have an easier job on finding and learning about the information in your documentation.

Resources

For more information regarding this practice please refer to:

projectdoc Document
projectdoc is based on projectdoc documents. Creating a projectdoc document is easy: A projectdoc document is a Confluence page using document properties and sections.
Document Types and Templates
Document types (or doctypes for short) define a set of properties and sections. Each doctype matches at least one Confluence Page Blueprint. Confluence Page Blueprints are a collection of templates, but often the collection contains only one element.
Document Properties Marker Macro
A table containing document properties. Three columns: name, value and meta data (aka controls) to a property.
Document Properties Supplier Macro
A table containing additional document properties. Three columns: name, value and meta data (aka controls) to a property.
Section Macro
Renders a section, if the body is not empty. Supports authors to create content, clutter-free rendering without empty sections. Allows to transclude the content.