![]() |
||||||||||||||||
| |
||||||||||||||||
home> articles > Designing Information Architecture Part 2 of Designing Good Navigation Designing Information Architecture part 2 of 3 Navigation Design Series By Todd Follansbee April, 2009 First published in Web Marketing Today the largest, oldest internet marketing newsletter on the web - and still free. This originally appeared in Web Marketing Today here.
also consider reading
We define Information Architecture (with thanks to the Information Architecture Institute) as: The structural design of shared information environments. The art and science of organizing and labeling web sites, intranets, online communities and software to support findability and usability We added – insuring that customers have sufficient information to enable a successful conversion Simply put, you have good information architecture when visitors can easily find the desired product along with the answers to any product question that may arise. Easily stated, not easily achieved. If you remember from part 1 in this series, as many as 50% of visitors can't even find the products they want to buy. By building a good IA, those once frustrated visitors are likely to become your customers.
Start with the Product Information Set Good Information Architecture begins with creating the Product Information Set. We define this as the complete set of information needed by a customer to make a buy decision. That set of information will vary by customer because of elements like: job role, personality profile, where they are in the buy decision, level of competition, sense of urgency and more. The goal though is to try to cover every possible question and let the buyer decide what he needs. On more sophisticated sites we research personas and learning styles to refine the message but that only comes once the basic information set is assembled.
Building the Basic Product Information set. Shipping and handling Anxiety Fears about the order process Company reputation Product Features Maintenance Pricing Warranty, etc.
We next rank the importance of each card to the buy decision. Each team member votes on its relative importance: crucial, helpful, and not significant. Next we note on each card all the places (pages) where the questions belong, for example: Product information general, Product information specific, thumbnail or full size photo, FAQ's, Home Page, Alt Tag, and About Us. Many questions will belong in several places.
One question might be: “what if the shirt doesn't fit”. That is a common question ranked “crucial”. No clothing customer would consider an order without understanding the return policy. We might find that question addressed on: the home page, Warranty, FAQ's, a return policy page and the products page.
For sites with many products this sounds like a huge undertaking but you typically only need to do it for each major product category, if that. Once you have filled out the cards for one category, you will use many of these same questions on the rest of the product categories and the process will go quickly.
With this brainstorming session done, “lay out” the pages for your site and paste the appropriate questions everywhere they belong. Title and organize these pages logically according to your best guess (it is easier then it sounds).
What you now have is a set of pages with titles and these pages include the questions. The pages are organized where your “brainstormers” decided that they arise in the buy decision. Be sure to include add one page for: “review/submit order” as the final cart page. Pay special attention to the details on this page to make sure you have a good, complete, summary of the essential product information on the order.
With the product information set “complete”, at least in the form of questions, and the nav bar labeled according to the guidelines in article 1, the next step is to build out the site map to match the page order just completed. If the Nav bar is the heart of good information architecture, then the Site Map is the visual representation of the “structural design”.
The hierarchy of the site map should match the nav bar and its submenus. Group the products in a logical manner as shown in the example below. Consider using your “brainstorming team” to review the categories. Avoid naming product categories with special terms which may be unfamiliar to visitors new to the company.
This sample piece of a site map shows one product category from a sample sites' nav bar (Sailboat Products) and its two submenus along with an About Us page with one submenu:
When the site map is complete, you should have: A nav bar with submenus A set of pages full of Product information questions, The page layout aka the site map
If you are building a new site you must now answer all the questions you have gathered. You can answer them using the variety of web tools including:
If you are redesigning your existing site, your job is to revise the existing content to insure that all the questions you raise are answered at the right point. If page content grows unmanageable, your site map and menus should change as the design evolves. Consider using hyperlinks to access more detailed information in the product information set. If you put in the necessary time to complete this step in addition to a better site, the building or redesign will go much quicker.
Where the process can fail . Your team has carefully assembled the questions and built answers. You know where the information is. As one example, you know that product return information is available in the 4 th paragraph of the policies page and question 34 on the FAQ page. It is obvious to you that the question about “returns” has been answered. However no customer is likely to dig deeply for this essential information and if you have failed to address important issues like this early enough, you will lose conversions. Until you can find objective users to review your site, you will make mistakes on placement and will overlook questions.
How to avoid failure and measure the effectiveness of your IA - 2 approaches
1. By far the quickest and most effective approach is direct user testing. Only direct user testing can provide conclusive proof that the information set is complete. Fortunately, more and more readers committed to building a great UX, are reporting back on how helpful even the simplest direct user testing can be. To evaluate your IA, you need only sit down with 5 (or less) people and task them with finding and purchasing one of your products while they discuss their experience out loud. Be sure to read Zero Budget Usability testing for more details. If you have to explain anything , something needs revision.
2. If you are not ready for direct user testing, your alternative is to try to discover gaps in your product information set by monitoring email and incoming phone calls. Query as many customers as you can about the site and listen carefully to the questions and comments they raise. Many questions may have several meanings , for example: How long have you been in business? Do you have a store? What is your phone number? In addition to the simple and obvious answers (10 years, yes we have a store etc), I would infer from these questions that my company was lacking credibility. I would review and improve: the About us, testimonials and probably the home page to improve credibility. Similarly if there calls about basic questions which were very prominently answered on the site, I would assume that people felt the need to connect with someone before ordering. If this were the case, I would expand and/or personalize customer service and support pages. Rather then wait (and hope) for questions to come in and also run the risk of misinterpreting them, the simplest, fastest and best way to really understand these issues is by direct user testing.
Making products or services easy to find and with clear information that is easy to understand is the single best thing you can do to improve sales. Improved Information Architecture will also cut customer service costs, reduce returns and improve customer satisfaction. More and more vendors are discovering that time spend improving the IA directly affects their bottom line.
Please feel free to contact Todd directly with your comments, questions or suggestions. To watch a short video of a usability test please visit the download page. |
||||||||||||||||
services | facilities | testimonials | resources | site map | about us | glossary | How to articles | One hour site review |
||||||||||||||||