Issues of Trust and Control
Over the past 10 years or so, I’ve gone from not generally making purchases or otherwise disclosing personal information online to regularly doing so. I’m sure this is the case for many people—online purchasing and using the Internet for social networking has required us to become more comfortable with it, or retreat. In this week’s reading “Privacy, Trust, and Disclosure Online,” Carina Paine Schofield and Adam Joinson examine the complex relationship between privacy and trust and our resulting willingness to disclose information in an online environment. A lot of what they covered seemed like common sense to me. Perceived privacy contributes to trust; both are necessary for us to be willing to disclose information online.
Schofield and Joinson’s explanation of the different aspects of trust stood out to me as being particularly relevant to my own evaluation of a company’s online presence. I think I regularly (if subconsciously) make judgments about companies based on the following.
- Ability, or the knowledge or competence of the company and its ability to handle my information appropriately.
- Integrity, or the belief that the company is honest, reliable, and credible.
- Benevolence, or the extent to which the company is doing right by me.
It’s almost common sense; I wouldn’t do business with someone face-to-face if I didn’t think they were competent and capable, honest and credible, and were taking my interests into account. Why should it be any different online? Admittedly, the stakes are higher in many ways online. After all, we’re leaving behind information about ourselves that doesn’t go away—ever.
I think that’s why providing users with a sense of control is especially important. Schofield and Joinson explain, “…where possible, users should be provided with control over whether to disclose personal information and the use of that personal information once disclosed” (p. 26). When we can decide whether we “prefer not to disclose” answers to certain questions, or whether we only populate the required fields, we maintain some degree of control. (For me, being able to indicate that I don’t want to receive email offers is one control option I greatly appreciate!)
Maintain some degree of control over information reminded me of the fiasco with Facebook’s privacy policy changes a few years back. Basically, Facebook changed their privacy policy, and users freaked out about it. Facebook addressed the issue a blog post, explaining in a forthcoming and straightforward way that on Facebook, people own and control their own information. This response illustrates that Facebook recognized that control (even if it’s perceived control) goes hand-in-hand with trust and privacy. By addressing users’ concerns in this way, I think Facebook did the best it could to mitigate the damage done to its users’ trust in it.
Information Society
Do you remember this band from the 80’s? There’s no real relation between this and the article, “Privacy, Trust and Disclosure Online” by Schofield and Johnson. but they included the following quote, so I couldn’t resist:
At no time have privacy issues taken on greater significance than in recent years, as technological developments have led to the emvergence of an “information society” capable of gathering, storing and disseminating increasing amounts of data about individuals. (p.16)
The focus of the article is on personal privacy and all the various aspects of that, such as psychological, physical, and interactional (p. 14), but one area that really impacts us is organizational privacy. By that I mean, the ability of the employees of our customers to retrie ve and share information without exposing it to our other customers (their competitors). We would love to implement the kind of communication that social media provides, but our customers are very concerned about keeping their proprietary information away from their competitors. Even just letting other customers see the kinds of questions they are asking could give away some key competitive details.
It is hard enough to really understand the difference between your actual privacy and perceived privacy as an individual, but I think it is probably even harder for people to make decisions in this area when they are making them on behalf of their employer. This might be the single biggest obstacle to implementing social media in business to business (B2B) communication.
The New Professional’s Guide to Interoffice Email Etiquette
In chapter nine of Digital Literacy, Rachel Spilka discusses the changes email has had on the workplace and the interactions between the people employed by them. Spilka explains (p. 241),
So pervasive and necessary are the uses of digital technology, that organizations and the people within them can be understood to exist almost literally in the digital realm… where our social and business interactions are carried out via email, video, podcasts, smartphones, Web sites and webinars, social media, listservs, wikis, and blogs.
With this phenomena the new standard, it is surprising that newly-hired professional’s aren’t given a guide of sorts on the intricacies of interoffice communications: most specifically the office email. I am not speaking of the entry-level basics of writing respectful, on-topic, spell-checked emails though. I am referring to the more nuanced happenings that we experience within email communication. And, more specifically, especially when we are emailing in an attempt to elicit a response from someone – most especially when that someone happens to be your superior.
I first noticed my dependence on the simplified, professional email approximately seven years ago. I was a newly-hired creative director working for a rapidly-growing company. The general manager, my direct supervisor, was the man with the answers… for everyone. He enjoyed this function, but as such was constantly bombarded with emails and unwelcome office drop-ins. To avoid being lost in his email inbox or shooed from his door, I utilized a very simplified email writing technique. The following rules will be of no surprise to tenured professionals, but let’s just consider this a quick overview of Interoffice Email 101.
The precursor to this email technique begins with a few simple rules:
- Always send an email if you can.
- Only call if the matter is urgent and incorporates multiple employees, and if you must call…
- Never leave a voicemail.
- Only drop-in the office if it is an emergency set to adversely effect the company budget.
When a question has lesser importance it moves down this hierarchy of communication techniques, with the least intrusive being the email. Email holds this place of honor due to this ability to be handled at the recipient’s convenience, rather than the requestor’s demand, as is true with a phone call or office visit. Once email has been determined as the communication medium of choice, other rules come into play:
- Only send one to two emails to your supervisor per day.
- Fully analyze the situation prior to sending the email and even then…
- Only ask the most important questions.
- Questions of highest importance are listed first
- Ask no more than a total of three questions.
- For each question provide the least amount of back-story possible.
More than likely this technique was not thoughtfully contrived for any professional, but rather achieved bit by bit through small successes and failures in communicating with overwhelmed supervisors. In my experience, following these self-imposed rules meant that my emails received a quick response, while other managers were not as fortunate. The higher-stake here, of course, is that without answers other managers could not move their departments efficiently toward the next task… and we all know what happens to managers of inefficient departments.
Resistance is Futile
We are the Borg. Resistance as you know it is over. We will add your biological and technological distinctiveness to our own.
– The Borg
A
t work my employee computer ID is QA4268. If someone logs into our CMS and wants to search for something that I have created, they can’t use my name, they have to know that QA4268 is me–or that I’m QA4268. Hmmm . . . now that I think about it, that is a teeny bit disturbing, which brings me to the article, Beyond Ethical Frames of Technical Relations, by Steven Katz and Vicki Rhodes. In it they state, “Have you ever noticed how some systems or procedures at work–say, a time tracking system, registration process, or evaluation procedure–are more adapted to themselves, more focused on their own efficiency and operation, than on the human being who is the ostensible object or user?” (p. 235)
They even follow this quote up with a specific mention to most CMSs and how they are often guilty of this–the one where I work is no exception. The software has all the technical capability that we require and is capable of fully delivering on everything we ask of it, but in many ways it ignores the requirements and limitations of the people that need to use it. For example, almost all the information about how information is related to each other is presented in lists or tabular reports. While this does provide all the detail, people are visual beings that work best when they can visualize relationships. The CMS asks us to bend people to the machine rather than bending the machine to the people.
The problem, as Katz and Rhodes, describe it is that you can’t separate people and technology when defining processes, procedures and tools. More and more we are merging with our technology (both literally and figuratively) to become some sort of hybrid. Katz and Rhodes point to examples like automatic spell-checkers and Bluetooth headsets as examples (p. 240). The point, as I see it, is that we need to view the relationship between people and technology more holistically. When we say that we want to implement a CMS, we can’t just select a tool and then throw people at it. Instead of a CMS we should be implementing a CME (Content Management Ecosystem). To get the most out of these technical relations, we need to make sure that the technology complements our people and that our human skills fully exploit the capabilities of our technology.
Culture Clash: Being Everything to Everyone
Once you have fully investigated your audience and considered their various cultural needs and preferences, you can fully comprehend how screwed you are and how utterly futile your attempts to please them will be. Given that most if not all technical information is delivered via the internet now, you just can’t presume to know where your audience is coming from–literally or figuratively (Blakeslee, p. 2o1). And, even if you could narrow down the geographic location, your quest could be further hampered by differences in gender or the device used to retrieve your content, as Kenichi Ishii describes in his article, Implications of Mobility: The uses of Personal Communication Media in Everyday Life.
All the authors that we read this week–Blakeslee, Ishii, and Thatcher–talk about how important it is it understand the differences between your audience segments, but unless you have a lot of time or a lot of writers, you have to make compromises. In fact, unless you know for sure that your audience is from a Particularist or a Universalist culture (Thatcher, p. 177) you are going to make some people unhappy.
According to Thatcher, a universalist approach, “. . . the default approach is to establish rule that define what is good and right regardless of the social standing of the individual” (p. 176). While in a particularist approach, “. . . the default approach is to apply rule and decisions depending on relations and context” (p. 177). So, as a technical communicator I can either choose an approach that treats everyone with respect regardless of their standing in society or a company, or I can try to write 12 versions of the content to reflect where each individual sits in the pecking order. Thank you very much, but I’m writing it once.
I like the idea of respecting cultural differences, but the internet is dominated by the universalist, western cultures that created it. The world understand the voice of the internet and has come to accept it. I would even venture to guess that that universalist voice has started to change the cultures of the people that use it. Perhaps that is why some governments (China, Iran, (formerly) Egypt) fear it so much and seek to control it. Maybe people that are addressed with respect regardless of their standing start to demand that from others within their society.
Here’s another problem I have with the idea of bending our writing style to suit the expected audience:
- We don’t often know the audience for certain.
- The audience often exists in many countries.
- What if we add another customer later that comes from another culture?
- If we use different styles for what we write, how do we reuse content to single-source new deliverables?
It surprises me that some of the articles mention that more and more content is delivered on the internet which means that we have no idea how or where it will be used, but they still advocate spending a lot of time investigating the audience. How are we supposed to do this exactly? The internet may not be a culture in and of itself, but it does have a voice and set expectations. How about we just go with that and spend more time creating better content.
I liked how Blakeslee described looking at the roles the audience members play to ensure that content meets the needs of that ROLE. I am 100% behind performing task analysis to create role-based content. I think that makes way more sense than trying to figure out how you should write a procedure differently for someone in Mexico as opposed to someone in Germany. If we can’t understand the user, we should focus on the use.
The Complexities of Audience in a Digital Age
It became apparent when I started my current job as a technical communicator that pinning down audience is no simple task. Working for a national student loan servicing company, the team of writers I work on creates deliverables for various audiences such as schools, lenders, borrowers, the U.S. Department of Education, and internal employees. Distinguishing between these audiences is relatively straightforward, but distinguishing sub-audiences within them—actually knowing whom I’m writing for and what they need to know—is something I have struggled with from day one.
Prior to taking this course, and even prior to this week’s readings, I hadn’t fully recognized that a great deal of the complexity I experience in my job today is because of society’s evolution into the digital age. Furthermore, the challenges I encounter at my company are not unique to my company or its industry at all; they are largely universal challenges that technical communicators are encountering throughout the world. Ann Blakeslee’s chapter (“Addressing Audiences in a Digital Age”) in Digital Literacy for Technical Communication illustrated many parallels to the challenges I encounter every day.
The Internet allows for the dissemination of information on a scale that has never been seen before. Our writing is often available to anyone who is online and looking for it. While this broad audience is an overwhelming thought, it doesn’t necessitate that we write for everyone at once. Blakeslee explains,
“While technical communicators may not know their exact audiences, the complexity of the product and typical environments in which the product is used provide them with guidance in understanding their prospective readers” (p. 204).
Basically, we can use information we know about the product and where/how it is used to make judgments about the audience. This is something many of do without even thinking about it. For example, I can assume that users of one of my company’s online applications are employees in a school’s financial aid office. Along with that, they are extremely likely to have a moderate level of knowledge about student loan disbursements. This makes it much easier than writing assuming a global audience with next to no knowledge about student loan disbursements—not to mention it makes for more useful documentation.
But learning about the audience beyond this, is where I think the biggest challenges lie. For me, this has largely been knowing precisely (or even generally!) what the audience needs to know and even better, a ranking of the tasks they must perform in the tool. The best way to get this information (obviously) is straight from the audience through interaction and/or feedback, which is not an easy (or even possible) task for many of us. Blakeslee’s case studies sounded so familiar I could have been one of them! Unfortunately, in my position I am not able to get direct feedback from the audience on the content my team writes. The main reasons for this are:
- The privacy of the customer. Any time there is financial information involved, privacy becomes a concern.
- My time and the customer’s time, or lack thereof. My company’s customers are widespread making travel not feasible. Also, many schools, for example, are under-staffed and under-funded; asking for their time would quickly become an inconvenience for them.
- Existing roles and processes are hard to change. Moving beyond the customer service and sales staff having all outwardly facing contact with customers is difficult and requires the buy-in of management (which is not super likely given the first two bullet points).
Virtually all of these were mentioned by the participants in Blakeslee’s case studies. In my case, we have made efforts to obtain information about audiences from sales and customer service staff. Often, they are able to tell us what confuses users and when/how they use a tool. While it’s not as good as interacting one-on-one with members of the audience, it’s better than nothing!
With communication technologies evolving at incredibly fast pace, it is certain our interaction with the audiences we write for will continue to evolve and improve. I am incredibly interested to see how this aspect of technical communication changes in the coming years.
Cultural expectations
In an era of increased written communication mediums, (i.e., email, text, instant message) oral communication seems to be dwindling. Indeed, this notion has been reinforced by both Erik Qualman in his book Socialnomics, and by Sherry Turkle, in her book Alone Together. Barry Thatcher, in his essay Understanding Digital Literacy Across Cultures in the book, Digital Literacy for Technical Communicaiton sheds light on the fact that this argument is less true in what he defines as collective cultures (i.e., Mexico) as opposed with individualistic cultures (i.e., USA). In essence, people of certain geographical locations may have different expectations regarding the need to develop personal relationships through face-to-face meetings and conversation prior to utilizing mediums such as email as a communication tool.
Thatcher notes, “Orality, though, seems to have a much weaker role in individualist cultures, perhaps relegated to expressing personal opinions and beliefs, but certainly not the backbone of society, as orality can be in many collective cultures” (180). By retaining the expectation of oral communication, collective cultures seem to have a more personal, and less objective tone compared with the very objective tone of individualist cultures. In many cases, I have never met the people I email in a face to face setting, nor do I know these people on a personal level. Thus, the communicaitons we share are, by default, solely professional in nature.
In every technical writing class or journalism class that I have ever taken, I have been taught separate out personal information and include only objective information crucial for the reader to understand the message. As a result, the communication pattern is typically serious and impersonal. This practice of objective writing is also true for the workplace writing tasks I am involved with. Other than indicating how I am involved with the project being discussed, I share no other information about myself, and I do not expect my readers to share any of their personal information.
Thatcher stated, “Instead of a dumbed-down readership level, collective communicators tend to complicate their interpersonal dependence as a way of stating the purpose of the communication and their involvement; this creates writer – friendly document design patterns” (176).
An additional difference between the individual and collecitve cultures is that the colelctive culture has an expectation of stating authoritative relationships as part of the personal style whereas the inndividual culture does not. Thatcher notes, “As exemplified in the two EPA emails, the U.S. email demonstrates strong individualism focusing on one reader and that person’s reading needs and processes, while the Mexican email is much more collective, focusing on interpersonal relationships, and especially on authority” (176). As a technical writing student, I make efforts to consider my audience. However, it seems that despite the best use of audience analysis techniques, there will always be cultural differences that cannot be accounted for. And, in certain cases, technical writers, perhaps even in the future, may need to participate in real-time conversations to maintain cross cultural client relationships and successfully transfer information.
Cross-cultural communication: Let’s start at the beginning
Obviously, any topic concerning cross-cultural aspects hits home for me. It is always interesting to learn new dimensions – especially when it is related to our professional field. That being said, Spilka’s chapter “Understanding Digital Literacy Across Cultures” was a great read. Then I tried to find information how German technical communicators would see this development. Unfortunately, the only article really relevant came from a UK author – and from 4 years ago. At least it is published in the tc-world, which is an online magazine published by the tekom (the German equivalent to the STC).
To bring another aspect into this discussion, I have to disagree with many authors who categorize Western cultures on one site of the cross-border work and cultures from Asian, African or South American countries on the other side. Even within the entire Western cultures (U.S. and many West-European countries) the cultural differences are larger than first thought of. Look at you and me: we experience differences in our cultural upbringings.
- Small ones – like different expressions for the same feeling. For example, Americans sit on cloud 9, when they are happy. Germans sit two-doors down on cloud 7. Thank God for Cloud computing.
- Bigger ones – like the use of social network sites. Concerning the relations of communication media and communicative situations, to many Americans being on Facebook is a daily or even hourly way of connecting with others. Germans just started out using it. The majority of my friends in Germany are not Facebookers.
The three values, Barry Thatcher describes are a great way of analyzing the differences between two cultures. The question is how often do we actually take that extra step and do this kind of research about other cultures. I believe the biggest obstacle we (all earthlings) have to overcome is our mindset. The old question and attitude about being superior to others has to be eliminated out of our way of thinking. Being proud of your country is one thing, feeling superior to other countries is a different story. If both parties can settle for tolerance, we will conquer any upcoming challenges. I guess what I want to say is that even though this topic concerning digital literacy is very interesting to know and to explore, I believe that is one of the last steps we have to undertake. First steps first. Pankaj Ghemawat states in his TED talk: “Actually the world isn’t flat”.
So, we might have to rethink our approach when it comes to cross-cultural communication, no matter if the means are digital or not. Let’s start at the beginning.
Facts schmacts, but not culture schmulture. (Week 11)
I found Ishii’s research to be informative, but somewhat… I don’t know… predictable? For example, on page 358, he offers figures demonstrating that tweens and teens are less socially skilled than adults. It seems that that is a basic attribute of people in these age groups – it’s largely physiology and brain development that humans generally develop more social skills as a result of maturity and life experience. Also, the discussion of adolescents using text messaging and mobile phones to keep their social interactions away from their family seemed fairly obvious. Perhaps it was worth investigating because Ishii is from Japan, where family seems to be more sanctified than it is here.
Anyway, the topic of differences in the use of technology based on culture is an interesting one. While I haven’t seen differences in “niceties” as demonstrated in Spilka’s examples on pages 172 and 173, I have definitely noticed differences in how people from different cultures view the urgency of e-mail messages. At work, we have a small percentage of foreign military sales (FMS) contracts, and under my title of contract administrator, I am the main point of contact for our customers. In one case, I have been trying to obtain some necessary information from a Brazilian customer whose product requires an export license. Our time zones are only an hour or two off and we could logistically speak on the phone, but I don’t speak Portuguese, and the contact person at that company writes much better English than he speaks, so he corresponds via e-mail only. I remember learning in an earlier college course that people in Central and South American countries rarely see things as urgent, and are not pushy because pushiness is considered rude. Obviously, any statement about the people of an entire continent is a generalization, but our Brazilian customer certainly makes a case for this generalized statement. Every time I need to send an e-mail requesting information, it takes at least a week or two to receive a response. This is very unusual in our industry, as customers generally want their products as soon as possible. In drastic contrast to the Brazilian customer is our customer in Japan. Regardless of the subject at hand or the urgency of the issue, it is unusual to wait more than 20 minutes for an e-mail response. Likewise, if they do not receive a response to an e-mail they have sent within an hour, they begin sending “second requests” or forwarding it to other contacts they have at our company.

Oh, hello, Mr. Japanese Customer. I see you flew to Wisconsin because it took me an entire hour to respond to your e-mail.
Yeesh.
In looking for evidence in the internet of how widely intercultural business communication is addressed, I found there is a website that offers guides specifically geared toward business communication unique to several individual countries, as well as guides for just about anything else in a country that is influenced by the surrounding culture. I can see how this could be of high value to industries involving a lot of interpersonal communication or where customer service in the traditional sense is of a high priority. In general though, it seems the nature of my particular industry trumps our respective cultural traditions, at least in part. There is a basic, professional, courteous-yet-firm “voice” used that is fairly universal, at least in my limited experience. When it comes down to it, we all just want to get our work done without having others walk all over us and the company we represent.
What LinkedIn means to paranoid employers (Week 10)
I’ve worked for the same company for seven years. Before that, I worked at my previous employer for eight years. It should be fairly clear that I’m a stable, loyal employee.
Our company had to lay off 50% of our workforce in June of 2011. It was a terrible day, because we are a very small company and our employees are a pretty tight bunch. I joined LinkedIn around that time to keep in touch with those who were let go and to see what kind of new jobs they subsequently found. Somehow, the senior company management caught wind that I had a new profile on what they considered to be a job-search website, and they questioned me about it within a few weeks of my joining. Why was I looking for a new job? Did I need to talk? Was there a particular individual layed off that I disagreed with?
Considering that was over a year ago, they are likely over it by now and realize I was honest in my reasoning behind creating an account on LinkedIn – that I simply cared about the people who were let go and wanted to see when they found new employment.
Apparently, a lot of people are annoyed by LinkedIn, judging by the 44% statistic at http://amplicate.com/hate/linkedin . Of course, this link should probably be taken with a grain of salt, since it seems to be a message board for complaints. Their complaints are relevant, though, especially those involving incessant e-mails from the company. Since joining LinkedIn, I get e-mails several times a week asking if I know certain people or telling me I should update my profile. To be quite honest, I’m hesitant to add contacts or add details to my profile because then the newly-added contacts receive e-mails telling them I’m expanding my network or that I’ve updated my information. My employer’s paranoia has made me paranoid, and I’m worried that another red flag will be raised and I will be considered “on my way out the door” at work. Maybe this would have a positive impact, and I’d get a raise or added benefits if they don’t want to lose me, but it’s probably more likely that I’d be considered disloyal.
The benefits of LinkedIn are fairly obvious to those actively looking for work or who work on a consultant basis. Those individuals need to create a large network and get the word out about their skills and what they can offer as an employee or consultant. Those of us with steady jobs, though, need to understand that from some employers’ perspectives, LinkedIn looks like a great website for headhunters and people “exploring their options.” Industries involving aspects of security requirements, employees in whom companies have invested time and money to train, intellectual property concerns and the like foster employees with incredible value, and they obviously don’t want them to go anywhere. I suppose LinkedIn could be seen as a threat to companies wanting to retain their workforce.
Old and New
Chapter 4 of Digital Literacy For Technical Communication presented insight on technical communicator’s ability to bridge generational differences. Salvo and Rosinski stated, “Second, technical communicators are well positioned to bridge past and future work involving information design” (105). In essence, because of the rate at which technology and communication mediums are advancing, different generations of information users are accustomed to different communication mediums and designs. Thus, technical communicators must find ways to communicate effectively with all generations—young and old, who make up the demographic of their clientele.
This concept is reinforced by the example of early web page design. Salvo and Rosinski noted, “Many new web designers, as their attention moved from communicating on the page to communicating through the screen, ignored traditional principles of page design in their eagerness to invent new design styles and practices” (106). This comment reminded me of a newspaper design class I took a few years ago. During the first portion of the class, we learned about content layout for traditional print style newspapers. The class then moved to designing layout for online newspapers. Beyond having to learn how to use Dreamweaver, we also had to design content pages for mock newspapers based on actual papers. Our professor was adamant about the need to retain some of the traditional print aspects of the layout such as headline and column font. In addition, the web version was to look fairly similar to the print version so users could recognize key aspects. Essentially, we were designing an electronic version of the print newspaper that traditional readers could, in theory, use and read.
However, within the electronic version of the newspapers, we added links to additional stories, images, and videos that readers could not access from the print version. That is, we retained certain aspects, but added features that allowed access to information only available via the internet. This concept parallels Salvo and Rosinskis’ notion that, “Since then [early web pages] many have rediscovered the value of font design and use of white space, and perhaps more importantly, the benefits of collaborating with users. . .toward the creation of readable and usable documentation,” (106). Indeed, while information design is certainly changing, communicators need to consider all possible users of information, and utilize the best methods to reach these users effectively. In terms of newspaper design, fundamental design principles are generally retained for identification purposes, (the newspaper looks the same in print as it does online) and so readers can quickly locate areas of interest.
As virtual space becomes more and more the standard for communication, technical communicators will need to retain certain aspects of tradition document design to reach all user groups. However, technical communicators will also need to develop new design layouts (such as incorporating links etc as in the case of online newspapers) to fully take advantage of the capabilities of virtual spaces. As I consider how the technology of my generation enables new spaces and practices for communication, I can’t help but wonder how things will change as future generations continue to advance information technology. At what point will my generation be the generation of old technology?
The Nuances of Information Design
If there’s one thing I’ve learned since starting my career as a technical communicator, it’s that content (information) is useless when the audience can’t find it. Moreover, it’s not much better than useless when the audience doesn’t know how to use or navigate it. I think Michael Salvo and Paula Rosinski’s chapter (Information Design) in Digital Literacy for Technical Communication covers some incredibly valid points about the potential for technical communicators’ contribution to information design.
Technical communicators, myself included, often have a hand in information design from micro-level sentences and paragraphs, to deliverable design and visual appearance, on up to the macro-level organization of information libraries. From my experience, an interesting byproduct of this is that, among technical communicators, skills and experience can vary so greatly. Additionally, the role of technical communicators varies significantly from organization to organization.
At my company I work in the marketing and communications department (which is definitely not always the case for technical communicators). My department consists of marketing writers and technical writers that produce client communications and supporting documentation among other deliverables. Interestingly, there is also an e-commerce department (not part of marketing) that produces the company’s website and its online tools/applications. The writers in my department regularly work with the e-commerce department. Together we aim to create the most impactful products for the audience, but I’m not going to lie, it can be a struggle at times.
By title, e-commerce doesn’t have any “writers” and marketing and communications doesn’t have any “designers,” but we both must contribute those skills—the skills of technical communicators—to perform our jobs successfully. The tricky part is knowing who is responsible for what, who has what expertise, and whose feedback or suggestions add the most value to the information and its usability. What’s clear is that there will always be information design overlap between these two groups. It’s also clear that we can provide the largest benefit to the audience of our deliverables when we successfully leverage the strongest skills of both groups.
From my perspective, a lot of the awkwardness of this arrangement stems from the fact that e-commerce and marketing and communications are two separate departments (and divisions of the company)—basically, office politics. I know there isn’t a quick or easy solution for all groups within a company to work cohesively together, but how can companies encourage an all-encompassing approach to information design? I’m not sure I have an answer.
Changing role of technical communicators
To me Salvo’s and Rosinski’s article Information Design made the perfect connection to Clark’s article in our journey to explore Emerging Media and the roles that technical communicators will more than likely take on in the near future. The authors state
“Digital literacy cannot be just the ability to use certain technologies. Rather, the term must apply to the thoughtful deployment of technologies that make intervention meaningful and informed by analysis, reflection and historical representations of the field” (Spilka, p. 123-4).
This is just possible if we take Clark’s advice to heart and think and assess critically, keeping in mind the rhetoric of technology.
Content management is in this context one of many examples of work areas technical communicators can evolve their skills and qualities. Hart-Davidson defines professionals in our field as “editors, information architects, usability analysts, interaction designers, project managers, client liaisons, and more” (Spilka p. 134-5). This definition stood out to me because I just started experiencing these different roles in real life work situations. I used to be just a technical writer with some responsibilities concerning managing small projects within our department. Now, I am required to slip into all those above-mentioned roles.
After reading the article Content Management a question that startled me from the beginning of this course finally got answered. Didn’t it seem to you like I asked endless times about the role of marketing in technical communication? I just couldn’t wrap my head around it. In this chapter, the authors mention when talking about the threats technical communicators face lately the “rise of user-generated content, and the broader phenomenon of Web 2.0, something that is perhaps best understood as a significant shift in user behavior from passive consumer to active contributor of content” (Spilka). That’s when it made click in my mind. Now it seems to all come together. The magical term was Web 2.0. I know we read and talked about interaction on social media with our clients all the way along, I just didn’t understand our role in it as professionals.
As of now I would consider us technical communicators as service providers for both parties (e.g. producer/consumer) in assisting them in their communication with each other – back and forth. We don’t just assist the companies anymore in providing materials that deliver information about their products. We now assist both sides in providing information, feedback and assurances or solutions. Not just the companies create content, but also the consumers. The authors summarize this in a better way:
“We must devise ways to listen carefully and move quickly to support the emerging needs of users by documenting new uses, supporting them with new features or services, and scaling-up capacity” (Spilka, p. 141).
Another step stone in my understanding was definitely the article Systems of Engagement. The table Evolution of Content was a great summary on how much has changed in the communication models throughout the last decades. I had to check out the AIIM website and found out that they offer a free webinar about ECM (Enterprise Content Management) on 10/31/2012. Might be interesting to attend.
All these bits and pieces seem to come together to redefine our current and future role as technical communicators. Emerging media changed how society communicates. These changes do already and will continue to influence our profession.
Week 9: Content Management is Never Done
(Post 2 of 2)
Content management is one of those things that we don’t really think about when it’s done well, but can make us very crabby when it’s not. We’ve all experienced the frustration of not being able to find something we need, especially if the need is urgent. Until I began the Tech Comm program here at Stout, I hadn’t thought of it in the least. Now I’ve had two classes in it, and I realize how much effort goes into the initial design of a content management system.
(Forgive me for the following big ol’ reference to quality management-I’m responsible for our quality system at work and we have a big audit coming up in November, so I’m armpit-deep in that subject right now.) One of the basic tenets of a quality management system is continual improvement. In the quality world, this means that once procedures are put into place, they are not set in stone. We should always be looking for a better way to do things, usually through inputs from our own employees and customers. The problem with continual improvement is that people in general don’t like change. The original writers of the procedures can feel dejected or insulted because it can seem others don’t think their work was good enough. Users of the procedures can be annoyed with having to learn how to do the same job a different way. Neither of these reactions is helpful. Everyone must buy in to the idea that they are all members of the company “team,” with a common goal of the business’s success.
I suppose continual improvement is a big part of both information design and content management. It’s not possible to please all of the users all of the time. Changes are bound to be suggested, even if we do all of the research beforehand, with usability studies and such. Not all problems can arise during testing stages, and the corrective actions are one of the forms continual improvement takes. Changes to information design concepts discussed in Spilka’s Chapter 4 are limitless, as there is no one correct answer to design issues. Content managers do their best with usability data they can accumulate and with skills and understanding of concepts of mapping, signposting and general use of space, but they need to stay open to suggestions for bettering their project. A teamwork attitude has to just be part of their personality in order for them to be successful, and pride can only hold the project and the company back from improvement. Their job is never really done – they make it the best it can currently be, but tomorrow a change might come along that makes it better.
Week 9: Businesses are to Individuals as Apples are to Oranges
(Post 1 of 2 for the week – they are fairly unrelated)
I don’t own a business, but sometimes I like to pretend I own the company I work for because it helps me learn more about running a business and therefore, makes me a better employee and expands my knowledge base. What I’ve learned while pursuing this pseudo-goal is that companies have different considerations than individuals have. Individuals have a lot on the line, but businesses have more on the line, because bad decisions can have a negative impact on the lives of many people. My opinion is that businesses are the “laggards,” as Moore says in his white paper, for good reason.
First of all, if business is good, why rush to take chances on new marketing and technological endeavors? An established company has a lot to protect – its existing customer base, trade information, employees, reputation. If the company is to begin openly and freely giving information to everyone, they are really giving that information to everyone, including the competition. Of course, the extent to which this is a concern is highly dependent upon the industry involved. Think of the companies that pride themselves on being thought of as stable, or the standard in their business – insurance or investment companies, for example. Jumping into new arenas is a big deal. My head is spinning thinking of all of the guidelines that might need to be put in place for employees entrusted with an organization’s virtual identity. Virtual identities aren’t that virtual anymore. The general population is going to form an impression of the company from its website, Facebook page or Twitter feed, and likely assume all of the information presented through those sources is representative of that company. There would need to be at least a second set of eyes on everything in order to mitigate the issuance of misinformation and faux pas. Why not wait and see how the competition goes about it, and analyze the response they receive? I firmly believe in letting someone else make the costly mistakes and learning from others’ experiences for free. This may make the company seem like they are behind, but once they are up and running, I don’t think people care.
Employees are as valuable as they choose to be.
For this post, I am mostly considering the “Management Principles and Practices” discussion on pages 59-68 in Spilka.
Now more than ever it is important for everyone to demonstrate his or her value as an employee, regardless of the industry or professional field. Our company has experienced an over 50% cut in our workforce in the past 18 months. Before the layoffs, I was our quality management system director. After the layoffs, I am still responsible for the quality system, but I am also taking care of all contract administration duties and some production management and executive assistant tasks with no raise in pay or any added benefit other than not having to join the unemployment line. I have taken on this added responsibility with a big freaking smile on my face because all four of those titles are considered “overhead” positions, meaning that financially they only cost the company money rather than make it money. People in these kinds of positions are easy targets for the chopping block, and being able to afford to hire individuals for these positions can be seen as a luxury when executive management is getting desperate to cut costs and ultimately save their business. However, just because the position is considered purely an overhead cost doesn’t mean the individual doing the job is doomed to provide no added value to the organization.
One recurring question in the Technical Communication bachelor’s degree program here at Stout was, “What is technical communication?” There is no single correct answer. The ambiguity of our profession really puts us at an advantage if we know how to present our answer when asked what exactly it is that we do. While simply going to work and doing one’s assigned tasks is widely accepted as a sufficient work ethic, it does not allow someone in an overhead position to add value to him- or herself as an employee. So how do we add value to ourselves? A value-added employee is always thinking of ways to do things smarter, more efficiently, more effectively. We need to always be on the lookout for areas in which we can apply our skills, even if it is outside of our comfort zone. If attending college has taught me anything it’s that I, and everyone else, is capable of much more than we assume ourselves to be. Our chosen field is something that can be applied in any industry, and it is difficult to think of a document we can’t generate from scratch or improve if we understand the intent and the “big picture” of the company and its goals. The more we learn about our employer as a whole, the better we can do our job and the more work we can find for ourselves to do within the company.
The only person that can make an employee valuable is the employee him- or herself. It is not always about learning the most up-to-date technology, but it is always about demonstrating a concern for the company and its needs and acting upon them. With a little extra effort, technical communicators have unlimited opportunities to do so.
“Friss oder Stirb” aka “Adapt or Die”
I found Myers “Adapt or Die” pretty intriguing from the get go. Instantaneously, I thought, “Friss oder Stirb”. Just for the heck of it I punched it into my (online) translator and got back the phrase “It’s sink or swim”. Oookay, let’s go for a swim or let’s say a stroll down memory lane. According to the articles by Spilka and Carliner, I would like to show you how digital technology influenced my work as a technical communicator.
I think I saw Phase Two, the desktop revolution. I remember when I first started in the Technical Writing department, my coworkers had sets of manuals for each machine type, which they then photocopied and filled out (by hand) with the technical specification of the particular machine this manual was for. But one of them had already a computer and digitalized those forms, etc. But I think I remember that it was kind of complicated to create a table because the software didn’t offer these features – yet. The graphics – like e.g. for the spare parts lists – were done by a sub-contractor who did so-called explosion drawings. These graphics really showed well how each part fit in with the other ones to form for example a gear. When the company acquired computer-aided design tools, those drawings were replaced by two-dimensional drawings that didn’t fulfill the purpose as well. The engineering department created all those graphics since none of us technical writers knew how to work with CAD programs.
Of the GUI revolution, or Phase Three, I didn’t feel the impact that considerably. For the same reasons Carliner states, we used PC’s. Microsoft Word was the program of choice to do the operating instructions, to integrate sub-suppliers documentation and so forth. We never gave our manuals out to print. They were all customized and delivered in such low numbers. From the copy machine to the laser printer was just a small step for our department.
Since our department created just manuals, not websites, the impact of Phase Four, the Web1.0, was also pretty low on us technical writers. I remember, we had some requests for online documentation. So we converted our word files into PDF’s and were proud that we could connect the table of contents to the appropriate chapters. The last change I remember before I left was that we gave clients a login possibility to our website where they then had the chance to download the PDF file to their specific machine. We were pretty proud of that service. No wait, yes, we just started to integrate our documents in a small content management system, but it was very difficult to navigate and work with. So we ended up using it just for one machine type – an insignificant one. The documentation procedures for all other machine types remained the same.
Of Phase Five (Web 2.0) I just learn here in this program. It is interesting to use some of the newest technology in a safe classroom setting before purchasing it on company’s expenses and then finding out that it doesn’t quite fit the requirements. Many programs are great to use in some part of our professional lives. Others are just not practical for some work situations.
However, when reading Spilka’s and Carliner’s works, I just realized how much I already adapted throughout my working years – without ever paying attention to it. It almost happened unconsciously. I guess what I would like to say is that if we are truly interested in this profession we will find a way to adapt to new technologies, as we will find our own place, our own niche to succeed as technical communicators. Do we have to adapt to each new technology that is out there? I don’t think so. We just have to pay attention and keep ourselves updated and then pick and choose for our specific situations. Sometimes there is a different way than “Friss oder Stirb” or “Adapt or Die”. Sometimes we don’t have to adapt to each new trend out there. Sometimes we won’t die right away.
Technology and Technical Communication
I always find it fascinating to read about the history of the technical communication profession. It is undeniable that technology—particularly the advent of personal computers and the Internet—has completely transformed the landscape for technical communicators. Saul Carliner’s chapter (Computers and Technical Communication in the 21st Century) in Digital Literacy for Technical Communication does a great job describing the impact of technological changes on the role of the technical communicator.
“Technology has always played a central role in technical communication. At first, it served primarily as the subject about which technical communicators wrote. As various publishing technologies emerged, the technology also became the tool that facilitated the work” (p. 45).
Advancements in technology have certainly made life much easier for technical communicators today than in past decades. Frankly, I can’t imagine the amount of rework that communicators had to put into early documents created using a typewriter, retyping content for each correction or addition. Additionally, the challenges that came along with printing and formatting in the 1970s and 1980s were considerable. Today we, as technical communicators, have fancy software that comparably makes it a breeze for us to perform our jobs, and to create an appealing and usable product that meets the needs of our audience.
While I came away from this chapter with a new appreciation for all the technological advancements we benefit from, I also now recognize that the role of the technical communicator has become a lot more complex as well. Not only do we have more than ever to document (i.e., our potential subject matter has increased significantly), but there is an infinitely larger audience to reach.
In my current position, audience is something we constantly try to evaluate. In writing about my company’s products, it is sometimes difficult to know what level of knowledge and skill an audience has right off the bat. Some users are probably well versed in using computers and technology, others may not be. What do we assume the user already knows? This is even further complicated by language and cultural barriers. Even when a company only produces content for an audience within the United States it can be difficult to determine an appropriate reading level and vocabulary.
I have to admit, I’m thankful to be a technical communicator today, with all the technology we have available to help us do our jobs. But I certainly acknowledge that this same technology does add to the complexity that exists within the field.


















