RE: assessing a lone-writer gig

["Gordon McLean" <Gordon -dot- McLean -at- GrahamTechnology -dot- com>]

Having never been a lone writer (at least knowing that I wouldn't be one
once I hired others folks), I have to say that this list, with a little
tweak of the English, is applicable to ALL interviews. It would give a good
insight into the company you are interviewing for, and let you see what the
current mindset is and what the barriers to change might be. 

As a hiring team lead I'd be intrigued to meet a candidate that asked
questions along these lines, but I guess it depends on your company politics
as to whether this approach would work or not?

Great stuff PT!

Gordon McLean 

-----Original Message-----
From: techwr-l-bounces+gordon -dot- mclean=grahamtechnology -dot- com -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+gordon -dot- mclean=grahamtechnology -dot- com -at- lists -dot- techwr-l -dot- c
om] On Behalf Of Pro TechWriter
Sent: 25 June 2007 17:34
To: Sydney Compson
Cc: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Re: assessing a lone-writer gig

Hi Sydney:

Being a lone writer at a company that is transitioning from "small" to
"medium-sized," here are some things I have asked about, and would ask that
I didn't.


   - How is this job classified (professional or administrative). (If
   it's administrative, ..run, do not walk, away from this job!)
   - What tools do you use now? Can I choose tools? Is there a budget for
   tools? Can I use open source tools if there is little to no budget? Are
   there any restrictions against downloading and testing trial versions of
   software, if I need to.
   - How has the documentation (if any) been produced up to now?
   Distributed? Who owns it? Will I "own" the documentation now?
   - Who has the final say about documentation quality (templates, look
   and feel, editing, language, standards)? (This is VERY important!)
   - Will anyone be able to change my documents? Tell me to use other
   language? Edit my work? Send out documentation without consulting me?
(This
   one is a "lessons learned" for me. It matters, believe me.)
   - How is the production schedule set for documentation? Who do I give
   my estimates and time lines to? How are those communicated to the
   development teams? Is there a master schedule? If so, can I provide the
   documentation project schedule to be added to the master schedule?
   - I have a documentation life cycle process that I follow. What is the
   best way to educate others in the company about this process.

These comments are based on my experience in situations like yours. I think
the biggest issue I have had is the lack of control over the documentation
that I am creating, and being perceived as some sort of secretarial person
who types things.

That's all I can think of for now. Others have provided some pretty good
comments that I don't want to repeat.

I hope this helps!
Cordially,

PT




____________________________________________________________________________________________________
This email (and any attachments) is private and confidential, and is intended solely for the
addressee. If you have received this communication in error please remove it and inform us via
telephone or email. Although we take all possible steps to ensure mail and attachments
are free from malicious content, malware and viruses, we cannot accept any responsibility
whatsoever for any changes to content outwith our administrative bounds. The views represented
within this mail are solely the view of the author and do not reflect the views of the organisation
as a whole.
____________________________________________________________________________________________________
Graham Technology plc
Registered in Scotland company no. SC143434
Registered Office India of Inchinnan, Renfrewshire, Scotland PA4 9LH
                                                
http://www.grahamtechnology.com
____________________________________________________________________________________________________

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Create HTML or Microsoft Word content and convert to Help file formats or 
printed documentation. Features include support for Windows Vista & 2007 
Microsoft Office, team authoring, plus more.
http://www.DocToHelp.com/TechwrlList

True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com

---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot- 

To unsubscribe send a blank email to 
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwr-l.com/ for more resources and info.