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.
Main guideline is productivity. If it happens, then it's
likely all is ok. Generally it is a good idea to have
weekly reports, usually on Friday, that tell what was
accomplished, what's planned for next week, and what are
the concerns or blocking issues that have been or are
likely to be encountered.
The teleworker *must* have an open phone line available
to receive calls at all times. A cell phone is best.
The in-the-office workers must be generally available.
And e-mail should work properly and not have weird restrictions.
For instance, there should be a way to e-mail the
huge document for review, and not have it flagged as
"EXCESSIVELY LARGE ATTACHMENT DELETED."
The teleworker should have the freedom to work on-site
at the office whenever appropriate, and there should be
regular on-site meetings. On-site or near-on-site lunch
is often a good idea.
If the teleworker shows up Very Early or Very Late to get
some on-site work done (like to use the scarce equipment
that he needs to test for writing his book) he should not
discover that his access card doesn't work outside of
"normal" business hours.
The teleworker must be invited to all appropriate meetings,
and not inadvertently forgotten. He must actively seek
inclusion on mailing lists in other parts of the organization,
groups that might otherwise overlook him.
If the teleworker is located very remotely, then all concerned
must make extra effort to avoid misunderstandings and faits
accomplis. "I'm sorry, I know your input would have been
helpful, but you'll have to document it the way it is, because
the development work is completed. If you really feel that
the lack of an UNDO command is a bug, file a bug report."
Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l
Doc-To-Help 2005 now has RoboHelp Converter and HTML Source: Author
content and configure Help in MS Word or any HTML editor. No
proprietary editor! *August release. http://www.componentone.com/TECHWRL/DocToHelp2005
