This morning while I was looking for some hazardous warning signs (don’t ask), I stumbled across the Interpretive Signage: Principles and Practice website which is run by Roy Ballantyne, an associate professor at the Queensland University of Technology.

As I started to read through the site, I found that the theory behind designing an effective interpretive sign is identical in crafting a pleasurable software experience. The concept struck a chord deep within my being: "Interpretation involves translating ideas and concepts into a format that attracts, interests and inspires visitors. Essentially, quality interpretation enhances people’s understanding and enjoyment of the places they visit."

Here are the rules for ‘effective interpretation‘. Next time you are developing a user ‘experience’ in your software, keep these in mind:

  1. Interpretation must be relevant to the intended audience.
  2. Interpretation should provide novel, varied experiences. and avoid repetition. (Note: For software, repetition is good).
  3. Interpretation should be organized with clear, easy to follow structures.
  4. Interpretation should be based around a theme.
  5. Interpretation should encourage visitors to get involved and give them opportunities to take control of their own experiences.
  6. Interpretation should understand and respect the audience.

I need to make a poster of this and put it in my office.



1 Comment

    Coding Horror (November 8, 2005 @ 12:31 am)

    Road Signs and Icons

    I’ve always been fascinated with road signs. And evidently so is Donald Knuth: During our summer vacation in 2003, my wife and I amused ourselves by taking leisurely drives in Ohio and photographing every diamond-shaped highway sign that we…


Sorry, the comment form is closed at this time.