One Tool, Several Names: The Software Naming Note

A colleague says "the project board." Another says the product brand. A third says the name of the workspace inside it. The meeting sounds as though it involves three systems, but everyone may be discussing the same place.

Product names are useful labels, but they are not always the words people use in daily work. A team can accumulate several names for one tool and use one familiar nickname for several different things.

A naming note is a modest response: record the product name, the team's nickname and the purpose people associate with it. It explains language. It does not recommend buying, cancelling or consolidating software.

Key takeaways

• A product name and a workspace name may refer to different levels of the same tool.

• A nickname needs context when the audience changes.

• A naming note records language, not account access or purchasing decisions.

• The reader should be able to recognize the tool without guessing.

Step 1: Separate the name from the job

Consider an invented team that calls its scheduling tool "the rota." That word describes the job the tool does for them. A new colleague looking for a product literally named Rota may search in the wrong place.

The note can state "Team phrase: the rota. Product: Example Scheduler. Purpose: arranging the weekly timetable." The names are fictional. The structure shows how a familiar task word can be connected to a product label without making either one wrong.

Step 2: Make the distinction visible

A few related columns can keep the explanation short: official name, local phrase and meaning in this team. Google's table guidance recommends tables when several related pieces of information belong to each item. This is one possible use of that structure.

Do not turn the note into a catalogue of every feature. The question is recognition: when someone says this phrase, which tool or workspace are they referring to? A detail belongs only if it helps answer that question.

Step 3: Write for the reader who has not heard the nickname

Google's audience guidance points out that colleagues with similar roles can still have different knowledge of a project. A nickname shared inside one team may be unfamiliar to the colleague helping for a week.

The first mention can use both names. Later mentions can use the shorter one once the connection is clear. The same approach works in a handoff note or a meeting invitation: a few extra words at the start remove an unnecessary puzzle.

A naming note is complete when another person can restate it correctly. It need not say whether the tool is good, whether the team should keep it or how its accounts should be managed. Those are separate conversations.

Sources for the definitions and writing principles discussed here: Google, Technical Writing One: Audience, last updated March 28, 2025; Google developer documentation style guide, Tables, last updated March 21, 2025. The examples and suggested discussion formats are illustrative.

Frequently asked questions

Should the note replace the product's real name?

No. Put the recognized product name beside the local phrase so the reader can connect them.

Does it need a screenshot?

Only if the picture explains something the text cannot. A name and a purpose may be enough.

Is this a software inventory?

No. It is a narrow language aid. It leaves licensing, configuration and access information to their own records.

A practical next step

Listen for one tool with two names at the next meeting. Writing those names beside each other may be the entire fix. Book a Decision-Clarity Call for help making technology work easier to explain.