http://tc.eserver.org/authors/Bernhardt,_Stephen_A. A bibliography of works by Bernhardt, Stephen A. in the field of technical communication. en-us Copyright (c) 2005-08 by the EServer. All rights reserved. tclib-editorial@eserver.org (TC Library Editorial Board) webmaster@eserver.org (Geoffrey Sauer) http://tc.eserver.org/images/newlogo.gif http://tc.eserver.org/dir/Bernhardt,_Stephen_A. http://tc.eserver.org/19068.html http://tc.eserver.org/19068.html We should not pursue specialization in our programs. We should not become the multimedia development program, or the computer documentation program, or the medical writing program, or the environmental communication program, or even the critical literacy program. We should build programs around a broad, useful rhetorical education, coupled with a skill set that all students share in writing and document design. We should make sure all students develop productive relationships with communication technologies. And we should allow students to follow their interests and to find the kind of specialization that is rewarding to them individually. http://tc.eserver.org/13910.html http://tc.eserver.org/13910.html This lecture describes the need for the field to clarify how we represent ourselves and think about ourselves. http://tc.eserver.org/10388.html http://tc.eserver.org/10388.html This article introduces a way of working with drug development teams that relies on writing as a key development activity. The work of cross-functional teams in pharmaceutical research and development can be guided by the use of tools normally thought of as 'writing' tools. Writing can be used intentionally to help teams develop their thinking, identify and respond to troublesome issues, and develop project documentation efficiently. The article introduces the use of a 'seed document' (one step in a systematic, wholly collaborative, document development process) to establish a conceptual knowledge bank for a development team, and demonstrates how complex documentation can flow naturally out of the evolving seed document. The authors argue that structured writing can help team members, who have varying perspectives and expertise, engage in substantive conflict and reach consensus on team responses to difficult issues.