02
09
10



OLPC: When Good Design Isn’t Enough

olpc.jpg

Saturday’s WSJ had an article about the trouble Nicholas Negroponte has had gaining adoption (e.g. sales) of his brainchild, the OLPC (one laptop per child) initiative. For those not familiar, the OLPC idea is embodied by a product, the $100 laptop, that is intended to bring computing and enhanced teaching and learning to children in impoverished countries. The laptop was designed by the current darling design firm Fuseproject.

In contrast to Amazon’s Kindle, The OLPC laptop computer is a case study for when design can’t help you sell more products. Where the Kindle is likely to disappoint its maker because Amazon failed to make the design of the unit a priority, the OLPC laptop did make design a priority, but neglected to consider elements critical to customers. The OLPC laptop is well-designed with an attention to detail and well thought out features and usability. It even has its own graphical user interface and operating system based on Linux. The product is quite cute and has garnered an awful lot of media attention. Mr. Negroponte expected to sell over 100 million units right out of the gate in 2008. But he’s not. Not even close. And the reason why is one of the biggest challenges that design has in certain situations. The end user is not the customer.

The OLPC laptop was designed to delight, engage, and enable children to learn in ways their country’s infrastructure doesn’t currently support. But OLPC laptops aren’t purchased by the children. Or their parents. The laptops are purchased by governments. What do you think these large institutional customers care about? Price, yes, and OLPC has had a hard time meeting the $100 price point, due in part to not being able to produce the product in extremely large volumes. But these customers also care about important aspects of the “whole product” like service, teacher training, and future upgrades. Something OLPC cannot sufficiently address as a company with no track record. The customers also want one more important feature, a connection to an industry standard, the standard of developed nations. That standard, of course, is Windows.

The marketing issue that Mr. Negroponte ignored is considering the actual customer for the OLPC laptop and their needs, concerns and desires. Instead of thinking only of the kids, Mr. Negroponte might have realized that these developing countries don’t want to be treated as second-class citizens. The fact that Mr. Negroponte wants to provide something to these countries that is not used in the U.S. or other developed countries creates the impression that they are not being treated as worthy of the same computing “standard”. These developing countries want the same computers for the children in their schools that kids in developed countries have. That means Windows-based laptops.

As I see it, the only way for the OLPC laptop to succeed as designed, is if it is accepted as a standard teaching tool in developed countries, and then marketed to the developing countries as Mr. Negroponte intended. Only then will the developing countries feel as though they are giving their constituents similar experiences to developed nations. Otherwise, OLPC might want to consider adopting Windows.

The media popularity of the OLPC laptop idea also caught the attention of Intel. And Intel decided to create their own low-cost laptop for the same market, but featuring Windows. Intel is giving the customer what they want. The users may suffer slightly, but that is the reality of the marketplace when a product’s customers are not the end users. Mr. Negroponte (and designers, too) needs to study some Geoffrey Moore and Clayton Christensen.

The best designers act as advocates for the end user, working hard to create a simple, elegant, and enjoyable experience for them. That works well when the users and customers are one and the same. However, very often there are intermediary customers that must also be considered. Maybe that’s a little more marketing strategy than designers want to be accountable for, but ignoring the needs of the customer and solely focusing on the needs of the user can be a losing strategy. Designers need to keep that in mind just as much as marketers do.

Posted on November 27, 2007 | Permalink |

3 Comments »

  1. Right on, except for the windows argument.

    Many countries in South America and Africa are using Linux as the official OS, not windows. This is based on the price and the fact that they feel that open source will eventually lead to a more robust and efficient OS. Adding the option to use windows would be great. Having MS donate Windows would be both doable and probably help lower the overall pricepoint since suppliers would then be willing to offer more discounts as well.

    IMO, and I think you agree, the main issue with OLPC is actually the same issue that we have in the US- money earmarked for education is sometimes spent in shortsighted ways that not everyone agrees with.

    Comment by billy — November 30, 2007 @ 10:28 am

  2. […] Greg Hinzmann » OLPC: When Good Design Isn’t Enough Great article about what happens when the end user is confused with the customers, also a good commentary on how developing nations want and should be treated. (tags: product design computing business) […]

    Pingback by designswarm thoughts » Blog Archive » links for 2007-12-01 — December 1, 2007 @ 2:19 pm

  3. I think your overall framing of the issue is right on.

    I think the Windows issue is pretty addressable, and maybe already is addressed by them. Windows is a bug, not a feature. It’s an OS designed for non-networked office drones. The OLPC is designed for collaborating creators who happen to be minors.

    Also, I’ll be curious to see how well the Intel unit performs when running Windows, and whether it’s human-rechargeable, etc.

    http://webseitz.fluxent.com/wiki/z2007-12-03-HinzmannOlpcUserVsCustomer

    Comment by Bill Seitz — December 3, 2007 @ 2:14 pm

RSS feed for comments on this post. TrackBack URI

Leave a comment

Line and paragraph breaks automatic, e-mail address never displayed, HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>

(required)

(required)