Luckily, that isn't all they do. Many are employed writing policies and procedures and internal business documentation. Any function that requires explaining concepts understood within a certain skill set that is a minority role in a company is a TW role.
Personally, I find it hard to separate the different roles. A well-organized business produces a well-organized product, which can then be easily introduced to the user. If a TW is able to give that feedback during development, and make the product better, the doc gets simpler and bottom line goes up. This is why I see the role of TWs as expanding, not decreasing, in the future. --- Technical Writer <[EMAIL PROTECTED]> wrote: > TWs complete a very necessary task; creating user assistance. Until > the final iteration, until all the requirements have been met, until > there is little or no possibility of changes to the end product, > there is little point in generating documentation that might become > obsolete at the next iteration. http://technical-writing.dionysius.com/ technical writing | consulting | development __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
