Nomenclature template

A nomenclature chart is made up of 4 sections. Content strategists may choose to change the titles of the 4 columns in order to better reflect the language that their team is comfortable with.

  1. Preferred term: This is the first column to be filled out. The team will likely have a list of key words or brand words. That list becomes the list of preferred terms, since each word is (most likely) the term the team is hoping their prospective customers will search for or use when describing them.
  2. Connotation: This is the definition of the preferred term, as understood by the team. It’s important to note that this is not necessarily the dictionary denotation of the word, but the way the team wants the term to be understood.
  3. Synonyms: These are the other terms that clients or customers might use. For example, the company might sell what they prefer to call “mobile devices,” but their clients call them “mobiles, phones, cell phones, ipads, and tablets.” All of the terms clients use are synonyms for their understanding of the word “mobile devices.”
  4. Associated terms: This last column is useful for identifying situations where the term might be used. It might also be called “Assets” or “Attributes.” For example, if the company has a preferred term “smart” to define how their devices work, and the synonyms are “intuitive, fast, connected” then the attribute would be “mobile devices.”

Here is a template that can be used to create a nomenclature chart. Ideally, the nomenclature chart should not include more than 10 terms.


Nomenclature Example

For a content strategist, a nomenclature chart, or vocabulary, is a specific set of terms that reflect the voice of the company.

In these examples of nomenclature charts, the content strategist has chosen a set of key words, and tested them with the organization’s target audience to see if they resonate. For each key word, the content strategist supplies a definition, as well as synonyms. What makes this different from a dictionary is that the synonyms are not necessarily direct equivalents, but instead words that the target audience or organization might use interchangeably with the key word.



Quick Turnaround for User Feedback

Usability and testing is a great way to learn how users are responding to your application, but it’s rarely quick and easy to do. Here are a few examples of testing options that can make a big difference to the user experience:

Testing a Concept

There’s an old Foxtrot comic strip where Jason announces “I’m going to invent shoes with wheels on them.” His sister Paige asks dryly, “will you call them roller skates?” Concept testing gets at far more than just double checking that no one else has come up with the same one. I’ve worked with a hospital where concept testing showed us the logo resembled a cigarette, and with a mobile development company that found through concept testing that their site’s messaging around “creation” made them sound like house painters, rather than developers.

Testing a concept involves first having one or more concepts to test: messages, images, or key words. I like to create a maximum of 8 messages to test, and then put them online, against a white background with no context. I can send people to see the various URLs from social media, and easily get a large number of comments on each concept.

For some projects it’s better to show all of the concepts to each user, though in most situations you want users to only see one concept (to decrease the likelihood that seeing one concept will influence their thoughts on another).

Paper prototypes

Paper prototypes (i.e. sketching screens onto paper, and allowing a tester to “click” on buttons with a finger, then showing them the next page/screen) get a lot of flack from testers saying that their users couldn’t get a sense for the application’s actual usability. They’re right – paper prototypes aren’t intended for testing ease of use. They are, however, an excellent way of testing messaging and flow.

The key to testing a paper prototype is preparation. If I have created an ecommerce flow, I need to sketch a screen for every page a user might try to get to. I need to make sure my paper screens have clearly identified buttons and links, and I need to get familiar enough with the variations within the flow to be able to easily hand the user his next “screen” based on what button or link he selects.

Most tests work best with one or more observers taking notes, so that the moderator can be free to ask questions without worrying about writing down answers. For a paper prototype, this is even more important. The moderator will be responsible for “changing” screens, meaning he or she will certainly not have time to make notes on when the user was surprised or frustrated or confused.

Tree tests

Tree tests are quick to put together and valuable for getting insight into both a user’s vocabulary and the viability of the IA.

In a tree test, the user is asked to find information on a topic, and then is shown the main navigation of a site (as they would when they saw the top nav bar). This is typically done with software such as User Zoom or Treejack, which allows the user to then click on a navigation item and see what pages or subnav appears. When the user is satisfied that he or she has found the section or page that would have information on the requested topic, they click “submit.”

For observers, this is a great way to identify user expectations.

Word association

We all know that words have power, but some have different connotations to different groups of people. With this in mind, picking key words from the taxonomy and asking target audience members to define or react to them is a great quick way to explore the audience’s vocabulary.

Ideally, a word association test should not ask about more than 10 words. More than that will begin to  influence the way the user is hearing the terms.

One piece of advice: given the variety of connotations for any given word, word associations  are only useful if they’re coming from the target audience.


Where most user testing focuses on exploring the user’s mindset, surveys are often less open ended, simply because they are not in real-time, and don’t provide opportunities to ask follow up questions. However, surveys are a great way to identify goals, expectations, frustrations, needs, and fears.

For example, if a project has a discovery period, and we want to identify the three biggest problems to address in a software system, we can accomplish that by asking all 300 employees to respond to an online survey much faster than if we were to interview even 30 of them.