Over the past several months, this blog has been a running log of a single large project: a full content audit and strategic roadmap for a real client, completed as the capstone work of a graduate course in content strategy. I’ve written about the prep work, the methodology, the qualitative criteria, the persona mapping, the gap analysis, the synthesis, the delivery. What I haven’t done — until now — is step back and address the course itself directly.
So this post is a little different. It’s aimed at people who are not already working in content strategy and who may not be entirely sure what it is or why it matters. It’s also aimed at people who are considering graduate-level study in technical communication or content-adjacent fields and who want an honest account of what that kind of course actually demands. And if potential employers happen to be reading: this is my attempt to articulate, as clearly as I can, what I know how to do and how I came to know it.
I’ll use three questions as a framework. They’re the kind of questions a good reflective practitioner should be able to answer at the end of a serious project. I’ve been sitting with them for a few weeks now, and here’s where I’ve landed.
Question One
What’s the most important thing someone learning about content strategy should do?
Answer: Start with why — and be willing to let the answer change what you thought you were going to do.
The central textbook for this course was Paula Land’s Content Audits and Inventories: A Handbook for Content Analysis. It’s a methodologically rigorous book, and it covers a lot of practical ground — crawling tools, rubric design, spreadsheet templates, audit report structure. But the part that Land returns to most insistently, across multiple chapters, is something that isn’t technical at all: the requirement to know, before you begin any of it, exactly why you’re doing it.
She frames this as three questions every auditor should be able to answer before touching a single page of content: Why are you auditing? What do you need to learn? And what will you do with what you find? Those questions sound simple until you try to answer them rigorously, and then they turn out to be genuinely hard. In my experience on this project, the honest first draft of my answers was approximately: “Because the client asked me to,” “Whatever seems important,” and “Put it in a report.” None of those are sufficient. Land’s point is that if you can’t answer them with specificity — tied to measurable business goals, defined audience needs, and a concrete plan for action — then the audit you produce will be technically complete and practically useless.
The course assignment that made this concrete was the stakeholder interview phase, which happened before a single page of content was evaluated. We were asked to design and conduct structured interviews with the people who own, create, and use the content — to understand their goals, their pain points, and their definitions of success before we imposed our own analytical framework on top of their organization. For me, coming from a documentation background where I often write for users I’ve never spoken to, this was a discipline that required real effort. The temptation is always to start evaluating. The training is to start listening.
What those conversations gave me was irreplaceable context. I learned things about this client’s content ecosystem that no crawler or spreadsheet could have surfaced — the political history behind certain content silos, the resource constraints that explained patterns I’d have otherwise misread as carelessness, the strategic pivots that had made large sections of the site quietly obsolete. That context shaped every decision I made in the audit and every recommendation I put in the roadmap. Without it, I would have produced something technically credible and strategically naive.
The lesson generalizes beyond this project and beyond this course. Content strategy is fundamentally about alignment — aligning what an organization says with what it’s trying to accomplish and what its audiences actually need. You cannot achieve that alignment if you start with the content rather than with the goals. Start with why. Let the answer be complicated. Let it change your plan. That’s not a detour; that’s the work.
Question Two
What’s the most important thing someone learning about content strategy should NOT do?
Answer: Do not confuse the deliverable with the outcome.
This is subtler than it sounds, and I didn’t fully understand it until I was sitting with a completed audit spreadsheet and realizing that I had done a great deal of work that had not yet produced anything useful for anyone.
The deliverable in this course was a content audit and strategic roadmap. Both of those things are documents. And there’s a very easy trap — one I almost fell into, and one I’ve watched others fall into across the content strategy literature — of treating the completion of the document as the completion of the work. You fill out every cell, you write up every finding, you compile every recommendation, you format the report, and you hand it over. Done. Except that nothing has actually changed for the users navigating the client’s site, or for the content team trying to manage it, or for the business trying to use its content to achieve its goals. The document is infrastructure. It is not the point.
Land addresses this directly in her chapters on delivering audit findings and achieving long-term change. She’s blunt about what happens to audit reports that aren’t paired with organizational readiness: they become “just another spreadsheet or document that sits on the intranet and never gets put into use.” That’s a precise description of what a deliverable without an outcome looks like. And the antidote isn’t a better spreadsheet. It’s understanding that your job as a content strategist doesn’t end when the document is submitted — it ends when the organization has what it needs to act, and some confidence that it will.
In practical terms, this meant that the most important work I did during the roadmap phase wasn’t writing recommendations. It was thinking carefully about my audience for each section of the deliverable, what decision they needed to make, and what information would actually move them toward making it. The executive sponsor needed a business case: costs, risks, projected returns. The content team needed an operational plan: priorities, timelines, ownership, definitions of done. The governance section needed to feel achievable rather than aspirational, or it would be the first thing cut when resources got tight.
For technical writers specifically, this is a meaningful caution. We are trained to produce complete, accurate documents and to consider our job finished when the document meets its specifications. Content strategy asks you to hold yourself accountable to a different standard: not whether the document is good, but whether the people who received it are better equipped to do the right thing. Those are related but distinct measures, and learning to think in terms of the second one is a genuine professional development.
Don’t produce the audit. Produce the change the audit was meant to enable. The document is how you get there; it isn’t the destination.
Question Three
What was most meaningful about content strategy for your own career goals?
Answer: It gave me a framework for the work I was already doing but couldn’t fully name or defend.
I came into this course as a technical writer. I have spent my career thinking carefully about how users encounter information — what they need to know, in what order, in what form, at what level of detail. I’ve written procedures, reference documentation, in-app help, API guides. I’ve done the painstaking work of making complex systems legible to people who didn’t build them and don’t have time to struggle with them. I’m good at it, and I know why I’m good at it: I take accuracy seriously, I think systematically about structure, and I keep the user in front of me at every decision.
What I didn’t have, before this course, was a way to connect that work to the larger question of whether an organization’s content — taken as a whole — was actually serving its purposes. I could evaluate a document. I could make it better. What I couldn’t do, with any confidence, was step back and say: here is the full content ecosystem, here is how it’s working and where it’s failing, here is what it would cost to fix it, and here is the plan. That’s a different scope of work, and it requires a different set of tools.
The content audit methodology gave me those tools. The inventory discipline — the habit of accounting for everything before evaluating anything — gave me a way to understand a content set in its entirety rather than piece by piece. The persona and journey mapping work gave me a way to connect individual content quality to systemic user experience. The gap analysis gave me a way to name what’s missing rather than just what’s wrong. The governance framework gave me a way to think about sustainability rather than just remediation. And the emphasis throughout Land’s book on communication — on presenting findings in ways that drive action rather than generate documentation — gave me language for the hardest part of the job: getting organizations to change.
Taken together, what this course gave me is a bridge between technical communication and content strategy that I didn’t know I needed until I crossed it. Those two fields share more than either community tends to acknowledge. Technical writers are already doing content strategy at the document level — evaluating audience needs, making structural decisions, thinking about information architecture, maintaining consistency across a content set. What content strategy adds is the organizational and systemic layer: the business case, the governance model, the cross-functional collaboration, the long view.
That’s where I want to operate. Not just producing documents that meet their specifications, but shaping content systems that serve real people reliably over time — that get maintained, that adapt as the organization evolves, that someone is actually accountable for. This project was the most concrete step I’ve taken toward that kind of work. It required everything I already knew how to do and pushed me into territory that was genuinely new. That combination is, I think, what graduate study is supposed to feel like.
I don’t know exactly what the next project will look like. But I know more precisely now what I’m capable of, what I’m still developing, and what kind of work I want to be known for. That clarity is worth more than any single deliverable — and it’s the thing this course, more than any other, helped me find.