Why Your Help Center Feels Broken (And It's Not a Writing Problem)

Most software companies I talk to describe their help center the same way: "It's a mess." Then they tell me the plan is to hire someone to rewrite the articles.

Here's the thing. Rewriting rarely fixes it.

A help center doesn't feel broken because the sentences are bad. It feels broken because users can't find what they need, articles contradict each other, nobody owns the structure, and it hasn't kept pace with the product. Those are architecture problems, not prose problems.

Signs your help center has a structure problem, not a writing problem:

• Users ask support the same questions your docs already answer

• Search returns five articles that half-answer the same question

• New features ship with no clear "home" in the docs

• Nobody can tell you who's responsible for keeping it current

• Articles were written for the product as it existed two versions ago

If that sounds familiar, better writing won't save you. What will:

1. Map what actually exists. Not the sitemap. The real content, including the orphaned pages and duplicates nobody remembers creating.

2. Group by user intent, not by product feature. Users don't think in your org chart; they think in "I'm trying to do X."

3. Kill duplicates before you polish anything. Two mediocre articles answering the same question are worse than one good one.

4. Assign ownership. Documentation without an owner rots the same way code without an owner does.

Good writing matters, but it's the last step, not the first. Fix the structure, and the writing problem often turns out to be smaller than you thought.

If your help center feels broken and you're not sure whether it's a content problem or a structure problem, that's usually the first thing worth figuring out before you spend a dollar on rewrites.