Categorisation is hard
What goes where?

Categorisation is hard

Categorisation schemes are tricky to create. Your local supermarket probably arranges their goods based on a planogram updated frequently by head office, specifying where various items are to be placed on shelves. Competing requirements will be balanced – findability, cross-promotion, visibility of “hero” product lines, payments for prime positioning, and so on.

If you visit a supermarket that belongs to a different parent company, or that is independent, you will likely be confused to some degree as items that seem like natural neighbours are inexplicably separated.

Categorisation online is also tricky. Do guitar strings belong under “accessories” or “guitars?” The virtual nature of an online environment means you can duplicate, and have items residing in more than one location, but this can create confusion and unanticipated consequences such as ambiguous or misleading breadcrumbs.

A compounding factor is, of course, human nature. I was working with a client that specialised in compliance. One of their customers told me a story about their Health & Safety system. Any accident or incident had to be reported using an online form at the earliest opportunity. A staff member was involved in a car crash late one night while working. The staff member duly filled in an incident report. When specifying the severity of the incident, they selected “fatality.”

On submission, the incident was automatically escalated. Various senior managers and crisis management personnel were awoken.

It transpired that the worker had struck and killed an unfortunate kangaroo. No humans were harmed.

For me this is a good illustration of the fact that no matter how much thought and effort you put into creating and testing and refining a categorisation scheme, you can be guaranteed that somebody will interpret it in a way you’d not intended or foreseen.

One of my favourite topics. Always have nteresting challenges. And tell what category is it that puts together vegemite and peanut butter and honey. I know it is usually “spreads” but it still isn’t right.

Lovely example - what did happen to the poor kangaroo :)

Like
Reply

To view or add a comment, sign in

More articles by Gerry Gaffney

  • In the echo chamber

    While we're all intellectually aware of the echo chamber effect on social media, I've recently had a personalised…

    2 Comments
  • 16 years of UXpod

    I started the UXpod User Experience podcast in the far distant past - 2006. For my final episode, Caroline Jarrett…

    12 Comments
  • Welcome to the Kafkaverse

    In Franz Kafka’s final (unfinished) novel, the protagonist (‘K’) is summoned by the authorities to do some work in a…

    5 Comments
  • The central importance of domain knowledge and lived experience

    The idea of involving real users or customers in early co-design is sometimes met with resistance. The arguments are…

    3 Comments
  • The "Minimum Viable" trap

    More than forty-five years ago Fred Brooks, known as the “father of the IBM System 360,” and no slouch, wrote: “An…

    11 Comments
  • Quality is a signifier of quality

    On many devices, replacing batteries is one of those occasional tasks that can be annoyingly difficult. Often you’ll…

    5 Comments
  • You can't fix design problems in the documentation

    The aphorism that "people don't read" can be difficult to accept. I often work with clients who spend a lot of time and…

    5 Comments

Explore content categories