31
Why Dashboard Design should be (but almost never is) based on Cognitive Science Thomas Watkins

Why dashboard design should be (but usually never is) based on cognitive science unconference

Embed Size (px)

DESCRIPTION

UXPA 2013 Annual Conference Friday July 12, 2013 by Thomas Watkins Unconference session

Citation preview

Page 1: Why dashboard design should be (but usually never is) based on cognitive science unconference

Why Dashboard Designshould be (but almost never is)

based on Cognitive Science

Thomas Watkins

Page 2: Why dashboard design should be (but usually never is) based on cognitive science unconference

Catalog Telebriz Partner Internet Direct0

1

2

3

4

5

6

Revenue by Sales ChannelsUS Dollars(millions)

A

B

Page 3: Why dashboard design should be (but usually never is) based on cognitive science unconference

Jan Feb Mar Apr May11

11.512

12.513

13.514

14.515

15.5

Operating Costs

Revenue

Costs vs. RevenueUSD

(millions)A

B

Page 4: Why dashboard design should be (but usually never is) based on cognitive science unconference

South

East

Central

West

$0 $50,000 $100,000 $150,000

Revenue by Region

A

B

Page 5: Why dashboard design should be (but usually never is) based on cognitive science unconference

Problem

• Most dashboards are far less effective than they should be.

• Is it the responsibility of the UX community to fix this?

• It is a difficult problem to solve.– Proper graph construction is not taught in school– Data visualization of business intelligence is an

extremely small niche area, even within UX!– There are usually many organizational and institutional

obstacles to doing things the right way.

Page 6: Why dashboard design should be (but usually never is) based on cognitive science unconference

Why is this important?

• Business intelligence is critical to the operation of virtually all modern institutions

• Visualization is the perhaps best way to process data

• Dashboards are a common tool; that tool is often broken; and it needs to be fixed.

Page 7: Why dashboard design should be (but usually never is) based on cognitive science unconference
Page 8: Why dashboard design should be (but usually never is) based on cognitive science unconference
Page 9: Why dashboard design should be (but usually never is) based on cognitive science unconference
Page 10: Why dashboard design should be (but usually never is) based on cognitive science unconference
Page 11: Why dashboard design should be (but usually never is) based on cognitive science unconference
Page 12: Why dashboard design should be (but usually never is) based on cognitive science unconference

What approach she we take?• Two opposing approaches to making graphs– Thinking like an artist?• Striving to express oneself, using the data

– Thinking like a translator?• Striving to translate the data from one language to

another language– The mathematical language of the data– The language of the human sensory, perceptual and cognitive

systems

Page 13: Why dashboard design should be (but usually never is) based on cognitive science unconference

Ready?

Page 14: Why dashboard design should be (but usually never is) based on cognitive science unconference

Find all the 5’s

987349790275647927137581201618129342095618203948947471039438018732626102856637491928126932872910837426396180293108815029186181893596609384716246940982621211493093847102947582923471928301472837216234682901

987349790275647927137581201618129342095618203948947471039438018732626102856637491928126932872910837426396180293108815029186181893596609384716246940982621211493093847102947582923471928301472837216234682901

Page 15: Why dashboard design should be (but usually never is) based on cognitive science unconference

Ready?

Page 16: Why dashboard design should be (but usually never is) based on cognitive science unconference

red blue orange purple orange blueorange blue green red blue purplegreen red orange blue red green red orange purple orange blue greengreen purple orange blue red orange

Page 17: Why dashboard design should be (but usually never is) based on cognitive science unconference

Ready?

Page 18: Why dashboard design should be (but usually never is) based on cognitive science unconference

red blue orange purple orange blueorange blue green red blue purplegreen red orange blue red green red orange purple orange blue greengreen purple orange blue red orange

Page 19: Why dashboard design should be (but usually never is) based on cognitive science unconference

• Color can help; color can hurt!

Page 20: Why dashboard design should be (but usually never is) based on cognitive science unconference

Ready?

Page 21: Why dashboard design should be (but usually never is) based on cognitive science unconference

A B

Page 22: Why dashboard design should be (but usually never is) based on cognitive science unconference

A B

Page 23: Why dashboard design should be (but usually never is) based on cognitive science unconference

A B

Page 24: Why dashboard design should be (but usually never is) based on cognitive science unconference

Ready?

Page 25: Why dashboard design should be (but usually never is) based on cognitive science unconference

A B

Page 26: Why dashboard design should be (but usually never is) based on cognitive science unconference

Conclusion from the 3 Demonstrations– Color attributes can help performance– Color attributes can hurt performance– Humans are good at judging length, and bad at judging area of

objects– These perceptual phenomena are universal (so why don’t we

use them!)

Page 27: Why dashboard design should be (but usually never is) based on cognitive science unconference

• Know the language of the human sensory, perceptual and visual systems

Page 28: Why dashboard design should be (but usually never is) based on cognitive science unconference

“Language” for Human Quantitative Judgment

Category Attribute Quantitative

Color Hue No

Intensity Yes, but limited

Form 2-D position Yes

Orientation No

Line length Yes

Line width Yes, but limited

Size Yes, but limited

Intensity Yes, but limited

Shape NoMotion Flicker Yes, based on speed but limited

Page 29: Why dashboard design should be (but usually never is) based on cognitive science unconference

What does this mean for us Uxers?

• The UX practitioner community should stay informed on the best practices for data visualization.

• Perhaps we should aim to steer data visualization design efforts in our own organizations

• Perhaps we should also aim to be the thought leaders in this area as the field continues to develop over time.

• Please take the handout sheet (up front), which is a basic guide on how to choose appropriate graphs for effective data visualization.

Page 30: Why dashboard design should be (but usually never is) based on cognitive science unconference

Study list

• Most useful & reputable authors in the field:– Edward Tufte– William Cleveland– Stephen Few

.

Page 31: Why dashboard design should be (but usually never is) based on cognitive science unconference

High visual impact

Low visual impact

Sparse data Rich data