I get this question a lot: How do content strategists work with IAs/designers/writers? Truthfully, they often don’t. But, they can and they should.

Not only should they work together, they should do away with the typical web project process that leaves content until last, resulting in a mad scramble. People don’t muck up web projects. Bad processes do.

Right? We define the problems, design something we think will fix them, and start building what we designed. Just before we launch the sucker, we populate the CMS with one of three types of content:

• Existing content from brochures and fact sheets haphazardly mapped to pages and components;
• Existing content from the old website that hasn’t been reviewed or edited;
• Brand new content from a copywriter who doesn’t know the purpose of the site, the audience, or whether the source content is reliable.

Boo. At that point it’s too late. And that’s when the wheels come off. But, a process that includes content strategy can help.

Here’s how:

PROBLEM #1: Great ideas, no content

I think it’s fair to say those of us who work on websites are idealistic types. We want to create the best websites ever known to the internet-using public. But, that trips us up sometimes.

As a former web writer, this scenario happened to me more than once: I got a site map and a link to the old website and an in-box full of brochures, fact sheets, and PowerPoint presentations, and was asked to write all the pages on the site. Everything was dandy, for a while. I wasn’t quite sure what source content applied to what pages, but I could deal with that.

But then, I got to some pages with no existing source content. I called my client, who said, “Oh, well, yeah, we don’t have anything for that. So, just do some research, and come up with something.”

Wrong answer. For a couple reasons:

• It takes longer and costs more to research and write content from scratch.  Most project budgets don’t make room for the additional time or cost.
• Writers can’t be expected to know which random online sources they find are credible, current, or appropriate.

A Content Strategy Solution
We’re fortunate at Brain Traffic. Our IAs are content strategists. So, we think about IA a little differently, perhaps. Here are a few content strategeristic solutions that can help with problem no. 1:

• Think hard about whether the pages you include on your site map contribute to meeting user and business goals. One way is to create a core purpose statement that guides your content choices.
• Once you’ve determined that the pages you want to include actually do “fit”, make sure writers have the source content they need to create new content. If they don’t, make sure the people who control the budget know that no source content means more time and money.
• Help your writers out by telling them what source content applies to what pages. If there’s no source content , provide possible sources they can use to write content that supports the site strategy (Those sources might be people).

PROBLEM #2: The content broke my design

I can imagine few things more frustrating than designing the perfect business-goal-driven, user-need-focused, aesthetically pleasing website and having the content make it look like crap. Yet, that kind of thing happens all the time.

Why? Because designers don’t usually know what kind and how much content their design needs to support. So, they have to guess. Or, they ask their client, who says, “We’ll plug the content in once you finish the design.”

That approach leads to oohs and ahs when the design is presented, and hisses and moans when the content is “plugged in” a day or so before launch. One of two things happen next:

• The site launches with crappy content that makes an awesome design look like vomit
• The launch is delayed to re-work the design to support the content or re-work the content to fit the design

A Content Strategy Solution
During the time I was writing this article, a client’s website launched. Client websites launch all the time. But on this particular website, the designer and content strategist worked nose-to-nose. And, the site was awesome. Here’s how it went down:

1. At the very beginning, when asking the really important questions—like what are the business objectives, who is this site for, what do those people need, and what political landmines should we be aware of—we were both in the room. Listening. Asking. Conferring. Together.
2. As my colleagues and I worked together to organize the content and surface the repeatable patterns that would make up the site, we kept the designer in the loop and asked her what she thought.
3. Before the designer started concepting, we asked our client to sign off on the information architecture, wireframes, and page outlines, to make sure all content had been accounted for and all design template needs were documented
4. While the designer was concepting based on wireframes, with specific content priorities noted and estimates of content length, the content strategist and writer wrote copy to show in the designs.
5. The designer presented concepts with content that realistically represented how the site would look live.
6. Not once did the client come back to me and say anything resembling, “This page kinda broke the design.”

PROBLEM #3: We thought you were creating the content

A few weeks ago, I was having drinks with a fellow content strategy enthusiast who works for an agency that specializes in web development. She told me about a project that had raised some red flags related to the content. When she’d brought up her concern—that the client thought the agency was creating the content—the project team brushed her aside, saying “Why would the client think we create the content? That’s their job.”

I’ll tell you why. Denial. No one wants to take responsibility for the content. People don’t know how much time writing content will take, so they have no idea how to plan accordingly.

So, what happened next? To be honest, I’m not sure. I bought her a drink and we changed the subject. But, there was probably a long discussion about why “content is not my job,” followed by a scrambling for resources, a revised project plan that pushed the launch out weeks, if not months, and a resulting website that looked and functioned great, but contained content that didn’t meet user needs or support business goals.

A Content Strategy Solution
I won’t comment on the fact that a website was being built before anyone knew what content it needed to support. What I will comment on is the simple idea that no matter whose job it is to create the content, all of us who work on the interwebs bear some responsibility for it.

Here are some things a content strategy does to help:

• Tells you how many people and how long it will take to create content to launch your website—based on things like page counts, a content creation workflow, and staff time.
• Helps you prioritize your content efforts so you focus resources on the stuff that will influence your most important audiences and help you achieve your business goals
• Gives you a plan for maintaining your content after launch so your website doesn’t become an overgrown graveyard of irrelevant content.

And here are some things developers and programmers can do. Okay. It’s only one thing: Demand actual content before you start building a website. Tell your clients that’s your process. It’ll force them to get granular about content early on. If they look scared, send them to a content strategist.

PROBLEM 4: Underpants on the outside

I like to say underpants in a professional setting. It makes me giggle. Ok, back to business. I tend to use the underpants analogy to talk about two scenarios:

1. A company’s website is organized the way the company is organized, but not the way the site’s users think about the content.
2. It’s apparent from a quick glance at a homepage that departments and executives are fighting with the web team for prime space on the home page, without considering users’ needs or what will drive business results.

Imma talk about the second one. When that happens, you end up with a lot of junk nobody cares about—or, if they do care about it, they’ll never know because they don’t know it’s for them. That’s when they hit the back button and make their way to the next link in Google’s search results. Lost opportunities abound—sales not made, relationships not built, brand not recognized. Dang.

A Content Strategy Solution
Here’s the cool thing about content strategy. It doesn’t just tell you what content should go on your site, but it answers a whole bunch of other important questions:

• Why should it go there? Or, how will it help you achieve your business goals?
• Where should it go? Or, how should it be organized so people can find it?
• What format should it be in? Or, what’s the most effective way to communicate it?
• How will it get there? Or, what are the people resources, tools, and workflow needed to make it all happen?
• How much should there be? Or, what can we realistically produce and maintain?
• How do we decide? Or, who is involved in content decisions and what are the guidelines we use to make them?

These questions get answered through a bunch of combinations of content strategy deliverables—ranging from editorial specifications and calendars to sitemaps and wireframes to web content style guidelines to messaging hierarchies to full blown governance plans and policies.

Why do you need them? So that you can direct content efforts rather than take orders from whomever thinks their content is most important that week. They give you the power to say no.

The moral of the story: if it’s broken, fix it

Have you heard of my friend Jonathan Kahn’s blog Lucid Plot? It’s  smart. One of my favorite smart things it has said is this:

“If your lack of content strategy is hurting the user experience, it’s time to throw out your design process and start over.”
(From Embrace Content Strategy: Throw Out Your Design Process)

It’s nobody’s fault that the people building websites back in the 1990s borrowed from the only processes they were familiar with. Print. Advertising. Software Development. But, it is our responsibility to acknowledge that those processes don’t work and come up with something better.

In almost every situation, a good process starts with content.