Skriftlig Info ➜ Methodology ➜ Modular writing ➜ Save time and money with reuse
Now you may object, saying that text from one document can easily be copied into another and that this is also "reuse". That is certainly correct. It also works fine as long as the copied text is not to be changed. How many places is it used? The same applies to translation. A copied text must be translated again, and even if the translation tools "remember" the text and translate it automatically, you still have to pay for it.
Reuse is defined as the electronic recontextualization of separate information elements (multimodal text fragments). The information elements must be established as separate data files or as addressable elements in a source file. The elements are inserted into one or more of the main documents using electronic references (links). In the event of changes to the source file, the information in all the main documents will automatically change accordingly.
One of the mistakes you can make in a technical manual is precisely using the "copy/paste" functionality in your tool. There is nothing wrong with copying text, but the text contains information, and you have to maintain it. If you copy information once you get a maintenance problem. If you copy the same information several times, you may have a maintenance nightmare. Can you remember at any time how many places in how many books you have used a given phrase, or how many places you have specified a technical detail?
It is very easy to include technical specifications in ordinary prose text. It could be something as banal as "the washing machine motor rotates at 1200 revolutions per minute". Suppose you copy this sentence into three or four places in the owner's manual, then a few places in the maintenance manual, a couple of times into a website, and finally a brochure. So what do you do if the product manager comes to you the day before launch and says "I forgot to tell you that the spin speed is changed to 1100 rpm. It shook to pieces when we tested it at 1200..."
In the true sense of the word, reuse allows you to change this in one place.
Reuse is a relevant principle in our time, even if it is mainly put in a different context than technical documentation. Norwegian Wikipedia writes:
Reuse indicates use more than once. The concept is strongly linked to environmental protection as the second level in the waste hierarchy but gives extended meaning in all situations where an existing object or concept is reused, after first being used in its intended main use. The new use can be the same as the first time or used as something else, in contrast to recycling where the object is picked apart into raw materials for new use.
Reuse is an energy-saving and resource-saving element of best environmental practice.
Examples of reuse also include second-hand sales, refurbishment and reuse of code in high-level programming.
Consideration of resource scarcity is the main reason for reusing objects and concepts, but in many cases, there is also economic profitability in reusing objects or concepts.
Norsk Wikipedia, [1] (Translated by the editor)
Note the last part of the last sentence: "but in many cases, there is also economic profitability in reusing objects or concepts".
There are of course some challenges here. Although you can save time and money with reuse, the infrastructure in your documentation system facilitates reuse. Important points are:
All external links open in a new window. I take no responsibility for information on external websites, even if I have linked to them. Please report links that do not work.
The information on this page represents my personal opinions and my understanding of the topic being described. Feel free to link to the page, but do not copy large parts of the content without permission. I take no responsibility for any errors, misunderstandings or missing information. I also take no responsibility for any mistakes you may make or cause as a result of incorrect or missing information. You are welcome to contribute with comments, relevant experiences or additional information. See Editor and contact information.
GR 2023-01-15