INDE/TC 455:User Interface Design

Module 8.1 – Design Tools &Guidelines: Thinking Hats

Interface Design Tools• Human factors engineering (IE 351)• Systems engineering principles• 10 step design sequence• Thinking hats• Furness 10 Commandments• Subject panel• Survey/questionnaire tools

Tools for Creative Thinking

Thinking Hats for CreativeProblem Solving

Thinking Hats (ref: De Bono)-- neutral, data gathering

-- idea generation, design synthesis, nojudgment

-- logical positive, reasons why it will work

-- logical negative, reasons why it won’twork

-- gut feeling, no judgment

-- process control (which hat to use when)

White Hat

Green Hat

Yellow Hat

Black Hat

Red Hat

Blue Hat

Creative thinking resources• Creativity web:

– http://members.ozemail.com.au/~caveman/Creative/index2.html

• Techniques for creative thinking– http://members.ozemail.com.au/~caveman/Crea

tive/Techniques/• Brainstorming

– www.brainstorming.co.uk• Creativity rules of thumb (course website)• Creativity killers (course website)

Selected Creativity Rules ofThumb

1. The best way to get great ideas is to get lots ofideas and throw the bad ones away.

2. Always look for a second right answer.3. If at first you don’t succeed…take a break!4. Write down your ideas before you forget them!5. If everyone says you’re wrong, you’re one step

ahead. If everyone laughs at you, you’re two stepsahead.

6. Never solve a problem from its original perspective.

Some ‘out of the box’thinking

For the multitasking male

A ‘Thinking Hats’ designproblem

Thinking Hats problem

• Design the interface for a‘transporter’

Thinking hats assignment• Solve problem in your teams (hand in with

prospectus)• Use all thinking hats• List process

– White hat– Green hat– Yellow hat– Black hat– Red hat– Blue hat

• How did you converge on a conclusion• Make recommendations• 2-4 pages

Thinking hat assignment• Solve problem in your groups• Use all thinking hats• List process

– White hat– Green hat– Yellow hat– Black hat– Red hat– Blue hat

• How did you converge on a conclusion• Make recommendations• 2-4 pages• Due Friday Lab 2

Feedback on thinking hats

• Thinking hats– No perfect information– Make a decision (red hat not final!)– Each green hat idea should have a black hat and

yellow hat analysis– Use blue hat to control process– Need to properly label tables & drawings in

text

Applying the Thinking Hatsto the Systems engineering

design process

User interface implications ofcreative design

Systems Engrg. Design #1Problem Characterization

• What is it supposed to do? (Concept definition)• For whom is it supposed to do it?

• In what environment is it supposed to work?

• How well is is supposed to do it? (features & performancerequirements)

Systems Engrg. Design #2Problem Characterization• How will I measure it? (metrics)• What are my assumptions?

– About the user– About the task– About the environment

• What are my constraints?– Development schedule– Development resources (money, people, tools)– End cost of interface

Systems Engrg. Design #3Problem Solution• What are my design alternatives?• What is the best alternative?• Make it better!• Build it!• Test it!• Redesign it!• Repeat entire process.• Document (build audit track)

Applying thinking hats touser interface design

Project sequencePhase Activity Thinking Hat

0 Project Assignment white

1 Project Prospectus white

2 Problem Characterization white

3A Persona Generation White/green

3B Scenario Generation White/green

4 Task Analysis, Maps, Screen Designs Green/black/yellow/red

5A Interface Representation: Flipbook or

simulations

Green/black/yellow/red

6A Interface Evaluation: Field Trial - 1 White

5B Interface Representation: Prototypes Green/black/yellow/red

6B Interface Evaluation: Field Trial - 2 white

7 Final Interface Configuration Green/black/yellow/red

8 Class Presentation White/green

9 Final Report white