Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Introduction to information architecture

Donna Spencer
January 14, 2011
180

Introduction to information architecture

This was a virtual seminar I presented for ASIS&T in January 2011. There were some great questions, and I answered some on the IA book website. In this virtual seminar, you’ll learn all about information architecture – what it is, why it’s so important to do well and the major things to do and not to do. We’ll discuss:
how people look for information and what they need to do with it when they find it
different ways you can organize information and when they are suitable
exactly how (processes) you can figure out the best ways to organize your content
the tricky issue of what to call things
other key IA tips
It’s all based on Donna’s experience designing information architecture, navigation and content for a wide range of information systems (usually big ones) such as government and corporate websites, intranets and document management systems.

Donna Spencer

January 14, 2011
Tweet

Transcript

  1. About me • User experience freelancer – information architecture, interaction

    design, content strategy • Far too long (10+ years) • Run UX Australia (Sydney, late August 2011) • @maadonna !"#$%&'#()*+ ,'-%.'%-#/.0%*#0".% 1'23%4'#%.50%-06+ 7%2#"1(1"8%*9/$0%.'% /)4'#:"(')%"#15/.01.9#0+
  2. Topics covered • Information-seeking behaviours • How people look for

    info & what they do with it • Classification schemes • Ways to organise information & when they work • Processes • How to determine the best IA • Labelling • Testing IA • I’ll answer questions at the end (ask them at any time in the ‘questions’ window)
  3. Browse or search • People say that an individual either

    browses or searches • Not true - depends on what they need to do
  4. Finding known items • Know what you want • Have

    words to describe it • Fairly good idea of where to start • Know there is an answer • Know when you see the answer
  5. Exploring • Have some idea of what you want to

    know • May not know how to articulate it/ terminology • May not know where to start • May never end
  6. Refine and narrow • Large set of items • Some

    criteria that matters • Narrow down to those of interest
  7. Getting a broad idea • Sometimes people just need to

    know the basics • Don’t need the detail
  8. Information behaviours • In your projects, think about what people

    need to do • Then figure out how to design for it
  9. Organisation schemes • For any set of content, there are

    many ways we could organise it – many different schemes • Some of the most common: • Subject/topic • Geography • Task • Audience • Mixed
  10. Designing IA • Process of synthesis - user research, business

    goals, content • Draft top level groupings/attributes • Just make something up! • Check it • See if it suits the content • See if it will suit the users • Revise it • Stop when it feels right • Start discussing it with people
  11. Tips • How many content groups? • Think about navigation,

    but put it aside • If stakeholders hate it... • Team or individual • Don’t do it in front of a computer • Make notes about rationale • Sequencing
  12. Great labels • Are dull! • Call things by their

    correct name • Are consistently used • Use terms the audience uses • Are as clear as possible
  13. Testing IA • Just tests concepts and labels • Still

    will need to test navigation/pages • Need • Draft IA • Scenarios • Participants
  14. Questions (if there are more than I can answer, I’ll

    answer some at http://practical-ia.com/)
  15. And a plug... Find out more in my full day

    workshop. 31 March, IA Summit, Denver (Colorado) http://2011.iasummit.org/