Information Architecture: Intro to the Job, Lecture Day 2

36
The Information School University of Washington Content Strategy Special Topic in Information Architecture Content Strategy Content Strategy

description

Some of my favorite references, links and visuals when discussing information architecture as a career with my students.

Transcript of Information Architecture: Intro to the Job, Lecture Day 2

Page 1: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

Special Topic in Information Architecture

Content Strategy

Content Strategy

Page 2: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

Objectives

Introduce and Understand • Overlapping practices in IA, UX• What do IAs actually do: skills and

deliverables • What is our IA Project Process?

Page 3: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

Readings• Cummings, Michael (2009). Information Architecture. Retrieved 23

March 2011 from Interaction-Design.org: http://www.interaction-design.org/encyclopedia/information_architecture.html

• What is IA. Retrieved 23 March 2011 from iainstitute.org: http://iainstitute.org/en/learn/resources/what_is_ia.php

• Davis, Nathaniel (2011). Framing the Practice of Information Architecture. Retrieved 1 December 2011 from http://uxmatters.com/mt/archives/2011/09/framing-the-practice-of-information-architecture.php

• Davis, Nathaniel (2011). The T-Model and Strategies for Hiring IA Practitioners Part 1. Retreived December 1 2012 from http://www.uxmatters.com/mt/archives/2011/10/the-t-model-and-strategies-for-hiring-ia-practitioners-part-1.php.

Page 4: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy Frank C. Müller

Page 5: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

Keywords

• User Centered Design• User Experience• Information Architecture• User Interface• Interaction Design • Content

Page 6: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

Keywords

Information Architecture is a set of methods for classifying, storing, accessing, displaying and using information.

OR

Page 7: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

Interaction Design Foundation

Information Architecture is a discipline and a set of methods that aim to identify and organize information in a purposeful and service-oriented way. It is also a term used to describe the resulting document or documents that define the facets of a given information domain. The goal of Information Architecture is to improve information access, relevancy, and usefulness to a given audience, as well as improve the publishing entity's ability to maintain and develop the information over time. It is primarily associated with website design and it is directly related to the following professional disciplines: User interface design, content development, content management, usability engineering, interaction design, and user experience design. It is also indirectly related to database design, document design, and knowledge management.

http://www.interaction-design.org/encyclopedia/information_architecture.html

Page 8: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

• The structural design of shared information environments.

• The art and science of organizing and labeling web sites, intranets, online communities and software to support usability and findability.

• An emerging community of practice focused on bringing principles of design and architecture to the digital landscape.

http://iainstitute.org/en/learn/resources/what_is_ia.php

Page 9: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

Explain IA

http://www.flickr.com/groups/explainia/ Murray Thompson murdocke23

Page 10: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

Explain IA

http://www.flickr.com/photos/boltron/4329185089/in/pool-1326826@N23/

Explain IA Grand Prize Award-Winning entry for the Explain IA Contest. Shot and directed by Nate Bolt and Kate Nartker who make these weird videos for fun as Beep Show. This one was for for Bolt | Peters. Starring Audrey as "daughter" and Frances James as "mother."

Page 13: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

Boersma T-Model for user experience design

Content Strategy

Davis, Nathaniel (2011). The T-Model and Strategies for Hiring IA Practitioners: Part 2. Retrieved 1 December 2011 fromhttp://www.uxmatters.com/mt/archives/2011/11/the-t-model-and-strategies-for-hiring-ia-practitioners-part-2.php

Page 14: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

Segmentation of UX practice verticals

The Information School University of WashingtonContent Strategy

Page 15: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

Competencies of a freshman IA practitioner

Page 16: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

Competencies of a junior IA practitioner

Page 17: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

Competencies of a senior IA practitioner

Page 18: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

Bingo

Page 19: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

Activity a job by any other name

Match the job title to the description

Page 20: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

Activity a job by any name

Page 21: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy Ron Armstrong

Page 22: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

WASP Curriculum Competencies http://interact.webstandards.org/curriculum/user-science/information-architecture-1?overview

Research/Project Definition

Content Organization & Structure

Process: Flows, Storyboards, Patterns

Structure: Maps, Diagrams, Wireframes

Interaction: Specifications, Prototypes

Page 23: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

Create Content Inventory Conduct Content Audit Create Content MapCard Sort

Conduct Client InterviewsUser Needs/Research OverviewProject Brief Create a Persona Conduct a Competitive Analysis Global Site Map

Page Description DiagramWireframe

Functional Specifications Prototype

Storyboarding Process Flows

Usability Test Plan Usability Testing

Activities and deliverables in an IA Project

Page 24: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

IA Project Process

InstructResearch Design

HowWhy What

Page 25: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

Research Design Instruct

Demonstrate Define Decide

IA Project Process

Page 26: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

IA Project Process

DemonstrateDefine Decide

Then What?

Page 27: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

IA Project Process

DefineResearch

DecideDesign

DemonstrateInstruct

Client •Business Goals•Business Brief

Organization Labels/Terms

Requirements

Users/Audience•User Needs•Persona

StructureMaps

Specifications

Content •Audit Analysis•Strategy

ActionsFlows

InteractionsPrototypes

Discovery Why

DesignWhat

DevelopmentHow

Page 28: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

Questions?

Page 29: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

Does it always have to be this way?

• It depends…

Page 30: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

How long does it take?

• It depends…

Page 31: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

Where does it really start

• Scope• Budget• Timeline

Page 32: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

DefineResearch

DecideDesign

DemonstrateInstruct

IA Project Process

Discovery Why

PlanWhat

Presentation How

Where will you be working?

Page 33: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

Extras: Match the ToolWhat is this deliverable?What can you use to make it?

IA Institute http://iainstitute.org/tools/

Konigihttp://konigi.com/tools/overview

Rapid Prototypeshttp://adaptivepath.com/ideas/rapid-prototyping-tools

User Experience Deliverables http://semanticstudios.com/publications/semantics/000228.php

Page 34: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

Examples of Why

Stories. A good story about a user's experience can help people to see the problem (or opportunity), motivate people to take action, and stick in people's memories long after we're gone.

Peter Morville “User Experience Deliverables” Semantic Studios http://semanticstudios.com/publications/semantics/000228.php

Personas. Portraits and profiles of user types (and their goals and behaviors) remind us all that "you are not the user" and serve as an invaluable compass for design and development.

Page 35: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

Examples of What

Concept Maps. In the territory of concepts, a good map can help us see where we are and decide what to do by establishing landmarks, clarifying relationships, and identifying true north.

Peter Morville “User Experience Deliverables” Semantic Studios http://semanticstudios.com/publications/semantics/000228.php

System Maps. A visual representation of objects and relationships within a system can aid understanding and finding for both stakeholders and users. Shift gears from "as-is" to "to-be" and you have a blueprint for structural redesign.

Page 36: Information Architecture: Intro to the Job, Lecture Day 2

The Information School University of Washington

Content Strategy

Examples of How

Specifications. An explicit set of requirements describing the behavior or function of a system is often a necessary element in the transition from design to development.

Peter Morville “User Experience Deliverables” Semantic Studios http://semanticstudios.com/publications/semantics/000228.php

Prototypes. From paper prototypes to pre-alpha software and hardware, working models drive rapid iteration and emotional engagement by showing how a product will look and feel.