What is Information architecture?Add to My Brief

Mike Hall | 14/03/2008

What is Information architecture?

Everybody wants it, everybody says they do it, but what is Information architecture?

Information architecture, or IA, is concerned with the naming and sorting of information into intuitive, logical groups. Libraries and other information-rich places traditionally use it to come up with their categories and category names or nomenclature. Online it’s concerned with the same basic principle; namely, the grouping and labelling of information into a structure or site map.

The name Information architecture or IA has been wrongly used for a long time now to encompass all aspects of usability (the ease of use of a website) or the entire user experience online. In its truest form, it is only concerned with the site structure and labelling and not the individual page layouts.

Website design can be split into 3 key stages; information design, interaction design and visual design. Information design is undertaken by an IA or information architect, with interaction design being undertaken by a usability expert, usability designer, user experience analyst or consultant. The interaction designs are then interpreted by a graphic designer and brought to life.

Traditionally (from my experience), when you start out in this field, you start out designing page layouts and when you get enough experience, you move on to designing entire sites. This has given way to the idea that an IA or Information architect is more senior to a usability designer or user experience analyst or consultant. As a result it has been used as a natural progression through the ranks for anyone working in usability; when in fact, they are quite different skills!

I know very good information architects, who know very little about page layout and general ease of use on a page level, but are very goods IAs.

So basically information architecture is concerned with the grouping and labelling of content on a website and what happens on each of those individual areas at a page level is really another skill altogether. The industry is slowly changing its ways and more and more you see positions advertised for User experience analyst, User experience consultant and User experience architects.

It’s clear to see that information architecture is changing the world of web design – one site at a time. What remains to be seen is the effect that IA has on a growing Web 2 online environment!

If your website isn’t going where you wanted it to, for your business – maybe it’s time for a health check. An updated organisation of information and structure could be the kick you need to take your brand further online.

Contact wiliam (http://www.wiliam.com.au) for more information, or for a free consultation with our sales team!

tags: Sydney Web DesignUsability

Interested in learning more?

Wiliam is a leading supplier of web solutions and can provide expert advice to assist your business or organisation online.

Make enquiry   Request quotation

Comments

In its truest form IA is ...

In its truest form, it is only concerned with the site structure and labelling ... " Well no, actually; it's not the truest or even the most original form. Information architecture as a discrete discipline existed long before the web, having its modern roots [mostly] in library management and cataloging systems and in information theory, and will probably still exist at a point in the future when the web as we know it is considered to be an anachronism. You make some good points about web architectures and current web deployment practices but by overlooking the wider and deeper context you're isolating the web 'designer' and cutting them off from key issues and elements in - for example - Intranet and Extranet design and deployment - in particular the underlying issues of data, information, and knowledge architectures and management when considering an organisation as a whole. Such issues become critical in an environment where the organisation a] has truly vast quantities of data and information [in the terra or peta byte range] and/or b] seeks to deploy a common "write once publish many times" or single-instance policy for ALL intranet, extranet and public-facing content. The type of information architectures and design/deployment strategies appropriate to a stand-alone public-facing web site are generally quite inappropriate for such a complex integrated system.

Robert Neuschul


RE: In its truest form IA is ...

Thank you for your comments Robert and you are of course right. There is a lot more to IA than just structure and labelling.


The very brief explanation I have given here is merely to distinguish between, Information design, Interaction design and Visual design. Although each of these terms have many different meanings and uses, in the context of the Wiliam development methodology, they are the split between; Information Architecture, looking at site structure and flow, Interface Design, looking at page layouts and functionality and finally Graphic Design, looking at the physical look and feel of the site.


At Wiliam we adopt a collaborative approach to Web Development, creating a project team early on in the project with an IA, a Graphic Designer, a Developer, a Project Manager, an Account Manager and sometimes a member from Emerging Technologies (depending on the nature of the job).


The team meet and discuss the Project Initiation Document, previously filled in by the client, in terms of possible solutions and are involved at key stages throughout the initial phase of the project, which we have coined Pre-Production. The principle of involving the team throughout the project lifecycle is two-fold, firstly to ensure that everyone is involved in all decisions throughout Pre-Production (including Visual Designers). This helps to ensure that we provide the best solution. The second principle is to make sure that there is no drop off once Pre-Production is complete and the project moves into Design (Graphic Design) and then Development.


The purpose of the split is not to exclude Graphic Design, but to ensure that we focus on ease of use before visual appeal.

Mike Hall


a different approach

I found this article to be very interesting as it shows that other people across different agencies have a different approach to a User Centric Design approach. At civic, we have a UX team (2 people) who are responsible for what you described as Information architecture but we take it a step further. This team or two individuals are called UX professionals and are responsible for the IA, the content strategy and the wireframes. They also identify KPIs so we can monitor the effectiveness of a site. The designer then takes this on and applies his UCD approach to make it not only look pretty but make sure it works for the user. The developers then make sure it functions, using best practice usability and accessibility guidelines. We all agree on the same principles but have similar but slightly different approaches. I found this article really interesting, thank you :-)

Kelly Jones
http://www.civicuk.com

Comments

Share this page

Print this page Email this page to a friend Bookmark and Share

No Brief added yet.

My Brief results-driven approach emphasises a commitment to our clients needs through strategic analysis and best-practice.

Add to My Brief

Click on this icon to save item into My Brief. Retrieve, email and print

Drag & Drop

Drag & drop any iten with this icon into My Brief. Retrieve, email and print

Search Blogs