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.
My approach may seem overly simple, but I would make a list of all the
projects that require documentation, and a list of the documentation set
that would accompany each of them.
If possible put together two time projections for how long it will take to
create those docs - One for how long it would take someone with knowledge of
the software and existing doc standards, and one for someone who has to go
through the learning curve.
I would then make a report of how much TW-consultants typically cost in your
area.
Finally, I would present the cost difference between what they would pay for
you to do the work and what they would pay for someone else to do the work.
I would present a one year plan and a five year plan.
You could consider upping your rate a bit and offering to work at home
making site visits only when necessary thus reducing the cost of physical
overhead for them and giving yourself the flexibility to look elsewhere.
Good luck.
Jennifer
-----Original Message-----
From: Jane Carnall [mailto:jane -dot- carnall -at- digitalbridges -dot- com]
Sent: martedì 3 settembre 2002 15.29
To: TECHWR-L
Subject: Tuesday's news: cost-cutting measures
It's not really worth sending this ANONFWD...
Okay, I've just been told I'm "at risk of redundancy"... and unless I or the
company can think up some "cost-cutting measures" by Friday, I'll be
formally redundant.
Assuming that they mean it when they say "cost-cutting measures" - my first
thought is to offer to go part-time. Working two days (or three days) a week
would give me a safety net plus spare time to try and build-up freelance
technical writing/copyediting/indexing work, which is something I've been
thinking of doing for a while.
(My second thought is, of course, to go home, polish up the CV, start
URGENTLY sending it out to all and sundry. The two thoughts can, of course,
be carried out in parallel.)
I'd appreciate hearing from anyone who's gone from full-time to part-time at
the same company, or any thoughts from people about how best to present the
plan of the company getting a part-time technical writer (and currently, I'm
the only one they have) instead of a full-time one.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Check out the new release of RoboDemo, our easy-to-use tutorial software.
Plus, buy RoboHelp Office in August and save $100 with our mail-in rebate.
Get details and download free trial versions at http://www.ehelp.com/techwr-l
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -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.
