The Double Diamond Model of Product Definition and Design

After I left Adaptive Path and started working in-house, I was disheartened to realize how retrograde most people’s view of design still was, with a focus on styling and execution. I needed a way to communicate the full breadth of activities my team and I did.

So, over the past couple of years, I’ve been using a double diamond model for talking about digital product design. It didn’t originate with me — from what I can tell, The UK Design Council created it in 2005. I’ve modified it to more closely track what happens with digital product design. I’ve shown it at a few events, and people seem to appreciate it. So, I’m sharing it here. Click the “full screen” icon to get all the nitty gritty details.

Some explanations

Why diamonds? Because I think the divergence/convergence concept is powerful and not practiced enough. Teams too often go with the first idea and attempt to execute that.

Why the red words about design at the bottom? Those emphasize the role that design plays in each stage. The double diamond is not just about design — it’s about product/service development. Design is a contributor, and I find it helpful to clarify the role. So, in the first diamond, the role of design is to make strategy concrete. In the second, it’s to deliver delightful and engaging experiences.

Hey! I don’t do those things in that order! That’s okay. It’s meant to be suggestive of a process, not enforced linearity.

And, the deliverables slide is just to connect the double diamond to more typical UX design practice. Again, this is meant to be descriptive, not prescriptive.

(Thanks to Thomas Küber and Matthew Milan for enhancing my thinking on this.)

In forthcoming blog posts, I’ll talk more about how I’ve used the double diamond, not just to explain process, but to better coordinate with other roles (such as product management) and to diagnose problems in product development.

If I made a podcast app…

I just returned from XOXO, a remarkable event celebrating independent creators of all stripes. Among the presenters was Marco Arment, former CTO of Tumblr, creator of Instapaper and founder of The Magazine. He talked about the challenges he’s faced as an independent software developer, and then announced his forthcoming product: Overcast.fm, a podcast app.

In hearing about this, my heart both rose and sank. As some friends of mine know, if I were to ever go independent and try to make a thing, it would be a podcast app (thanks to my commute, I listen to podcasts around 2 hours a day). My heart rose because, given Marco’s track record (particularly with Instapaper), I’m excited to see what he does. It sank because of my personal reality that, practically, designing and developing a podcast app is nothing I could undertake at this point of my life, with my career, family, and, oh right, I’m not a developer.

Given that, I thought I’d share why I think it’s a great time to create a great podcast app.

This might seem counterintuitive at first, because the podcast player space is quite crowded (over a dozen apps, such as Instacast, Downcast, Stitcher, and the app I use, iCatcher), and has one exceedingly dominant player, Apple. (If memory serves, Apple launching podcast capabilities was what lead to the demise of Odeo, which lead to the rise of Twitter, but that’s another story.)

The thing is, none of these players are great, or, in my eyes, even good. The ones I’ve tried out all have significant drawbacks. I settled on iCatcher because it had a couple personal must-have features — playlists (so I can have different streams in my morning and evening commutes, and then different again on the weekend), and true double-speed playback (most podcast apps “2x” speed is actually 1.5). But it’s user interface is a wretched disaster that I stumble over even after a couple years of use.

So, even though the market seems saturated, I believe that there’s an opportunity for something truly great to rise above. And there is room to improve across many aspects.

UI Design

Podcast apps would benefit from truly elegant, detail-oriented design, the kind of fit-and-finish we’re seeing, in the note-taking space, with Vesper or Evernote, or what Instapaper pioneered in reading.

However, a shortcoming of every podcast app I used is the amount of visual attention it requires. Developers confuse “UI” with graphical user interface. The thing is, I don’t want to look at my phone when I’m listening to podcasts. Typically, I’m driving, and fiddling with small touchscreen controls is distracting (and potentially dangerous). Podcast apps are ripe for voice user interface exploration and innovation.

Discovery

Finding and subscribing to podcasts of interest is a largely manual, and often arduous, process. My typical mode of discovery is through the AV Club’s weekly Podmass column, and if something sounds interesting, I then have to hunt it down through my app’s search feature. Yet, nearly 15 years ago (has it been that long?) TiVo showed the power of taste-based recommendations, which Netflix has taken to a new level. Where’s the intelligence that takes the podcasts I subscribe to, matches it with others, and makes suggestions?

Management

Once I’ve found podcasts, organizing them into playlists is also a chore, because it proves to be an interface challenge within a smartphone screen. Instacast is smart to support cross-device management and syncing, which means I could use the bigger screens of a tablet or PC to organize my podcasts, and the phone acts primarily as a player. (This was the brilliance of the original iPod — other MP3 players were loaded with features for organizing and managing your music, which made their interfaces unwieldy, whereas Apple offloaded all that to the PC, so the iPod could be simple.) Still, tagging, rating, and organizing podcasts (for those interested in doing so) has much room for improvement.

Playback

This is where everything we’ve learned from Pandora (just hit play and go) and Netflix (leaving off and picking up) could come into play. Additionally, this is where a voice UI becomes crucial — when I’m listening to podcasts, the last thing I want to do is looking at my phone, and fiddle with controls.

Sandbox for media consumption

Ultimately, my interest in designing a podcast app was that it would provide a sandbox for exploring media consumption behaviors and models. As a media junkie, I have a vested interest in the tools we use for listening, watching, and reading, and I’m sure there is heaps of room to explore and improve these experiences. What’s great about podcasts is that this is freely accessible media, with creators eager to give away their material, so you have this massive corpus of content to play with, and no worries about licensing and fees.

Now there’s no Nielsen numbers for podcasts, so it’s unclear just how large the current audience is, and how actively they listen. Podcasts have not yet broken ‘mainstream’ to compete with terrestrial or satellite radio. It’s possible that a killer app could provide podcasts that quantum leap of exposure. More likely, it will be like blogs and RSS feeds, where there is a sizable, but relatively limited, ultimate audience. I suspect that integrating podcasts with other media will be where this all heads. Experimenting with podcasts, you could develop new paradigms for media consumption that could then also be applied to “premium” content.

It’s not a layoff, it’s a fauxquihire

A phenomenon I’ve recently witnessed is what I’m calling the “fauxquihire” (a purposefully ugly mouthful, though not any worse than acquihire.) In particular, there was a company, with a decent-sized design team, that made a strategic shift in its business, that meant it no longer made sense to have an in-house design team. If it were 5 years ago, this would be a simple (and unfortunate) layoff, with things like severance and, one hopes, a program to help folks find new work.

Now, in this overheated job market (at least in Silicon Valley), this team was being served up as a kind of acquihire, where other companies were offered the opportunity to hire the entire team, and were expected to give the provider some kind of premium in terms of a per-head fee. This way, the provider turns a liability (a team that they can’t get enough value from) into a highly desirable asset. But, it’s not really an acquihire, because the providing company still exists and continues to go about its business.

I don’t have anything more to say about this, except that I find it interesting, and indicative of just how nuts things are in terms of design talent around here.

Don’t “design for mobile”, design for your customer relationship

Last night I saw Luke W give his excellent “Mobile to the Future” presentation. In it, he questions many of the interface paradigms and assumptions that underlay our desktop web experience, and demonstrates the power of thinking “mobile first.” He shares great ideas for improving mobile interfaces, many of which are applicable to desktop web as well. It got me fired up to overhaul our designs.

Relatedly, there’s been enormous buzz about mobile in the past week. Mary Meeker’s internet trend report seems mostly about mobile (Groupon is featured in slide 35!). Sheryl Sandberg recently claimed that every team at Facebook is now mobile first.

All this talk about mobile is necessary. However, it’s also misleading. In that it sets up a false distinction. The idea of “mobile first” or “design for mobile” is in order to contrast it with “design for desktop”. But, as the ascent of mobile demonstrates, “design for desktop” was also always flawed. The problem is to focus on the specifics of a platform or technology. These things will continue to change. In five years, will we be saying “wearables first!”?

It’s never been about the technology. It’s about where your customers are. If you design for your customer relationship, then the rest falls into place. If your customers are moving from web to smartphone, you’ll just move with them. If your customers are moving from smartphone to tablet, head there. (Though, as we’re seeing, it’s less about moving from one to another than it is about customers using a variety of devices throughout a day.) USAA was the first to offer mobile check deposit not because they’d embraced a “mobile first” mindset, but because they have a remarkably attuned sense of customer care and service, and realized they could address a real need, one that happened to use that platform in the solution.

My concern with “mobile first” is that we’ll mistake that for “mobile only” (the way that the Web was seen as the end-all be-all for quite a while) and not appreciate just what our customers are actually doing, nor prepare ourselves for what’s next.

 

Supply and demand of digital product designers

12 years and 1 day ago, a group of 7 founded Adaptive Path. If you look at the NASDAQ 100 around that time, you’ll see just how far things had fallen, and they actually got worse over the course of the following year.

But, no matter how bad the internet economy was, there was always work for digital product designers. Even with layoffs or companies dissolving, I never knew any designer who went long without work. It might not have been the most desirable work, designers might have felt continually compelled to prove our ROI, but there were always jobs.

What I realized then was that, even at its lowest point, there were still more jobs than there were designers to fill them. Up until 1995, design for software meant working on packaged goods, and there simply wasn’t as much need. Beginning in 1995, the web created a sea change in the job market, and then the launch of iPhone in 2007, and iPad in 2010, has lead to successive waves of need for digital product design.

So now, supply and demand in the market of designers is frighteningly out of whack. The competition for designers is fierce. I remember getting paid $60,000 in 1997, roughly 4-5 years into my career. That is the equivalent of $87,000 today, and I can tell you that capable designers with 4-5 years experience are earning much more than that.

There is a paradoxical risk when designers are in such demand. The demand reflects the value that is seen in design work. But, with such demand, most organizations have too few designers given what they’re trying to deliver. That means those designers are spread too thin, and are focused on execution that keeps the light on. Which means design isn’t being used to its fullest extent, driving not just execution, but product strategy and definition.

Because designers are seen as so valuable, they are not able to deliver their ultimate value.

3 inspiring people and thoughts from BusinessWeek’s Design conference

Last week I attended BusinessWeek’s first conference dedicated to design. I got more out of it than I thought I would. Many had eye- and mind-opening things to say. I thought I would share a few.

Brian Chesky, CEO of AirBNB

Among my favorite presenters was Brian Chesky, CEO of AirBNB. He has a degree from the Rhode Island School of Design, and is very design-forward in thinking about how to run AirBNB. Some of his thoughts/beliefs:

  • Designers have the opportunity to remake the world around them. If there’s something we don’t like, we can fix it.
  • Early on AirBNB followed Paul Graham’s advice of being loved by 100s rather than kinda liked by millions. They felt that passion was important, and they were very explicit in designing the service to stoke that passion in their customers.
  • At one point he said, “You’re not going to A/B test your way to Shakespeare”. Too often companies defer decisions to A/B testing.
  • “Take a method acting approach to design”… Develop deep empathy for your customers so that you can then really understand what it’s like to be them. This will allow you to develop magical experiences, and you can help your customers elevate their expectations of what a great service can and should be. I LOVE THIS.
  • When asked about what flaws designers have, Brian said, “They can lose touch of who they are designing for. Particularly when they silo themselves. Designers have to watch their ego. And collaborate with every function throughout the company.”
  • Brian also stressed the importance of physical space. He remarked on how most offices interiors are awful, and most home interiors are delightful. They’ve designed their conference rooms as re-creations of spaces available in people’s homes on AirBNB.
  • AirBNB doesn’t offer a desk for every person. Some people need permanent desks, yes. Many don’t, because they’re always collaborating, or rarely at them. So AirBNB favored creating spaces to promote collaboration rather than making sure everyone has a dedicated desk. I ALSO LOVE THIS.

Paul Bennett, Chief Creative Officer at IDEO

Paul used a metaphor of flying flocks of wild geese to talk about designers and design teams:

  • the lead goose creates uplift for followers
  • when the lead gets tired, it moves to the back of pack
  • the followers honk as a way to motivate the leader

Tony Fadell, CEO of Nest

Tony Fadell, lead designer of the iPod and iPhone at Apple, and now CEO of Nest, the dynamic thermostat folks, stressed that any design/product team needs to have a “point of view, a vision.” The reality is that not every decision can be fact-based, that many will be opinion-based, and with a shared point-of-view, teams can arrive at a shared opinion.

For me, this tied into Brian Chesky’s comment about A/B testing. If you simply let A/B testing decide your future, you’ll have a product that might perform well in the moment, but that could miss out on a much more impactful gestalt. You need that point of view, that shared perspective, to ensure coherence and the best experience over all. I think you should then use A/B testing to optimize those parts of the experience.

“Product designers” and design team evolution

(This may or may not end up being part of a series of my reflections as in my role as VP of Global Design at Groupon.)

In Silicon Valley, there’s a new(-ish) design role called “product designer.” I first heard about it at Facebook a few years ago, and since then, many other companies have adopted it (including Groupon, where I work). Product designers are jacks-of-all-trades, expected to deliver interaction design, information architecture, visual design, and even front-end code. From what I can tell, “product designer” emerged for two primary reasons:

  1. Startups don’t have the resources for many employees, and so needed individual designers who could cover a lot of ground
  2. More and more young designers demonstrate these cross-trained skills, and don’t want to be pigeon-holed

The title also suggests a tight relationship with product managers.

With the rise of the product designer, there’s a simultaneous progression and regression in digital experiences. Using Jesse’s 12-year-old diagram (!) as a framework, we’re seeing the top two planes getting tastier and more interesting — look at Path, Square, AirBNB. Luscious full-bleed high-design screens where it’s clear that designers obsessed over every pixel and element of movement. But in that middle plane, digital experiences suffer from a lack of attention to flows, taxonomies, relationships between content areas, etc. (Any attempt to navigate Path turns into a trip down the rabbit hole.)  We’ve forsaken managing complexity in favor of delight in the moment.

Additionally, a challenge seems to occur as design organizations scale, and the product designer (or 2) needs to turn into a product design team. People who are able to deliver effectively across the entire “product designer” set are few and far between, and so if you require all of those boxes to be checked, you’ll be looking for a long time.

So, organizations end up changing requirements, looking more for “T-shaped” people (strong in one thing, able to work well cross-discipline). This leads to an uncomfortable interim where you have these jacks-of-all-trades who feel a sense of ownership of the whole trying to figure out how to collaborate with a designer who is focusing on a part.

This means designers (and the organizations they work for) must embrace a team model of design. I’ve never worked in a context other than that of team design, so I’ve been staggered by the Silicon Valley startup model where team design is considered optional. (I had coffee with a friend from New York today, who said that Silicon Valley is becoming notorious for the ‘design unicorn‘, whereas New York startups are more, well, traditional in their thinking about teams.)

Another interesting aspect to this is productivity. I’ve always sought to hire generalists, because I believe a small team of capable generalists (who each might have different emphases) is stronger and can deliver more than a large team of dedicated specialists. Product designers often work alone, and because they’re expected to do so many things, end up working on projects of limited scope. (I think this contributes to the problem of managing complex user experiences). My supposition is that the small team of generalists can also out-produce an equal number of team-of-one product designers. You get higher quality, because folks who have a functional emphasis (such as visual design or interaction design) can deliver better than those whose priority is developing a broader set of tools. And you get greater output, because their mastery of those areas means they can deliver more quickly. What you give up are the transaction/overhead costs of teamwork, but I don’t think those are as great as the gains.

An essential element to making this all work is leadership. Design teams *will* be less effective than a squad of singular designers if there’s no clear leadership and authority. Someone needs to step up and be accountable, or design teams will flounder. For reasons I’ve never quite understood, design teams can be quite bristly about leadership, but it is essential. Much the same way that there’s one director of a film who makes the final call, there needs to be one leader of a design team who makes decisions and keeps things moving.

 

 

New York Designers–Interested in working with me at Groupon?

In two weeks, on November 8 and 9, we at Groupon will be visiting New York to talk to people interested in working with us in design, product management, and engineering positions in our Chicago, Palo Alto, San Francisco, and Seattle offices. As I’ve explained earlier, there are lots of tasty design challenges we’re tackling, online and offline, for merchants as well as buyers. I also think this could be a remarkable career move for the right candidate — an ability to lead teams and elevate your practice within a passionate internal design community.

If joining a burgeoning world-class design team compels you, please let us know by submitting through our listings for product designers and visual designers, or emailing me directly at [peterme] AT [groupon] DOT [com].

(And I promise this is my last post soliciting designers for a while. I know I need to get back to addressing design ideas! And the NBA! And Top Chef, when it returns.)

Calling all designers!

Truly! I am calling all designers.

I’m in my third week at Groupon, and one thing is very clear–to tackle all the interesting stuff we’re doing (reducing the friction in local commerce between merchants and their prospective customers with web/mobile/tablet solutions, marketing and brand work, print and packaging), we need heaps more design talent.

We have design needs in Chicago, Palo Alto, San Francisco, Seattle, and Berlin.

We are looking for full-time digital product and visual designers from junior all the way to director level. We pay competitively for Silicon Valley/tech.

If you like your freedom and independence, we are happy to collaborate with contractors and freelancers. (This is particularly true for our marketing and communication work, which spans all media.)

And we are looking to partner with small design shops (digital product, ux, marketing) in those locations as well.

If this is you, please contact me directly at peterme (at) groupon (dot) com.

Why I’m excited about joining Groupon

Today I begin a new job — VP, Global Design at Groupon. I’m thrilled for the opportunity to work on what I consider to be one of the most interesting design challenges of the Connected Age.

Now, if you’re someone who, when you think of Groupon, you think of daily deals, you probably wonder what in hell I’m talking about. And that’s going to be one of my big initial challenges. Because Groupon’s vision is to become the operating system for local commerce. Thanks to the daily deals, Groupon has relationships with hundreds of millions of shoppers, and hundreds of thousands of merchants. The objective is to activate those relationships in interesting new ways in order to reduce the friction in local commerce, to make it easier for local businesses to attract and serve customers, and for those customers to find and buy what they desire.

You could think about it as taking the kind of e-commerce intelligence found within a single site like Amazon, and figure out how to distribute it to local businesses throughout the world. To give these local businesses access to the kinds of technology and data that currently only big box or online retail has. And in a time of increasingly boarded-up shops, it’s clear local commerce could use every advantage it can get.

And, hoo-boy, what a design challenge. Across merchants and shoppers you have a remarkably complex eco-system of devices, touchpoints, desires, and processes to serve. To make this real, we will need to bring to bear every tool in the design toolkit — service design to understand end-to-end customer journeys, brand design to better communicate Groupon’s evolution, interaction design at every touchpoint, whether a shopper using the website or mobile app, or a merchant processing a payment (yep, Groupon helps merchants take payments now). Addressing this all is going to be hard, but it’s also going to be a lot of fun.

Groupon has been a punching bag for the tech and finance press the past year, but I think the company has only remarkable opportunity ahead of it. With their (our!) phenomenal growth in the past few years no other company is so embedded on both sides (shopper and merchant) of the local commerce equation. But don’t merchants hate Groupon? Given all the bad press about unhappy merchants, you might think so, but it turns out that while it makes for compelling stories that fit the media’s overarching narrative about Groupon, it’s not indicative of broader merchant sentiment (yes, that’s a link to a press release, and yes, it’s research commissioned by Groupon. For a broad and deep look at Groupon and merchants, try this article.)

What cinched the deal for me was how impressed I’ve been, up and down the line, with the people I have met, and their commitment to serving their customers with great experiences. My job is not to try to convince Groupon that it should care about its customers — they already do that. My job is to help Groupon figure out how to sustainably deliver great product and service experiences that appropriately reflect its internal passion for customers.

If this all sounds interesting to you, we’re hiring (product designers for web and mobile, visual designers), and I’d love to hear from you.