A different perspective on single sourcing

09 Apr

Posted by Scott as documentation, single sourcing, technical communication, writing

This blog post asks whether or not single sourcing is the best option for creating documents. I’m not sure that I fully agree with everything in the post, but something that the author wrote struck a chord:

I know a single source of content will save me a lot of work. But for other people in the company it won’t. It will mean more work for them, not to mention a very steep learning curve, an investment in software and a strong training commitment. It will save me lots of time and effort—in the long run—but it’s going to double the work effort of ten other people. Where is the benefit?

Thoughts? Feel free to leave a comment.