Theory Is Foundation For Learning Skills

Theory, Not Skills, Guided Me Through My Internship
(Much to My Surprise)

My internship reinforced my decision to return to school. When I applied to the Boise State University’s Masters of Arts in Technical Communications, I had not had a fulltime professional position for over 10 years. The technical communications program introduced me to new theories and skills used in today’s workplace. My internship allowed me to combine my past work experience with my recent academic studies.

Relying On Theory Instead Of Skills

To be honest, I came back to school to gain new job skills. I was tired of teaching myself how to use new software and other technology. I wanted to take time in an academic setting to learn how to use these tools efficiently. I considered the readings and discussions about the theories of technical communications a by-product of what I planned to take from the program.

My technical communication classes provided the opportunity to learn new tools; however, I did not rely on these skills during my internship. Instead, the theories we discussed in class helped me focus on the scope of the work we were completing.

For example, every class discussed the importance of understanding the audience, purpose, and context of a project. As a result, I started most projects asking, “Who is the target audience.” The answer expanded to a discussion about the purpose of the task, and the requirements of the context.

Our decisions about context determined the software and other tools we needed to use. I taught myself how to use Adobe Acrobat Pro to develop the forms used for the evaluations. In addition, I taught myself how to create a Google site as the central communications point for the project.

In both instances, I discovered that it was easier to teach myself how to use new software and tools when I have a defined purpose. Instead of fumbling through setting up a Google site, I defined what I wanted from the site, and then determined what instructions I needed to review. Instead of learning how to create a form in Acrobat Pro, we finalized the content and sketched out a conceptual form.  At that point, I reviewed Acrobat Pro’s help and tutorial modules for information specific to the type of form that met our needs.

The Marketing and Tech Comm Partnership

Much of my career has involved marketing and public relations responsibilities. My passion, however, is employee and customer relations. Thus, I prefer to work behind the scenes within an organization and let others take on the role of salesperson and spokesperson. I have strong organizational skills, but lack artistic abilities. For these reasons, I chose advanced studies in technical communications instead of marketing or public relations.

I had this dream that if I focused on documentation, I could get away from advertising. My internship, however, pulled me back into the world of marketing plans, logo designs, and sales. I was reminded that there is a strong partnership between a good marketing plan and useful documentation.

The first task we undertook was announcing the program. It was challenging because we were developing the marketing message at the same time that we were developing the program. However, discussing the documents at the design stage helped us create useful forms and instructions. Also, I realized that staying focused on the target audience, purpose, and context kept our discussions and tasks focused throughout the design stage.

Using the SME Relationship in a Non-Engineering Organization

Discussing the roles of technical writers and subject matter experts (SMEs) in class helped me step into this new position with more confidence. Even though most of our class examples came from engineering companies, I found the same relationship at the non-engineering organization where I interned.

When beginning new projects in the past, I usually felt the need to present original ideas and recommendations for approval. This time, I considered my supervisors to be the SMEs for the project. My goal was to “download” their ideas for the program that they discussed before I was hired. Understanding the role of the technical writer and the SME helped me ask better questions, and use my time more efficiently.

I definitely had a sense of being an information designer. I expanded on what I considered the most useful ideas, instead of creating new ideas. There were differences of opinion, but the process was less personal for me. Again, the conversations focused on audience, purpose, and context instead of “my ideas” versus “your ideas.”

Pulling together this program within a short period as a part-time employee has been thrilling, a little scary, and all consuming. To state it more simply, I could not have asked for a better opportunity to realize that theory is a good foundation for developing new skills.