What Do We Learn? Skills. When Do We Learn Them? On the Job or Whatever!
Posted by lttaylor3
Working as a technical communicator over the past two years without an undergraduate grounding in the skills, methods, and research tools has been enlightening. While it has given me a greater appreciation for the work being done by my coworkers and others in the field, it has also caused me to reach out to sources like the Society for Technical Communication and a master’s program in order to secure essential skills and new tricks to show off to supervisors and future employers.
What exactly am I looking for, you may ask? Social media, content management systems, Adobe Creative and Technical Communications Suite, User-Centered Design, and Project Management, to name but a few. Beyond the skills that I have a personal interest in or am curious about, I find that trolling through job descriptions to look for what will impress and keep me relevant in a community that is designing, defining, and streamlining what technical communications means and what is necessary to work in the field.
One of the key skills I am looking to pick up from the MSTPC program and put into practice is learning how to learn, and I have found that it is definitely a critical skill that I’ll need on my side moving forward.
As Michael J. Salvo and Paula Rosinski (2010) said, “search and retrieval – or findability – as well as navigability become increasingly important as the information age produces more documents than ever. As the volume of information increases, designing for storage and retrieval becomes more important in the planning stages of writing. After all, information that cannot be easily retrieved when needed is useless” (103).
Now this makes sense when you’re talking about the basics of the technical communications field. Authoring, editing, designing, displaying, distributing, and analyzing all the content constantly put out by companies, universities, social networking sites, and academics takes a lot of time and effort by practitioners and academics under fire by Chief Financial Officers Wading through the amount of content that
When it comes to us as a class however, my mind starts thinking about how we as technical communicators work to gather, study, and disseminate information. Learning how to read, analyze, and write papers for my English undergrad along with internships for my Journalism minor made me an attractive, moldable candidate for the Technical Editor position I got shortly after graduating, but that position did not offer anything in the way of training documents or files.
It was entirely a mentor-based position. That was both a positive and a negative, I came to find as I delved into the world of technical editing. It was great to work side by side with practitioners who had years of experience in the field and in the government contracting sphere; I was exposed to a lot of insider information that no one bothered to write down because it was industry standard or specific. There were breakdowns in email content based on the office I was contacting and the military or civilian title in front of the person’s name.
I learned quickly and started keeping my own folders and Word docs with acronyms, workflows, and Department-specific language no one would ever use (and I would get graded down for if I showed any of it to one of my professors).
The problem was that as soon as I was hired, the company started to lose employees. When I was hired I was told it was a stable contract with no turnover but everyone was leaving so all of the great mentors were jumping ship and it was up to those of us who were newer to train employees and help them learn the process.
So while we were learning we were also training new people, designing SharePoint sites, and teaching classes to government employees. Needless to say, the situation could have better. It was enjoyable to take more of a leadership role with incoming coworkers and I also got the chance to design a few training sites and standard operating procedures. Whatever problems I may have had with the company, it was clear that I had been allowed to really grow into a role and put on the different hats expected of me by the field.
My next job was a different story. I had walked into a great company with an understanding boss, but the work itself functioned on a sink or swim basis. I was expected to dive into the work and start working. No real oversight. Clear cut design and structural rules to follow but how I got there was all up to me. Yes, I was encouraged to reach out with any question but I wanted to make a great first impression so I just got my hands dirty with the research, writing, and designing of technical materials and documents for client approval.
The chapters talk about information design, content management, and the rhetoric of technology, but how do we use this in our full- or part-time job lives? For me, it’s become critical to seek the keys to staying up to date on information, technology, communication, and other trends essential to my work and moving forward in the field.
Spilka, Rachel. (2010). Digital literacy for technical communication. “Information design: From authoring text to architecting virtual space. Taylor & Francis Group. New York, NY.
This site uses Akismet to reduce spam. Learn how your comment data is processed.