Humane Information Architecture

1 - I can do better 2 - Jury's out 3 - Pretty darn good 4 - Splendiferous 5 - Awesometastic by 0 people | Log in to rate

Ranked #30,823 in Tech & Geek, #639,999 overall

Humane Information Architecture

Jef Raskin's definition of a humane interface - "An interface is humane if it is responsive to human needs and considerate of human frailties" - inspired this lens. It is here to answer the following question:

What is humane information architecture?

Humane Information Architecture resources 

The following sites discuss the principles of humane Information Architecture.

Humane Information Architecture: An interim definition 

This article is subtitled "An interim definition" because I am pretty sure I can't come up with a definition as wonderful as Jef Raskin's the first time around :)

By sheer plagiarism, I will start with "An information architecture is humane if it is responsive to human needs and considerate of human frailties." Nothing wrong with that one at all. But it could stand a little clarification. Which humans? Which needs? What frailties?

Are we talking about just the end users here? Does the humane information architecture need to be responsive to the needs of the IAs working on the project?

What constitutes a need from an IA perspective? To me, this will be a two-part answer:

* whatever the requirements documentation says is a need, and
* whatever the IA believes is a need and can be reasonably negotiated into the requirements set that is vital for the successful operation of the system from an IA perspective.

Examples of the latter are legion. It is not as if the IA is the Knight in Shining Armour come to rescue the poor end users from the evil Project Manager - far from it - but there are times when things get missed in the best of requirements sets. So we could take "do the best you can within the allowed budget in a humane way" and add to it "to meet the needs of all users and in so doing, make the system both useful and useable".

And frailties? There are the normal interface design motherhood statements like:

* "there should be no unexpected behaviour",
* "clickable regions should be readily identifiable",
* "use visual hierarchy to ensure that the most important stuff is easily found",
* "the navigation system must be clear and intuitive", and
* "use navigation labels that make sense to your audience".

How do you find out if these are enough? By testing - informal if needs be, but test early and often, with a minimum representative sample of ALL user types.

So now we have this: "do the best you can within the allowed budget in a humane way to meet the needs of all users and in so doing, make the system both useful and useable, and test to ensure that it recognises and compensates for apparent human frailties". This is a bit of a mouthful - I am sure I can come up with something better in time!

Canberra IA Cocktail Hour 

Some photos of Matthew Hodgson's Grand Unified Theory of Everything

The Grand Unified Theory of Knowledge Creation by facibus

The Grand Unified Th...

The Grand Unified Theory of Knowledge Creation in creation by facibus

The Grand Unified Th...

Matt's Grand Unified Theory previewing at Canberra IA Cocktail Hour by facibus

Matt's Grand Unified...

Canberra IA Cocktail Hour - the calm before the storm by facibus

Canberra IA Cocktail...

Reader Feedback 

Like this lens? Want to share your feedback, or just give a thumbs up? Be the first to submit a blurb!

by facibus

Facibus is the nom-de-net of Andrew Boyd, a consultant Information Architect living in Canberra, Australia.
(more)

Favorited By

Create a Lens!