I thought it might be useful to look at a simple question: Why is there a need for single sourcing\u00a0technical documentation? For people who aren’t technical authors, it’s often unclear why technical authors talk so much about “single sourcing”. Isn’t that just cutting and pasting? What’s the problem?<\/p>\n

In later posts we’ll look at the possible solutions, but this post will focus on the need to change things.<\/p>\n

What’s the problem?<\/h3>\n

Many documentation departments produce detailed and well-designed documentation. Increasingly, however, one manual is often not enough.<\/p>\n

Users are rarely all the same. They have different product knowledge, different backgrounds and they may have different reasons for using the product.<\/p>\n

Customers don’t want to search and scanning through lots of information that’s irrelevant to their situation.\u00a0They often need specific documentation rather than a standard one-size-fits-all document.<\/p>\n

In addition,\u00a0as companies expand their product offering into new markets and strive to broaden the product offering and stretch the lifecycle of existing products, so the producers of the technical information must manage, at the same time, more than one edition of their documents.<\/p>\n

Internationalisation intensifies the burden even more, with the need to provide translated versions of documents. Indeed, it’s illegal to sell a product in the European Union if\u00a0it doesn’t have documentation written in the language used in that country. That’s not to mention the \u00a0risk of out-of-date legal, safety and compliance information being sent out to customers.<\/p>\n

This means there is often a need to produce lots of documents that are only slightly different from each other.<\/p>\n

If these new documents are created by cutting content from one document and pasting it into another, you do not have an automatic way of keep each version of these documents up to date and consistent to each other. Someone has to remember to change “Document B” whenever “Document A” is updated – and have the time available to do it.<\/p>\n

When many versions of the same core document exist, they have a habit of becoming more and more different from each other. Differences in wording and content start to creep in, which can lead to confusion in the minds of both your customers and your document authors.<\/p>\n

It also means that same information can be written and translated more than once. Translation costs, even when “translation memory” software is used, can be very very expensive, so it makes sense to re-use existing content as much as possible.<\/p>\n

In short, poor and inefficient management of content is expensive. Staff can spend hours dealing with content that’s unstructured, disorganised and unable to be reused.\u00a0The company can waste money on unnecessary translation costs.\u00a0As for the poor old customers – they can end up with\u00a0 documents that just don’t meet their needs.<\/p>\n","protected":false},"excerpt":{"rendered":"

I thought it might be useful to look at a simple question: Why is there a need for single sourcing\u00a0technical documentation? For people who aren’t technical authors, it’s often unclear why technical authors talk so much about “single sourcing”. Isn’t that just cutting and pasting? What’s the problem? In later posts we’ll look at the… Read more »<\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[174,175,155,162,166,200,158,194,236,192,156],"tags":[273,274,275,276,269,277,272,262,278,279,280],"class_list":["post-419","post","type-post","status-publish","format-standard","hentry","category-collaborative-authoring","category-content-management","category-dita","category-documentation","category-management","category-single-sourcing","category-technical-authors","category-technical-communication","category-technical-documentation","category-translation-tools","category-xml","tag-collaborative-authoring","tag-content-management","tag-dita","tag-documentation","tag-management","tag-single-sourcing","tag-technical-authors","tag-technical-communication","tag-technical-documentation","tag-translation-tools","tag-xml"],"acf":[],"yoast_head":"\n