Design Discourse - Composing and Revising Programs in Professional and Technical Writing, 2010a

Design Discourse - Composing and Revising Programs in Professional and Technical Writing, 2010a Design Discourse - Composing and Revising Programs in Professional and Technical Writing, 2010a

elearningcommons
from elearningcommons More from this publisher
06.09.2021 Views

Knievel, Belanger, Keeney, Couch, and Stebbins edges that the process of naming is complex and fraught with competing motives, asking, “Is the naming of programs a determinist enterprise that takes on a life of its own? Or are we being creative in our endeavor to associate thing to thing, spiritual fact with embodied form?” Johnson recognizes the need to let local factors guide naming but cautions against promising more (or less) than can be delivered: “…should we think twice about unnaming ourselves in the process of trying to embrace too much?” Generally speaking, the implications of program naming have been inferred from broader conversations about connections between program development and institutional politics (Cunningham and Harris; Hayhoe, et al; Latterell; MacNealy and Heaton; Mendelson; Rentz; Sides; Sullivan and Porter) and intersections between disciplinarity and professionalism (Faber, Savage). With their focus on larger programmatic and disciplinary issues, many of the aforementioned authors typically address program naming in tangential fashion, although some acknowledge what might be at stake when naming a program or, in some cases, an entire field of inquiry. MacNealy and Heaton suggest that the name “Professional and Technical Communication” may best represent the field’s scope and hope for acceptance: “…if we want to enhance our image among those outside the field, the term ‘professional’ might be a better choice than ‘technical’ because it is more inclusive and it sounds less mechanistic.” (55). Dayton and Bernhardt’s 2003 survey of ATTW (Association of Teachers of Technical Writing) members asked respondents what the field should be called, offering a variety of fixed-response possibilities from which to choose. The top three choices included: “Technical Communication” (39%); “Professional Communication” (32%); andProfessional Writing” (10%). However, in an open-ended follow-up question, respondents offered still more alternatives and noted the importance of having a name that communicated clearly to outsiders but that acknowledges specific contexts (29-30). We know, then, that naming—of the discipline, of programs—is a contested process. But beyond being a critical choice in the early stages of a writing program, we believe that a program name is a powerful site from which to begin examining a program’s history, politics, and function—a program name tells a compelling story. We argue that any study of naming becomes, in part, a study of 1) historically-situated program development, and 2) program execution, one test of a name’s veracity and scope, as well as the implications of its signification. Thus, in this chapter, we trace the development of the professional writing minor at the University of Wyoming through a narrative chronology that constructs a constellation of the voices (writing faculty, other English department members, administrators, and students) giving shape to the minor as it currently stands; specifically, we examine our “starts” and “false starts” before turning to 20

Starts, False Starts, and Getting Started the present challenges of “getting started.” In doing so, we map the vast array of connected and disconnected questions, concerns, and values that come into play when a program of this kind is developed and named. We believe that the archaeology of a program name can be uniquely generative as a site of research, a catalyst for institutional critique, and, consequently, a means of reclaiming a name and program. And while we acknowledge the power of more abstract conversation about naming, we assert that a local focus might yield more granular insight into this highly contextualized process, insight that has the potential to enrich—and complicate—our sense of the complexity of both naming and program development. finding our own voices: windows to past, present In approaching the question of program naming, we prioritized the two broad currents identified above: 1) historically situated development and 2) program execution. To that end, we crafted a quasi-ethnographic approach to researching our name and the issues and events that both precipitated and emerged from it. In short, we compiled information and perspectives through examination of: • our own personal narratives written from the perspective of writing faculty deeply invested in planning, teaching in, and overseeing the program • semi-structured interviews with past and present members of the English Department (faculty, students, administrators), many of whom played an integral role in the development and launch of the program • files and archives containing a variety of documents pertaining to the minor (e.g., course approval forms, meeting minutes, related grant proposals, email correspondence regarding the curriculum, computer classroom, etc.). As writer-researchers, we represent both a historical cross-section of the writing history at UW and the range of responsibilities for program execution at our university. All of us are situated in the Department of English. Some of us work as academic professional lecturers (APLs), which are extended-term teaching positions (six-year renewable appointment and opportunity for promotion). Others are assistant and associate professors, respectively, in writing-related fields. 1 Some of us have a significant measure of professional writing experience outside the academy in addition to experience in other fields; others have 21

Starts, False Starts, <strong>and</strong> Gett<strong>in</strong>g Started<br />

the present challenges of “gett<strong>in</strong>g started.” In do<strong>in</strong>g so, we map the vast array<br />

of connected <strong>and</strong> disconnected questions, concerns, <strong>and</strong> values that come <strong>in</strong>to<br />

play when a program of this k<strong>in</strong>d is developed <strong>and</strong> named. We believe that the<br />

archaeology of a program name can be uniquely generative as a site of research,<br />

a catalyst for <strong>in</strong>stitutional critique, <strong>and</strong>, consequently, a means of reclaim<strong>in</strong>g a<br />

name <strong>and</strong> program. And while we acknowledge the power of more abstract conversation<br />

about nam<strong>in</strong>g, we assert that a local focus might yield more granular<br />

<strong>in</strong>sight <strong>in</strong>to this highly contextualized process, <strong>in</strong>sight that has the potential to<br />

enrich—<strong>and</strong> complicate—our sense of the complexity of both nam<strong>in</strong>g <strong>and</strong> program<br />

development.<br />

f<strong>in</strong>d<strong>in</strong>g our own voices: w<strong>in</strong>dows to past,<br />

present<br />

In approach<strong>in</strong>g the question of program nam<strong>in</strong>g, we prioritized the<br />

two broad currents identified above: 1) historically situated development <strong>and</strong><br />

2) program execution. To that end, we crafted a quasi-ethnographic approach<br />

to research<strong>in</strong>g our name <strong>and</strong> the issues <strong>and</strong> events that both precipitated <strong>and</strong><br />

emerged from it. In short, we compiled <strong>in</strong>formation <strong>and</strong> perspectives through<br />

exam<strong>in</strong>ation of:<br />

• our own personal narratives written from the perspective of writ<strong>in</strong>g faculty<br />

deeply <strong>in</strong>vested <strong>in</strong> plann<strong>in</strong>g, teach<strong>in</strong>g <strong>in</strong>, <strong>and</strong> oversee<strong>in</strong>g the program<br />

• semi-structured <strong>in</strong>terviews with past <strong>and</strong> present members of the English<br />

Department (faculty, students, adm<strong>in</strong>istrators), many of whom played an<br />

<strong>in</strong>tegral role <strong>in</strong> the development <strong>and</strong> launch of the program<br />

• files <strong>and</strong> archives conta<strong>in</strong><strong>in</strong>g a variety of documents perta<strong>in</strong><strong>in</strong>g to the m<strong>in</strong>or<br />

(e.g., course approval forms, meet<strong>in</strong>g m<strong>in</strong>utes, related grant proposals,<br />

email correspondence regard<strong>in</strong>g the curriculum, computer classroom,<br />

etc.).<br />

As writer-researchers, we represent both a historical cross-section of the<br />

writ<strong>in</strong>g history at UW <strong>and</strong> the range of responsibilities for program execution at<br />

our university. All of us are situated <strong>in</strong> the Department of English. Some of us<br />

work as academic professional lecturers (APLs), which are extended-term teach<strong>in</strong>g<br />

positions (six-year renewable appo<strong>in</strong>tment <strong>and</strong> opportunity for promotion).<br />

Others are assistant <strong>and</strong> associate professors, respectively, <strong>in</strong> writ<strong>in</strong>g-related<br />

fields. 1 Some of us have a significant measure of professional writ<strong>in</strong>g experience<br />

outside the academy <strong>in</strong> addition to experience <strong>in</strong> other fields; others have<br />

21

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!