This podcast is a recording of a presentation I gave to students at the Missouri State University technical writing conference on April 23, 2010. With this presentation, because the audience was students, I focused mainly on the changing roles technical communicators are playing. My basic premise is that many IT environments have an assumption that “anyone can write.” Because of this assumption, technical writers are changing their roles, becoming hybrids with additional skill sets, or moving beyond the basics of writing in order to provide both value and find fulfillment.
Several weeks ago I wrote about my trip to Brigham Young University-Idaho and the presentation I gave there titled “Debunking the Boredom Myth of Technical Writing.” This podcast is a recording of my presentation.
This paper discusses the author’s experience of teaching an English as a Second Language (ESL) technical writing class. The class consisted of students from several European and Asian countries who work for the same company as the author. The class began as an email “correspondence” class, but the author developed a web page which served as a “home” for the class to meet. As with most good classes, the teacher ended up learning as much or more than the students. This paper shares some of what the author learned from teaching.
Most of us view government regulations negatively. Yet they provide a multitude of opportunities for technical writers. What are these opportunities? Where are they? How can you take advantage of them? A chance opportunity knocked on the author's door. Her experience can guide you to find and knock on opportunity's door.
This presentation describes the standard structure of a lab report and provides a methodology for successfully producing such a report. It includes a description of the generic structure of a report and variations on this theme.
While gathering information for a documentation project, what challenges do we have to overcome? A presentation of data based on responses to an online survey.
Electronic information products can be made accessible to blind and low-vision individuals. This is easier to accomplish with thorough planning and execution. This paper describes a five-step model for creating accessible documentation. The steps are (1) Preparing a source file (2) Producing accessible output, (3) Testing output for accessibility, (4) Modifying a source file if needed, and (5) Modifying a production process if absolutely necessary.
Tomorrow I’m driving up to BYU Idaho to give a presentation titled “Technical Communication Careers: Getting Started and Finding Your Niche.” Below are the “slides” for my presentation.
A PDF document intended as a resource for teachers. The overview handout defines technical writing, lists examples, states rationale for teaching technical writing, reviews principles for writing instruction, explains basic technical writing concepts to be taught to students, and outlines methods for evaluating technical writing.
The rapid growth in demand for technical communicators is mirrored and driven by the continuing evolution of emerging technologies. Businesses striving to use technology to effectively position themselves must understand the role that the technical communicator plays in this evolution. As we continue to acquire a toolbox of skills, we enhance our proficiency as Renaissance communicators and propel our roles into the realm of knowledge management.