| The title page clearly provides the author's name, the date of the document, and its version or revision number. |
| The author states his point of view clearly, without obfuscation or mealy-mouthed bureaucratic writing. Good writing alone helps a document become more effective and scannable. Both high-level recommendations and low-level opinions are clearly stated. |
| The author has provided a summary of his recommendations, followed by links to supporting material that readers can review at leisure. It is helpful when each chunk is clearly either a high-level chunk or a piece of detailed supporting material. |
| For each chunk of material, the author has provided a summary that helps time-conscious readers skim and read more effectively. |
| The author discusses each point only once, providing links wherever it is necessary to refer to the same material in several locations. Readers encounter little redundant material. |
| The argument pages have highlighted points in bold to facilitate skimming. |
| The author adds images in the map to add corporate "ambiance," and links to images and external files wherever these support his arguments. |
| Wherever colleagues have helped significantly, or material has been brought in from elsewhere, the author follows good ethical practice in giving credit to the original source. (Hypertext structure lets you put such acknowledgements near the relevant information chunks.) |
| To take full advantage of Trellix, you can include standard sections in all documents produced by your organization or group. The topics in "Corporate Background" here provide an example. |
| There is no need to reinvent the wheel; if a well-organized resource exists on the web or on a local intranet, you can simply link to it from the relevant locations. |
| Wherever a chunk is out of date, the author has noted this and provided pointers to more current resources. |