Leadership

3 steps to great product design


*Step 1*: Find the best, most experienced, most professional product designer you can.

*Step 2*: Ask them what to do.

*Step 3*: Do what they say.


Profit! Ok, maybe a little more detail would help.

For *Step 1*, your goal is to find the person with the most experience designing products that will work with you. This may or may not be someone with the title “designer”; if you find a “product manager” or “engineer” who has successfully led a dozen projects to good results, that might be the best person to trust. You’re looking for quantity of past work (remember [the ceramics class](http://russelldavies.typepad.com/planning/2007/02/quantity_equals.html)) and quality (defined by whatever metric is most important to you and the project–innovation, aesthetics, market success, reliability, etc). Whatever their title, you should make it clear to everyone on the project that *this* person is the lead designer.

Don’t know any great designers? Ask everyone you know who their favorite designer is, then ask that designer about the best person they know. Repeat until you run out of time and/or money.

*Step 2* is pretty straightforward but often forgotten. In the heat of the moment, most people revert to voicing their own answers rather than asking questions. Designers work best when their opinion is sought out, not when they have to shout to be heard. Their job is to make design decisions, so bring them everything you can. A good designer will be humble enough to say they don’t know when that’s the case.

The wrong way to interpret *Step 3* is to assume every lead designer should act like a dictator–shouting orders and demanding obedience. A great designer will first set up a design process that includes everyone on the team in the right way. They’ll probably ask more questions than give answers (see Step 2), and will want to understand all the various options and known constraints.

But at some point decisions have to be made (specified in that process) and at that point you have to follow the person you’ve entrusted with design authority. A project where only half a design is followed can turn out worse than one with no design. A great design is holistic and integrated, and if you choose to compromise it–through impatience, penny-pinching, or simply lack of appreciation for the design quality–your product will not be great. On the other hand, products that do fulfill their designed form and function are a breath of fresh air and a shock to a world accustomed to mediocrity and imitation.

Three steps. Easier said than done…but worth trying.

On knowing

When I was a senior in high school, a teacher asked me to join the [impromtou speaking](http://en.wikipedia.org/wiki/Impromptu_speaking) team. In this competitive speech event, you received a question from a predefined category–for the category “transportation”, it might be something like “Should seatbelts be mandatory?”–and had just 6 minutes to prepare and deliver a speech on it. I had previously acted in drama events, and even improv comedy, but never spoken seriously without preparation.

The first time I tried it, alone with the teacher, I nearly cried. Standing in front of the room, I stumbled through a few points loosely related to the question, forgot to express an opinion, and trailed off to silence after only a minute or two. Undeterred by my failure, my teacher showed me a few tricks to help connect my thoughts and pace my speech better. After a lot of practice and a few competitions, I began to feel more comfortable and deliver better responses. Eventually I made it to the state finals, alongside competition who had much more experience than me.

The most interesting thing I learned from my impromptou experience was the power of nonsense spoken with conviction. I found that with just 5-10 unique stories or data points on a category (e.g. “transportation”), I could string together a compelling argument for almost any question. It wasn’t important that I believed what I was saying, or even that my arguments were consistent across questions. In fact, I would frequently use a single anecdote or data point multiple times in a single day to argue completely opposite things–and as the judges were different for each question, my shifting opinions were no problem. The important thing was that what you said sounded believable on the first pass, which was influenced as much by how you said it as what you said. My bar for “knowing” something was lowered to pass anything that received superficial approval and sounded confident.

As you might expect, this taught exactly the wrong lessons to a self-centered and overconfident teenage boy, which I’ve spent years painfully unlearning in the real world. As I progressed through university and various jobs, working on increasingly difficult and complex topics, it became clear that [falsely knowing](http://www.ryskamp.org/brain/?p=4584)–and acting as such–was a liability, not an advantage. My polished speaking skills, and the belief in my own ability to spin believable solutions out of thin air, combined to set me up for a bigger fall when I encountered situations I wasn’t actually prepared for. The questions I worked on now demanded real, not postured, solutions, and the critiques I received were not from sympathetic teachers at weekend student events, but from brilliant and exceedingly logical friends, mentors, and colleagues searching relentlessly for the truth.

This problem actually gets worse as you gain experience. It’s natural to believe that your years of experience have given you an instinct for “what works” and what doesn’t; that because you’ve been around for a while you can skip some of that boring background work. But in a rapidly-changing world–and anything worth working on seems to be “rapidly-changing”–the facts themselves are shifting so fast that prior experience can also be a handicap. The more you learned on the last project, the more you need to unlearn on the next. It’s the cognitive equivalent of [the Innovator’s Dilemma](http://www.businessweek.com/chapter/christensen.htm): as soon as you get good at something, it becomes useless and your investment in it becomes a burden.

What’s the alternative to this? For me, the solutions have all involved humility and patience: learning to say “I don’t know”; asking for advice; listening more than I speak. Practicing mindfulness through reflection and meditation, to recognize when things have changed and require new approaches. Recognizing that knowing takes time, _especially_ when you’re experienced, and planning extra time to figure things out.

People often think leadership is about personality; that no one knows the right answer, and that you just need to act like you do. Steve Jobs said early in his career, “Pretend to be completely in control and people will assume that you are.” With his recent [geek-beatification](http://sallanscorner.files.wordpress.com/2011/10/memorial-3.jpg), [people are taking this statement as gospel](http://althouse.blogspot.com/2011/12/pretend-to-be-completely-in-control-and.html), and acting confident despite not knowing a thing. I’ve personally watched an entire generation of product managers and designers turn into wannabe-Pied-Pipers based on this advice.

But that’s exactly the wrong lesson to learn from Steve’s work. Instead, look at what he actually did–[continually disrupt his own past successes](http://blogs.hbr.org/cs/2011/10/steve_jobs_solved_the_innovato.html). Apple under Steve Jobs was a place that [repeatedly cancelled](http://en.wikipedia.org/wiki/List_of_products_discontinued_by_Apple_Inc.) [successful products](https://discussions.apple.com/thread/188174?start=0&tstart=0) and replaced them with new ones; Steve himself would make [outrageously](http://www.applematters.com/article/april-30-2004-steve-jobs-dismisses-an-ipod-with-video-support/) [opinionated](http://www.youtube.com/watch?v=8Vq993Td6ys) [statements](http://www.wired.com/gadgetlab/2008/01/steve-jobs-peop/) about product features and then [completely](http://www.apple.com/pr/library/2005/10/12Apple-Unveils-the-New-iPod.html) [change](http://www.youtube.com/watch?v=xo9cKe_Fch8) his [mind](http://en.wikipedia.org/wiki/IBooks) with the next generation. In some cases this may have been [calculated misinformation](http://www.ovguide.com/video/mahalos-jason-calcanis-on-steve-jobss-lies-922ca39ce10036ba0e11430040f47530), but in others he clearly [made an about-face](http://www.cultofmac.com/125180/steve-jobs-was-originally-dead-set-against-third-party-apps-for-the-iphone/) on something he had strongly believed.

Don’t act like you know when you don’t. It’s ok to not know right now. Wait and work until you do know, and recognize that what you knew yesterday may be holding you back today.

Doing what no one else will

> While I could assign most good ideas, every once in a while I’d get a great idea that I simply could not sell…It took me several times to realize that this was a signal. It said, “This is the one you have to do”…

> What I had been inadvertently doing was weeding out good ideas that I could do (but others could do as well) from those few great ideas that only I could do…Work at its smartest means doing that work that no one else could do. – [Kevin Kelly](http://www.kk.org/thetechnium/archives/2011/09/what_you_dont_h.php)

I’ve noticed this recently…no one else understands your truly unique ideas, you have to lead them yourself.

Real leadership

> Leaders are not what many people think–people with huge crowds following them. Leaders are people who go their own way without caring, or even looking to see whether anyone is following them. – [John Holt](http://www.goodreads.com/quotes/show/177781)

Notes from “I’m Feeling Lucky”

I found [this book](http://www.amazon.com/Im-Feeling-Lucky-Confessions-ebook/dp/B004X7SYQI) fascinating, as it not only contains stories from the earliest days of Google, but does so from the perspective of someone in a creative role–[Doug Edwards](http://xooglers.blogspot.com/), Google’s first head of marketing and a person who helped set the tone of Google’s design and communication.

His insights are remarkably similar to what it’s like to design products there today–both the good and the bad. Fortunately, having Doug’s stories to draw on really help me understand the culture better and hopefully improve my work. I only wish I had read this book (and [his blog](http://xooglers.blogspot.com/)) 6 years ago!


*Notes and quotes* (with Kindle locations)

“Your greatest impact as an engineer comes through hiring someone who is as good as you or better,” he exhorted everyone who would listen, “because over the next year, they double your productivity. There’s nothing else you can do to double your productivity. Even if you’re a genius, that’s extremely unlikely to happen.” – 776

“That’s because marketing likes to lie,” Larry let slip. He smiled when he said it, but I sensed we were being held to account for everything engineers hated about the nonquantifiable world, with its corrupted communications and frequent flyer programs. God help anyone who offered a marketing opinion as if it were a scientific fact. – 815

“Let’s do a gap analysis,” I used to say at the Merc. “What’s the unmet need? Where’s the market opportunity? How much share can we gain?” Engineers hate that kind of thinking. If you’re an engineer with a brilliant idea, seeing it dumbed down or abandoned because it doesn’t test well is like watching a bully pull the wings off a butterfly. The right thing to do is build it regardless, to prove that you can and because building cool things is—well, you end up with cool things. – 1055

Google’s official office dress code was “You must wear clothes.” – 1620

A week later we changed the label back to “cached” and I plotted three new data points on my Google graph: Nothing was final until Larry said it was. Larry communicated directly to the people who could implement his decisions. Larry erased what he had etched in stone if the walls crumbled around him. – 1792

The madness was not without method. Not only did Larry and Sergey’s hyperbolic proposals force us to reason more tightly, but starting at the ideological antipodes exploited the full value of the intelligence in the room. After Larry or Sergey made one of their outrageous suggestions, nothing that followed would seem inconceivable. – 1945

Larry even hated the stiff black cardboard that agencies used to present creative campaigns—each concept perfectly center-mounted to convey greater gravitas. To Larry, a good idea was self-evident, even if scrawled on a wrinkled napkin in blotchy ballpoint. Ad agencies, he hinted, were full of bumbling simpletons and evil dissemblers. – 2495

“‘An order of magnitude is qualitative, not quantitative.’ When you go up by an order of magnitude, the problem is different enough that it demands different solutions. It’s discontinuous.” – 3008

If you want to make a killing trading tech stocks, find a friend in the t-shirt business between San Francisco and San Jose and ask to be alerted any time a rush order gets placed. – 3150

“Larry and Sergey had certain things they wanted worked on,” Gmail creator Paul Bucheit explained, “and there were these standing groups that were making up their own things and not doing whatever it was Larry and Sergey wanted.” – 3984

“So … what I underestimated,” he went on, “is that managers always make judgment calls. They have to in order to function. If you’re in a highly technical area, you can’t make good judgment calls if you’re not highly technical yourself. We changed at that point our strategy for hiring managers—away from coordination to saying that what matters most is technical leadership.” – 3994

Part of the power of Google’s brand was the cluelessly geek chic it projected, as though a site serving millions of users around the globe were being run by a handful of nerds who didn’t know any better than to put whatever struck their fancy on the homepage. I think I had a pretty good ear for that nerd voice and was able to channel it into the communications I crafted, but I also know that I always wanted to smooth out the rough edges and make things flow a little more nicely across the screen. It was the English major in me. Sand down too many protruding bits, though, and you end up with a perfect sphere that’s not terribly interesting. – 4322

> Does design do the same thing?

When users posted multiple correct translations, they earned editorial power to overwrite awkward or incorrect submissions made by others. – 4502

My role still had value, because I worked on the language that went into the product itself. But thinking about how users perceived the product, and the company as a whole, was a low priority. The product would speak for itself, so what mattered most was the technology and the cool things that could be done with it. – 4940

The day after the deal went live, John Bauer added code that boldfaced the keyword a user had searched for when it appeared in an ad, making it obvious that the ad was relevant. That single improvement increased clickthrough rates by four hundred percent. One engineer. One change. Four hundred percent. – 5296

For the rest, they gave the okay to go ahead. I quietly rejoiced. I had sold a branding campaign from the nation’s hottest ad agency to two guys who hated anything to do with marketing. It had taken four years, but I had figured out a way to work the system. – 6155

When I first arrived at Google, I felt strongly about things and was often wrong. Fortunately, Larry and Sergey ignored my ideas. I had learned from that experience. Now I felt strongly about things and was often right. Unfortunately, my ideas were still being ignored. I wasn’t sure which slight was more painful, but I suspected it was the latter. – 6340

To launch a radically new product from an established company, Paul asserted, you needed someone who not only believed in it but also was able to make the organization “do the right stuff.” – 6359

Co-design principles

[Some good perspectives on running design workshops](http://adaptivepath.com/ideas/the-ux-of-co-design-experience-principles-for-successful-client-workshops) from Adaptive Path.

I especially liked the reminder to set the context:

> Knowing what’s going on is the gateway to empowered participation. To this end, there is nothing wrong with stating what you might assume is obvious to the people present.

And her closing bit:

> When I think of a workshop, I imagine each person walking into the room with a carefully wrapped puzzle piece. Over the course of the workshop we unwrap the pieces, collect them, sort them and assemble a very big picture. It’s not quite what any one person expected to see, but when we look upon it we have both a sense of satisfaction, and a yearning and curiosity for the good things to come.

‪A Day In The Life of John Lasseter

Really cool insights into how Pixar, and John specifically, makes the magic.

5 things I noticed:

  • The teams applaud after every successful review, even the short daily ones.
  • John sees himself as the head “cheerleader” for his film crew, and his personality reflects that. Even negative feedback is done with positive reinforcement for the team.
  • John uses cool custom-built applications to review work and record feedback. Benefits of close ties to Apple!
  • The “atrium” in the headquarters building perks him up several times a day. Having something inspiring and natural that you pass through regularly seems like a great workspace design principle.
  • His line about “the art challenges the technology, and the technology inspires the art” seems like something worth aspiring to in a creative role at any tech company.

The design long game

> Look at the long game. There are no seasons in design, it is a continuum of minor successes. Measure your success by the ability to rise after numerous defeats. – [Chris Bangle](http://www.fuelyourproductdesign.com/chris-bangle-on-being-a-better-design-leader/)

Leadership lessons

At a high level, I think leadership still comes down to what I previously observed: [know your stuff, and be a good person](http://www.ryskamp.org/brain/?p=252). But there are a few specific practices I’ve learned from great leaders and discovered to be helpful myself:

* *Ask people what they think you should do* – Regularly go to your team and ask for feedback and suggestions on your personal behaviors and the overall team operations. They’re supporting you, after all–why not use their full knowledge? As a leader, the ultimate decision may still be up to you, but start the decision process as fully informed as possible. At the very least, asking for input will give people ownership in the team strategy and operation. Show your intelligence by asking good questions, not making up answers.
* Tell your team when and how decisions will be made, and have it be on a predictable, regular schedule. Similarly, make sure they know when it’s time to hold questions for later. Decision time and execution time should be separate but predictable and regular.
* Keep everyone pointed forward. It’s tempting to look sideways at your competitors, backwards at where you were, or straight down at your current location. But as a leader you should keep the focus on your chosen target, encouraging discussion in that direction and discouraging diversions in the others.
* When you ask people to any meeting, ask them to tell you what they want help with and answers to. Similarly, be clear about what you want them to help you with.
* Help each person on your team be the best they can be–individually. People have a wide variety of skills, interests, and opportunities, even in the same type of job. Helping them achieve their individual potential will often seem at odds with achieving the goals you planned. But if you empower people and encourage them to grow, you’ll likely get things you never imagined possible.
* Ask people what they need to do great things. This might be tools for their work, training to become better, resources for a project, connections to other people, or time to reflect and reset. As an individual, one of the best practices I’ve found is simply asking for what you want. As a leader, make sure your people do that.
* Talk about things from others’ point of view. It’s easy to phrase everything in your terms, with your goals and milestones (“Everyone will report weekly to me”). Instead, try to explain changes and requirements from the perspective of your team–how this will change their work, or how it will help them (“Every week I will be available for reviews and feedback”).

More to come…I hope!

Vision and leadership at Pixar

From [Ed Catmull’s talk](http://www.scottberkun.com/blog/2010/inside-pixars-leadership/) at the [Economist Ideas conference](http://ideas.economist.com/):

> I do believe you want a vision, so you start off with a person who has a vision for a story. And we do things to try and protect that vision and its not easy to protect it, because they feel these pressures.

> One of the protections is the notion that they have the final say so. Now this is a very hard thing to say because we say we are filmmaker led. The reason its hard is if they can’t lead the team, we will actually remove the person from it.

> We will support the leader for as long and as hard as we can, but the thing we can not overcome is if they have lost the crew. It’s when the crew says we are not following that person. We say we are director led, which implies they make all the final decisions, [but] what it means to us is the director has to lead.. and the way we can tell when they are not leading is if people say ‘we are not following’.