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: Need help with a recommendation From:"Steven J. Owens" <puff -at- NETCOM -dot- COM> Date:Wed, 10 Mar 1999 06:40:48 -0800
>Wendy Lewis writes:
> How? Simple economics. Write up a cost justification on how it will
> benefit ***the company***. Do some tracking and figuring on how much
> time you waste in switching between windows and different scaled
> views of each window.
I think the book _Peopleware_ might be useful here. The part I'm
thinking of is the concept of "workflow" (i.e. when you're in the
groove and productive as hell). The book claimed that interruptions
knock you out of workflow and take as much as 20 minutes to return to
workflow. The interruption of moving from application to application
isn't as great, but it's constant; you could make a case that it
prevents you from achieving workflow and (if the book had any concrete
productivity comparisons) calculate the damage to your productivity.
Peopleware is fairly old, you may be able to find more recent
works with more statistics and such. Check in the human factors
fields. Also check in ergonomics fields, they're the sorta folks
likely to go looking for these kinds of statistics.
I'd also start by describing an appropriate hardware setup so you
have a "norm". Describe the ideal, then describe a compromise system
that is still acceptable.