Delivering a Great OOBE
If Steve Jobs didn’t invent the term OOBE — out of box experience — he certainly set the expectation. Only a handful of tech products have made the general public sit up and take notice. And with few exceptions those products have come from Jobs’ fertile mind. It pains me, a Microsoft alum, to say it, but Jobs, first with the Mac and now with the iPod, has set the standard for how tech gear should be packaged and operate.
The reason Infusion’s user group meeting this spring was such a pleasure to attend was that it was packed with satisfied customers using its product in a myriad of different ways.
Like Jobs, the team at Infusion doesn’t seek attention. They grab it. While the rest of us sent out one-page press releases to announce new products, Jobs rented auditoriums and put on a show. While we advertised our gear in the trade pubs, Jobs ran commercials during the Super Bowl.
You should think twice before spending your hard won VC dollars on a Super Bowl ad, but there are some incredible lessons to be learned from masters like Jobs when it comes to delivering an unparalleled customer experience.
OOBE For The Rest of Us
In the early days of the PC industry, the customer was typically a geek who became something of an extension to the company’s engineering team. He tinkered with buggy products until they worked. But Jobs aspired to bring the miracle of computing to Joe Q. Public. To pull it off, he had to make good on the hype, a tall order for an industry where bugs were the norm. Jobs didn’t just set the expectation – he delivered on the promise.
At Microsoft, when those of us on the Windows team realized our customers had trouble getting their PCs up and running we blamed it on the difficulties of marrying disparate hardware and software. In those days, I spent a lot of time talking to frustrated Windows users.
There are three simple things you need to do to deliver a great OOBE.
- Designate a user-experience manager, one person responsible for all aspects of the product that impact its ease-of-use
- Require people in your company to set up the new product without any assistance from the developers
- Observe customers set up your product, over and over again
Without being aware of it, product designers adjust their own behavior to accommodate product flaws. As a result, it’s important to bring customers who come to the product with a fresh eye and without pre-ordained behaviors.
To get funding for my OOBE group at Microsoft, I videotaped a whole bunch of people – from our top user interface designers to marketing managers – setting up a new computer. Features that today we take for granted – like color-coded cables and ports — came out of those early observations.
Great Experience = Happy Customers
To state the obvious, the computer industry has matured and with maturity has come higher expectations. Few customers have patience for products that don’t work straight out of the box. Only a few companies are so entrenched that customers have no choice but to suffer until the supplier gets its act together.
In most cases, the customer has other credible options. Blow it once and it’s unlikely they’ll give you a second chance. That holds true in even the most technical of vertical markets. Deliver a great OOBE and you too, can preside over a packed room of happy customers.
1 Comment
Leave a comment
Subscribe
Recent Posts
Popular posts
Archives
- February 2012
- January 2012
- November 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- November 2010
- September 2010
- August 2010
- July 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- March 2009
- December 2008
- November 2008
- October 2008
- August 2008
- July 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- March 2006
- December 2005
- October 2005
- July 2005
- May 2005
- April 2005
- February 2005
- November 2004
- October 2004
- September 2004
- August 2004




The Microsoft vs. Apple discussion on OOBE is informative in style, but also in terms of how you put together the products that create the interface.
Apple has a better interface because Jobs almost always creates his own independent and integrated architecture. iPod, Mac, and iPhone almost always are completely under Apple control, deployed with a combination of Apple hardware and software, and keep product development (mostly) under a single roof.
Microsoft has always been a part of a broader ecosystem, where other players (including legacy) are actively involved and are innovating on various components that they specialize in. Therefore, Microsoft’s in-house innovation and experience appears to lag Apple’s, but Apple’s own in-house stuff tends to jump out to an early lead and then stall as the multiple players in Microsoft’s ecosystem all improving their own piece drive cost savings and performance that tends to sum up to something better than what Apple can offer alone.
We haven’t seen this in iPod/MP3 yet, but we certainly did see Apple leapfrogged in the PC wars and it looks like it may happen again in Smartphones.
So a design question for entrepreneurs is: do you go with the integrated walled garden that moves the initial needle, or do you let pieces of the system go and let other parts of the ecosystem take credit and make your piece seem a bit clunkier…but grow your overall space faster? What’s hip/cool may not be the best monetization strategy out there…and each approach seems suited differently for market creation vs. fast following.