I’ve lost count of how many website projects start the same way.
There’s real excitement in the room. A fresh design. New features. A genuine chance to finally get it right. And then, somewhere in the middle of it all, someone asks the question that brings everything to a grinding halt:
“So… who’s writing all this content?”
That pause is familiar to anyone who has run a complex web project. It is the moment the room realizes that content was never really on the plan. It got assumed, deferred, left for later. And later has arrived.
That pause is familiar to anyone who has run a complex web project. It is the moment the room realizes that content was never really on the plan. It got assumed, deferred, left for later. And later has arrived.
None of this is negligence. It is what happens when an organization treats content as a deliverable rather than a discipline. You produce it, you ship it, you move on. Content gets driven by whoever asked most recently. One team carries the load while everyone else has opinions. Messaging shifts from page to page depending on who wrote what and when. And once it goes live, it gets abandoned.
What content strategy actually is
Most organizations have already invested in content: writers, workshops, brand audits. They still end up with the same mess two years later because they treated it as a production problem. It is an organizational one.
Content strategy is the practice of deciding what you publish, why it exists, where it lives, and who is responsible for it over time. It is less about the writing itself than about the system that makes good writing possible at scale and keeps it that way.
The real question isn’t “what should we publish?” It’s “how do we make coherent content decisions when six teams have competing priorities and no shared criteria?” That is the harder problem, and the one worth solving.
Why it matters more than most people expect
You can’t design a great experience with bad content. People don’t visit your website to admire the layout. They come to find something, learn something, or do something. If the content doesn’t support that, the design won’t save you.
The set it and forget it trap
A website is not a finished product. Content gets outdated, duplicated, and it drifts as organizations grow and priorities shift. Many teams still treat launch as the finish line when it is really the starting point.
Governance is the part that gets cut first. It doesn’t show up in a design comp and it has no client deliverable. But it is the difference between a site that holds up and one that quietly deteriorates.
Where to start
Take stock before you create anything new. A content inventory consistently reveals more than teams expect: duplicate pages, outdated messaging, content nobody can find.
Plan content and structure together. Designing first and figuring out content later is one of the most common and expensive mistakes in web projects.
Ownership almost always lands with the team closest to the content, not the team closest to the audience. That is usually the wrong assignment. Name who creates it, who can change it, and who notices when it is wrong six months from now.
Build a review rhythm. Organizations that treat content as a living thing end up with dramatically better outcomes than those who do a major overhaul every few years.
Write for people. Internal language has a way of creeping into content until it stops making sense to anyone outside your building.
A final thought
This is a structural problem that requires structural answers: clear ownership, defined processes, honest governance. Plan it. Build it. Keep working on it. The work doesn’t end at launch. It just changes character.
