The help centre is part of the product

A customer reading your help centre is usually in one of three moments: deciding whether to buy, trying to fix something, or trying to understand a limit. None of those is a good time to be told something untrue.

So I led an audit of the ReelUse help centre. It found about 45 inaccurate claims and 40 undocumented features.

Two kinds of drift

The 45 inaccurate claims were pages that had stopped matching the product. Each one set an expectation the product wouldn't meet.

The 40 undocumented features were the opposite: work we had shipped and never explained. Those are features customers effectively don't have, because nobody can find them.

Both come from the same root cause. The product and its explanation were being changed at different times by different people.

Fix the process, not just the pages

Correcting the pages was the easy half. The lasting change was a release standard: every customer-facing release updates the help pages, feature pages and support answers in the same change.

Not later and not "we'll document it next sprint", but the same change. If the explanation isn't ready, the feature isn't ready.

It connects to everything else

The same thinking runs through the rest of how we talk to customers. Every release gets an in-app What's New entry and a changelog line, and major features get their own page. Lifecycle email uses one product vocabulary across the app, the help centre and the inbox, so the customer never has to translate between three names for the same thing.

The takeaway

Documentation isn't a finishing touch. It's the part of the product people read when they're deciding whether to trust the rest of it.