Every few years, we reconfigure the information architecture (IA)—the menus—of UUA.org to keep up with changes in our shared language and priorities. We rely heavily on user input (from surveys, constituent feedback, and data from Google Analytics) and testing (surveys, card sorting, and tree testing) to maximize our chance of success. Here are some of the resources we use and the lessons we have learned.
For congregational sites, check out our recommended structure for congregational site content.
Reading, Tools, and Data
- A Practical Guide to Information Architecture is a fantastic overview of IA principles—Donna Spencer lays it all out in an easy-to-read format, and points to several useful tools and processes.
- Getting The Website Information Architecture Right: How to Structure Your Site for Optimal User Experiences is another great guide.
- Optimal Workshop has online card-sorting and tree-testing tools so you can get input from people all over, and their results-analyzing tools are really impressive. If your tests are small, the site is free; larger tests can be affordable if you schedule them well (the site offers monthly and yearly subscriptions—we save up several tests at a time to take best advantage of an occasional month-long subscription to test refinements).
- Google Analytics, of course. This is where we gather the bulk of our data about what was “most popular” on our site. We look at page visits and site searches—what sections get the most traffic, and what content people search for most often (and what words they use to do so). If you're building a new site, perhaps you can borrow some of this data from a similar site, like a neighboring congregation.
IA Goals for UUA.org
We have a few goals for our menus:
- Make material easy to find via menus.
Language and groupings should be obvious and unambiguous to as many people as possible. When we aren’t sure how to label a topic, we use what people type into our site search or suggest in card sort tests. We run card-sorting exercises to help determine how resources ought to be grouped together, and then we tree-test those organizations to make sure they made sense to as many people as possible. We add cross-referencing links when there was more than one “best” place to put something.
- Avoid vague menu labels.
If a label is vague (like "Resources" or "Library"), people have to guess what's there. We do our best to eliminate vague labels, also known as “evil attractors” or “dirty magnets”—labels that attract clicks when they shouldn’t. For example, “Membership” turns out to have too many meanings to people to be useful as a label, even though lots of people suggested it during our card sorts, so we used “Growing Your Membership” to more clearly convey what would be in that section.
- Control the depth of our site.
Our most popular content should be just a few clicks away from any page.
- Keep URLs short.
Sharing a page via speech, print, email, and social media should be easy, so shorter (but meaningful) URLs are important. Being able to say/write, “Go to UUA.org/immigration” is so much nicer than “Go to UUA.org and search for ____” or “Go to UUA.org and click on ____ then on ____ and then ____” or “Go to UUA.org/members/justicediversity/immigration.”
Don't Argue; Test
When egos or ideas conflict during the process, put it to the users. Everyone has the tendency to believe that their way of thinking is somewhat universal, but letting a whole bunch of people show you how they think about your content will clarify where the best home is for each of your resources.
For example, we learned via Google Analytics that people search for “email lists” more than “listservs” and “religious education” more than “faith development.” Where the language people were accustomed to using wasn’t incorrect or misleading, we used it, even in preference to our own branding. (Sometimes we used both, if the numbers were about even, e.g. “Our Whole Lives Sexuality Education.”)
Use Topic- or Task-Based Organization
In most cases, a topic-based or a task-based organization will serve people best.
Why audience navigation usually doesn’t work gives some fantastic examples illustrating why people find audience-based navigation confusing. An audience-based organization can work if the groups in question are totally distinct and separate from one another, and if the tasks related to each group are totally different. The UUA Health Plan page is a pretty good example of an audience-based organization (the headers) with a subsequent task-based organization (the bullet points). Most of the time, our audiences aren't so distinct, so a task- or topic-based structure will probably work better.
Communications and Social Media for UU Congregations is a good example of a topic-based structure. How to Run the Welcoming Congregation Program is a good task-based list.
You can have more than one kind of organization—you might use your sidebar to organize things topically, and your landing page to organize by task (or vice versa). (Either way, good usability and search engine optimization dictate that everything in the sidebar ought to also be linked in the page body, and everything in a section ought to be included in the sidebar.)
Sometimes an alphabetical organization might work, if the items you're listing have universally agreed-upon names and spellings (like U.S. states).
Listing by importance can also be handy: people will pay more attention to the top of your text area than anyplace else on the page, so putting your most popular or most important resources there is rarely a losing proposition.
Often data from your site's analytics can offer support to one approach or another, and content experiments (A/B tests) can help you determine what works and what doesn't for the people trying to use your site.