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.
Tool changeover validation processes and requirements
Subject:Tool changeover validation processes and requirements From:geoff -at- userdox -dot- com To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Tue, 9 Mar 2004 10:10:15 +1100
Gotta say that I'm quite interested in this one as well. I've gone through the
whole analysis process, tool1 -vs- tool2 -vs- tool3 -vs- tool(n) analysis,
produced rough figures, received approval for more in-depth research, produced
detailed figures, created and costed change over plans, come up with a saving
higher than my original rough estimates, the team has a *very* high level of
buy-in, team leaders want the change, immediate manager wants to move away from
Word, and I still haven't been given the go ahead to implement.
I'm not moving to OOo (its not suitable for my circumstances), but the whole
process of validating a decision for management is what I'm looking for.
>
> No problem, John. It's just that every time I've ever
> tried to pitch a tool change that will cost $ to upper
> management, at every company I've ever been at, one of
> the inevitable parts of the discussion was why I couldn't
> do the things I wanted to do with the tools I already
> had. It's amazing how much time people at director and
> VP levels will spend researching subjects they normally
> couldn't care less about (and in most cases, shouldn't)
> the moment they become potential budget line items. I'm
> really interested in how you managed to pull a tool change
> off without having to slog through all that tool vs. tool.
>
> Gene Kim-Eng
>
>
> ------- Original Message -------
> On Mon, 8 Mar 2004 13:35:22 -0500 John Posada wrote:Gene...I want to address
> this in more detail, but I have a draft to get
> ready for presentation at 10am tomorrow and I can't spare the time to
> address this properly. Let me see if I can get back to this later.
>
-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/
ROBOHELP IS THE INDUSTRY STANDARD IN HELP AUTHORING
New RoboHelp X5 includes all new features such as,
content management, multi-author support, distributed
workforce support, XML and PDF support, and much more!
---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
