Harkness-Regli, Susan. “What is the Relationship Between Professional Writing and Rhetoric?” in Professional Writing and Rhetoric: Readings from the Field. Ed. Tim Peeples. Addison Wesley, 2003.
A quick re-reading of this essay because I needed a way to bridge Rhetorical Analysis (one of Clark’s 4 Categories of Rhetorical Technology) and the Rhetoric of Technology (one of Spilka’s 3 Areas of Knowledge for TC). Brooke provided a design link, but I recalled Harkness-Regli’s (HR) early essay as an attempt to recover big R Rhetoric from within TC practices.
Here HR is reclaiming invention, as an act of meaning making, as the TCer’s activity. Similar to Brooke’s move to cast the five cannons as performance, HR is arguing that the TCer’s expertise in invention lies in an ability to adapt rhetorical heuristics “to situations of interdisciplinary collaboration.” This aligns nicely with Alber’s later model of the TC interdisciplinary/practice hub: IA, ID, Human Factors, and Management; with TC in the hub position.
HR asks: “If we believe the technical writer is a professional rhetor and not simply a document technician, we have to ask ourselves where is the expertise the technical writer contributes to the invention process?” My marginalia indicates that HR should see Brooke for an answer. In the meantime, she provides a model in which the TCer is a rhetor who treats knowledge as an activity. “…the rhetor’s expertise lies in knowing how to perform knowledge in a communal, dialectical context…”
Specific to my purposes (and my initial reason for revisiting HR) is her treatment of information structure analysis as a TC meaning making activity. Before IA was the label de jure, HR was claiming that practicing TCers have a “deep understanding of how information is typically structured according to the principles of grammar, usage, and genre conventions…” This is the most succinct statement about the traditional relationship of TC to IA that I have found. It is perhaps so because HR does not identify IA as such, and perhaps because she writes of a place of practice from which I came.
Tuesday, July 24, 2012
Sunday, July 22, 2012
look, up in the sky
I wanted to bring in some notes from this text simply as a means to create continuity with my previous placements of Johnson-Eilola’s work across my major exam. In supporting my minor exam efforts, Johnson-Eilola (JE) provides a lens through which we can consider the activities of information-based (actually, information-saturated) cultures. From this expansive position, we can narrow the focus to individuals (symbolic-analytic workers) who perform specific meaning making activities.
JE is asking us to see culture and technology as contingent, multi-dimensional, fragmented and constructed locally rather than universally. “Technologies are not isolated and neutral things that can be moved from context to context without change. “…technological inventions are not simply dropped from the sky… we integrate them into our specific, local situations. We create, import, use, and misuse them… often for purposes their inventors never intended.” – Spinuzzi’s point in his ethnography of DMV workers; Brooke’s point about why we need to understand the rhetorical nature of modern technologies and the way they shape and are shaped by culture. In direct alignment with Brooke’s rhetorical performances, JE claims “Information is not a tool, record, or plan of work: It is the environment for work and the work itself: the datacloud. Moreover, information is not something to be rigorously controlled and structured: it is not something to be easily understood: it is something to be played with, challenged, and confused by, experimented with and transformed. These are all aspects of postmodern work.”
Technology creates profound shapes and patterns of working, living, and communicating. Akin to Spinuzzi’s workplace analysis and ethnographies… “We have come to work with information as a primary environment and resource… Rather than established frameworks and ground rules early on, users [learn and create] on the fly… the users manipulate preexisting data, filter, cut, paste, and move…” – My point exactly in regard to the ubiquity of technology and the devaluation of the TCer’s position.
The necessity for Information Architecture as a modern practice and discipline? “We live in a cloud of data – the datacloud – a shifting and only slightly contingently structured information space. In that space, we work with information, rearranging, filtering, breaking down and combining. We are not looking for simplicity, but interested in juxtapositions and commonalities.” The knowledge worker as practicing IAer.
For my purposes, I want to focus on JE’s use of symbolic-analytic work in his framework. “People in this type of work identify, rearrange, circulate, abstract, and broker information and symbols to produce reports, plans, and proposals.” Pre-1990s this was a functional description of the TCer. Recently, this is a job description for an IAer. Practically speaking, this is what every knowledge worker in an information economy does. There should be no surprise why scholars such as Albers, Still, Mazur, and Carliner continually seek ways to re-value TC as a practice.
JE uses a simple observation to make an important point: How we use computers has changed dramatically in the last 50 years. Specific to his position, JE is demonstrating hwo the “space” of the computer interface has changed the way we interact with information – how we shape and are shaped by various conceptual objects that are tangible and ephemeral, present and inferred, explicit and implied.
Specific to my focus and reading, I want to make an equally important point: Who uses computers has changed dramatically in the past 50 years. The ubiquity of computer-mediated communication, information processing, and knowledge creation has led to the rise of the symbolic-analytic worker and the skills such a worker needs to function. My claim is that these skills were in the traditional toolkit of the TCer. As the toolkit became democratized, TCers began to look for alternate specialized skills. Hence, the move toward IA and UX, among other practices and disciplines.
“Where previously work was enmeshed in a social context – and learning how to work involved a process of education over time – work now is increasingly fragmented and flattened… In effect the interface is not simply a tool, but a structure for work…”
“Nearly every type of symbolic-analytic or articulation work requires the ability to work at an advanced level with information spaces… Unfortunately, formal education often fails to provide the complex environments necessary to teach students these skills.”
Specific to my exam: IA as a means of exploring the new information spaces of work. IAers bring order to space, balance form and function. “Yet information architecture… is not capable of providing and environment proper for articulating symbolic-analytic work in the datacloud.” IA’s short-comings: IAers work “under the assumption that order can and should be brought to chaotic information… Symbolic-analytic work is an ongoing oscillation between chaos and order.”
IA provides a starting point – it is not the goal.
ewe ex
I’ve mapped usability (user experience or UX) to the Human Factors spoke on Albers’ Technical Communication hub (TC at the center of IA, ID, Management, and Human Factors). I also find a relationship among Digital Literacy, Information Literacy, and Human Factors – particularly in regard to the practices, activities, and performances of UX professionals (workflow visualization, work process analysis, usability evaluation, and user-centered design).
Here Redish reinforces the relationship of IA-like activities to the traditional position of the TCer within design and development teams. While she agrees that UX professionals come from many different origins, (“[U]sability, user-centered design, and UX design also come from technical communication"), her narrative documents TC’s progression toward usability, mirroring some of my own experiences. Redish writes of interdisciplinary design teams in the late 1970s in which TCers performed front-end user analysis, task analysis, context analysis, and evaluation. TCers, she notes, were performing these tasks as natural extensions of their training in rhetoric and communication years before the term “user experience” was used in a job title. “Not all realize that while technical communication is a practice, it is also a field with underlying theory and research – in rhetoric, discourse analysis, conversational analysis, Speech Act Theory, pragmatics, information design, typography, and cultural studies.”
In a corollary published two laters, Redish and Carol Barnum revisit Redish’s earlier claims and expand the position looking at UX/uasbility from the inside out. This allows them to show the interdisciplinary nature of UX/usability in much the same way TC has done over the years. Yet I find in this positioning some amount of reaching to demonstrate how the continuing expansion of TC roles and responsibilities is reason enough to place TCers at the center of UX/usability. When Barnum states that “… technical communication has grown and expanded beyond the basic tenets of rhetoric and become a discipline,” I have to wonder why so many TC scholars continue to find it necessary to express TC’s relationship to Rhetoric and its shared DNA with Composition.
At a practical level, the corollary does help to further flesh out my map by identifying a range of UX/usability positions, formally held by individuals with “technical writer” on their business card (information architect, usability specialist, user experience designer, usability consultant, user experience architect, etc.).
Monday, July 16, 2012
what's yours is (was) mine
Salvo carves out a more detailed position in the proximal space that Still and Albers identify between the TCer and the end user. Here, Salvo is looking at IA as a practice – as an activity; some set of procedures accomplished rather that something conceptual. Specifically, he wants to see IA become a critical practice for the TCer. In this way, Salvo is looking for TC to not only reclaim activities recently lost to HCI, IA, and usability studies, he wants to claim IA’s activities as those belonging to TC.
Ah, the discipline wars…
“Technical communicators are not necessarily technical experts; they are information architects who practice a rhetorical craft necessary to build solutions that address the contextual needs of users.”
Salvo see the TCer as an “informed rhetor” who moves away from the common practice of describing the world to a practitioner who interacts with and engages the world (there are hints of Brooke in this call). “The technical rhetor interacts with technology … by creating the context for technological design … the metaphor information architect … ably represents the demands made the technical rhetor.”
Similar to Still’s and Albers’ proximal space, Salvo sees IA (as activity) occurring between analysis and performances that inform the technical rhetor’s design. IA as an art, science, and business of organizing communication. Yet going to back to my earlier comments, when scholars attempt to move IA this far into activity and performance, it feel more like ID.
Back to the TCer doing more than describing: the challenge is to move from describing the rhetorical situation to engaging the situation. “I do not expect technical communication practitioners and faculty to look beyond documentation as the predominant activity of technical communication professionals [thank you!] … Information architecture presents an opportunity to shift the focus of TC from end-user documentation, and from short-term needs, to the critical articulation of the technological future of organizations and in culture at large… Information architecture is not a protected space from which to observe technocultural development but a place within and among technology users and designers where technical rhetoricians engage technologies and social relationships.”
Salvo is making this call in reaction to the devalued position of the modern TCer. He cites outsourcing as one cause of this devaluation, but it is more complicated than that. The ambiguity of technology and information production tools is more to blame than outsourcing. As knowledge workers develop the skills to create and manage information products (see Spinuzzi), the role of the TCer is marginalized. Casting about for traction, IA (as a discipline) becomes a space in which the trained TCer can feel comfortable – the nomenclature and language is the same. A deeper look at once inside reveals that applied IA theories look strikingly similar what the TCer has been doing for a good long time. With a simple tile change and new business card, the TCer is now an Information Architect value, which went unrecognized in the past, back to the organization.
In this way I see IA not as something entirely new or unique. The TCer has long performed the activities associated with IA. Labeling these activities as such – as a new discipline, practice, and field – allows the TCer to draw a distinction between the practices of the skilled and self-taught knowledge worker and the formerly educated and trained TCer – the informed rhetor.
proximal spaces
Still and Albers provide a brief editorial outlining a direction for TC. Their call for TC’s movement toward (into) usability practices is one area of disciplinary overlap for TC and IA.
Still and Albers are claiming that the TCer’s perspective is valuable (and therefore should not be ignored) as usability practices increasingly require knowledge from user experiences, which were previously ignored. While their claim is heavy with presumption about the range of skills and tools available to the TCer, it does highlight the TCers traditional (modern?) position in proximity to the end user. This proximity – actually, the space between the TC and the end user – is where I see IA trying to stake out a piece of HCI and usability studies. I similarly see this space as a territory formerly occupied by TC, yet increasingly encroached on by IA, HCI, Usability, and other more timely, modern, and sexy disciplines.
“… technical communicators have a vital role to play in retooling usability… Poised on the line between quantitative and qualitative, theory and practice, producer and user, science and rhetoric, and information and knowledge, technical communicators have important insights that have the potential to make usability studies into a more relative and more relevant discipline.”
further organization and orientation
Information architecture has somewhat different meanings in different branches of IS or IT architecture. Most definitions have common qualities: a structural design of shared environments, methods of organizing and labeling websites, intranets, and online communities, and ways of bringing the principles of design and architecture to the digital landscape.
Example definitions include:
- The structural design of shared information environments.
- The art and science of organizing and labeling web sites, intranets, online communities, and software to support findability and usability.
- An emerging community of practice focused on bringing principles of design and architecture to the digital landscape.
- The combination of organization, labeling, search and navigation systems within websites and intranets.
- An emerging discipline and community of practice focused on bringing principles of design and architecture to the digital landscape.
The difficulty in establishing a common definition for "information architecture" arises partly from the term's existence in multiple fields. In the field of systems design, for example, information architecture is a component of enterprise architecture that deals with the information component when describing the structure of an enterprise.
While the definition of information architecture is relatively well-established in the field of systems design, it is much more debatable within the context of online information systems (i.e., websites). Andrew Dillon refers to the latter as the "big IA-little IA debate". In the little IA view, information architecture is essentially the application of information science to web design, which considers, for example, issues of classification and information retrieval. In the big IA view, information architecture involves more than just the organization of a website; it also factors in user experience, thereby considering usability issues of information design.
Friday, July 13, 2012
ia and tc - again
I started with Morrogh some weeks ago and then went off on the threads dangling out of this narrative. From a historical perspective, this is a great foundational text (similar to Adams and Connors within Tech Comm). I’m wrapping this up here just to get a sense of closure and to affix a working definition of Information Architecture to my theory/practice map.
I recommend this text for anyone interested in the history of computing and related technologies. In that regard, it’s a really quick and fun read. For my purposes, Morrogh provides a timeline for the practice of information architecture and identifies the point at which that practice becomes formalized as a discipline.
Starting with ENIAC and ERMA, we see the emergence of a need to consider how computerized information technologies are and could be used by multiple types of end users for multiple purposes. With the advent of personal computing, this need becomes a necessary focus – the first usable conception of information architecture. “… professionals from multiple disciplines (information architects) are developing an orienting vision that is inclusive of new computing technologies, the individual human intellect, the conceptual structures humanity has collectively developed for managing information over many centuries, and the unique and pragmatic needs of clients and users” (64).
Specific to the relationship of TC to IA – the need to document, communicate, and instruct users each time new organization, navigation, interaction, flow, etc. is introduced in the information product. At this point the TCer begins to practice information architecture. Moving the TCer closer to the design phase (a move which began in the early 1980s) required a broader understanding of IA and an awareness of how the multimedia information space is more complex than traditional print and static information spaces (see Brooke). “This new kind of information space was complicated, confusing, undefined, and defied the traditional conceptual models used by information designers to design usable and coherent information environments” (69).
IA begins to emerge as a recognized field in the late 80s/early 90s when organizational computing and personal computing shifts away from a communications-engineering point of view toward an information-centric point of view. “From this conceptual shift emerged the notion of cyberspace, an information space that exists apart from, rather than stored in, any single of multiple computing device.” This shift causes the TCer to emphasize interaction with information (rather than the interface) and the design of information within computer-mediated information environments (see Spinuzzi).
Jump ahead to the era of the web. “Because the Web is a networked, multiuser, multimedia environment where users communicate, collaborate, and interact … it shares organization, navigation, interaction, and flow characteristics with all the information and communication technologies that predate it. All of these characteristics have yet to be fully synthesized in the Web information space. This monumental task is the focus of the emerging profession of information architecture” (93).
Morrogh's narrative starts to break down for me when the he moves toward defining IA. My position is that when IA becomes a design process, it shifts into Information Design (ID). It's the "big IA / little ia" debate. So for my purposes, at this point I’ll recover an earlier effort to clarify the shift.
Similar to IA, ID carries multiple definitions and applications. In web contexts, ID ranges from developing maps and signage to simple web pages. As a practice, ID has been described as an interdisciplinary approach that combines skills in graphic design, writing and editing, illustration, and human factors. On a more ephemeral level, ID has been described as a position or stance one takes. Beth Mazur has likened this stance to a political or moral stance that we take the design or an information product to improve the quality of the communication. More specific to [my understanding of IA]; ID has been described as the act of designing and deploying content in such as a way to achieve the performance objectives for specific end users – objectives captured during IA analysis.
Of most value to my mapping effort, Morrogh identifies trends in IA curricula development. Clearly, IA is an interdisciplinary discipline – co-opting aspects of other disciplines in much the same way that IDDE has evolved. At the graduate level, library science and information science programs hold sway. At the undergraduate level, there is ample space for IA in the TC classroom – particularly a classroom based on the studio model. “A design studio/laboratory approach to teaching IA would help to situate the discipline among design professionals, would provide models for IA pedagogy, and would also provide a path and model for the professional development of individual practitioners and for the profession as a whole” (141).
Thursday, July 12, 2012
of cannons and new media
Admittedly, I came to Brooke with the purpose of building out the theory/practice map for my first minor exam. I realize he is not speaking directly to the relationships among various disciplines. However, his emphasis on new media has implications for practicing information architects (IAers) and technical communicators (TCers). While his interest is clearly on teachers of Comp and Rhet, the extension to those who practice in these spaces is logical (or so I will claim). My reading below is therefore well short of a critical summary, and likely rife with misinterpretations.
In regard to my mapping effort, Brooke aligns nicely with Clark’s rhetoric of technology (the hub/spoke metaphor is working well so far). Brooke’s sandbox is hypertext – specifically the claims and arguments of the post-hypertext era. He places his call for a modern treatment of hypertext between technology (new media) and rhetoric (more accurately, his re-imagining of the five cannons). “We shape our technologies even as they shape us.” Brooke is concerned with practices of new media technologies that enable and assist – and this is precisely the point of intersection where IA and TC practices occur and overlap.
Technology as a linga franca – connections and crossings of boundaries.
Specific problem in IA and Human-computer Interaction (HCI): “… we frequently assume that our individual (or even community) experiences with various technologies can be extrapolated for all users, or that the values of those experiences are the same at every level of interaction.”
“Any rhetoric of new media should begin with an understanding that our unit of analysis must shift from textual objects to medial interfaces.” What are the implications for teaching this shift in the TC classroom? What does this shift look like at the curricular level? Brooke is calling for a disciplinary bridge – “… teachers and student of writing … are indeed uniquely positioned to contribute to discussion and debates about new media … this presumes that we reorganize the various contributions that information technologies make to rhetorical situations.”
This is where IA and TC can help! The implication for IA – and by extension TC: “… we must begin to move from text-based rhetoric, exemplified by out attachment to the printed page, to a rhetoric that can account for the dynamics of the interface.” This move Brooke calls for is based on his re-imagining – really a modern interpretation – of the five cannons: invention, arrangement, style, memory, and delivery. This re-imagining asks us to consider the practices associated with the cannons (cannons as activity, rather than static objects) against new media and the rhetorics of technology.
Invention: “… practices of invention, writing, and reading do indeed differ from those associated with print technology” – this is a critical point understanding for the IAer and TCer. These differences are realized through a broader understanding of invention not as a singular activity with a single end point, but as an ongoing activity – a continual process of rhetorical activity.
Arrangement: Brooke pulls arrangement back out of invention and delivery, recasting it as “arrangement of pattern.” This re-imagining is only possible in a context of technology-mediated production and products. Implications for IA – “The model of [online] space … is an active one when compared to the passive conception of space as container … attend to the spaces that we build through the creation of [online] presence… work ourselves free of the regularity of sequential media…”
Style: We must consider style in terms of “interfaces” rather than static texts. Implications for IA – “… new media interfaces … help us move from the abstracted single perspective of the reader of a static text of the viewer of a painting to the multiple and partial perspectives necessary for many form of new media.” The modern IAer must allow for an expanded concept of style as interface that encourages examination of the viewer/user/reader. “Just as we look at and through interfaces, we also look from a particular position … an emergent quality of a specific interaction among user, interface, and objects.”
Memory: Implications for IA – we need to understand the effects that changes in technology have on conceptions of individual memory. “…we need to think of memory not simply as storage of data, but also in terms of the construction of pattern…” This expanded notion of memory is complicated by the “persistence” of information and technologies that support and create that persistence. “…new media challenges our traditional notion of memory as storage … its ability to emulate … background processes … through new tools … aggregation…”
Delivery: Implication for IA – delivery as performance in the context of new media – more precisely the technologies that enable this performance. IAers and TCers need to understand delivery as performance if they are to fully understand the rhetorical complexities of communicating with and through new media. “Although we understand at some level the idea of performing a role or particular identity, however, the notion that discourse is performed is largely foreign, except in certain contexts…”
My reading only, with humble apologies to an accessible scholar, a wonderful teacher, a candid mentor, and all-around good guy…
Wednesday, July 11, 2012
ia/tc and ...
Clark provides another useful organizational structure for my purposes. I’m already seeing an intersection with Brooke and Albers. Similar to Spilka, Carliner, Albers, Johnson-Eilola, Selber, etc., Clark is making a claim for an expanded understanding of Technical Communication theories and practices. His specific claim is that technical communicators need to be actively aware of the rhetorical nature of the technologies they use in their work. Echoing Spinuzzi’s claim and abutting much of Brooke’s argument, Clark is drawing off activity theory, rhetorical theory, and genre theory to buttress his position. “Technologies are tools with rhetorical constructions and implications.” With this simple statement, Clark seems to move the tools vs. writing debate to a meta level. What does it mean to be a rhetorically savvy user of technology?
Clark’s rhetoric of technology is based on four extremely useful categories which, like Spilka’s “areas of knowledge”, serve a heuristic function in my mapping effort. 1) Rhetorical Analysis, 2) Technology Transfer, 3) Genre Theory, and 4) Activity Theory.
IA/TC and Rhetorical Analysis: thinking about technological problems from a rhetorical perspective. “We must argue for a rhetorical approach to technological designs and implementations that place users, rather than systems, at the center of our focus…” (93).
IA/TC and Technology Transfer: the study of the process by which technologies are moved into an organization and adopted or rejected. The rhetorical approaches of vendors, customers, and users… the marcom and RFP – the evaluation documentation. I’ve been on all sides of this transfer at different places in my career. I do read a bit of anti-objectivist/positivist sentiment in Clark’s claim here – if not “anti” it’s certainly a less objectivist position than others. “There is no clearly objective fact or physical entity that proceeds uninterrupted from the lab to the market. The entire process is one of interpretation, negation, and adjustment.” This just feel like a position on one side of the Science Wars debates of the 1990s, but I do appreciate Clark’s position and sentiment.
IA/TC and Genre Theory: focuses on the rhetorical construction of the information product. Miller’s definition helps here: Genre is “typified rhetorical actions based in recurrent situations.” Genres are not different formats; they are regularized structures (of concern to the Information Architect).
IA/TC and Activity Theory: the social perspective; designates structural ways for incorporating discussions (of concern to the Information Architect). Groups or individuals are analyzed with a triangular approach that emphasizes the multi-dimensional interconnections among subjects (individual, dyad, group), mediational means or tools, and the object or problem space on which the subjects act.
first minor exam
A quick note about Spilka and this text… the chapters herein extend claims and arguments made Albers, Johnson-Eilola, and others. She wraps the chapters around three “new” areas of knowledge in the field [of technical communication]: 1) Rhetoric of Technology (see Brooke, notes forthcoming), 2) Information Design, and Content Management. The sum of the text is an argument that these three areas of knowledge now constitute the fundamental knowledge (and associated skills) in the field of Technical Communication.
Spilka is working through claims about how technical communicators must adapt to the effects of a digital revolution that has altered how information is gathered, assimilated, applied, recreated, repurposed, etc.
Organizing thoughts for Minor Exam 1
A few organizational points to help frame my thinking and the resulting disciplinary/theory map…
Information Architecture (IA) focuses on the system in which information resides. Information Design (ID) focuses on the information. How these two foci map Technical Communication (theoretically and practically) is what we’re concerned with here.
On ID and Tech Comm – The technical communicator’s range of digital literacy; data and information about that data (meta). In addition to the traditional focus on sentence-->paragraph-->document, the technical communicator must understand and be qualified to deal with design-->context-->reception – to be able to respond to the rhetorical exigency of information production.
ID is attentive to context by transcending sentence- and paragraph-level content and the design or written communication intended to be placed on the page; it now points toward the organization and storage of that information for future use (IA).
My new business card: “Rhetorically trained, human-centered communication specialist”
Tuesday, July 10, 2012
hubs, spokes and extensions
Longo, Bernadette. Human + Machine Culture: Where We Work in Digital Literacy for Technical Communication: 21st Century Theory & Practice. Editor Spilka, R. Routledge, 2009.
I’m bundling Albers and Longo here because they provide a nice transition into my first minor exam, which considers the relationship of Technical Communication to Information Architecture (IA). Both Albers and Longo are addressing the expanding role (more precisely, the expanding skill set and tool box) of the modern technical communicator. IA and related activities (web design, information modeling, human-computer interaction, etc.) are very much a part of that expansion, which provides one space of intersection between the disciplines.
With Albers, we see a re-articulation of the tools vs. technology issue (DreamWeaver is a tool which you might teach in the tech writing classroom; markup languages used in DreamWeaver are technologies that you might also teach in the tech writing classroom). His central point is one that we made for WRT 417 – we tend to confuse tools with technology (RoboHelp is a tool, but help authoring is comprised of various technologies).
“More than dealing with issues of how to use one tool to perform a task, we need to teach and consider how using various tool’s features or technologies affect the documentation process” (Albers 267).
Albers does provide a useful schematic of the relationship of various activities to Technical Communication. Albers’ schematic places Technical Communication as a hub within a wheel. Spokes emanating from the hub connect to Information Architecture, Information Design, Management, and Human Factors. Technical communicators need to “coherently participate in the conversation occurring around the cross-functional and interdisciplinary team table” (Albers 269).
The terminal points at the end of the spokes will, no doubt, have spokes of their own as we move through the remainder of the readings. I’ll use the schematic as the foundation to an argument/position map similar to the one developed for the major exam.
Longo (who I’ve always thoroughly enjoyed -- every practicing technical communicator should be required to read Spurious Coin), is also making a claim that practicing technical communicators need to be aware of technology – of how computer mediated environments shape cultures based on those the technology includes AND excludes. “Technical communicators especially need to understand the human + machine culture, since we operate within it and it profoundly influences the communications we craft and their effects on groups of people… technical communicators also have the power to invite people into the community with/through technological knowledge and teach them the rules – or not… technical communication is a techno-scientific tool through which value is assigned to knowledge” (148-54).
A heady piece – the implications of digital literacy on conceptions of culture, community and knowledge. In the past decade, scholars such as Longo and Albers have used these claims of disciplinary expansion and inclusion to align the discipline and practice of technical communication with the likes of information architecture, information design, and human-computer interaction.
Subscribe to:
Posts (Atom)