Don’t Design the Box

Published on Author Christopher Fahey2 Comments

What happens when Microsoft’s marketers design the iPod’s box. How, if given a chance, might this thinking have shaped the product itself?

There’s a classic [1] product design exercise called “Design the Box” in which a product’s packaging is conceptualized first, before the product itself is designed. The idea is to view the product from the consumer’s point of view as they are thinking about buying it, to think about who the customer is, what is important to them, what will make them desire the product, and what makes the product different from the others on the shelf.

This thinking is nothing new. It’s called merchandising. Merchandising is the strategy and implementation of how a product is displayed in stores, how it shows up in photography, how it is described on a web site. It’s a consciousness of — and responsibility for — the final step in the product supply chain.

(It also happens to be the very subject of my talk this week at the Web 2.0 Expo in NYC and at Euro IA in two weeks — consider this post a bit of a preview.)

Merchandising is critical to traditional product design and marketing. But in the world of interactive product design, the word merchandising is rarely even uttered. How did we get here?

Henry Dreyfuss, the great mid-20th century industrial designer (and, in many design historians’ minds, the father of ergonomics and user-centered design) was a great champion of product merchandising. To Dreyfuss, merchandising is one of a designer’s fundamental responsibilities and core skills, right up there with things like usability, style, and business and technology constraints. Merchandising, traditionally, is the aspect of a product’s design that makes it desirable before the consumer owns the product — even before they’ve seen any advertising or heard any facts about the product.

It’s important to note that merchandising has two very different aspects. The first is showroom-centered, where a store displays the products it is selling in compelling ways. Think of a retail store’s window displays, the tables with featured products, the blouse-wearing mannequins. This form of merchandising is generally managed by the retailer themselves. In the interactive world, the analogy would be the design of an e-commerce experience: The products that are featured on a home page, the personalized recommendations for users, the ability to zoom in on an item, or to view other users’ ratings.

The second form of merchandising is centered around the product itself, and is controlled by the product’s manufacturer, developer, and designer. This ranges from the design and appearance of the product itself to the product’s packaging and display.

In consumer product design, merchandising is alive and well. Physical objects are designed to allow shoppers to imagine carrying them in their pockets and installing them in their kitchens.

In interactive design, I’m not so sure this is the case. That’s actually the subject of my upcoming talks. For now, I want to focus on the difference between merchandising via packaging versus merchandising via the product itself.

Obviously I agree that merchandising is a critical part of design. I question, however, the idea of worrying about it too early in a design process, because when you do so you are engaging more in a marketing exercise than a product design exercise.

The real power of merchandising is its ability to make a given product look better and more desirable than it actually is. Great merchandising, however, can exaggerate features, hide flaws, promise miracles. It’s certainly a great idea to show your product in the best possible light, and I’d argue that there’s always a measure of deception inherent in product marketing (will the latest web To-Do list really make your life easier?), but I think that the deceptive component of marketing and merchandising cannot be the first step in a design process because it prevents us from focusing on the user experience. Which is critical because, in today’s market, the actual user experience itself (not the promised UX given in the showroom, in the ads, and on the box) is likely to be the most important factor in ongoing user satisfaction.

So how useful can the traditional attitude towards merchandising work, then, in a marketplace where the customer and corporation have so many more touchpoints than just the showroom floor? Today’s consumer is more focused on the user experience than ever, and has more ways of evaluating that experience than ever before. Word of mouth, online reviews, test-drive videos and unboxing photos, and free beta products allow consumers to get past the bullet points and sunbursts.

The “design the box” exercise can be a powerful tool for generating ideas and for getting into the mind of the consumer. It is also, I fear, a trap insofar as it refocuses the designer from user experience to salesmanship.

The classic video seen here, “What if Microsoft designed the iPod box” is a great illustration of this. The video imagines Microsoft’s marketing department slapping bullet points, stickers, and exaggerations onto the iPod’s classic minimalist box. Imagine a product designed with this methodology and you can. (I’ve not used a Zune, but I suspect its simple design would have been a very hard sell at Microsoft if it were designed before the iPod redefined the market for everyone else).

Designing the box was once a great product strategy idea in an economy where a clear line could be drawn between the pre-sale consumer and the post-sale consumer. If a product’s cool features couldn’t be explained to consumers in a box on a shelf, they might as well not exist.

But now, with Web 2.0 products and services, that that line between pre- and post-sale is blurred or even completely lost. Now I think we should focus on designing the product as if the box — illustrations, bullet points, specs, everything — was an inherent amd permanent part of the product, not an entirely separate entity.

[1] As far as I can recall, “design the box” has been an industrial design school exercise for ages, but like many compelling ideas the concept has many parents. Jess McMullen credits Joel Spolsky, who in fact learned it from Jim Highsmith, who claims it was invented by Bill Shackelford.

2 Responses to Don’t Design the Box

  1. I’m wondering if the merging of pre- and post-sale could go both ways. It may mean that there’s no place for deceptive merchandising in design, or it could mean _every_ place is open for deceptive merchandising. It may mean emphasizing a cool trendy look and feel rather than functional innovation in a web app. It may mean focusing design exclusively on initial impressions and early-stage novice use. Consumers may never find out an alternative app is better in the long run because they never use it for the long run.

  2. Well, I’m not sure what you’re talking about, but your sentences are lovely and perfectly punctuated. I’m proud of you!

    My frustration with web sites, as a person who’s hired to “fill in the content”, is that the “boxes” are often the wrong size for the messages.

    Sometimes I get a refrigerator-size box for an iPod-sized message — and vice versa. Too many website designers are all about packaging and totally clueless about what needs to go in the box. In fact, they don’t even care about what the site user needs and wants. It is ALL about the box.

    So I get site maps missing crucial pages — or loaded with pages for which I can find no possible rationale.

    It drives me nuts!

    Why web design firms don’t include a serious, analytical writer in their design teams is beyond me. And then they wonder why they run into so many problems with content organization.

    A good web writer is a good reader — i.e. user.
    Hire a good, fast, smart writer and your user testing is already half done.

Leave a Reply

Your email address will not be published. Required fields are marked *