Information Architecture Rules

December 19, 2003 | View Comments (10) | Category: Information Architecture

Summary: Are there any definite rules of Information Architecture?

After doing the redesign of the site, which required a complete rethinking of the Information Architecture (IA), I began to wonder are there any "rules" of IA that should never be broken? To me the web is still in its infancy so it is hard to picture there being any rules at all. Sure there are guidelines that change every couple of years, but what are the hard rules that must be followed?

Global Navigation

Certainly every site has to have a global navigation system. I mean without no one would be able to navigate through the site seamlessly. However, after seeing simpl(e)y done I wondered if this counted as global navigation? If you do have a global navigation system, does it always have to be separate from the rest of your navigation? In some cases wouldn't it be better to integrate the navigation with the content? I think so because it will help the user stay focused on the content. It should provide for a fluent experience through your site. However, implementing something like that would not be easy and probably not practical.

Falling Into A Trap

I don't know how many of you read the great IA sites out there such as Boxes and Arrows or iaslash, but you should. So called "Information Architects" are professionals that are experts in IA (too obvious). They can make many great points about how a website is structured and the guidelines/rules that should be followed. Being designers/programmers we may sometimes read their ideas and not take a second glance to consider maybe they are wrong or at least maybe there is a better way to go about things. You are designers and your are programmers. Creativity runs through you because that is the essence that will make you successful at what you do. Why not be creative enough to expand on the thoughts of IAs?

I write this post because while I go looking at IA sites I notice that they all follow the same trends of other sites. I wonder how come none of them thought that maybe a site could be done differently. Do IAs follow their own conventions so strongly that to them only one way is right? Since they are the supposed experts of site structure are we stuck following them? I say all web professionals listen to other's advice, but question everything. The web is too young for rules and to think there is only one right way.

If you can think of any hardset rules that must be followed on the web then please share them with me. I am always willing to listen.

Trackback URL: http://9rules.com/cgi-bin/mt/mt-tb.cgi/80

Comments

#1

Sure...

No hamster dancing.

Your under construction sign is not cute. It isn't. It really isn't.

Please, god, no goatse

Sorry... no serious suggestions at the moment (though those are definitely heartfelt requests)

JC (http://www.thelionsweb.com/weblog)

#2

I mean the first rule that I can think of, but am not sure what this has to do with IA is making links distinguishable from regular text. That should always be a given.

Scrivs (http://www.9rules.com/whitespace/)

#3

IA is the same thought as Systems Analysis in that it has to follow a develoment life cycle process in order to be done right.

PADIM
Plan - A high level (initial) view of the project and intended goals

Analyze - Refine the goals. Investigate not only the company, but also the clients, competitors and vendors. In terms of websites - discover what and how these users are expecting to use the interface.

Design - Document clearly and in detail the layout and operation for those who be using the site or uploading content to it

Implement - test, test, test and run

Maintain - changes, correction, additions...

In regards to the simpl(e)y done website you referenced. I like the minimalist look and think the the sitemap type navigation works - however, I think most people who don't work in the "biz" as web production professionals are not going to understand how to navigate it - or that the orange text is major chapters and the cutesy words are sublinks within those chapters. Also, on that page I think most people (again outside the biz) would expect to be able to click on the email link.

In other words, that website is designed to attract other designers - not the average businessperson looking to build / rebuild.

Bottom line, build (architect) for your audience.

Mark Fusco (http://www.lightpierce.com/ltshdw)

#4

Creativity and lateral thinking as a whole relies on unpredictability and spontaneity. When you try to apply vertical thinking rules (absolute rules that must never be broken), the web falls apart and you inevitably get opposing factions. Seamless integration is yet to be seen, in my opinion.

David House

#5

You are right in that the context of design should take into consideration the audience. The procedure that you have broken down could be applied to almost any profession then I guess. Those however aren't rules, but a methodology to follow.

David: I like what you said.

Scrivs (http://www.9rules.com/whitespace/)

#6

Scrivs -

Actually, the process I outlined is specifically for IT systems (including web-based) design and development.

Perhaps I am not getting how you're differentiating between "laws" and "methodology." Both are a set of conventions to follow in order to achieve a purpose - correct? Maybe law implies something more strict, but if you're not going to strictly follow a methodology why establish one?

From Boxes and Arrows -
Information Architecture: Blueprints for the Web

"A guru, in Wodtke's terms, is nothing more than a critic who prescribes rigid, oversimplified “rules” of website design. Dictating rules is risky, she implies, because inexperienced site planners and designers tend to take them at face value. They operate under the mistaken assumption that following those rules is all they need to do to create a good site. But there simply aren't enough well-designed sites out there to justify that approach.

Wodtke argues that good site design is complex, nuanced, and context-specific. You have to look at the problem fundamentally and create a plan that serves the needs of your specific users. You have to create a blueprint based on solid thinking..."

After introducing her principles, Wodtke provides a nicely succinct definition of the role of the information architect: “It's your job to create a design that balances the users' desires with the business's needs.” (62). She then discusses how to tackle the first part of that mission: getting to know your users."

Mark Fusco (http://www.lightpierce.com/ltshdw)

#7

I am very knowledgable with Christina's writing seeing how I have read her book 3 times already. It was one of the inspirtation for this post. The difference between methodology and rules to me is a methodology is more of a set of steps to follow. A rule is something along the lines of all links must be underlined.

Scrivs (http://www.9rules.com/whitespace/)

#8

Ok, then it's obvious that hard rule number one is to understand and build for your customer and their "world."

Can this hamper your creativity? Possibly. But if you're building a site for a customer whose only concern is selling $15 million worth of inventory -your creative concerns should be focused primarily on how to place those underlined links both in a manner that is easy for the site users to understand and also motivates them to click. The only way to do that is to follow the PADIM process.

This applies, even if you're building an experimental site designed to do nothining more than push the envelope of design techniques.

Make a plan - work the plan - dominate the world.

Mark Fusco (http://www.lightpierce.com/ltshdw)

#9

So the building for the customer should be the only rule then? Even something as chaotic as design has a process. Some people simply take the time to name these processes and give them steps as you have done.

When it comes to IA I believe there are some common sense rules and general guidelines that should always be followed. One day I will have to sit down and generate a list for discussion.

Scrivs (http://www.9rules.com/whitespace/)

#10

I think too many of the above comments lean into not the IA realm, but into the usability or design realms. IA is not usability, it's not about identifying links from text, avoiding hiddious graphics or using the proper colors. It's about architecture.

You really have to think about this with the analegy of constructing a large building. In the case of IA, they are really the blueprints, not the color of the walls, what color to paint the door trim, if the eves will have a stright edge or a carved wave edge, etc.

Nick (http://www.digital-web.com)

Keep track of comments to all entries with the Comments Feed