Information Architecture: My Process
Ever since I left school, I've stopped formalizing the entire information architecture procedure until recently whereby a client requested that a document outlining the information architecture of the site be a necessary deliverable at a certain phase in the project.
Information architecture is simply a blueprint for a web design / development project. It helps create the skeleton for your website and provides you with a direction to work in. Below I'm listing key sections defining my information architecture document. Do note that my process might differ from the others', I'm sure there are quite a few ways to get the same end result.
What do you want to achieve with this website?
Here, we are concerned about what the client aims to achieve with this project.
Is it to establish a stronger online presence for the company? To provide services for users? If so, what value does it add to the users?
Basically you want to know what are the goals for this project.
Who are the target audience?
This is a question that I'm sure you are probably bored of seeing. But let me be quick and just say that we'll be needing detailed demographics about the target market as this will help in the next section.
Personas
Based on the target market and it's demographic information, I typically go on and create 3 to 5 profiles of fictional characters that match the information provided in the previous section.
Use Cases
This is the fun part. Using the personas created, I'll go into storytelling mode and craft out scenarios of why and how my fictional characters will use the completed website. Be creative (and even absurd if you want).
Content Organization
After crafting out the use cases, I tend to get a clearer picture of what features will be required on site to help users achieve what they want. With these, I can move on to group related features and draw out a navigation scheme for the website.
Sitemap
Now, we know what features are needed, how they are grouped as well as the navigation system to be provided, we can now draw up a list of pages and organize them in a hierarchy model ala a sitemap.
Wireframes
The final part of my process is the creation of wireframes for pages identified in the sitemap. I don't use a software for these wireframes, just a normal ballpoint and my moleskine.
Note that when I present my wireframes, I tend to go back to the use cases created in the earlier section to give my clients a clearer picture of my sketches.
So this is how I approach developing an information architecture for a website. To clearer illustrate this process, I will throw up a fictional project in my next blog post.
Cheers!




