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.
> -----Original Message-----
> From: Nina Panzica [mailto:panin -at- MINDSPRING -dot- COM]
> Sent: Thursday, July 08, 1999 9:04 AM
> To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
> Subject: Re: The Telecommuting Myth
>
>
> >> While there are certainly unscrupulous people who are less
> >> productive [off-site] ... how do honest people fight the
> >> perception that this is the rule rather than the exception?
>
> The only thing I can think of to add to David Brown's answer to this
> question is some detail about "communicating constantly." This phrase
> doesn't just mean phone calls to me, although of course it's
> important you
> be proactive in that area and not wait for your manager to
> check in on you.
> Many employers really appreciate--particularly if they don't
> already have
> something like this in place--a weekly report from you in
> which you list (1)
> the activities you've performed or tasks accomplished that
> week (2) the
> things that you hope to accomplish next week and (3) any problems or
> difficulties you encountered or anticipate encountering. With this
> narrative report I usually supply the client with an hourly
> time record in
> table format which has, as column headers: Date, Time Spent
> on that day
> doing a particular task, Code for the Task, Description of
> the Task. The
> codes for the task appear in a legend under my table and
> cover specific
> writing tasks such as manual layout or desktop publishing, editing,
> indexing, research, meetings or interviews, graphics creation, review,
> incorporating others' edits, etc. There are about 15-20 of
> these codes. In
> the description column, I give brief but detailed notes about
> what part of
> the document I was working on, subject of meeting and who it
> was with, what
> specific subtasks within the general task I did, etc.
>