First up, what is Information Architecture? Before this subject, Information and Content Management, I had never heard of this concept but could have made a reasonably accurate description of it. It's name suggests that it is the collection or representation of certain information. I know now that it is much more complex than this. In fact, the book 'Information Architecture' by Morville, on page 4, suggests that there are 4 definitions-
The structural design of shared information environments.
The combination of organization, labeling, search and navigation systems within web sites and intranets.
The art and science of shaping information products and experiences to support usability and findability.
An emerging discipline and community of practice focused on bringing principles of design and architecture to the digital landscape.This is all relevant to planning, designing and building a website which is all part of the development process. At first one might think of this development process as only requiring a user-centered focus to develop a successful website but it is very clear that the Information Architecture is just as, if not more important. This is because, a user must not just find the website appealing and easy to use but they must understand what they are seeing, where they can get the information but most importantly, they must be able to actually get the information they are after.
There are many downfalls and expensive costs to a website that handles its Information Architecture badly, including-
- Cost of time for employees, customers and general browsers looking for specific information. 5 mins per person per query can add up to hours if not days of wasted time.
- Cost of not finding information can be even greater. If the information is there but the customer, employee or uniformed worker can't find it, this information may be reported as non-existent and the data may be re-entered causing duplicate data and wasted time inputting it.
- Cost of extra training, maintenance, longer searching time and loss of customers through frustration are just some more problems.
Another downfall is that it is hard to measure well structured Information Architecture, as the best examples are often the ones where the user doesn't even consider Information Architecture as even existing. This means that a successful development can be measured by a lack of complaints and increased members.
After all of this, I can honestly say that an Information Architect plays a very important role in any successful website development. Any time devoted to improving this structure and representation of information early on can greatly improve the worthiness of the same information and therefore the overall website later down the track.
Until next time.
Riley Van Zeeland.
