Re: Integrating a new writer

Subject: Re: Integrating a new writer
From: Dick Margulis <margulisd -at- comcast -dot- net>
To: "TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Tue, 15 Feb 2005 14:34:11 -0500




technical -at- theverbalist -dot- com wrote:



I’m also looking for some advice on sharing the work--my initial greedy
thought of 'I'll do the interesting stuff; you do the boring scut work. Oh
and also? Indexing." doesn't seem like the best way to parcel things out.
Any thoughts on how to split up a two-product, 15-doc set?

The natural division of labor in this scenario is that you are the author of all Product A docs, responsible for them from interviewing SME's to editing the index; and Junior is the author of all Product B docs, equally responsible for completing them. The working relationship has a few dimensions:

• You will set the style standards, with his input and with an open mind toward good suggestions for improvement, but also with final authority on all arbitrary choices. (Explain the concept of "arbitrary choice" as it pertains to matters of style.)

• While you will peer-edit each other's docs, just because it's always better to have two sets of eyes look at a document, nonetheless you're still the boss and mentor; so your edits of his docs carry more weight than his edits of your docs and you have the final say.

• You will be more than happy to answer any questions and explain your reasoning about anything at all, subject to the limitation that arbitrary decisions are arbitrary. He can ask you questions informally at any time, or you can set up a mentoring session once a week if that seems more comfortable. If he's someone who likes to take notes and get everything down in writing, assign him the task of collating your various pearls of wisdom into a first draft of a company style guide. That exercise will help him become a better technical writer, fer sher.

• You are his direct supervisor and so you have the duty to know how much progress he is making on his assignments and whether he is behind schedule. State this clearly up front so that he doesn't get defensive when you ask for a progress report. Be prepared to coach him on how to work faster (more productively) and also be prepared to jump in and rescue the project by taking some of his deliverables away from him and doing them yourself if he gets into trouble.



Mandy...also figuring out how to get my hair looking like there's a big
orange marmot living on my head...


I'd settle for looking like there's still hair living on my head.

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

WEBWORKS FINALDRAFT - EDIT AND REVIEW, REDEFINED
Accelerate the document lifecycle with full online discussions and unique feedback-management capabilities. Unlimited, efficient reviews for Word
and FrameMaker authors. Live, online demo:
http://www.webworks.com/techwr-l

Doc-To-Help 7.5 Professional: New version with new features, improved performance and reliability, plus much more! Download your free trial today at www.componentone.com/techwrlfeb.

---
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- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.



Previous by Author: Re: Mini Manuals
Next by Author: Re: [Fwd: Re: Is this really a tech writing job?]
Previous by Thread: Re: Integrating a new writer
Next by Thread: Re: Integrating a new writer


What this post helpful? Share it with friends and colleagues:


Sponsored Ads