skip to content

In information architecture, what are organization schemes, and how do exact schemes differ from ambiguous ones?

level: juniorimportance: should knowfreq 38%

answer

  1. the rule for grouping
  2. exact: alphabet, time, place
  3. ambiguous: topic, task, audience
  4. one rule per list
  5. match scheme to how people seek

basics

~20 s

An organization scheme is the rule that groups content. Exact schemes — alphabetical, chronological, geographical — give each item one right place and suit known-item lookup; ambiguous schemes — by topic, task or audience — need judgement but support browsing.

solid answer

~40 s

An **organization scheme** is the principle that decides which items sit together. **Exact** schemes divide content into well-defined, mutually exclusive groups — alphabetical, chronological, geographical — so every item has one correct home; they work when people already know the name, date or place they want. **Ambiguous** schemes group by **topic**, **task**, **audience** or metaphor; they need judgement and items can plausibly belong in two places, but they serve people who know roughly what they need without knowing its name. On a museum ticketing kiosk, today's timed entries fit a chronological scheme, while “Buy tickets”, “Collect booked tickets” and “Member entry” form a task scheme. The classic mistake is **mixing schemes in one list**: “Adults”, “Exhibitions”, “Today” and “Collect tickets” side by side force visitors to guess which rule applies.

go deeper

for a junior

Recall the two families: exact schemes such as alphabetical and chronological, and ambiguous ones such as topic, task and audience, with one example of each.

for a middle

Explain which kind of seeking each family supports, and why mixing schemes within one list makes people guess which rule applies.

for a senior

Show how you pick one scheme per level from evidence about how people seek, and how you keep a hybrid structure from decaying as stakeholders add items.

for a principal

Weigh a single shared scheme across many products against schemes tuned to each audience, including the cost of keeping cross-listed content consistent.

## What an organization scheme is **Information architecture** (IA) is the structural design of an information space: how content is organised, labelled and navigated so that people can find what they need and understand where they are. An **organization scheme** is the rule that decides which items belong together — the *criterion* of grouping. It is distinct from an **organization structure**, which is the *shape* the groups form: a hierarchy, a flat list, a hub with spokes, a set of combinable facets. The same content can be grouped by several schemes, and the choice changes what is easy to find. Schemes fall into two families. ## Exact schemes Exact schemes divide content into **well-defined, mutually exclusive** sections, so each item has one correct home: - **Alphabetical** — names, glossaries, directories. - **Chronological** — events, timed entries, histories. - **Geographical** — galleries by floor or wing, branches, regions. They are easy to design and maintain, and ideal for **known-item lookup**: a visitor who knows an exhibition's title or the time slot they want gets there quickly. Their weakness is that they help only people who already know the key they are searching by. ## Ambiguous schemes Ambiguous schemes group by meaning, which requires judgement: - **Topic or subject** — exhibitions by theme, collections by period. - **Task** — what the person wants to do: buy, collect, renew, donate. - **Audience** — adults, families, schools, members. - **Metaphor** — grouping modelled on a familiar thing; risky when the metaphor is not shared. They are harder to design and maintain, and an item can plausibly live in two places, but they support **exploratory** seeking — people who know what they need but not what it is called. Most useful navigation is built on ambiguous schemes, which is exactly why it needs validating with real users. ## Choosing a scheme | Scheme | Works when… | Museum kiosk example | Risk | |---|---|---|---| | Chronological | Time is how people think about the item | Today's timed-entry slots | Useless for anything not tied to time | | Alphabetical | People know the exact name | Exhibition index | Fails if they know the theme but not the title | | Task | People arrive with a goal | Buy, collect booked tickets, member entry | Tasks must be ones visitors recognise | | Audience | Needs genuinely differ by group | School groups, members | People may not know or accept their category | | Topic | People browse by interest | Exhibitions by theme | Categories overlap; labels need testing | A walk-up kiosk is a strong case for a **task scheme at the top level**: visitors arrive with a goal and little patience, and a handful of dominant tasks cover most sessions. Deeper levels can switch rule — chronological for choosing a slot, audience for ticket types. ## Mixing schemes and hybrid structures A **hybrid** is legitimate when each level, or each clearly separated region, uses one rule. The defect is mixing rules **within one list**. A kiosk home screen offering “Adults”, “Special exhibitions”, “Today” and “Collect tickets” combines audience, topic, time and task; a visitor holding a family booking made online cannot tell whether to press “Adults”, “Today” or “Collect tickets”. Mixed lists also grow badly: every new stakeholder adds an item under whichever rule suits them, which is how menus reach forty options. ## A decision procedure 1. **List the main things people come to do or find**, from logs, front-line staff and research. 2. **Ask how people describe each one** — by name, by time, by goal, by who they are. 3. **Pick one scheme per level**, usually the one matching the dominant way of seeking at that level. 4. **Validate** the grouping with users before building it. 5. **Revisit** when the content changes; a scheme that fitted twelve items may not fit forty. The reasoning is the same whether the structure appears as screens on a kiosk, pages on a website or views in a native mobile app: the scheme is about grouping, not about the widget that displays it.

  • What is the difference between an organization scheme and an organization structure?
    The scheme is the grouping criterion — by time, name, task, audience. The structure is the shape the groups form: a hierarchy, a flat list, a hub and spokes, or a faceted model where items carry several attributes, such as date, audience and price, that people combine to filter. One structure can use different schemes at different levels.
  • When do audience-based schemes backfire?
    When people do not know which audience they belong to, do not want to self-classify, or need content that serves several groups. A grandparent bringing a school-age child to a museum may hesitate between “Families” and “Seniors”, and content duplicated across audiences drifts out of step over time.

saying these in an interview costs you the question

  • Alphabetical order is always the most usable way to organise a menu.
  • Mixing audience, topic and task in one menu gives users more ways in.
  • Exact schemes suit browsing when people don't know an item's name.
  • An organization scheme and the navigation widget showing it are the same thing.