Human engineering, customer research prior to design concept, GUI concept and progression testing, usability testing, quality control, user advocacy, basic GUI verification and operability (short of rigorous software design testing)... the list goes on. There are a lot of areas where TWs could ply their skills, provided a corporation values something other than blind typists who just write what they're paid to write. Perhaps those areas are things that TWs should pitch and demonstrate their skills toward.
Rene Stephenson Bill Swallow <techcommdood at gmail.com> wrote: Agreed. I'm surprised this isn't a more common practice. On 10/18/07, Chris Borokowski wrote: > What makes more sense in my mind is for technical writers to expand > their role to the life-cycle of the product, from conception to > maintenance, by investing in understanding interaction design/interface > design, quality control and user advocacy positions. -- Bill Swallow HATT List Owner WWP-Users List Owner Senior Member STC, TechValley Chapter STC Single-Sourcing SIG Manager http://techcommdood.blogspot.com _______________________________________________ You are currently subscribed to Framers as rinnie1 at yahoo.com. Send list messages to framers at lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscribe at lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/rinnie1%40yahoo.com Send administrative questions to listadmin at frameusers.com. Visit http://www.frameusers.com/ for more resources and info.