Exact schemes (alphabetical, chronological, geographical) have one right place

What it is

Exact organization schemes arrange content by an objective coordinate—letter, time, geography—so each item has one correct slot. Rosenfeld and Morville split these from ambiguous schemes: a contacts list by surname, news by date, stores by city leave almost no room for argument. Exact does not mean “more user-friendly.” It only means membership does not depend on interpretation—“starts with A” has no second reading.

An exact scheme answers “I know the attribute, which cell do I open.” It does not answer “what topic is this.” A product manual filed by year helps people who remember the year and fails people who remember a feature name.

Why it happens

An exact attribute turns the collection into an addressable axis. Alphabetical order exploits already-automatized spelling lookup; chronology exploits order in event memory; geography exploits unique place reference. Because the coordinate comes from a field of the content rather than an editor’s judgment, two people filing independently land in the same cell, and maintenance does not need another taxonomy meeting. The cost is that the user must already hold that coordinate. Without the author’s surname the alphabet is unusable; without the year the timeline is unusable.

The axis also demands complete, uniformly formatted fields. Dates written as “2024,” “last year,” or left blank break the axis. Mixing “North China” with “Beijing” destroys uniqueness and the exact scheme collapses into an ambiguous one that needs interpretation.

Studying it

The test is not attractiveness. It is whether known-attribute lookup is unique, and whether missing fields collapse the scheme.

• Paradigms: known-key lookup tasks (surname, date, city) comparing an exact axis with a topical one; then key-absent tasks to see the exact axis fail.
• Independent variables: organization key (letter / time / geography), completeness of the key, granularity (year vs day, country vs street).
• Dependent variables: first hit on the correct interval, oscillation across adjacent intervals, and whether people can say why the item lives there.
• Methodological note: high success on an exact axis is highly conditional on the task supplying that key. If the script writes the date into the prompt, the study overestimates how often people remember dates in the wild. Query logs show which keys people actually bring.

Where it stops holding

Alphabetical order of proper names depends on language and collation: pinyin versus stroke count for Chinese, umlauts in German, whether Spanish treats ch as a separate letter—all make “one right answer” into “one right answer given this collation.” Timelines split across time zones and lunar versus Gregorian calendars. Geography fails when borders are disputed or people use non-administrative units such as “on the way home.” If the content has no natural exact key (“how to file an expense”), do not invent one.

Applying it

• Use an exact axis only on collections people actually approach with a letter, a time, or a place: contacts, logs, stores, file numbers.
• Make the key a visible scale (letter index, year ticks, a map). Do not sort internally by the key while showing topical names in the UI.
• Freeze a single format and a single granularity. Do not mix “2024,” “last year,” and “Q3” on one axis.
• Verify by having two people file ten items independently; locations should match exactly. Then run the same lookup with people who do not know the key. Mass failure means a second scheme is needed, not a more polished exact axis.

Related

• Within the group: G1.02.2 Ambiguous schemes (topic, task, audience) depend on judgment · G1.02.3 The same content can live in multiple schemes · G1.02.4 The scheme depends on what the user already knows
• Adjacent: G1.03 Taxonomy and hierarchy · G1.09 Types of organizational structures
• Search terms: exact organization schemes · alphabetical index · chronological organization