How To Show Management Your Value As A Technical Communicator
Chapter 1 and 2 of “Digital Literacy For Technical Communication” focuses on the history, the role, and the value of technical writers. Chapter 2 can feel like a downer because it discusses how the role of the technical writer can be vague for managers. In fact, Dicks writes “Technical communicators need to worry about how they are perceived and evaluated and whether they might be likely sources for being reengineered and either either eliminated or outsourced” (64).
I have felt these worries myself at times. After a copywriter left the company, my manager decided to hire a different role versus hiring a new writer. It made me wonder if he didn’t see the value of having two writers on his team. Dick outlines his four points for how technical writers can still show their worth in today’s companies. In my post, I’m going to discuss how I show my value to my managers and company. I’ve discussed iterative design enough in my previous posts, so I’m going to leave this skill out of the list (although I heavily suggest gaining design skills as a technical communicator).
UX Expert or User Advocacy
I believe technical writers have a better understanding of the company’s customers than most employees in a organization. That’s because technical writers have to think about the needs of the customer whenever they write a blog post, a case study, documentation, etc. This puts technical writers in a prime position to lead UX (User Experience) efforts in a company.
I commonly contribute to UX discussion, especially in regards to the design of my company’s website and products. However, it is not enough to simply know UX. In “Don’t Make Me Think, Revisited“, UX professional, Steve Krug, states that most believe they know UX regardless if they have been trained or not.
As technical writers, that means you must become versed and trained in UX practices. Back up your assumptions about users with usability tools. I am currently designing a usability study using a research tool called UserTesting. With this tool, I plan to run 10 unmoderated tests that will help me understand how users feel about my company’s website. I am also running a survey to better understand user’s direct feedback about the company. Through these efforts, I am showing my company that I can lead my company’s UX efforts. I am bringing consistent value by helping them gain more insights about our customer base.
I don’t think I need to discuss how content strategy works because most of us already know it. But I do believe we possibly underestimate the value of this skill. In my experience, I’ve run into two types of writers in companies — those who just want to write, and those who strategize and write. I totally understand just wanting to be left alone to write and not focus so much on the strategy part. Content strategy takes away time from writing. And most of the time, the content plans you put together can be hard to stick to. However, you will gain respect from your colleagues if you do spend time putting this strategy together.
I realized the value of content strategy after interviewing marketing directors. I’ve been interviewing directors a lot because my company is currently looking for one for our marketing team (this person would essentially become my boss). One candidate asked me some interesting questions after our interviews. She was extremely interested to know how I spend my time as a writer. Based on her questions, I could tell she was trying to figure out if I was a writer who just wrote, or if I was willing to be content strategist as well. This caused me to reflect on other questions director candidates have asked me, and they are always asking me about my content strategy. Even when I meet with my non-marketing director, he is asking me about my content strategy.
Even though content strategy isn’t my favorite thing in the world, I’ve learned that many see tremendous value in taking the time to spin up a plan.
The Bottom Line
You may be feeling that this list is extremely marketing oriented. Like Saul Carliner’s history of the technical writer in Chapter one of our readings, my list has a personal dimension to it. There are still many ways technical writers can add value to their company through other means: programming, documentation, product management, etc. I would love to hear how the rest of you have found ways to bring value to your company, organization, or even to yourself, in your profession.