Stay updated
Keep current with the latest trends in technical communication by subscribing to the I'd Rather Be Writing newsletter. 6,100+ subscribers. (See email archive here.)

Search results

How to tell if you're a content strategist

by Tom Johnson on Oct 26, 2016 •
categories: technical-writing

Recently MindTouch published a list of the top 25 Content Strategist Influencers. In contrast to previous top influencer lists, this year's list shifts from the term 'tech comm influencer' to 'content strategist influencer'. They also broadened their measures for determining influence, including less online presence and more offline influence, such as conference presentations. I just barely made the list this year. It got me thinking about whether I am in fact a content strategist or a technical writer.

First, check out MindTouch’s post: Announcing the Top 25 Content Strategist Influencers for 2016.

As you can see, there are some people on the list who don’t have a strong online presence but who present at conferences and publish material in other ways. In previous years (2014, 2013, 2012, 2010), MindTouch used online analytics tools such as Little Bird to calculate influence algorithmically. This favored people like me who live and breathe online but didn’t do justice to the leaders who are shaping and motivating people at conferences and other venues. Since this kind of online/offline measure is difficult to do, MindTouch used a panel (consisting of Scott Abel, Al Martine, and Jack Molisani) to determine the influencers.

At first I was happy to simply make the list. But then I got to thinking … will there be a separate list that focuses just on “tech comm influencers,” or has the term shifted permanently to “content strategist influencers”? And if it did shift, am I really a “content strategist”? Should I consider myself a “technical writer” or a “content strategist”?

When the term “content strategy” first emerged about 5 years ago, I resisted the term because I felt that as a technical writer, I already did strategic thinking in my role as a technical writer. With the introduction of the term “content strategist,” suddenly a “technical writer” was reduced to something more base and tactical, like a monkey pounding on a keyboard. A technical writer would perhaps create a help topic, but a content strategist would shape the company’s brand and orchestrate a consistent experience across all customer touchpoints.

Overnight, some tech comm consultants latched onto the term “content strategist” and rebranded themselves. I was still content to be called a “technical writer,” because most of the jobs used the term “technical writer,” and because almost no one’s title was “content strategist” anyway.

It’s been interesting to see how content strategy has played out in the past few years. For the most part, if you search for content strategist jobs on, you’ll find that content strategists fit more commonly in Marketing and UX writer groups.

For example, here’s what this content strategist will do:

As a Content Strategist, you’ll be the first person to help shape and define the Robinhood voice. Working directly with our CEO and C-level executives, you’ll craft brand messages across existing and future platforms (from iOS and Android to Web), overhaul our existing brand voice across our social media and customer support channels, and develop content strategy as we move into new international markets.

And here’s this content strategist’s role:

The Senior Content Strategist is tasked with taking a more direct hand in the guidance and daily operation of the Inbound Marketing team. This role is expected to maintain a strong knowledge of SEO best practices, content marketing techniques and high-level strategy as directed by their manager. The Senior Content Strategist is an experienced operator in digital marketing trends and is capable of assisting their less senior colleagues through training, work review and project oversight while maintaining their own clients and workflow.

I’m told that at Facebook, “content strategists” always focus on in-app content, such as form labels and help text, while “technical writers” focus on developer-facing documentation.

Sponsored content

I doubt the originators of content strategy appreciate the cheapening of the term. They clearly intend for the strategic thinking principles that underlie content strategy to permeate across disciplines into something larger. For example, see Kristina Halverson’s presentation Content Strategy for Everything.

Scott Abel has helped push the principles of content strategy more thoroughly within the tech comm industry through his regular webinars, conferences, and books addressing content strategy. In contrast to the more superficial marketing copywriting tasks listed in the above job descriptions, Scott incorporates a lot more strategy, analysis, and critical depth into the content strategist’s role. In addition to creating intelligent content, one frequent message is that we need to focus on all customer touchpoints, both pre-sale and post-sale, and ensure consistent, unified content throughout these customer experiences.

It almost seems as if there’s a “content strategy in Marketing,” and a “content strategy in tech comm.” The former is like doing marketing copywriting, the latter is like doing strategic consulting.

Instead of steering my career in the direction of content strategy, I decided to become an “API technical writer,” focusing on developer documentation. I respect those who do content strategy in tech comm, for sure, and I wish I had time to do more of it. I simply like the API doc space more.

So making the “content strategist influencers” list from MindTouch has given me pause to reconsider whether I’m truly a content strategist. Ultimately, it’s not so difficult to discern whether I am (or whether you are, etc.) someone who thinks strategically about content. The basic question to ask is how much “strategy” you incorporate into your work. When are you being tactical, and when are you being strategic?

Here are a few examples comparing the two activities:

Tactical Strategic
Document feature X. Analyze what information your audience needs in the first place.
Organize your help topics into a logical arrangement. Look at analytics (hits, time on page, keywords) for your help content to determine how the navigation should be arranged
Attend a scrum meeting and start working on items assigned to you during the sprint. Assess all the work the engineering teams are doing and prioritize which areas would most benefit from documentation based on market trends.
Add details from a KB article logged by your support group into the documentation. Look at reports in support logs and determine gaps or other missing areas in the documentation, and then investigate the causes for the gaps.
Set up stylesheets for a help authoring tool. Set up your authoring tools to be scalable enough for engineers and non-technical writers to contribute.
Edit and publish material from an engineer onto the doc site Evaluate whether the content addresses user needs and uses language that matches into your user’s lexicon.

It’s not rocket science to classify activities as being more strategic or more tactical. Ideally, content strategists do a lot more of the strategy than the tactics. As Halvorson says, they do planning for the creation, delivery, and governance of useful, usable content.

I could definitely do more strategic thinking than I currently do. It’s easy to get caught up in documentation task after documentation task. (I probably do most of my strategic thinking on this blog, actually.) Unfortunately, sitting down to do strategic analysis and planning requires bandwidth. But in the end, it should make our work more effective.

Overall, strategy without tactics, and tactics without strategy, are both hollow endeavors. Incorporating both modes into my weekly work as a technical writer is something I can certainly improve on. For that encouragement, I welcome MindTouch’s term “content strategist influencer.” Careerwise, though, I prefer to think of myself as an API technical writer … who thinks strategically.

Buy me a coffeeBuy me a coffee
Stay current with the latest in tech comm
Keep current with the latest trends in technical communication by subscribing to the I'd Rather Be Writing newsletter. 6,100+ subscribers. (See email archive here.)

follow us in feedly

About Tom Johnson

Tom Johnson

I'm a technical writer / API doc specialist based in the Seattle area. In this blog, I write about topics related to technical writing and communication — such as software documentation, API documentation, visual communication, information architecture, writing techniques, plain language, tech comm careers, and more. Check out simplifying complexity and API documentation for some deep dives into these topics. If you're a technical writer and want to keep on top of the latest trends in the field, be sure to subscribe to email updates. You can also learn more about me or contact me.