Transcript
Page 1: Introduction to Information Architecture

Class 1: How we will learn

Information Architecture

Instructor: Abby Covert

Page 2: Introduction to Information Architecture
Page 3: Introduction to Information Architecture

The world is complex

3

Page 4: Introduction to Information Architecture

The world is complex

• People face more choices and avenues

3

Page 5: Introduction to Information Architecture

The world is complex

• People face more choices and avenues• Businesses are under more pressure

3

Page 6: Introduction to Information Architecture

The world is complex

• People face more choices and avenues• Businesses are under more pressure • Technology is advanced, but constantly

changing

3

Page 7: Introduction to Information Architecture

The world is complex

• People face more choices and avenues• Businesses are under more pressure • Technology is advanced, but constantly

changing• We are all personally experiencing

information overload

3

Page 8: Introduction to Information Architecture

Information is not found, it is Communicated

4

Data Information Knowledge Wisdom

• Research• Creation• Gathering• Discovery

• Presentation• Organization

• Conversation• Storytelling• Integration

• Contemplation• Evaluation• Interpretation• Retrospection

Slide adapted from Nathan Shedroff’s Diagram “An Overview of Understanding”

Page 9: Introduction to Information Architecture

Communication is about understanding

5

Page 10: Introduction to Information Architecture

How people understand

6Slide adapted from Nathan Shedroff’s Diagram “An Overview of Understanding”

Page 11: Introduction to Information Architecture

How people understand

6

Data

• Contextless• Exhaustive,

not curated• Not meant to

inform the consumer

Slide adapted from Nathan Shedroff’s Diagram “An Overview of Understanding”

Page 12: Introduction to Information Architecture

How people understand

6

Data Information

• Contextless• Exhaustive,

not curated• Not meant to

inform the consumer

• The careful arrangement of data to perform in a context

Slide adapted from Nathan Shedroff’s Diagram “An Overview of Understanding”

Page 13: Introduction to Information Architecture

How people understand

6

Data Information Knowledge

• Contextless• Exhaustive,

not curated• Not meant to

inform the consumer

• The careful arrangement of data to perform in a context

• Gained through experience with the same set of data from a variety of perspectives

Slide adapted from Nathan Shedroff’s Diagram “An Overview of Understanding”

Page 14: Introduction to Information Architecture

How people understand

6

Data Information Knowledge Wisdom

• Contextless• Exhaustive,

not curated• Not meant to

inform the consumer

• The careful arrangement of data to perform in a context

• Gained through experience with the same set of data from a variety of perspectives

• An intimate understanding of patterns and meta patterns enough to allow for novel uses

Slide adapted from Nathan Shedroff’s Diagram “An Overview of Understanding”

Page 15: Introduction to Information Architecture

How people understand

6

Data Information Knowledge Wisdom

• Contextless• Exhaustive,

not curated• Not meant to

inform the consumer

• The careful arrangement of data to perform in a context

• Gained through experience with the same set of data from a variety of perspectives

• An intimate understanding of patterns and meta patterns enough to allow for novel uses

Slide adapted from Nathan Shedroff’s Diagram “An Overview of Understanding”

Page 16: Introduction to Information Architecture

Some (of many) Enemies of Understanding

7

Page 17: Introduction to Information Architecture

Some (of many) Enemies of Understanding

• Familiarity: Being too close to the problem can make you forget to remember what it is like to NOT understand

7

Page 18: Introduction to Information Architecture

Some (of many) Enemies of Understanding

• Familiarity: Being too close to the problem can make you forget to remember what it is like to NOT understand

• Looking good vs. being good: Tricking yourself into thinking something is good because it is good looking

7

Page 19: Introduction to Information Architecture

Some (of many) Enemies of Understanding

• Familiarity: Being too close to the problem can make you forget to remember what it is like to NOT understand

• Looking good vs. being good: Tricking yourself into thinking something is good because it is good looking

• “Uh, Huh”: Not admitting ignorance when faced with it

7

Page 20: Introduction to Information Architecture

Some (of many) Enemies of Understanding

• Familiarity: Being too close to the problem can make you forget to remember what it is like to NOT understand

• Looking good vs. being good: Tricking yourself into thinking something is good because it is good looking

• “Uh, Huh”: Not admitting ignorance when faced with it• Unnecessary Exactitude: Including more detail than is helpful

7

Page 21: Introduction to Information Architecture

Some (of many) Enemies of Understanding

• Familiarity: Being too close to the problem can make you forget to remember what it is like to NOT understand

• Looking good vs. being good: Tricking yourself into thinking something is good because it is good looking

• “Uh, Huh”: Not admitting ignorance when faced with it• Unnecessary Exactitude: Including more detail than is helpful• Rainbow Worship: Believing that more color or colorful flowery

language is always better

7

Page 22: Introduction to Information Architecture

Some (of many) Enemies of Understanding

• Familiarity: Being too close to the problem can make you forget to remember what it is like to NOT understand

• Looking good vs. being good: Tricking yourself into thinking something is good because it is good looking

• “Uh, Huh”: Not admitting ignorance when faced with it• Unnecessary Exactitude: Including more detail than is helpful• Rainbow Worship: Believing that more color or colorful flowery

language is always better• Edifitis: Belief that a better, shinier “such and such” could and will fix

the problem

7

Page 23: Introduction to Information Architecture

Some (of many) Enemies of Understanding

• Familiarity: Being too close to the problem can make you forget to remember what it is like to NOT understand

• Looking good vs. being good: Tricking yourself into thinking something is good because it is good looking

• “Uh, Huh”: Not admitting ignorance when faced with it• Unnecessary Exactitude: Including more detail than is helpful• Rainbow Worship: Believing that more color or colorful flowery

language is always better• Edifitis: Belief that a better, shinier “such and such” could and will fix

the problem• Not asking Why: Simple as that. Always ask why.

7

Page 24: Introduction to Information Architecture

Some (of many) Enemies of Understanding

• Familiarity: Being too close to the problem can make you forget to remember what it is like to NOT understand

• Looking good vs. being good: Tricking yourself into thinking something is good because it is good looking

• “Uh, Huh”: Not admitting ignorance when faced with it• Unnecessary Exactitude: Including more detail than is helpful• Rainbow Worship: Believing that more color or colorful flowery

language is always better• Edifitis: Belief that a better, shinier “such and such” could and will fix

the problem• Not asking Why: Simple as that. Always ask why.• How before What: Thinking to specifically about solutions before the

problem is defined7

Page 25: Introduction to Information Architecture

What HAppens without understanding?

8

Page 26: Introduction to Information Architecture

Spray-n-Pray is common wisdom

9

Page 27: Introduction to Information Architecture

Corporate Underpants start to show

10

Page 28: Introduction to Information Architecture

Shiny, dusty objects accumulate

11

Page 29: Introduction to Information Architecture

Trends win out over needs

12

Page 30: Introduction to Information Architecture

Information Architects to the

rescue...

13

Page 31: Introduction to Information Architecture

14

everything is complex

I intend to because I believe

facilitate understanding organize meaning, create clarity and establish truth

put the what before the how

make the unclear clear

information architect

understanding is always good but it is equally important to not understand

clarity is a prerequisite of truth

I am an

by: Abby Covert & Dan Klyn

architecture frames problems, design solves them

support goals, makers and users

Page 32: Introduction to Information Architecture

15

What Are we doing?

Why we need Change?

Who to Consider?

When Are we Doing what?

How will we do this?

tools I use +questions I help

Answer

Stakeholder Interviews

Goal Setting Workshop

Wireframes and Prototypes

User Research Flow, Maps and RoadmapsScoping WorkshopCollaborative Design Session

Competitive ResearchHeuristic Evaluation

Persona Development

Existing User Research

User Segmentation Workshop Functional SpecificationsContent Inventory

Experience Brief

Touchpoint Mapping Workshop

Page 33: Introduction to Information Architecture

16

Page 34: Introduction to Information Architecture

17

Page 35: Introduction to Information Architecture

18

Page 36: Introduction to Information Architecture

#1 question: What about

Content Strategy and Interaction

Design?

19

Page 37: Introduction to Information Architecture

Information Architecture

20

• Facilitates understanding• Orders meaning• Establishes truth• Creates clarity• Makes pictures of consensus

Page 38: Introduction to Information Architecture

Content Strategy

21

• Determines content requirements• Documents page level info hierarchy• Informs content creation by

establishing content level goals• Shares content level audience insight

Page 39: Introduction to Information Architecture

Interaction Design

22

• Designs the pieces• Refines the flow• Determines the edges and errors• Documents the solutions

Page 40: Introduction to Information Architecture

User Research

23

• Informs Strategy• Tests solutions• Compares performance• Measures success

Page 41: Introduction to Information Architecture

#2 question: Whats this UX

thing?

24

Page 42: Introduction to Information Architecture

User Experience is a result, not a tool

25

How users feel? How users act?

effect you have Your return on investment

Page 43: Introduction to Information Architecture

#3 question: Who does what?

26

Page 44: Introduction to Information Architecture

Most people in this world wear

many hats

27

InformationArchitecture

InteractionDesign

UserResearch

Content Strategy

As a result...

• UX has become a catch all word for people working in these fields

• Job titles tend to be confusing• Outsiders tend to not understand the

difference between these things

Page 45: Introduction to Information Architecture

Questions?

[email protected]@ Abby_The_IA

www.Abbytheia.com

(Slides are on Blackboard)


Top Related