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.
After I wrote that email, I contacted the client and said what *is*
possible, given the constraints. They sighed, said, well if we don't ask, we
never know, have agreed to let me bid, based on what is possible, rather
than what they want.
Part of our business - Anthrobytes, I mean - is to help the client see what
can be done, given their time and budget constraints. We would never say we
can deliver the world on a shoestring. That leads to upsetting the client
when we can't deliver it.
It was not the rush aspect that concerned my crew - god knows we have LOTS
of those - it was that physically, it was not possible to do what they said
they wanted with the constraints they set out - not even if we held all
other current projects and everyone worked on it for 60 to 80 hours a week
for 4 weeks. But of course, I would come back to the client with, well,
here is what is possible.
I just wanted to make sure that I didn't overlook something - we are a
little tired around here lately and know we don't think best in that case.
The consensus has been, nope, we thought of everything.
sharon
Sharon Burton-Hardin
Anthrobytes Consulting
909-369-8590
www.anthrobytes.com
Vice-president, Programs of the Inland Empire chapter of the STC
www.iestc.org
| Sharon Burton-Hardin wrote:
|
| <
| I am talking to a potential client. In 4 weeks, they want a complete
| user
| manual, including examples and scenarios and a CBT that "supports the
| user
| guide" (must reflect the complete user guide). The product is a web
| based
| supply chain product. There is no existing documentation, although an
| online
| help is being scoped now and a beta help should be ready by the time we
| start our part.
| <snip>
| My crew says that with a week to plan - outlines, storyboards, prototype
| designs, approval from client - and 3 days to internal QA, we cannot do
| this
| project.
| <snip>
| I am looking for a reality check. The client seems immovable about the 4
| weeks. I keep saying starting now and they keep saying in mid Feb.
| Before I
| call and explain why this seems like a train-wreck in the making and we
| try
| to limit our wrecks when possible, can anyone think of anything we are
| not
| thinking of?
| >
|
| Gee, can I have your client?
|
| I love doing these sorts of projects--somehow putting the seemingly
| impossible out under tight deadlines.
|
| What aren't you thinking of? The client's needs. The client needs
| something to put in front of their users to help them get going.
| And, they need it in four weeks, when (presumably) the product ships.
|
|
| Correct me if I'm wrong, but aren't they (trying) to hire you to
| help them solve this problem?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Collect Royalties, Not Rejection Letters! Tell us your rejection story when you
submit your manuscript to iUniverse Nov. 6 -Dec. 15 and get five free copies of
your book. What are you waiting for? http://www.iuniverse.com/media/techwr
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
