Originally published: Sep 11, 2009
When I teach information architecture, the most common questions aren’t about the principles, but about the process. Just how do you decide on a particular method, how do you choose categories, how do you know what you’ve come up with is right?
As a teacher I’ve spent much time thinking about this, reflecting on my own process and how it actually works for me. And I’ve figured out the answer.
When I teach, I tell people this answer. Most are surprised, but there are always a couple of people in the room who nod to themselves and look comforted.
Would you like to know the answer?
Here it is.
Wait for the surprise.
Just make it up.
Yep. As some high profile product says, just do it.
This is surprisingly easy, but there is a dependency. You need information. You need to understand what you are trying to achieve, what users of the service need and know, and you need to know the content well. If you don’t have these things, it will be hard. But if you do have them, pulling them together into a first draft is surprisingly easy.
When you have made something up—and I don’t care whether you do it on a whiteboard, in a spreadsheet, or in your head—then start thinking about whether it will work for the users, and whether it will work for the content. Revise and play with your idea until these things start to fall together.
At some point you’ll start to feel good about your made up draft IA. In your head, it will look like it will work for the users and the content will fit in. You can see how it will help the organization achieve its goals. (If you can’t get to this point, it’s likely you are missing some kind of information. You’ll need to do something to fix that, or it will never work).
For me, there’s a funny feeling at this point—it feels simple and clear and makes me wonder why it took me so long to figure out. That’s when I stop fiddling and start talking to people about it. And I’m yet to be majorly wrong, so there must be something in it.
So I was doing this today for a client (I won’t say who, not that it’s sensitive—I just haven’t mentioned this to them). I took photos as I played with the new IA & thought you might be interested.
The background is that this is a fairly straightforward redesign of some government content. I know what the team wants out of it, have done some basic user research, cleaned up the content, and decided what to keep and create. It will be for a simple hierarchical site, so the IA in this case is a set of categories/subcategories to be used in navigation.
I don’t always do it like this, but today I jotted the main content chunks onto sticky notes. Apart from being physical, this helps me get away from the way content is organized now.
Then I jotted things we learned from user research onto a different color note.
Then I shuffled them around into groups of things that go well together.
I played with these for a little while and moved a couple of things between piles, but it wasnít hard. It fell together easily. All the user needs are catered and all the content fits in. There are some spots where we need some extra content, and there is no content that someone doesnít need. I could come up with sensible titles for all the groups.
My follow up step from this was to create a quick spreadsheet with the categories, subcategories and main content pages that came out of this shuffle; and also add a couple of special navigation items that will pull together some things across the piles (like forms and publications, which are scattered across the piles according to their topic, but will need separate entry points for some user tasks).
Tomorrow Iím going to run through this with the client team. Iím not drawing it up into a sitemap now. Iím going to talk them through it as I draw it on a whiteboard. This lets me describe each section and the rationale behind it, without them being distracted by something I have already written down. Iíve done this before and it is a great trick for communicating the draft IA—it lets me present it as a story, and triggers sensible questions.
Then, of course, there is lots more to do. Iíll be using an existing navigation approach, so donít need to design navigation. But I need to design all of the index pages - these will introduce each topic and provide deeper links plus cross links.
And we need to revise all the content. As this happens, the IA will change, but if Iíve done my job well it wonít change dramatically.
OMG, I just wrote a book on card sorting, and didnít run a card sort. Why not?
Well, I did other forms of user research which gave me a fairly good idea of the main issues and needs for users. Most users only ever need one or two content pieces, so there was little point getting them to do a card sort on things they donít care about. And I didnít feel like I had big gaps in my knowledge that would mean a card sort would help. So I didnít.
Weíll do usability testing on this as well, probably before content rewriting and after.
This November's User Interface 14 Conference has a full-day workshop with Donna Spencer on Information Architecture Essentials. Donna will cover the latest best practices for organizing large web sites. Sheíll introduce you to a variety of techniques to solve hard IA problems, such as choosing good labels and matching the right organization scheme for your audiences. Her session is sure to fill-up, so regiester soon.
Whatís your process when creating an information architecture? We'd love to hear your thoughts at the UIE Brain Sparks blog.
Read related articles: