Compete on Usability

making The Switch: My MacBook user experience

I had several good reasons for purchasing a MacBook but, anticipating my new laptop's arrival, I still was nervous about switching.  About a month later, it's been a positive overall experience for me.  I hardly miss my old PC at all.

The positives

Great keyboard and trackpad. The keys are springy and let me type fast. The touch pad responds better than other pointing devices I've used in the past.  It's hard to describe, but a combination of the touch surface and the way it responds to fast and slow motions, somehow make it better.

It sleeps and wakes up intuitively.  I've dealt with multiple laptops and desktops where the sleep or hibernate commands don't work the way you set them in Windows.  It's common for machines to ship straight from the vendor with memory-resident software that messes up power saving.  Not so with this MacBook!  Close the lid and it sleeps immediately.  Open the lid and it comes back on almost instantly.  It doesn't get much simpler than that.

Lots of applications open?  No problem.  Mac OSX is designed to handle multiple open applications without cluttering up the interface.  I find that when the Windows XP Taskbar has more than four or five applications, all the rectangles and ellipsis text look crowded and bug me.  The OSX Dock holds many applications by icon, marking them subtly and without lots of cut-off text.

Quicksilver. Although I like the Dock, I don't use it to launch applications.  On the advice of coworkers, I downloaded the freeware Quicksilver launcher. Quicksilver opens with a key combination, and then typing only a few more letters launches an application.  It has many more functions, but I'm content with the fast, no-pointer-required application launching for now.

The negatives

My slippery, dirty case.  The matte surface of the black MacBook is quite slippery, almost like the inside of a nonstick pan. I've come close to dropping it more than once. Other times, I caught myself holding on so tightly that the case was flexing.  At length, I decided it's only safe to pick it up with two hands.

After a month, my laptop has picked up several noticeable fingerprint marks. Cleaning them safely is not straightforward, because Mac community resources are flatly contradictory on the best way to clean the case.  Is an isopropyl alcohol solution fine, or will it strip off your finish?  Does Apple's iKlear polish work on black MacBooks, or not?  My favorite comment from this post was that the dangerous wood fibers found in paper towels will scar your case like sandpaper. Hmm.

Keyboard layout.  The Command buttons for keyboard shortcuts are crowded close to the spacebar, unlike PCs, which puts the Ctrl button at either edge.  On my Wintel laptop, for keyboard shortcuts, I can easily reach the Ctrl key with my pinky finger and hit a letter key with my index finger. That's not possible with the Command keys on this keyboard layout.

I also miss the PC Delete key (aka "delete forwards").  It's difficult to remember (and reach for) Fn+delete for that.

It's a two (or three) mouse button world.  Come on, Apple. Is there any reason left not to ship your computers with two buttons for the trackpad?  After all, if you plug in a two-button mouse, it will work.  You even sell two button mice. We're years past the point when even diehard Mac fans could argues that Command-Control-Shift-clicking is a good idea.

On my PC the scrollwheel is clickable as a third mouse button, and I use it to open a link in a new Firefox tab. So, I really feel two buttons behind.

The Finder is so missing.  Maybe I'm old-fashioned, but since I know the file system is based on a hierarchy of folders, widgets layered on top of that make it more difficult to orient myself and save things where I want them.

In the Mac OSX Leopard screenshot to the right, there's a little Home row of breadcrumbs that mimics the UI I've seen in iTunes. However, that was turned off by default on my Macbook.

The button to create a new folder is also needlessly buried.  I guess I'll have to learn the keyboard shortcut for that one.

And the final score ...

I very much like the MacBook overall, but for reasons beyond all these pro and cons.  II'll need one more blog post to expound on those reasons.

making The Switch: Upgrade choices

Today was Steve Jobs's annual MacWorld conference keynote, a perfect opportunity to post about my experience with my new MacBook.  Last year I needed to upgrade my old Dell, but I really wasn't interested in "upgrading" to Windows Vista. The irritating security warnings I've read about, with a very poor signal-to-noise ratio, make me believe that Microsoft has lost any empathy for real end users. Still, I was resigned to limp along for as long as possible on Windows XP before grudgingly transitioning.

Instead, a confluence of events convinced me to take the Mac plunge. Reports of the diminished cost difference between PCs and Macs and Apple's growth in market share helped me think different, but not nearly as much as the examples set by my peers. My wife is a teacher, so it's not surprising she's a longtime Mac user. The tipping point came when I started my new job, however. I was impressed to find the most thoughtful engineers preferred not Linux boxes, and certainly not Wintel devices, but Macs.   

In the end, and say what you will about Apple's marketing hype, it's clear they are among the leading companies in the world who have chosen to compete on user experience. I want to support a company whose values are so closely aligned with my own.

So at the beginning of December, for my birthday, I purchased a black MacBook.  (I wanted the sophisticated black shell no matter what, but since my wife already owned a white MacBook, it was practical to get the different color for myself.)  This post is becoming a little long, so I'll follow up soon with my sense of whether the product has fulfilled my expectations.

Next: My MacBook user experience

Tips for presenting screen mockups

I just finished Dan Brown's excellent Communicating Design. It's a very practical cookbook of design documentation: how and when to use ten different types of deliverables. Brown writes from a consulting background, which is different from mine, so it was interesting to contrast it with my methods of working with internal company stakeholders.

When presenting a design to coworkers, I try to remember the following guidelines:

Do outline your specific goals at the beginning.  One mistake I used to make was presenting people with a mockup (whether in a meeting or over email) and simply asking for feedback without context. This laissez-faire approach tends to result in incorrect assumptions and irrelevant feedback.

Instead, introduce the mockup by explaining the rationale behind your design process, and ask for feedback on the specific aspects you need. If the conversation wanders, explain that parts of the visual aren't final enough to be ready for comments.

Don't show people many design alternates, even if you explored them yourself.  As Brown points out, this often brings about the dreaded Franken-design, when the stakeholder says "I like the header component from mockup 1, but the content component from login 2."  Research shows that comparing multiple choices can lead to greater dissatisfaction than if the stakeholder simply had one design to evaluate.

Moreover, stakeholders don't have time to look at your different directions and listen to you ruminate on the inevitable tradeoffs of design. So hang onto all your work, but don't introduce alternates unless they're needed to address a specific point that comes up.

Do tailor the process to individuals. On an internal team, you can learn what's aspects of design are important to each stakeholder and colleague. Ensure that your design addresses likely concerns and requirements and be ready to articulate how it does so.

Don't leave interactivity to a stakeholder's imagination. Web page mockups as a design deliverable are on the way out -- or, at least, they're no longer sufficient.  The nuances of how screen elements respond to users' actions can be critical for your larger team to understand, particularly when you're defining a new behavior not reflected elsewhere in your product.

Low-impact ways to model interactivity include keyframing and annotation.  For higher-fidelity prototyping, you can employ the interactive features of Visio or Powerpoint, or code a prototype using Axure or Flash.

Why I miss my deadlines, often

In my new job, I've been doing a lot of interaction design for a highly capable rich Internet application. It's a great job so far and I'm really enjoying it, except for one thing: I am almost never on time finishing things.

I did a fair amount of project management in my previous jobs, and missing deadlines bothers me.  As a result, I've been feeling pretty stressed lately at work.  Thinking about the problem over the winter holidays, I realized I've been underestimating two important learning curves.

The first is what I need to learn about the system.  After four months, I've learned a great deal about how everything works, but there's still a lot I don't yet understand.  There's no documentation to review -- I have to experiment with the system and talk to developers to get up to speed. Typically, the biggest problems arise from questions I didn't know to ask.

The second issue is how to document interaction for rich Internet applications.  Up to now, I've used annotated storyboards to document for stakeholders, developers, and QA.  There are good, well-received articles online describing how to do this, but in my work I've seen problems.  With some interactions, even the best description possible doesn't quite convey what you want to see in moving, 3D, real life.  In these cases you need an interactive prototype.

Specific tools exist for interactive prototyping, but what I'd really like is to learn Flash better, and use that to illustrate how UI such as drag-and-drop should function. I could learn Axure, or another interactive prototyping tool, but with Flash I'd have a much more flexible skill.  The problem is making the time to become proficient in Flash!  As a stopgap, I've been messing around with interactive prototypes made from Visio and Acrobat, and even from Powerpoint.