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.
--- Uma Catherine <uma_catherine -at- usa -dot- net> wrote:
[SNIP]
> While the processes are still incipient, is it necessary to be unpleasant to
> engineers to ensure that they give inputs on time and do not try to tell me
> how to do my work? Also, can anyone give me guidelines on what to include in
> processes so that unpleasantness can be avoided.
> TIA,
> Uma.
No, I don't think it is necessary to be unpleasant to engineers. In fact, I
think it is neither productive nor satisfying to be unpleasant to anyone,
though at times it may feel very pleasant to return unkindness with unkindness.
As for guidelines, I'm sure there are lots of fine books out there, but one I
particularly would recommend is a classic: "How To Win Friends And Influence
People" by Dale Carnegie. It has been a best seller since forever; it is
constantly updated and in print in various forms and guises. It is still the
best, IMHO.
