Re: Estimating a Project - A real lulu

[Tara Barber <Tara -dot- Barber -at- GALEGROUP -dot- COM>]

Long ago, when I was a newbie tech writer, I was sent out by the senior
partners of the three-person writing firm I was working for to spec out a
project for a prospective new client.

The project was a fairly complex inventory software system.  The client
wanted all user documentation, including installation guide, procedure
manual, and trouble-shooting materials.  They estimated (don't ask me how)
400-600 pages, with lots of screen shots and cross-references.  And oh, by
the way, A) there was no working prototype of the software available --
maybe in three weeks; B) all the materials they had for us to start working
with were some programming specs and some update memos; C) we were not to
bother the programmers, as they were very busy trying to get the system to
work, and there were no other SMEs for that project; D) they wanted the
whole thing, printer-ready, in SIX weeks, which was when they were going to
release it.  Oh, and they were on a tight budget, so they wanted costs kept
down.

When I gently informed the manager I was talking to that this was not
possible, he replied "Why not?  How fast do you type?"

My partners were not at all upset with me when I returned and told them the
circumstances, and explained that I had informed this gentleman that I
didn't think we could help him.  The senior writer, a woman of twenty-five
years experience, said to me, "Never be afraid to turn down a job where
you're being set up to fail; where you KNOW you can't do good work, or make
the customer happy."

"Good, cheap, fast; pick two" is a good maxim to remember, as others have
mentioned.  But even if you get paid a bundle, the stress and strain of
rushed (and usually therefore poor) work done under unreasonable client
expectations is rarely worth it.

Personally, I'd pass.

- Tara Barber
Senior Technical Writer
The Gale Group

 From ??? -at- ??? Sun Jan 00 00:00:00 0000=