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.
RE: Documentation Architect...is there really such a creature?
Subject:RE: Documentation Architect...is there really such a creature? From:"Bonnie Granat" <bgranat -at- granatedit -dot- com> To:<techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 17 May 2006 17:23:25 -0400
> Hi all,
> I have the interesting opportunity to take on the role of
> "Documentation Architect" (or, as my company calls it...Staff
> Technical Writer).
Your company has a job called "staff technical writer" that it wants you to
perform? Where are you getting "Documentation Architect" from if it's not
your company's name for the job?
What's your job now?
I'm trying to figure out just what this
> job should/could be. There is a job description, but it's
> kind of vague.
What is the work that the company wants to get done?
> So, just out of curiousity, if you were appointed your
> group's "Documentation Architect," how would you define this
> job...or what would YOU do if you had such an exalted (or
> pretentious?) title?
Titles don't mean much. What means something is what work needs to be done.
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today!. http://www.webworks.com/techwr-l