There Is Documentation. You Searched One Spelling.

One feature. Three names.

"Geographical Pricing" in the technical design. "Geo Pricing" in all seven stories. "Geo-pricing" across four QA pages.

Twelve artefacts, written in the same week, by people in the same programme, about the same thing. And no search on any one of those spellings returns the other two.

The Documentation Was Never Missing

This is the actual mechanism behind the most common complaint in delivery: there is no documentation for this.

Almost always, there is. It was written. Somebody spent an afternoon on it. It is sitting in the same knowledge base you just searched, one token away from where you were looking.

It is invisible to everyone who did not personally attend the meeting where the name was chosen.

That is worth stating plainly, because it changes who the problem belongs to. Nobody failed to document anything. The failure is that three groups documented the same feature under three keys, and search does not know they are the same key.

Why Search Cannot Rescue You

Search matches tokens, not concepts.

"Geo" and "Geographical" are different tokens, and no expansion happens on your behalf. A hyphen creates a third token that matches neither of the first two — and depending on the platform, it may be treated as one word or as two, which means even a person who guesses "Geo-pricing" correctly may still miss it.

So the person doing impact analysis six months from now types the one spelling they happened to hear, gets a partial result set, and reasonably concludes that the partial set is everything. There is no signal in a search result that says "you are seeing a third of what exists."

That is the dangerous property. Naming drift does not produce an error. It produces a plausible, incomplete answer.

The Second Axis: Format

Three of those four QA pages are pasted screenshots. No text at all.

A screenshot cannot be searched, so it is invisible even to somebody using the exact right spelling. It cannot be quoted, so nobody can paste a line of it into a story or a test case. And it cannot be diffed, so when the design changes, nothing anywhere shows that the page is now stale.

A screenshot in a knowledge base is a photograph of knowledge. Fine as an illustration next to the text. Ruinous as the only record.

The combination is the worst case: content that is misnamed and unsearchable. Even a colleague who knows the page exists cannot find the sentence in it that they need.

The Ten-Minute Fix

None of this requires a documentation initiative. It requires three small habits, and all three are cheap enough that arguing about them costs more than doing them.

• Pick one canonical term and use it everywhere. Decide it once, at the point the feature gets a name, and put it in the design document as the name. Not the prettiest form — just one form, chosen and stated.
• Leave a redirect note under every alternative spelling. One line at the top of the page, or a page that exists only to say "Geo Pricing — see Geographical Pricing". Searching a wrong spelling should land you somewhere that points at the right one, which is exactly what a redirect does on the open web and almost never happens internally.
• Paste text, not pictures of text. Screenshots go alongside the words, never instead of them. If the source is a table in a spreadsheet, paste the table. If it is a design diagram, put a text summary underneath it.

Ten minutes each. All three are permanently cheaper than one person's afternoon of not finding the page.

The Move That Is Actually Yours

You will not always control how things get named. You do control what you conclude from a failed search.

Before writing "no documentation available" into an analysis, run the spellings. Generate them mechanically rather than from memory:

• Expand and contract every abbreviation. Geo and Geographical. Config and Configuration. Promo and Promotion. Both directions, because the abbreviation and the expansion are equally likely to be the one that was typed.
• Vary the separators. Space, hyphen, no space at all, and the camel-case version if any object or field is named after the feature. Four searches, thirty seconds.
• Search the neighbouring nouns instead of the feature name. A field name, an object, a price point, a specific value from the requirement. Content whose title you cannot guess often contains a technical string you already know.

That habit is not thoroughness for its own sake. It is the difference between an analysis that says "undocumented, assumptions listed below" and one that says "here is the design, and it contradicts the story."

Why It Never Gets Fixed

Because naming drift has no owner and no failure event.

It does not break a build. It does not fail a test. It never appears as a defect, because the artefact it damages is somebody else's future search, and that person does not know what they missed. The cost is real and entirely distributed — a few hours here, a duplicated analysis there, one requirement tested against a stale design.

And the one group who would notice it is the group who cannot: the people who chose the name. They can always find the page. For them, the knowledge base works perfectly.

The last time you concluded something was undocumented — how many spellings did you actually try?