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.
Yes, Jill, "technical design docs, architectural overviews,
application roadmaps, and development methodology descriptions"
do fall under the category of technical writing. But that
doesn't mean that you need to shut up and attempt them if
they're not what you expected to be doing. You mention
"years of technical writing" but not how many years with
your current employer. If you've established your value at
the present workplace, you can certainly talk out your
reservations with your boss. If not, then it may be a bit
more difficult to refuse the assignment but you can certainly
make it clear that you'll need plenty of support and assistance.
Just ask for it forthrightly as something you deserve, not
plaintively as something you need.
And if you do write your way through all that technical
material, you'll be the better educated for it.
Mark L. Levinson
Herzlia, Israel
markl -at- gilian -dot- com
