+ All Categories
Home > Technology > Up a Tree

Up a Tree

Date post: 27-Jan-2015
Category:
Upload: optimal-experience
View: 116 times
Download: 4 times
Share this document with a friend
Description:
At UXNZ in Wellington November 2013, Dave O'Brien spoke about tree testing.
Popular Tags:
75
Up a Tree Dave O’Brien Nov 2013 Using tree tests to evaluate your IA
Transcript
Page 1: Up a Tree

Up a Tree

Dave O’Brien Nov 2013

Using tree tests to evaluate your IA

Page 2: Up a Tree

Easy to find

UXD easy to use

IA easy to find

Page 3: Up a Tree

Bad navigation

Page 5: Up a Tree

Bigger = harder

“Getting to the right page within a website or intranet is the inevitable prerequisite to getting anything done.”

- Jakob Nielsen

Page 6: Up a Tree

How do we make it easier to find stuff?

How do we

make it easier

to find stuff?

Page 7: Up a Tree

We research our target users

Page 8: Up a Tree

We design up a bunch of ideas

• French

• Italian

• German

• Japanese

– Sushi

– Teppanyaki

– Yakitori

• Chinese

• Breakfast

– Hot

– Cold

• Lunch

• Dinner

• Snacks

• Beef

• Poultry

– Chicken

– Turkey

– Duck

• Pork

• Vegetarian

Recipes

Page 9: Up a Tree

We test our ideas to find out which work best

Page 10: Up a Tree

Revise and re-test…

Page 11: Up a Tree

…until we get something that works really well

Page 12: Up a Tree

Test early

Test early

Page 13: Up a Tree

Today we’re going to look at tree testing

Page 14: Up a Tree

Doing a real tree test

Volunteer?

Page 15: Up a Tree

So, what did we just see?

Page 16: Up a Tree

Just like a real site

Like a

real

site…

Page 17: Up a Tree

But not really

…but not

really

Page 18: Up a Tree

So why test this way?

So, why test this way?

Page 19: Up a Tree

Quick to set up

Page 20: Up a Tree

It isolates two basic elements

Page 21: Up a Tree

It makes analysis easy

Page 22: Up a Tree

Don’t need to design a website first

Page 23: Up a Tree

Just a spreadsheet

Page 24: Up a Tree

What do we find out?

What do we find out?

Page 25: Up a Tree

What we look for

Did they succeed?

Did they backtrack?

How fast did they click?

Which sections need work?

Page 26: Up a Tree

Some data, please!

Page 27: Up a Tree

At a glance

Page 28: Up a Tree

Low-scoring task

Page 29: Up a Tree

Low-scoring pie tree

Page 30: Up a Tree

High-scoring task

Page 31: Up a Tree

High-scoring pie tree

Page 32: Up a Tree

It’s not about the tool

Are there other ways to test this?

Page 33: Up a Tree

Closed card sorting

Page 34: Up a Tree

Card-based classification evaluation

Your 9-year-old son asks

for a new belt with a

cowboy buckle

Page 35: Up a Tree

Other ways to test trees

Page 36: Up a Tree

Best bang for the buck

Online TT tools = quick and easy

Fast to get up and running

Easy for participants, on their own time

The analytical gruntwork is mostly done for you

Choice of commercial tools…

Page 37: Up a Tree

C-Inspector (Steffen Schilb)

Page 38: Up a Tree

UserZoom (tree-testing module)

Page 39: Up a Tree

Treejack (Optimal Workshop)

Page 40: Up a Tree

It’s not about the tool

It’s not about the bike tool

Page 41: Up a Tree

Lessons learned

Some lessons we’ve learned

Page 42: Up a Tree

When to test

When to run

a tree test?

Page 43: Up a Tree

Phases in design process Research

Open card sorts

Baseline tree test

Design

Test tree 1, 2

Revise, retest

Testing

Usability test

Page 44: Up a Tree

Test against an existing tree

Test

new vs. old

Page 45: Up a Tree

ACC old tree

30%

Page 46: Up a Tree

ACC new tree

67%

Page 47: Up a Tree

test alternative trees

Test

new vs. new

Page 48: Up a Tree

recipes

• French

• Italian

• German

• Japanese

– Sushi

– Teppanyaki

– Yakitori

• Chinese

• Breakfast

– Hot

– Cold

• Lunch

• Dinner

• Snacks

• Beef

• Poultry

– Chicken

– Turkey

– Duck

• Pork

• Vegetarian

Recipes

Page 49: Up a Tree

DIA example

Page 50: Up a Tree

test iteratively

Lather, rinse, repeat

Page 51: Up a Tree

Typical test schedule (design phase)

Week 1

Create tree 1

Create tree 2

Week 2

Run test 1

Run test 2

Week 3

Analyse results

Revise best tree

Week 4

Run revised test

Analyse results

Round 1

Round 2

Page 52: Up a Tree

Revising the best tree

+ =

Page 53: Up a Tree

Different tasks for different groups

Different strokes tasks

for different folks

Page 54: Up a Tree

Shimano example

Page 55: Up a Tree

How many?

How many?

50 Users/group

10 tasks/user

Page 56: Up a Tree

Analysis – what should you be looking for?

What should we look for?

Page 57: Up a Tree

Low success scores

Page 58: Up a Tree

Where did they go?

Page 59: Up a Tree

Lots of backtracking

Page 60: Up a Tree

Evil attractors

Page 61: Up a Tree

Current limitations of the method

All sunshine and lollipops?

Page 62: Up a Tree

Only works with traditional tree structures

Page 63: Up a Tree

WebMD

Page 64: Up a Tree

Only tests certain factors

Organisation

Labeling

Navigation (e.g. menus, see-also links)

Content (e.g. supporting text)

Visual design

• Good and bad

Page 65: Up a Tree

How good are your tasks?

Too many tasks

Badly worded tasks

Page 66: Up a Tree

Don’t give away the answer!

“You need to get reimbursed for expenses. Find the form.”

•Library

•Expenses/Reimbursements •Rules for claiming expenses

•Expense forms

•Who to contact

•Travel

Page 67: Up a Tree

No perfect tool (yet)

Page 68: Up a Tree

Not a replacement for usability testing

Page 69: Up a Tree

What next?

What next?

Page 70: Up a Tree

Better visualisation of results

Page 71: Up a Tree

Testing navigation too

Page 72: Up a Tree

Summary

Tree testing = organisation and labeling

Gives you a rough answer, very early

Brings some objective data to the discussion

Reveals IA problems to u-test later

One more tool for your UX toolkit

Page 74: Up a Tree

Let’s talk IA!

Dave O’Brien

[email protected]

Page 75: Up a Tree

Make like a tree…and leave


Recommended