Microsoft.com Usability broken.

29
What you gonna talk about Scott? A grab bag of ideas on evaluating design & principles that govern them.

description

This is a deck i would often use highlighting the mess of website irrelevance I call today, Microsoft.com and its associate sites.There is way to much noise and not enough signal and the deck hopefully highlights one slice of this reasoning.

Transcript of Microsoft.com Usability broken.

Page 1: Microsoft.com Usability broken.

What you gonna talk about Scott?

A grab bag of ideas on evaluating design & principles that govern them.

Page 2: Microsoft.com Usability broken.

UI?User Interface?

Page 3: Microsoft.com Usability broken.

What is a good user interface?A good user interface design encourages an easy, natural, and engaging interaction between user and a system, and it allows users to carry out their required tasks.

Page 4: Microsoft.com Usability broken.

What is UsabilityUsability can be defined as “the extend to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context”

Page 5: Microsoft.com Usability broken.

What is ContextThe setting in which an item of information appears

Page 6: Microsoft.com Usability broken.

Chapter 1

THE WHY…Why do we bother with design?

Page 7: Microsoft.com Usability broken.

HUMANS

You know they are bloody annoying

Page 8: Microsoft.com Usability broken.

Mental Models.We humans have models of ourselves, others, the environment and the things with which we interact. Humans form mental models through experience, training and instruction

Page 9: Microsoft.com Usability broken.

HabitualAny change scares most humans. Humans are by nature habitual creatures.. we all have our daily rituals that when disturbed can really upset us

Page 10: Microsoft.com Usability broken.

EmotionalEmotion plays a role with UI today. A poorly designed solution can increase stress levels of employees which can actually be linked to sick days and/or under performance.

Rage Against the machine (Compaq 1999), found that, for one reason or another, stress and frustration levels with workplace technology are rising.

Oct 2002. Research for British Telecom (BT) Home Computing found that 70% of personal computer users suffered from “PC Rage” – that is, the users surveyed admitted to shouting, swearing, or being violent to their computers when problems occurred.

Page 11: Microsoft.com Usability broken.

The story?How design begins…

Page 12: Microsoft.com Usability broken.

Well…we need to rebuild our pipelines a lot, given plans have changed…

Page 13: Microsoft.com Usability broken.

“..That sounds expensive.. Can’t we just upgrade / patch it a bit more?..”

NO!

Page 14: Microsoft.com Usability broken.

It’s not expensive..

We need to stop putting band-aids on broken limbs.

We need long-term vision and synchronization.

Stop gaps aren’t helping the ecosystems roles & skills out…

Page 15: Microsoft.com Usability broken.

Chapter 2

THE WHAT…

Page 16: Microsoft.com Usability broken.

Let’s look at WHAT we own

Let’s work with those WHOown them

Let’s BEGIN..

Where do we start?

Page 17: Microsoft.com Usability broken.

What do all of these have in

common?

They can be quite frustrating to discover and use..

They require unnecessary persistence…They echo the same data at times.. at a rate thatmakes your head spin..

They require you to think in multiple personalities and roles..

they all try and be different, but the end user is usually the same…

Page 18: Microsoft.com Usability broken.

Question:Are these sites serving OUR needs or the

CUSTOMERS?

Page 19: Microsoft.com Usability broken.

Answer:Well..that’s not fair…not all customers are the same!!

e.g. Designers and Developers are different from one another,So therefore the content and approach is likely to always require different tactics.

Page 21: Microsoft.com Usability broken.

Each role or skill we cater for is different, this is true.

Building multiple sites isn’t the answer to solving this. It just makes them more confused and helpless.

However, Contextual Synchronization is a possible answer…

Page 22: Microsoft.com Usability broken.

CONTEXT?(The setting in which an item of information

appears)

Page 23: Microsoft.com Usability broken.

Let’s use Zune as an example of context working..

Page 24: Microsoft.com Usability broken.

You can explore based on taxonomy…

You can browse based on visuals...…

You can explore based on recommendations..

Or.. You can Search…

Page 25: Microsoft.com Usability broken.

Context is when your answer will always come back in a manner that suites your end users needs…

Q: Do you notice how the zune results shows “The Fray” in black, and the rest of the words in gray?

A: It’s always reminding you of the chosen context in which you are searching..

Page 26: Microsoft.com Usability broken.

POINT?We aren’t being contextually sensitive to our online consumers needs. Instead we’re separating context into their own branded existence. The problem is the answer is never obvious, it instead requires HUNTING….

How long do you think it will be

before a new site is added here?

Page 27: Microsoft.com Usability broken.

Question:What’s the difference between an ASP.NET

developer and a Silverlight Developer is?

Page 28: Microsoft.com Usability broken.

Time to play the role of innovator..

Not follower..

Page 29: Microsoft.com Usability broken.