Thursday, October 17, 2013

Concluding thoughts (where'd the time go?!)

"What Do Technical Communicators Need to Know about Genre?" Well, according to Henze, tech comms need to be familiar with the company's genre(s) of writing. This will help the tech writer be effective in the job as well as modifying existing genres. To illuminate: Henze gives the example of a tech writer in a cell phone company who had too many steps in an instruction manual, potentially causing customers to think the phone it too difficult to assemble (342). So, it's important for tech writers to review the company's documents to get a feel for the ways a company uses genres. I wonder about genre here: What about audience? Is it more of an issue? It seems like genre is getting thrown around and maybe used incorrectly?

Then there's Blackeslee and Gerald's: "What do Technical Communicators Need to Know about Writing?"
Also thinking about how tech comm need to be flexible enough to adapt to changing workplace environments, but now the focus is on writing. Tech comms need to continually learn about stuff related to the company, expand on writing skills, and learn new technologies (382). I guess what bothers me about this piece is that you could exchange 'writing' with 'genre' and it wouldn't change the meaning of the text all that much. I felt that the collaboration and international environment article were more insightful...

Burnett et al.: "What Do Technical Communicators Need to Know about Collaboration?"
Pretty much the same thing as in-class collaboration, only now it's a part of daily life rather than an occasional class activity. This hinges on the other articles because one can use the same idea when it comes to collaboration, that is, one must be flexible, knowing that not all groups will work the same, dealing with "social loafing," conflict and how disagreements can move things forward rather than hinder progression. I think this is super important for folks to realize that the workplaces they enter into could require group work. They will need to know how to do this well, in spite of what they might feel about collaboration vis-a-vis college. 

Amant: "What Do Technical Communicators Need to Know about International Environments?"
I kind of liked how Amant made broader cultural awareness as a selling point for tech comm ("...skills than can increase job security today and in the future") (494). This may not be the most noble way of looking at cultural awareness, but it's honest! And I think that even if people go creating more cultural awareness by looking at the monetary aspects, doesn't mean they won't be impacted more ethically in the long run.

This last run of articles has me wondering about the other side of 402: the professional writer and how these articles could be of utility for them as well. Do these articles cross over? If so, which ones and how to make them accessible for the professional writer?

Wednesday, October 9, 2013

Brad Mehlenbacher: "What is the Future of Technical Communication?"

Mehlenbacher identifies the problem technical communicators face is an issue that "is largely a communication challenge" (189). In today's workplace, the idea of tech communicator as "expert" is mostly nonexistent, so it's more important to be a facilitator between technology and employees. As the workplace is downsized, tech writers are expected to do more. This had led to the increase in "wicked problems" for tech communicators (191). In the past, problems were "tame problems" or issues that have a clear beginning and end. Mehlenbacher uses the example of chess and how one can use similar strategies to win games, strategies that are repeatable, learnable, and can be improved on (191). Wicked problems, on the other hand, have no real beginning or end; strategies that worked in one instance may not work across others; and repetition won't necessarily make for better tech communication. Wicked problems are bad because 1. tech communicators may generalize a problem and apply the same method to any issue that's similar (becoming static rather than dynamic). 2. The general becomes the rigid and used on more complex issues requiring a different solution. 3. Tech communicators can ignore what they don't understand and use what they do know to make it easier for them, rather than what's most valuable for the situation (192).
Because of wicked problems, "rhetorical self-consciousness" is decreasing. To be rhetorically self-conscious, is to know about modes of persuasion, understanding that wicked problems take time to figure out, and to reflect upon the problem (193).
Tech communicators no longer need to be experts. The increase in wicked problems calls for tech comms to be facilitators, "to strive to understand and mediate the relationship between complex symbolic systems and human beings" (194). In other words, to be the go-between technology and humans. Mehlenbacher stresses the importance of tech comms to reflect; to think about what went right and what needs to be improved on; to think about knowledge, how it's gained, what the person already knows, and how to navigate these spaces(197-98).
To teach this, the author also stresses that teachers themselves need to reflect on their "own learning and communication processes" (198). He recommends using many problem-solving activities in class to give students a chance to play around with a new understanding of knowledge so that decisions are influenced by "reflection rather than reaction" (200). That's what the take-away from this article is: with the workplace as it is today, tech communicators need not be experts, but facilitators. To be the most effective, tech communicators need time for reflection on issues, and to not rely on past ways of problem-solving strategies, but to continually revise as to not get lulled into a false sense of security by using strategies that are the easiest.
Connections:
Longo and Fountain- rather than looking to the future, think of the past to unearth what has worked, reflecting on who is serves (or doesn't). Close to Mehlenbacher's article in that it calls for a high degree of reflection.

Swarts- wants tech communicators to " understand the user's tasks and the functional capabilities of the tools used" (146). Goes along with future of tech writing as being the facilitators between technology and humans.

As I was reading this I was reminded of Johnson's "user-friendly" posit. Mehlenbacher wants tech communicators to be better equipped at solving problems and being mediators of technology and other employees.

Questions:
Is it possible to do the level of reflection Mehlenbacher's asking for? He admits that the workplace has become "busier." If tech communicators are on board with this idea of reflection, what if the higher-ups at a job aren't? What if they're more concerned with product than process?
 
Because Lauren always has cool pictures in her blog, here's a gratuitous picture of my Ry-guy 

Wednesday, October 2, 2013

(Don't be) Jealous of My Boogie

This week I had the nicely titled, "Living Documents Liability versus the Need to Archive, or Why (Sometimes) History Should be Expunged" by Beverly Sauer.
Sauer identifies the problem of "living documents" (which I'll get to unpacking that in a moment) and how the use of cultural studies can help technical communicators better write about risk in high stakes occupations. Cultural analysis already deals with "economic and political dimensions of science," so it only makes sense to integrate the two fields. But it's not a one-way street: she also acknowledges that technical communicators can help cultural studies, which I will elucidate later (172).
Sauer is concerned with "living documents," which are documents that are always changing to keep up with "new information, new technologies, and changing local and institutional practices" (172). She feels that using a cultural analysis lens will help technical communicators ask questions like, who is writing the documents, for what purpose, who does it serve, and what should be included in the document (175-76). So, cultural analysis then can help technical communicators by close reading documents to analyze risk for certain times in history. And it's important for tech communicators to help cultural studies folks by cluing them into moments where writing isn't sufficient in understanding and describing risk (177-78).
Sauer uses coal mines most specifically as the subject to demonstrate how to apply cultural theory. She points out how hard it is to write standards when dealing with a high risk environment where people's lives are at stake.
This is where the issue of having "living documents" and outdated material is detrimental to workers' safety. Sauer's answer is to remove the extraneous information completely from the "living document," so that it can best indicate where potential risks are, and for workers to be able to respond appropriately (180). To be clear, she is not suggesting to throw away documents, but to remove the outdated material and store it in archives.
This brings us back to Sauer's main point that tech communicators and cultural studies theorists can work together reciprocally to make better decisions on what needs to stay in a document, what needs to be removed, and what users really need to understand from the document (186). Or, as I like to think of it: don't be jealous of my boogie, let's boogie together. (I say this because there's too much dissonance between academic disciplines, and if you know the song I'm referring to by RuPaul, then you'll know it's a good metaphor for academia.)

Questions:
Of course I gotta ask it: how to implement this into the classroom? It seems like Sauer is writing to an audience who's maybe more in the field rather than teaching it. So, it seems hard to put this into practice in a classroom, but it is important to think about. Do you think students would be receptive to working with cultural studies folks? As I mentioned in my parenthetical comments, the sciences and humanities don't get along so well. I have never understood this, other than we're just skeptical of each other because we don't understand each other enough. Sauer's idea of bringing the two together are spot on (we could get a whole lot more done if we had each other's backs), but what needs to happen first?

Connections:
Graybill: Like Sauer, Graybill also argues that cultural studies can help tech communicators identify problems of authority and create social change (151-52). Unlike Sauer, Graybill goes into specific detail on methodologies, which makes me think his piece was written more for teachers of writing, rather than how Sauer seems to be talking to professionals in the field.

Britt: Calling for cultural studies into tech communication, but also adding sociology and anthropology to look at institutions (134). I find it very interesting how Britt is calling for a critique of "microinstitutions" like a writing center (135). Disciplines are too small and "macroinsitutions" are too big. Britt sees that institutions get too big and stop accounting for itself, so that's where cultural studies et al. can help bring into focus what goals an institution has and if they need changes. I like the idea of bringing the wc into the mix, but the problem there is that it has no real power to change institutional power, and wc's are now going through a shift since computers have entered the mix.

I also wonder about the Russell article from earlier this semester. It was the one where he said that lit crit should say out of tech and professional writing classes. Kind of seems like maybe that argument has been blown out of the water, but I still wonder if Russell has a point in keeping the two separate.
 

Wednesday, September 25, 2013

The world of research has gone berserk. Too much paperwork.

While fumbling my way through this week's readings, I am beginning to notice an underlying problem that, although talked about at great length, hasn't been nailed down yet: the problem of assessment in writing classes. I don't think that as teachers in the English department we don't know anymore what composition is. We've pulled comp into so many parts, then coalesced it together to where now it's gotten so big that we've almost made it obsolete. It may seem like I'm straying off topic, but stay with me...
I find this problem most evident in the "Technical Communicator as Author" piece. The authors state: "Rather than authors producing certain discourses, certain discourses are understood to produce authors" (25). Hmm. I like the use of chiasmus, but I'm dubious as to the truth of their claim. Something about this statement stinks, I just can't put my finger on why exactly. Maybe it's just the bleakness of it. Maybe because I'm not sure how this fits into their argument.
Slack et al, go on to argue that they "...would advance the re-articulation of technical communicators...as having authorial power" (41). Okay. I'm not sure exactly why this is a problem. Is it that the authors want tech communicators to take agency over their work and therefore be accountable for what they produce, or is the argument here that tech communicators aren't given their due? It seems like it's the latter, but I don't know why this is relevant to a tech writing class. Can someone help me on this one?! It's very likely that I'm missing a point. 
So, how this relates to my rant is that I think the goal of teaching tech writing is to increase the rhetorical effectiveness of the writer; to be able to communicate rhetorically in the ways that a business audience will appreciate, and that can lead to change. But articles like this one seem to have the goal of trying to make the comp field even bigger (too much paperwork), rather than getting to the root of the problem. In other words, creating more problems before solving the first set of issues.
 I'm not suggesting that issues of social import aren't relevant to a tech writing course, but what I'm wondering here is-what needs to come first? Before we consider issues like this shouldn't we be more focused on what we're doing in the classroom to prepare students to become effective rhetors, even if they don't think of themselves in that way? And it seems that it would lend itself to the issues that these authors raise when they say, "In a sense, technical communicators need to be shaken from the somnambulistic faith that their work is ethically neutral" (43). That's a heck of a sweeping statement to make! As if they don't already have the knowledge that it isn't ethically neutral and are able to control it. That's where the rhetorical effectiveness comes into play.
The Dilger piece I felt met its goal of the implications of extreme usability. It was bringing the argument back to what the Johnson book had posited, only now the issue has changed from ignoring the user to now ignoring the user under the pretense of being "user-friendly." For example, Dilger gives a list of things that should be included in web-based text, like "paragraphs should contain one idea, using topic sentences and simple sentence structure" (53), all in the name of making the web text "user-friendly." The problem with this way of writing is that it would work for some businesses, but not all.
Moses and Katz's article was interesting to me on a personal level (i.e. it made me think about email and how it was designed with business in mind, and the ways in which the professional world is insidiously taking over the private sphere), but again I wonder, how would one teach this to students? I don't know, maybe social justice issues don't have much of a place within tech and professional writing classes. I can't imagine trying to get a group of students who already look with suspicious eyes on the humanities and try and get them to care about the social, ethical, and economic issues that surround the corporate culture. And even if I did get through, they'd be mighty disappointed once getting into the professional world, set on making changes, only to realize that businesses don't want you to try and change them.
My blog this week may seem really disjointed, and I guess that's because I'm trying to figure this all out. And the more I read, the less I know. Ha!  

Wednesday, September 18, 2013

Learning Intercultural Communication Competence Linda Beamer

As we all know, the workplace is ever becoming a diverse place, yet there's a lack of multicultural practice within business culture. The thrust of Beamer's article is concerned with creating a paradigm in which to pull from, that explains intercultural communication competence is learned/taught (399). She states: "The best way to understand intercultural communication is to focus on the decoding process and the role of perception in communication" (400).
Decoding is done by the recipient of a message and do to social and cultural ideals, the message may not be clear, that is, the sender may not have the same set of mores as receiver, thus having different signs which obscure meaning for the receiver. Perception, on the other hand, is knowing that a message is being sent. Beamer clarifies this idea with differentiating signifier and the signified: "The signifier...is the sensorially perceived signal without meaning yet attached. The signified is the meaning" (401). To put this into understandable terms: I see a yellow sign on an Idaho highway with the blackened-out image of a goat. I've never seen this image on a sign before because I'm from Nebraska and we have cows, not goats. But I am from the same culture in which the sign was produced, and I have seen similar signs in Nebraska, so I know that I should be on the lookout for wandering goats. I have perceived the sign and was able to decode the message based on previous knowledge and cultural influences.
So, to increase intercultural communication competences requires those making the signs to be constantly aware of what other cultures use, by looking at their "values, attitudes, beliefs, and behaviors" (402). Beamer introduces The Intercultural Learning Model as a way of demystifying the ways in which professionals can develop intercultural communication. This entails five levels:

  • Acknowledging diversity
  • Organizing Information by Stereotypes
  • Question the Stereotypes
  • Analyse Communication Episodes
  • Generating "Other Culture" Messages      (404)
This model is both "incremental" and "cyclical" in that it's continually reinventing itself to better fit the needs of the intended audience (404).

The breakdown of the model:
Acknowledging diversity: what it sounds like- to conscientiously realize that there are differences between cultures that could block meaning for the receiver by the sender.

Organizing information by according to stereotypes: Beamer gives the example of Arabs may stand closer to you when they're speaking or that Chinese will refuse hospitality when first offered (406). She acknowledges that stereotypes don't make a culture and that's why the next level is important.

Posing questions to challenge the stereotypes: questioning stereotypes can open up the ways in which a culture may view business-related stuff like: time, technologies used, and how they make decisions (406). To aid in questioning stereotypes, Beamer offers these suggestions:

  • Thinking and Knowing: how a culture "acquire, organize, and transmit information" (408)
  • Doing and Achieving: as it sounds- what a culture does and how they go about getting it
  • The Self: if the culture values individualism or interdependence
  • The Organization of society: if there's a strong caste system versus an egalitarian culture 
  • The Universe: if a culture looks at the world revolving around humans (humans in the center), or if the world/deities are at the center.


Analyzing communication episodes: once copious amounts of information has been gathered, then the knowledge can be applied by looking at past communication. This is where one can look at what went right, what went wrong, and what was in the middle with regard to effectively communicating signals for a culture.

Generating "other culture" messages: now senders can empathize with a culture's communication style. They can create news signs based on the culture's needs or modify existing models.

Connections:
Thrush article pointing to same issues as Beamer; the workplace is diverse and we need ways of communicating cross-culturally. Thrush is different in that she adds the layer of masculine and feminine. This was missing from Beamer's article- and maybe it should have been because I got the sense that Beamer was thinking about multicultural communication from a masculine perspective, and maybe could have gone to how female perspectives can add complexity to culture.

Fukuoka, et. al.: Complicate Beamer by asking are cultures that different or is it that "assumptions" about what cultures want is what makes the difference. They look at manuals and how many illustrations are in Japanese versus American. And that's where I lose the connection because then their inquiry became more about how these respective cultures liked/didn't like lots of pictures in their manuals.

Breuch: This may be a stretch to pull a connection from "technical literacy" into multicultural communication, but the former does hinge on the latter. Breuch's posit that computers are not "neutral" but rather "political in development and use" (487), which makes me think of Beamer's notion of looking at stereotypes and how a computer could play into that. Would a professional in another culture feel "othered" in some way if she didn't possess the same tech literacy? Or would she feel more included by having that shared knowledge?

Selber et. al.: They make the call to see tech literacy as "a complex set of social practices through which meaning is made collaboratively" (501), drawing on Beamer's Posing Questions to Challenge Stereotypes to make communication inclusive v. exclusive. In other words, the more eyes on the project the better communication will be transmitted.

Questions: While we all see that the workplace is changing in diverse ways, and folks like Beamer have given an explicit way of going about teaching multicultural communication, do you wonder if the real work is in making more people aware, and therefore care, about the changing environment? Are there ways in which teachers could do activities that show the effects of missed communication? Or do teachers go over this stuff, and not push too much of the literary crit way of doing things that Russell and others are concerned about?

Wednesday, September 11, 2013

You just kinda wasted my precious time (Freedman and Adams), but don't think twice, it's alright

For this week’s reading I will be blogging about Aviva Freedman and Christine Adam’s Learning to Write Professionally: “Situated Learning” and the Transition from University to Professional Discourse.”
The authors are arguing that “[w]hen students move from the university to the workplace, they not only need to learn new genres but they also need to learn new ways to learn those genres” (311). Freedman and Adam define genre as not just reoccurring style in a text, but also how genre is also reinvented by social, cultural, ideological, and political influences (311). They then make the move to dichotomizing the ways in which the university and workplace teach and write.
Universities usually employ the guided participation method. This is the more traditional view of learning where students are given a set of issues to work on and are guided by a professor (mentor) who both supports students’ learning and models how to go about fixing a problem. The idea behind guided participation is that once the student has gained awareness of a genre, then she’ll be able to reproduce as needed what was modeled in class.
The authors then contrast guided participation with Lave and Wenger’s “legitimate peripheral participation (LPP).” Unlike guided participation, the focus of LPP isn’t so much based on learning, but rather apprenticing in real life situations where material production is the concern (312).
How Freedman and Adam’s then assessed these types of learning in the classroom versus the workplace was looking at undergraduates in financial analyst course, and graduate students who were actively interning.
What they found was that the undergrads learned from the professor modeling how to perform tasks, and then carried out their own strategies based on what they had learned in class. The grad students in the workplace had the same element of mentor-learner, and also the method of delivery (i.e. using computers), but now the writing is very different from the university. Rather than having a clearly defined rubric from which to work, the interns needed to figure out what information to include in a document, in what order, and think about for whom they were writing for, which got even trickier when they would be pulled away from an assignment to go work on something completely different.
What I felt was the most particularly interesting difference between university and workplace learning was the notion of “authentic” writing. Students are given situations that are based on actual events and then write about it, whereas the workplace is the actual event. For example, an inter taking meeting notes and has to make sure the information is accurate and easily understandable; if she fails to do this then there is no rewrite: it can hurt her credibility (323).
The authors also make the distinction that in the university, the professor has a more vested interest in students by way of the grade. If students aren’t learning then the professor is failing. In the workplace, however, there may be some evaluations based on work (almost like a grade), but, according to Freedman and Adams, evals are few and far between. Evaluations in the workplace also tend to look at the whole rather than its parts, and that there’s “sparse use of praise and blame” that goes into the eval.
Freedman and Adams conclude that there needs to be more research done on both these types of learning and how they work within their respective places, so then university student-to-workplace employee has better use of different genres.
That is where I stop being nice with this article. The authors may have done extensive research, but it seems to me that they only picked out the places that supported their claim, rather than to actually give something of import to technical writing teachers. They say nothing of how to blur these lines; nothing of how students can and do learn more than just how to write in one genre of professional writing. It’s not like there’s a lot of sonnet writing going into the kinds of writing the workplace does. To say another way: workplace writing is pretty straightforward, and it seems like the authors tried to complicate something that isn’t necessarily all that complicated! I know because I’ve been there.
Freedman and Adams also neglect to go into detail what happens when one is in the workplace, has a so-called mentor, but the mentor is unwilling to pass on what she’s learned. I saw this happen a lot- young blood comes into the office and the seasoned employee is intimidated, thus resistant to helping the new employee. With regard to evaluations: evals are grades, and some companies do give evals quarterly. Often one is not just evaluated based on the whole, but as an individual, unlike what Freedman and Adams claim.
Overall, I felt this piece was written to show the authors’ prowess, rather than giving anything substantial to the tech writing teaching field. It did help me think about the implications of the Russell article I read for last week, that if one only focuses on teaching text-based prose, and doesn’t bring in some of the criticism and how to apply that to texts then students, then they could potentially have trouble navigating the workplace discourse.
Connections: The authors are working from the same place Berkenkotter and Huckin are in that the genre of professional writing has been myopic, and that this can hurt the creditability of the workplace writer. Spinuzzi’s article is also calling for a broader view of the types of writing that takes place in the classroom versus the workplace, which has been a connecting thread so far in most of what we’ve been reading in this class. The only difference is that Freedman and Adams did it less masterfully than some of the other articles I have read.  

Questions: If it’s true that there is dissonance between the university and workplace writing, what do we do to better facilitate the move of students being students to actually being workplace producers of texts?   Should we discuss the political underbelly of the workplace? That is, when an incumbent resists helping the novice? That sometimes workplaces only want their employees to be only so literate to do their jobs, but not to think too much?

Wednesday, September 4, 2013

Lame course objectives for tech writing class (to be revised)

Objectives that students will be able to do by the end of the semester:
Learn the means of persuasion (ethos, logos, pathos)
Find the medium in which best fits the field (e.g. video, commercial, email)
Different rhetorical tropes and schemes useful in writing
How to offer feedback in meaningful ways
What goes into different genres of writing
Consider other cultures and how that might shape the writing

Russell's argument trajectory

The article I had this week was David R. Russell's "The Ethics of Teaching Ethics in Professional Communication: The Case of Engineering Publicity at MIT in the 1920s"

Russell starts off with two questions: "To what extent, in any, should business and technical writing courses serve the pragmatic needs of business and industry, and to what extent, if any, should those courses teach the concerns of literary studies? And two, What is the responsibility, if any, of the instructor of these courses to teach ethics?" In plain speak, teachers teaching technical writing classes, that come from a lit crit background, want to teach their students ethics from a humanities perspective that doesn't attend to the needs of the students. Humanities teachers don't need to teach ethics because these students already come from backgrounds that have ethically importance (working for the common good), even though it varies from the lit crit way of ethics.

He answers one right off: yes teach ethics, but "how, when, and for what purposes they should be promoted" (167). From there Russell goes into ethos of a profession- "Those values, those rules or conduct...that create and maintain the professional community, that give it its "integrity," its identity" (167). Thus begins Russell taking teachers from a lit crit background that teach tech writing. Russell traces the history of the "two cultures" : lit crit and industry writing. Tech writing is mostly taught by English folks submerged in lit crit- a field of study that has been alienated from other departments because it's seen as unnecessary. Marginalized and feeling undervalued, lit crits banded together; seeing the alienation from other professions as a badge of honor. The consequence of this is that tech writing teachers are coming into the classroom, mostly unknowingly, undermining the ethics of the various disciplines students are in, by trying to humanize them in a lit crit way. The result is that teachers are doing a disservice to the students by pushing their own agendas rather than what is beneficial for the student. I know there's a lot of lit crit, but Russell comes down hard on this particular field of study.

Russell uses the Engineering Publicity at MIT in the 1920s to illustrate how teaching tech writing can be done effectively. It was initially set up as a way for students to learn to show their ethos to government, the public, and employers (177). Used a holistic approach by featuring language, writing, reading, and speaking. Students weren't taught ethics from a humanities POV, but with case studies and how people in the field dealt with the issues. Last, students wrote as engineering professionals in genres like reports or memos rather than a critical analysis paper. The MIT program went through changes (being wildly reductive here): ending up with the same holistic view, only now with professionals, not just teachers, being invited into classrooms to speak on a broad spectrum of topics.

This all leads to Russell stating that it's not the job of a tech writing teacher to impugn the students' discipline, but rather to find out more about the field(s) in which they're teaching, so that when they do make critiques, it's coming from a knowledgeable place and knowing when those times arise (kairos).

Questions:     Is it possible to do this? To remove yourself from your beliefs enough and be willing to lean in to another perspective?

Is there space to teach some aspect of lit crit in a tech writing class?

This piece ties into Miller's article directly. He uses her argument as one of the ways in which tech writing is being approached by a lit crit POV (Ex: "...questions about whose interests a practice serves and how we decide whose interests should be served" (158).

I like Porter's article, because I think it accentuates and complicates Russell's piece. Porter takes a different spin, but like Russell, believes that kairos is important. Different spin in that where Russell was more about learning a lot about different fields, Porter is saying that teachers shouldn't interfere with students' writing, but support as needed (189). I think Russell was remiss in the idea of support.  

Tuesday, August 27, 2013

For Johnson's book User-Centered Technology, his main issue is with how technology is centered around those who produce tech stuff like computers, rather than being user-based (i.e. to have the user in mind when designing a computer so the user can take care of all issues herself.).
Johnson must have an extensive background in classic rhetoric because he brings up ideas of techne; Pg 52: "Techne...goes a long way toward providing us with a more thorough understanding of, and basis for, user knowledge."
He also talks about metis; Pg 53: "Metis, or what is also called cunning intelligence, is the ability to act quickly, effectively, and prudently within ever-changing texts."
Combining these two ideas, Johnson sets out on the arduous journey of bringing to light the issue of moving away from designer-based to user-based technology. Techne as the means to think about users of technology during construction, and Metis for knowing that tech users, even basic users, have some knowledge of what to do when a computer crashes, but may not be sophisticated enough to decipher a critical error message (Johnson 45.
This book makes sense to me as a person who has basic understanding of technology; mostly because Johnson does a good job as a rhetorician speaking to other rhetoricians who may/may not have any tech savvy-ness.
What I am more confused about would be where he's talking about, on page 94, SCOT and multidirectional artifacts. Also, pretty much anything from the last chapter- number 7.

I know this isn't very specific, but it's mostly the terms I'm getting bogged down in (I think).