Tag systems need user-defined labels, not only presets

What it is

Tagging content is so it can be found again by one’s own cue. User-defined means people can type a word that is not in the system list and use it on this object at once. Presets only (“Work / Personal / Urgent”) cover the designer’s boxes, not “client-A-contract” or “wait for advisor.” This is where words come from. Whether multi-tag retrieval is AND or OR, how a vocabulary is reined in, and how machine tags split from human ones all assume people can coin words. Bulk select and drag-reorder do not produce this vocabulary.

Why it happens

Personal classification cues come from the job, not from the product’s IA. Presets force the job into a few boxes; when the boxes run out, people abandon tags for title prefixes, folders, or an outside list. User-defined hands the vocabulary to the moment of use: the first time “Q3 budget” is needed, it can be typed, without waiting for an admin enum. Fully open vocabularies spawn spelling variants; that is a later convergence problem, not a reason to keep the list closed. If custom lives under Other and needs approval, the moment for coining has already passed. Presets can still suggest, for cold start; suggestions must not block typing.

Studying it

Give a pile of personal material that three or four presets cannot cover. Ask people to mark it so they can retrieve it two days later by a purpose. Compare presets only, presets plus custom, custom with no suggestions.

Independent variables: whether a new word can be typed, whether it is immediately filterable, whether presets can be skipped. Dependent variables: actual tag use, bypasses such as title prefixes, retrieval two days later by the coined word.

A lab that says “please use tags” inflates use. Make tagging optional. Completeness of an admin vocabulary is the wrong success metric.

Where it stops holding

Compliance archives and clinical codes must use a controlled list; custom can only be extra, never a substitute for the legal code. Fully free coining in a shared space creates synonym fights; offer space-level suggestions, still allow typing outside them as a personal word. Machine classes (spam, invoice) can be system presets; people must be able to override, or the subject is system tags, not a human vocabulary.

Applying it

• The tag field accepts a new word and creates it on enter. Presets are dropdown suggestions only.
• The new word appears at once in filters and in that person’s vocabulary, with no refresh or approval wait.
• In a shared space, keep personal words and space suggestions apart so one typo does not pollute everyone.
• Verify: give a purpose the presets do not contain (“advisor proposal”). People should coin a word and retrieve with it in a filter. If they can only pick Work or drop tagging, user-defined never happened.

Related

• Within the group: H8.10.2 Multi-tag retrieval must state AND versus OR · H8.10.3 Unbounded tagging destroys retrieval value · H8.10.4 System tags and user tags need a visible source
• Adjacent: H8.05 Save for Later · G1.04 Tagging Systems · H8.02 Batch Operations
• Search terms: user-defined tags · folksonomy · controlled vocabulary