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.
Subject:Re: Hours of Labor per work day. From:"Brierley, Sean" <Brierley -at- QUODATA -dot- COM> Date:Wed, 28 Apr 1999 10:07:33 -0400
Pull a reverse-Scotty and settle for 5.5 hours per day. 6.5 or 7 seems high.
I would imagine that a PC crash, software snag, unexpected phone call,
email, memo, meetings, bathroom breaks, and daydreaming, or any such
combination could easily wreck your 6.5 or 7 hour estimate of productive
worktime. Reading your email and writing mine took a couple of minutes away
from my day (of course, I came in 90 minutes early). Also, this morning, a
failed attempt by Sysop to install some antivirus software on my PC burned
20 minutes or so.
As I said, 5.5 hours is my best guess and it leaves a little wiggle room.
sean -at- quodata -dot- com
>>>From: Michael Egan [mailto:Michael -dot- Egan -at- DACG -dot- COM]
>>>Sent: Wednesday, April 28, 1999 9:47 AM
>>>To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
>>>Subject: Hours of Labor per work day.
>>> At the company where I work, the planning project officer
>>>the number of hours a project would take. The director
>>>wanted to find out
>>>the number of workdays required.
>>> The obvious solution would be to divide by 8. But is that
>>>there any studies that suggest otherwise. Or even an
>>> The planning officer added up typical meetings, required
>>>and came up with 6.5 to 7 hours of work per day.
>>> Michael P. Egan
>>> Senior Consultant