TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
"...but the reality seems to be more like you're committing to an open-ended custom software development project."
Could you elaborate on that last part a little bit? I'm not sure I understand.
From: robert -dot- lauriston -at- gmail -dot- com [mailto:robert -dot- lauriston -at- gmail -dot- com] On Behalf Of Robert Lauriston
Sent: Monday, October 27, 2014 9:43 AM
To: Janoff, Steven
Subject: Re: Resources for learning Structured Writing?
On Mon, Oct 27, 2014 at 9:23 AM, Janoff, Steven <Steven -dot- Janoff -at- hologic -dot- com> wrote:
> Couple of questions, if you don't mind.
> What made you decide the migration would not be cost-effective?
We couldn't identify any benefits. The docs were distributed only in English and there was very little need / opportunity for topic reuse.
> How many such investigations have you been involved in?
I've considered it at two other companies but the situations were similar.
I love the idea of using standard source that's compatible with multiple off-the-shelf tools but the reality seems to be more like you're committing to an open-ended custom software development project.
Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1lRPd2l