Â
Jensen Harris lives at http://blogs.msdn.com/jensenh/
Â
The story of the Office
Â
Conventional wisdom said that the Office is good enough.
Asking real people told different story, which was that the user interface was failing users.
Â
Symptoms they noticed:
They added new features, but hardly anyone found them
Office was supposed to be done, and that everyone though that it’s not going to change
Â
How did they get to the first office?
Â
The first version – Word 1.0 (1989) -Two toolbars, quite simple.
Word 2.0 – 640×480 (1992), Number of toolbars: 2
Word 6.0 – 800×600 (1994) – Toolbars: 8
Word 95 – 800×600 (1995) – Toolbars: 9 (defined red-squiggle spell checking)
Word 97 – 1024×765 (1996) – Toolbars: 18 (added clippy); people used to describe it as bloat
Word 2000 – 1024×765 (1999) – Toolbars: 23 (reducing the perception of bloat)
– IntelliMenu; the menus are too long, we can shorten them. But instead of shorting them we can just hide the things in the menu. But to make it extra tricky to the user, we’re intertwine the showed and hidden. On top of that, the computer learns how to arrange the visible/invisible menu.
 – Rafting; all the menu items that wouldn’t fit, fell of the screen
– It proved out to not work really well
Word 2002 – 1024×768 (2001) – Toolbars: 30
– Created the Task pane (the right column). Since anyone couldn’t find anything in the menu, they added the things into right column.
Word 2003 – 1024×768 (2003) – Toolbars: 31
Â
Word 1 – 50 menu items to 300 in the end.
Â
Menus and toolbars we designed for less full-featured programs. The feature set of Office had grown and stretched the existing UI to full limits.
Â
A new UI was needed .. To reawaken the soul of software
Â
The Design process of Office 2007
Â
Part 1: The Art part – Research
Â
People have an emotional relationship with their computer.
They learned from “real peopleâ€. Video, visiting, interviews etch.
Â
The fish – Framework for understanding the different kinds of feelings that people had at the overall using the office.
Â
When people are frustrated, why are they frustrated. Which of the factors are important and which less.
Â
Revelation: The sense of mastery of our software was gone
Â
We don’t know just what the software is capable of, but we actually understand how to go around it.
Â
Science: The Role of Data
Over 3 billion (anonymous) data sessions collected from Office users
Every month, tracked 150 million command button clicks in Word
Tracked nearly 6000 individual data points
We couldn’t have done this without the data
Â
The data doesn’t lie
Â
Part 2: Design tenets
Â
Design tenets – a set of principles that your team believes in, and it allows your team to have a shared goal.
Igor Stravinsky – [I feel] a sort of terror when, finding myself before the infinitude of possibilities that present themselves, I have the feeling that everything is permissible…Â
…If nothing offers me any resistance, then any effort is inconceivable, and consequently every undertaking becomes futile.â€
[Showing Office 2007 UI Design Tenets]
Â
Design tenets have to be religion
Â
Part 3: Prototypes
Created hundreds of discrete prototypes
Â
Conceptual prototypes
Designed to explore a few key concepts deeply (as opposed to broadly)
Â
Â
Part 4: Evaluation Is it Good or not
Â
Standard Usability Tests – give you a good sense of what someone’s first 30-90 minutes turn out. But it’s different from the other users.
Longitudinal Usability Tests – Weeks or months of observing users. Singular most usable usability testing tool.
Â
Eye Tracking – “special monitor that watches youâ€. It turns out that users mouse is in a totally different spot that what the user looks at. Heat map and screen gazing.
Â
From initial design to final product – ITERATION
Â
Iteration Built Into the Product Cycle – Planning to iterate. From product schedule to changes in code that allowed late prototype
Â
Happy ending
Â
The attention to Design Pays Off. Lots of awards and people buying the software at 2x the size of the earlier versions.
Â
Â
So that's what rafting is for! Thanks!