RE: any cons to single sourcing?

["Hyde, Barb # IHTUL" <Barb -dot- Hyde -at- tulsa -dot- cistech -dot- com>]

I can see the value of single sourcing to develop different online formats
(Help, HTML, etc.) However, not for help and paper. In addition to all the
development-side pitfalls pointed out in Mark Baker's post, there is a
consumer-side problem with single sourcing Help and paper.  I have
personally #%$*%^*&#ed the economies that make this kind of single sourcing
attractive to developers.

Nothing is more frustrating than this scenario: I am learning to use a new
tool and need information. I look through the Help and other online
information, but don't find what I need. Then I turn to the paper guide only
to find it contains exactly the same material as the Help. 
What is the point? Rather than spend the money for paper that doesn't say
anything new, just go with the online and tell your customers that's what
they get. 
 

-----Original Message-----
Subject: any cons to single sourcing?
From: ctraynor -at- cybermation -dot- com
Date: Wed, 16 Feb 2000 09:31:48 -0500
X-Message-Number: 15

Hi folks. I'm in the midst of researching single sourcing for the purpose
of putting together a business case. I'm well aware of the benefits, but
how about the other side of the story? Any difficult experiences or failed
attempts to implement a single sourcing process?  What were the obstacles?
Were they overcome?
Lets here your stories (I need to know what I may be up against!!).

Thanks
Christina
Barbara Hyde
barb -dot- hyde -at- ndcorp -dot- com