Skip to main content

The UX of Windows 8

Jensen Harris, the Director of Program Management for the Windows User Experience Team, gave a really compelling talk where he explained the work his team had done in crafting the UX for Windows 8. They knew they needed to shake things up and re-imagine some concepts that had become stale. They threw out the Start menu and built a cool new tiled interface.

He talked about how important it was to sweat the small stuff. For example, he talked about the herculean effort it was to eliminate a little blue flash in the boot sequence the first time you power on a device straight from the manufacturer. His point was that the seemingly small stuff REALLY matters when we're creating an experience for a user. A little bit of sand in my hamburger is going to spoil the whole experience. 

I had to compare my own experience as a user of Windows 8 with the description I was hearing from Harris. I thought it still had a lot of rough edges and it was an uncomfortable melding of two paradigms that made it uncomfortable for the user who wasn't always sure which paradigm was in operation. My frustration was pretty well captured by Brian Madden in a post today

And then there's that whole problem of having the Tile interface mode and the desktop mode which are side-by-side and not at all related. It's like two OS virtual machines side-by-side. How are regular users supposed to understand what the [heck] is going on? Even worse is that Internet Explorer exists in both modes, yet the two versions are different. They don't even share bookmarks! So I can use Tile mode IE which is all nice and touchy, then maybe I want to use Word. I click on the Word tile and I'm flipped over to desktop mode to run Word. Now I want to go back to IE. Hey cool! There's an icon for IE on the bottom of the screen in the desktop mode taskbar. I click IE and it launched, but it's "different" IE. The menus are different and the URL bar is on the top. And I have no bookmarks. And my tabs aren't open anymore. WTF? 
Sure, as a geek I understand that I'm now running desktop IE and not Touch IE, but how's a regular user supposed to know that? I set this thing down while running Word and came back later. I hit the power button to wake it up, logged in, and clicked the IE icon on the bar. Was I supposed to remember "Oh yeah last time I used this I was in desktop mode, so I have to remember that this IE is not the one I want. I have to switch back to Tile mode then launch IE." 
Seriously people?

As I embark on my own journey's to craft great user experiences, I want to learn from Harris' failure with Windows 8. It isn't enough to sweat the small stuff if the big stuff has serious problems. 

Comments

Popular posts from this blog

Hammers and Nails: Technology Push Design

"We need to refine our requirements first, before we look at tools." This is a common phrase that I hear. While I sympathize with the sentiment, I think it is frequently wasteful. I suspect that we'd get to the right requirements faster by looking at tools already available in a given problem space. Pushing the concept further, is it foolish to find a cool technology and then look for ways that that technology can apply to current problem spaces?  What if you don't even recognize you have a problem space? Without a constant search and openness, we'll miss many serendipitous opportunities. Here is BYU professor Larry Howell discussing this issue. I often enjoy doing something ... that is sometimes controversial. In this approach, rather than starting with a need, you start with a new technology and you search to identify a need that it can fulfill. This second more controversial approach is called "technology push design."   You can imagine t

The "True Cost" Phantom in Project Cost Tracking

I want to know if I should wear a coat when I go out the door on an unpredictable spring morning. The temperature from the weather app on my phone isn't going to match exactly the temperature just outside my front door, but it will be close enough to make the decision. If the question at hand is whether or not I should wear a coat, it would be a costly mistake to set up an elaborate system of thermometers around my property to try increase the precision of my measurement of the temperature. The added expense wouldn't yield any better decisions about whether to wear a coat, so why bother? We are interested in tracking the relative costs of the various projects we undertake in our organization. We must admit up front that we will never be able to measure the precise cost of each of our projects. Consider the following things you could include in the "true cost" measurement of a project. Where will you draw the line? An engineer reads an article on the bus that give

Process Ain't a Post-It

Some ITIL advocates insist that having a good process is separate from having a good tool. "If the process is right, you can do it on a post-it note. Putting it in the tool will speed things up, but it won't fundamentally change the nature of the process." This is rubbish. It may be true for small scale processes, but technology automation can open up new process possibilities that just wouldn't be possible without a technology assist. I think that we should plan our processes with a tool in mind that can accomplish the task. Think of a Service Catalog that gives an executive insight into the costs of the things he orders. He can dynamically scale up or down his order or services to meet his projected needs. He can tweak variables and make decisions because of the power of the tool. It gives him a visualization that simply wouldn't be available in a paper-based process. The NewScale demonstration (a prominent Service Catalog provider) really drove this point