The Need for Information Architecture

The importance of Information Architecture is described by Richard Saul Wurman as a way of “creating of systemic, structural, and orderly principles to make something work–the thoughtful making of either artifact, or idea, or policy that informs because it is clear.”  It helps breakdown complex and/or large amounts of information by allowing us to map out how it is structured, establish paths of execution, and most importantly, the form of understanding. 

An example of how I personally used Information Architecture is by designing an automated lab machine that processes a doctor’s lab order, verifies the patient with the order, dispenses the correct sample collecting container (with the patient’s information label on it), providing instructions (if the patient requests it) and finally collecting the sample from the patients.  The goal is to eliminate long wait times when the patient needs to check-in at the laboratory department when it deals with urine, saliva, and stool samples.  It would also alleviate patient load for lab technicians when they can focus more on blood draws or analyzing samples.

The machine deals with a large amount of information ranging from which doctors ordered what sample type to be collected from certain patients, verifying the patient’s personal information, all the way to notifying lab technicians that sample cups need to be refilled and the collection area is full and needs to be taken out.  Here is a data model to show what kind of information is being processed/verified by the machine.

The difference between Information Architecture and Interaction design can be defined by how information is structured and found vs. harnessing reactions between a product/application & users.  As Interaction designers, knowing how to create Information Architecture is an important skill to obtain; without it, there would be no sense of direction for the experience or application you are designing.  And by combining these elements together, it will help create a more positive, enjoyable user experience by emphasizing the form of understanding and clarity.

Print Friendly, PDF & Email

4 thoughts on “The Need for Information Architecture

  1. Your diagrams in details definitely show your depth of thoughts and understanding of the medical system. IA always starts from the understanding of the system.

  2. Hi Phil! I’m really glad to see your Systems project in your post, you put a lot of thought into your work so I’m happy to see it referenced here!

Comments are closed.

Close
Menu