FIELD GUIDE · 6 MIN READ
Test names with questions that lead to revisions
Move beyond “Do you like it?” and observe whether a name helps someone complete a task.
Choose a decision to test
A useful check begins with a task: find the harbor on a map, identify the clerk in a dialogue, choose the right item in a list, or remember which group maintains a public route. A preference question can reveal taste, but it does not settle those tasks. Write down the decision you want the name to support. If the name appears only once in a poem, a different kind of feedback may be appropriate. The test should match the work rather than impose an unrelated standard.
Prepare a small realistic sample
Use the actual neighboring names, approximate text size, and amount of surrounding context. A candidate tested alone has no competition for attention. For a character, provide a short exchange with two other speakers. For a location, provide the relevant part of a map and one instruction. For an item, use the real list labels. You do not need a polished interface to ask a focused question, but the sample should preserve the source of any ambiguity you are trying to understand.
Ask what someone can do
Try “Which person would you ask about the archive record?” or “Which landing is the instruction sending you to?” Observe the answer before explaining the intended meaning. A hesitation can point toward an unclear label, missing context, or poor presentation. It does not automatically prove the name itself is wrong. Ask the person what they used to make the choice. Keep their explanation separate from your own inference about why the design succeeded or failed.
Record the limits honestly
One person’s response is one observation. A small informal exercise is not a validated usability study, and an editorial read-through is not a user test. Record the sample, task, response, and uncertainty without inventing a confidence score. You can still make a practical revision. If three names look similar in a narrow menu, changing one is a reasonable editorial choice even before conducting formal research. Accuracy about the evidence makes the note more useful to a collaborator.
Change one relevant feature
Revise the opening letter, syllable pattern, spacing, short form, or title placement. Repeat the same task so you can see what the change addressed. Avoid changing the whole sample and then attributing every improvement to the new name. A revision log can be very small: original form, observed problem, new form, and remaining question. Keep internal identifiers stable so the visible change does not break references in a working application.
Test delayed recognition carefully
If remembering the label matters, introduce a short unrelated task before asking about it again. Keep the delay and context modest and describe them accurately. A failure to recall may result from unfamiliar material, competing information, or a task that did not make the name relevant. Do not turn a casual memory exercise into a universal claim about pronunciation or intelligence. Use it to identify which candidates deserve another draft, not to rank people.
A practical review sheet
Record the intended task, surrounding labels, display context, observation, revision, and open question. Include a screenshot or a short passage if it helps reproduce the problem. Try the final name in both its full and short forms. End the review when the identified problem is resolved or when the remaining uncertainty requires a different kind of expertise. Repeating the same check indefinitely does not guarantee a perfect name; it can simply delay writing the next scene.
PUT IT INTO PRACTICE
Try the method on a fresh name.
Open the related naming toolCreative drafts. Check suitability and existing uses before publication.