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.
We are pretty lucky here, because we've got great senior program management.
We're writing specs now and the senior PM has told everyone that the goal is
give the test team something from which to develop test cases. In addition,
as part of the process, the specs have gone through one of our tech writers
for an editorial check. That's given our team the opportunity to ask a mess
of questions along the lines of "I don't get it" and "that's fine, but what
does it DO?" I've also worked with teams where we've outlined the docs based
on the spec and had the engineers review the outlines - that's worked fine
too. That's a badly written response to your question (sorry, I'm still
waking up) but gives a general idea of our salutation. As I said, I think