Information architecture patterns

We have patterns for buildings, patterns for interaction design, and patterns for software development. But are there patterns for information architecture?

Of course there are - patterns emerge from use, and there certainly are enough information architectures around to identify a set of patterns.

This presentation will describe a wide range of commonly-used information architecture patterns, including hierarchies small and large, different types of database structure, hypertext, subsite models, sites with multiple entry points and ways of combining these (and more that I discover before April).

For each I will describe the core elements of the pattern, discuss the most appropriate uses and show real-world examples.

Understanding the different patterns will help attendees to select the most appropriate structures for their content.

Transcript

1. Information architecture patterns Information architecture patterns
2. About me • User experience (IA, IXD, user research, content etc etc) for 10+ years • Freelance in Canberra, Australia • UX Australia (late August, in Melbourne) • 3 books Card sorting How to write great copy for the web A practical guide to information architecture
3. IA patterns A pattern is an emergent A pattern is an emergent answer to a common problem p
4. Hierarchy
10. Hierarchy • Good for:  Small sites – little need for anything else  When you are guiding, allowing people learn more and more detail • The relationship between content chunks is naturally hierarchical b d d  broader and narrower
11. Database
15. Database • Content chunks are independent  There are relationships, but not dependent on each other • Good for:  Single ‘product’ with consistent structure  Storing content once, display it in many ways
16. Hypertext
20. Hypertext • No planned structure • Content is linked together in context • Good for:  Content not known in advance  Developing content domains  Collaborative work • Main challenge ‐ knowing what is available to link to
21. Linear
22. Simple hierarchy & database
27. Simple hierarchy & database • Very common pattern • Good for a wide range of medium sites that have a need for some database‐style content
28. Catalog
34. Sub-sites
44. Subsites • Good for big organisations with lots of separate topics/responsibilities • Subsites may have a consistent structure/pattern or vary • Need to decide how often people need to cross between subsites
45. Focused entry points
52. Why do patterns matter • Help you choose an appropriate way to structure your content • Provide an overall concept
53. Questions & thanks htt // d b / • http://maadmob.com.au/ • +61 409‐778‐693 • donna@maadmob net • donna@maadmob.net • Twitter etc: maadonna