93
DESIGNING INTERFACE

Designing The Interface For Use

  • View
    1.675

  • Download
    4

Embed Size (px)

DESCRIPTION

From the recent class "Fundamentals of User Experience" given 12/13/2013 in NYC

Citation preview

Page 1: Designing The Interface For Use

DESIGNING INTERFACE

Page 2: Designing The Interface For Use

2

“Like putting an Armani suit on Attila the Hun, interface design only tells how to dress up an existing behavior.” – Alan Cooper

Page 3: Designing The Interface For Use

TRANSFORM YOUR FLOWSMaking pages out of boxes and arrows

Page 4: Designing The Interface For Use

A task analysis

From Information Architecture: Blueprints for the Web, this is a task analysis for a website for Sundance film festival, featuring a schedule

planner

Page 5: Designing The Interface For Use

Each task could have a page

Page 6: Designing The Interface For Use

First Yahoo 1994

1995: first graphic logo

Remind you of something?

Page 7: Designing The Interface For Use

Including the schedule creator tool…

Page 8: Designing The Interface For Use

Wizards: Many boxes,many pages

Page 9: Designing The Interface For Use

Use Wizards:

‣ When users want to accomplish a goal that has many steps. Wizards are good at making sure you don’t miss a step.

‣ When the steps must be completed in order. Wizards are linear, so it’s impossible to complete them any other way.

‣ When the task is seldom performed. Wizards can seem slow and plodding, so they are best used in tasks you do only once in a while, like setting up a printer.

‣ The audience is not technically savvy and is likely to be confused by a page with a lot of choices on it. A Web site can have novice users, and a wizard makes complex tasks seem easy.

‣ Bandwidth is low and downloading a single big page could take forever, or the tasks require several server calls, which would also slow the page’s load.

‣ The task has several steps in it, performed only once a visit, such as checkout.

Page 10: Designing The Interface For Use

DESIGN A WIZARDTask:

WHAT SHOULD BE A WIZARDDiscuss:

Page 11: Designing The Interface For Use

You can group tasks together

Page 12: Designing The Interface For Use

Control Panel

Page 13: Designing The Interface For Use

You see them on software in preferences, set occasionally, by experts

Page 14: Designing The Interface For Use

On the web, they are often account settings

Page 15: Designing The Interface For Use

DESIGN A CONTROL PANELTask

WHAT SHOULD BE A CONTROL PANELDiscuss

Page 16: Designing The Interface For Use

TOOLBARSBring the settings and the thing modified together

Page 17: Designing The Interface For Use

What if we put the tasks with the thing they were modifying?

Page 18: Designing The Interface For Use

It’s a toolbar

Tools here Item affected here

Page 19: Designing The Interface For Use

Toolbars

Tools here Item affected here

And here

And here

Photoshop: toolbars on steroids

Page 20: Designing The Interface For Use

The web uses toolbars more sparingly

Page 21: Designing The Interface For Use

ToolbarsTools here

Item affected here

A simpler design is better for

infrequent use.

Page 22: Designing The Interface For Use

GROUP LIKE ITEMSLocation, palette

Page 23: Designing The Interface For Use

23

DRAW A PLACE SETTING – 30 SECONDS

Fork, spoon, knife

Page 24: Designing The Interface For Use

An Interface is like a table setting, the tools you need are next to the food you eat. Content is the meal.

Page 25: Designing The Interface For Use

Two videos sites.The “meal” is the video, and the tools to consume (or play with) it

are arrayed around the main meal.

(P.S. There are toolbars too)

Page 26: Designing The Interface For Use

Why is the response so far from the invitation?

Page 27: Designing The Interface For Use

27

ARTICLE OF CLOTHING:WHAT TOOLS WHERE?

Task

Page 28: Designing The Interface For Use

ZONE YOUR PAGE

Page 29: Designing The Interface For Use

When designing the page, group items by similarity and similarity of task (navigation items together, editing items together)

Give them visual importance based on user number, usage frequency and importance to business.

Page 30: Designing The Interface For Use

‣ Create “zones” for functionality groups.

‣ You can group them by putting white space around them, or use lines

‣ Remember to keep tools close to the thing your working on

Page 31: Designing The Interface For Use

Zone this page

Page 32: Designing The Interface For Use

ZONE YOUR HOMEPAGE

Page 33: Designing The Interface For Use

HOW TO MAKE A WIREFRAME IN 30 SECONDS

Page 34: Designing The Interface For Use

Draw a rectangle

Page 35: Designing The Interface For Use

Add global elements

Page 36: Designing The Interface For Use

‣ Next, add the key zones

‣ Start with a list of elements, perhaps written on post its. Group them, then find them homes on your page.

‣ The fill in the actual elements

Page 37: Designing The Interface For Use

FINALLY, ANNOTATE

Page 38: Designing The Interface For Use

Consider

‣ Where does the content come from? If you have a list of related articles, specify how they’re related. Are they the most viewed? Most viewed from that section?

‣ What is the nature of the content? Does it vary greatly in length, size, language, and type?

‣ Is the element required or optional? What happens if the element doesn’t appear on that page? Does the layout change?

‣ Is the element conditional? Does it vary based on other factors? For example, do administrators see additional links? What happens if an article doesn’t have an associated image? What if it does?

‣ What’s the default or expected state? Ideally, what’s supposed to happen on the page.

‣ What are the alternate or error states? How does the design change when things don’t go right?

Page 39: Designing The Interface For Use

INTERFACE INGREDIENTSWhat goes in your wireframes?

Page 40: Designing The Interface For Use

40

HEADER

Page 41: Designing The Interface For Use

41

TODAY’S CLASS

CORE PRINCIPLES & CONSIDERATIONS

Page 42: Designing The Interface For Use

42

THE LANGUAGE OF INTERFACE

LayoutObjectsTypeColorLineHierarchyRelationships

INTERACTIVE (DOING)Affordances HUDFeedbackModesInputNavigation

GRAPHICAL (UNDERSTANDING)

Page 43: Designing The Interface For Use

43

INTERACTIVE INTERFACE DESIGN

DOING

Page 44: Designing The Interface For Use

44

THE LANGUAGE OF INTERFACE

AFFORDANCES

Page 45: Designing The Interface For Use

45

THE LANGUAGE OF INTERFACE

BUTTONS LOOK PUSHABLE

Page 46: Designing The Interface For Use

46

THE LANGUAGE OF INTERFACE

BUTTONS WITH MEANING

Page 47: Designing The Interface For Use

47

THE LANGUAGE OF INTERFACE

LINKS LOOK

CLICKABLE

Page 48: Designing The Interface For Use

48

THE LANGUAGE OF INTERFACE

LINKS HAVE HIERARCHY

Page 49: Designing The Interface For Use

49

ON SUBTLETY

When you don’t want to interrupt an action, be subtle (think of footnotes). If they are reading, don’t bother them.

When you need to prompt an action, subtlety will send you to the poor house.Tell your users what to do. Clarity is relaxing, not annoying.

Page 50: Designing The Interface For Use

50

A QUICK BUTTON COMPETITIVE

ANALYSIS / CRITIQUE

GO TO 3-4 WEBSITES AND FIND 2 BUTTON / LINK INTERACTIONS YOU REALLY LIKE. 2 THAT YOU DISLIKE.

Page 51: Designing The Interface For Use

51

HEADS UP DISPLAY

Heads Up Display:

Information user needs

nearby to be effective

Page 52: Designing The Interface For Use

52

HEADS UP DISPLAY

AN EMAIL HUD

All HUD, no content

Page 53: Designing The Interface For Use

53

HEADS UP DISPLAY

A SOCIAL

HUD

Page 54: Designing The Interface For Use

54

FEEDBACK

Page 55: Designing The Interface For Use

55

USER FEEDBACK

Page 56: Designing The Interface For Use

56

INPUT

Page 57: Designing The Interface For Use

57

FORM PRINCIPLES

FORM PRINCIPLES

Consider ContextSet expectationsUse appropriate inputsGive sift and clear feedbackAsk for lessAB test

Page 58: Designing The Interface For Use

58

FORM PRINCIPLES

Page 59: Designing The Interface For Use

59

ACTIVITY: DESIGN YOUR SIGNUP FORM

15 MIN.

1. Individually design a sign-up form for your project.

2. Think about the following element:

1. Name (first/last?)

2. Username/nickname?

3. Password (enter twice?)

4. Terms of Service (link/display?)

5. Sign up with Facebook/Twitter?

6. Optional demographics?

7. Over 13?

STRUCTURE OBJECTIVES

INDIVIDUALLY

Page 60: Designing The Interface For Use

NAVIGATION

Page 61: Designing The Interface For Use

61

Navigation: IA made visible“Like putting an Armani suit on Attila the Hun, interface design only tells how to dress up an existing behavior.” – Alan Cooper

Page 62: Designing The Interface For Use

62

Most IA is invisible

A lot of work no one sees‣Synonym rings‣Controlled vocabulary

If it was seen, it would be too much to understandWe show only a part via navigation

Page 63: Designing The Interface For Use

63

The magic number?13 tabs– no one saw them. Six tabs, everyone saw them

Page 64: Designing The Interface For Use

64

But not everything is simple

masthead

Global links

Folders

Mail tools

ad

Other properties

upsell

Web search

Related Services

tip

inbox

ads

ad

Related Services

upsell

Mail toolsLog out

inbox Write mailAnd there isn’t even content!

Page 65: Designing The Interface For Use

65

Navigation orders complex pages

Page 66: Designing The Interface For Use

66

Understanding NavigationMessage and Access

Where Am I?

Wh

at's N

ea

rby?

What's RelatedTo What's Here?

Global Navigation

Lo

ca

l N

avig

atio

n

Content Lives Here,With ContextualNavigation Inline

Or Separate.

Page 67: Designing The Interface For Use

67

Global navigationWhere you are‣Brand/masthead

Where you can go (site offering)‣Top level categories

Safety nets‣Where’s my (shopping cart/account/help???)

Page 68: Designing The Interface For Use

68

Global Navigation ‘03 vs ‘12

Page 69: Designing The Interface For Use

69

Global navigation, Blogs

Page 70: Designing The Interface For Use

70

Global navigation ‘03 vs ‘12

Page 71: Designing The Interface For Use

71Local Navigation

I’ve started down the path…Now what?‣What are the categories of items?‣What are the siblings of what I see?‣What are the subcategories?

Page 72: Designing The Interface For Use

72Local Navigation 2003

Page 73: Designing The Interface For Use

Secondary navigation is now temporal

Page 74: Designing The Interface For Use

74

Local Navigation

Page 75: Designing The Interface For Use

75Contextual navigation

Inline linksRelated itemsDocument management

Page 76: Designing The Interface For Use

76Inline links

Page 77: Designing The Interface For Use

77Related items

Page 78: Designing The Interface For Use

78Pagination

Useful to reduce page download speed and cognitive overload.

Annoying for printing.

Impossible to predict what you’ll get

Users would rather scroll than click

Page 79: Designing The Interface For Use

79Ad negotiation

Page 80: Designing The Interface For Use

80

Print/email/share

Page 81: Designing The Interface For Use

81

Facets as filters

Page 82: Designing The Interface For Use

82Sort

Page 84: Designing The Interface For Use

84

Have you ever seen this page?

Page 85: Designing The Interface For Use

85

How about this one?

Page 86: Designing The Interface For Use

86

How about this one?

Page 87: Designing The Interface For Use

87

You can make it helpful

“After testing several different sitemap designs on users, I decided to try putting one on every page of my small Columbian web site. I then decided to track how often it was used for navigation. It turns out the sitemap is used for over 65% of all navigation done on the site.” -- Usability Report by Peter Van Dijck of poorbuthappy.com (Guide to Columbia)http://www.webword.com/reports/sitemap.html

Page 88: Designing The Interface For Use

88

Conventions

It is certainly probable, then, that placing these objects in expected locations would give an e-commerce site a competitive edge over those that do not…

-- Examining User Expectations for the Location

of Common E-Commerce Web Objects

Usability News

4.1 2002

Page 89: Designing The Interface For Use

89

ConventionsIf 90% or more of the big sites do things in a single way, then this is the de-facto standard and you have to comply. Only deviate from a design standard if your alternative design has at least 100% higher measured usability.

If 60-90% of the big sites do things in a single way, then this is a strong convention and you should comply unless your alternative design has at least 50% higher measured usability.

If less than 60% of the big sites do things in a single way, then there are no dominant conventions yet and you are free to design in an alternative way.

-- Jakob Nielsen, November 14, 1999 Alertbox column

"Identifying De-Facto Standards for E-Commerce Web Sites“ © 2003 Heidi P. Adkisson

Page 90: Designing The Interface For Use

90

Conventions

Some things are becoming de rigorDeviate when you’ve got something betterNot because you are bored

"Identifying De-Facto Standards for E-Commerce Web Sites“ © 2003 Heidi P. Adkisson

Page 91: Designing The Interface For Use

91Now combine

Follow expectations based on conventionsDesign a hierarchy based on task importanceErr on the side of simplicity

Page 92: Designing The Interface For Use

EXERCISE: COMPETITIVE ANALYSIS OF NAVIGATION

Page 93: Designing The Interface For Use

93

Q&AHEADER