A few months ago I opened a textbook to prepare for a content audit. I’ve written about that project in pieces on this blog — the upfront goal-setting, the stakeholder conversations, the inventory, the qualitative criteria, the personas, the gap analysis, the struggle to turn a very large spreadsheet into something a client could act on. This is the last post in that series, and I want to try to do two things at once: close out the project honestly, and think through what it means for where I’m headed.
The roadmap has been delivered. The client has it. And however this particular engagement plays out from here, I already know that this project changed the way I think about my work — not just content auditing specifically, but the whole arc of what a career in technical communication can look like when you follow it all the way to its logical conclusions.
What the Final Deliverable Actually Is
If you’d asked me at the start of this project to describe what I was going to produce, I would have said something like: an audit report and a set of recommendations. That’s technically accurate. It’s also a pretty thin description of what the work actually became.
The final deliverable is a layered thing. There’s the audit itself — the detailed, criteria-based assessment of the content, page by page and section by section, scored against the goals we established at the outset with the stakeholders. That part is the evidence base. It’s thorough, and it has to be, because every recommendation that follows needs to be traceable back to something specific we found in the content rather than a general impression or a professional hunch.
Then there’s the strategic roadmap, which is the document I’ve been building for the past several weeks. It takes all of that evidence and organizes it around three horizons. The first is immediate: the quick wins — the content that can be fixed, archived, or consolidated without anyone needing to approve a new budget line or restructure a workflow. These matter because they build momentum and demonstrate that the audit wasn’t just an expensive diagnosis. Something changes, visibly, within weeks of the deliverable landing.
The second horizon is medium-term: the structural work. The template consolidation, the content model refinement, the terminology standardization, the rewrite backlog organized by audience priority and business impact. This is the work that takes months, requires coordination across content owners, and produces the kind of durable improvement that actually changes how the site serves its users. It’s also the work that’s most likely to stall without active governance — which is why the third horizon exists.
The third is long-term: the governance framework. The rolling audit cadence, the content lifecycle policies, the updated style guide, the ownership model that assigns accountability for each section of the site. Paula Land describes this as the “virtuous circle” — the feedback loop that allows an organization to learn from its content continuously rather than waiting for it to degrade badly enough to trigger another expensive remediation project. Getting a client to commit to this part is always the hardest sell, because it asks them to build a habit, not just complete a task. But it’s the part that makes everything else last.
What the Client Has Now That They Didn’t Have Before
Beyond the documents, what this client has is visibility. That might sound like a small thing, but it isn’t. Before this project, nobody at this organization had a complete, current picture of what was on their site — how much of it, where it lived, who owned it, how it was performing, whether it still served any recognizable purpose. Content had accumulated over years through the efforts of multiple teams, multiple vendors, multiple strategic directions that had since been revised or abandoned. The site had grown in the way that things grow when nobody is tending them: outward and upward, without much shape.
Now there’s a map. Not a perfect map — no audit produces a perfect picture, and I’ve been honest with the client about the limitations of what a snapshot in time can show. But it’s enough to make decisions from. Enough to know which content is genuinely serving users and which has been sitting unread for years. Enough to see that the evaluation-stage content for their primary buyer persona is thin and inconsistent while the post-purchase support content is actually pretty strong. Enough to understand that the brand inconsistency isn’t random — it clusters around content produced before the last rebrand, which means the fix is targeted and manageable rather than site-wide and overwhelming.
That specificity is the whole point. General impressions that the site “needs work” are easy to dismiss or to address superficially. Data-backed, audience-mapped, journey-contextualized findings are much harder to ignore and much easier to act on. The roadmap translates “the site needs work” into “these specific pieces of content are failing this specific audience at this specific stage of their journey, and here is exactly what to do about it.” That’s the difference between a report and a plan.
What the Future Looks Like for Them, If They Do the Work
I want to be careful here, because there’s a version of this reflection that turns into a client testimonial, and that’s not quite what I’m going for. The honest answer is: I don’t know yet what the future looks like for this client. The roadmap is delivered. Whether they implement it faithfully, partially, or not at all is a function of organizational will, resource availability, and the dozen other factors that determine whether strategic recommendations become operational reality — factors that were mostly outside my control the moment the document left my hands.
What I can say is what the future could look like, if the work gets done. A site where every piece of content has a clear owner and a known purpose. A content team that’s auditing proactively rather than reactively, catching drift before it becomes a problem. Users who move through the site’s content with less friction — who find what they need at the moment they need it, in a form they can actually use, in language that speaks to them rather than past them. A brand that feels coherent across channels because the people producing the content are working from shared standards that are maintained rather than posted once and forgotten.
That’s a high-functioning content operation. Most organizations are nowhere near it. But the audit and the roadmap create the conditions for it, and that feels like meaningful work to have done regardless of how fully it gets implemented.
The Through Line, From Where I Started to Here
When I started this project, I was a technical writer preparing for a content audit. That framing was accurate but incomplete. Technical writing is where my instincts were formed — a background built on the discipline of precision, the habit of thinking about how a user moves through information, the discomfort with ambiguity that makes you keep refining a procedure until it actually works. Those instincts didn’t go away during this project. They turned out to be exactly what the project required.
But what this project asked of me that my documentation work rarely had was the strategic layer: the ability to move from individual observations to systemic insight, from findings to recommendations, from recommendations to a prioritized plan that accounts for organizational reality. The ability to tell a story about content to people whose job is not content — to make them understand why it matters, what it’s costing them, and what a better version of it is worth pursuing.
That combination — technical precision plus strategic communication — is not a standard job description. It sits at the intersection of content strategy, information architecture, technical communication, and whatever you want to call the soft skill of helping organizations understand what they have and decide what to do about it. I’ve spent my career moving toward that intersection without always having a clear name for it. This project gave me a clearer sense of what it looks like in practice and confirmed that it’s where I want to be.
“The content inventory and audit are means to an end: the development of a content strategy and user experience that delivers for both the business and the users.”— Paula Ladenburg Land, Content Audits and Inventories, 2nd ed.
That sentence from Land’s conclusion has stuck with me since I first read it. Means to an end. The inventory, the audit, the roadmap — none of it is the point. The point is content that works: that serves real people, supports real goals, and gets maintained well enough to keep doing both over time. Everything else is infrastructure in service of that outcome.
I think that’s true of a career in this field, too. The deliverables accumulate — the documents, the audit reports, the roadmaps, the governance frameworks — but they’re not the measure of the work. The measure is whether the people using the content were better served because you were involved. Whether the organizations you worked with came away with stronger practices, clearer thinking, and better tools for the ongoing work of communicating with their audiences. Whether something lasted.
That’s the standard I’m holding myself to. This project was one step toward it. There’s more work to do, and I’m glad to have a clearer sense now of what direction it’s in.