May 22, 2012
Nest’s Tony Faddell on Prototyping and Getting Projects Approved

I recently attended the 99% Conference in New York, a refreshing gathering whose focus is less on the generation of ideas and more on their execution. (The conference’s name is a riff on Edison’s famous quote about the need for only 1% inspiration and 99% perspiration.) The next few posts will feature some of the highlights, with the sought-after accolade of My Favorite Speaker* going to Tony Faddell.

The former Apple designer (Faddell was responsible for the iPod) has recently been lauded for his success with the Nest “learning thermostat,” a simple-to-install device that helps people to understand how their home uses energy (and therefore set it to save.) Faddell was energetic, inspiring and utterly committed to the concept that it’s the team that makes the difference between a launch’s failure or success, not simply the value of the idea itself. And it’s clear that the curiosity he described as being present from his early youth is still an integral part of the way he does business.

Prototyping, too, is a key skill that he believes needs to be mastered by more than designers. As Faddell described, in the 1990s people would all too often come to him with a great idea for a “kitchen computer.” They’d tell him all about how it would work, how beautiful it would be and how people could use it to get recipe information. And yet, he’d reply to them:

“You understand the hardware, the screen, the internet connection… but you didn’t attack the real problem. You didn’t prototype the user experience. You prototyped the hardware to get people to say that’s cool. But you didn’t look at the hard, hard pieces of the puzzle: how will people interact? How will they get two touches on the screen? How will it work? Too often people go for the easy thing but it’s the hard thing that sets the schedule, the budget and whether it’s doable.”

His advice: “find the hardest thing… the thing you really want to change, and look deeply into that.”

I also liked his three necessary qualities for getting projects approved:

1. Passion. This includes both the passion of youth and team members but, Faddell described, what is necessary is a “thoughtful passion, not an egotistical passion.” This is about being introspective about what you’re trying to do and then communicating that effectively to the people you’re trying to get join your team or who can approve something to move forward.

2. Presentation. This isn’t merely about making something look slick, but about looking at all the details and anticipating concerns, questions or risks, especially those of importance to those outside a core team. “Make them a part of the process,” advised Faddell, and acknowledge the challenges ahead and explain how they’ll be managed. By anticipating difficult questions and having, if not answers, at least the ability to show that they’re considered, the quantiest of analysts can be brought on board an innovation project.

3. Partnership. Getting the right senior leadership on board any innovation-related project is critical, Faddell advised. If conversations are starting with questions about shipping, product numbers or return on investment then as far as he’s concerned, you’re not working with the right person who will be able to give the necessary amount of air cover to your nascent idea. Instead, make sure you’re working with people who can be emotionally and rationally engaged in an idea’s worth. They’re the folks who will help you when others raise reasonable doubts.

Finally, a lovely, honest admission of the reality of innovation and entrepreneurship. “If it doesn’t feel like a rollercoaster day, you’re not doing something right,” said Faddell. “You need to feel that doubt every single day.”

* This is not a real thing.

[Photo: Julian Mackler]

January 26, 2012

The World Economic Forum took over the ski town of Davos in Switzerland this week, sparking all the uproar one might expect from an event that attracts billionaires and global business leaders. Lots of reports coming out, including from those worried about the state of the global economy — and those, such as PIMCO CEO, Mohamed El-Erian, who suspect the forum is more talk than action. Showing social media savvy (and that she clearly learned a thing or two about to-camera reporting during her stint at NBC), General Electric CMO, Beth Comstock, has been filing video reports from her two days at the forum. Here, she sums up the critical themes as she sees them. Smart stuff.

December 19, 2011
"When we have a better-than-skin-deep understanding of technology, two things happen: We have better ideas and we also treat our internal and external partners in a considerably more effective manner."

Mel Exon, founder of BBH Labs explains why she is sending along creatives and strategists to learn more about coding. It’s a great idea. I loved this other quote from her: “I think it’s wrong when people use expressions like ‘the language the developer can understand’ and make them sound like an alien nation. It’s not an alien nation; they are human beings who have just got a particular skill set. It’s about speeding up and improving our relationships with the people who are actually writing code.” I often talk about the need for designers to learn the language of business (and vice versa), and I still think that’s a critical skill. But this is a good reminder that at the end of the day, we’re all people, and true success comes through effective relationships with one another.

December 9, 2011
"Intense psychological stress tends to shut down the part of the brain responsible for innovative, creative thought. Instead, we tend to revert to the familiar and the well-rehearsed."

What Really Happened Aboard Air France 447 is the chilling story of the cockpit conversations aboard an Air France plane that inexplicably crashed into the Atlantic in 2009. Turns out the accident wasn’t so inexplicable after all. Instead, it’s a sad story of confusion and miscommunication. Innovation projects don’t tend to have quite such high stakes (lives are rarely at risk, though millions of dollars might be) but it’s interesting to think about the conditions necessary to nurture creativity and the idea that too stressful an environment might biologically impair those looking to innovate. See also designer Stuart Karten’s piece in Fast Company about innovation’s “secret sauce” — friendship.

November 28, 2011
"Designers can’t wait to be “hired” to enhance or improve these offerings. We must be active participants at their inception. If designers are truly skilled at identifying unmet human needs and creating the breakthrough products to address those needs, then, increasingly we will need to prove our value as entrepreneurs."

I’ve been banging this drum for some time. Designers need to be able to explain why they do what they do in terms to which others can relate. Yes, business leaders need to sharpen up too, and learn to respect and trust practitioners of a profession that might just provide the keys to a sustainable future. But it’s a two-way street, and there’s a long way to go before the potholes and bumps of confusion are filled in and the tarmac of true collaboration runs smooth. (No excuse for that verbal butchery. Sorry.)

I was really confused by the U.S. myopia of the recent Fast Company issue on design, but in American Firms Now Embrace Design, But They’re Aging Fast. What’s Next? Frog VP of creative, Robert Fabricant, poses some important questions for those in the States to ponder. In particular, I liked his analysis of some of the American tech giants’ approach to design, which seems more grasping and desperate than considered and strategic. And yes, Apple, that’s you too: 

Under Apple’s influence we are watching an entire generation of aging geeks recycle their early experiences with technology as iPhone apps with the look of Pong or Blade Runner. It feels like Back to the Future. Is this the future of American Design?

November 22, 2011
"Projects tend to be judged based on how clever their name is (I’ve learned lots of exotic bird names), and that tends to correlate with how popular the stakeholder is, not with objective value nor usefulness. Many folks have left in past few months, triggering waves of FUD [fear, uncertainty, doubt — ed] within the ranks. There are plenty of turf wars, and a lot of strong personalities with conflicting views as to what the product is, how it works, and what it means."

— I don’t flag this post for its “tell-all” inside scoop on Twitter, as in fact this seems to be one of those more standard “I’m leaving, hey are you hiring?” type of notes that have become de rigeur for those in the Valley looking to send out a signal to potential future employers. But among the platitudes, On Leaving Twitter does usefully remind of the difficulties faced by companies charged with managing scale, particularly at the rate that companies such as Twitter have had to deal with it. The above stories, that projects are judged based on the cleverness of their bird-related name or the popularity of their stakeholder are surely not the whole truth, but they do sound some alarm bells. Certainly, they act as a signal that perhaps internal processes and systems aren’t yet robust enough to ensure that innovation and ideas can be brooked from all quarters internally. That’s an all-too-common problem will only get bigger as the company continues to grow.

October 28, 2011
One of my favorite presentations at Design at Scale was the conversation between Roo Rogers, president of Red Scout Ventures, and Cameron Tonkinwise, associate dean for sustainability at Parsons. By this point, we’d heard from a number of huge brands, including Frito-Lay, Starbucks and Coke. All of these were interesting in their own right, but at that point in the proceedings it’s safe to say I for one was feeling a little megabranded out. Rogers and Tonkinwise came to the rescue with a neat analysis of where we are in terms of defining a global “sharing” economy. Rogers is the co-author of the book What’s Mine Is Yours: The Rise of Collaborative Consumption, so knows of what he speaks, while this is also an area of passion for the supremely articulate Tonkinwise. I was hosting this session, so sadly don’t have notes on the many smart things that were said, though I was really taken with Tonkinwise’s challenge to the design community: Think about redesigning objects so they are specifically intended for shared use. As he pointed out, most of the objects that are currently used in the public sphere are lowest-common-denominator hideous, designed to survive nuclear attack but hardly to lift the soul or the spirit. Can’t designers come to our rescue? Please?
[Image c/o DMI.]

One of my favorite presentations at Design at Scale was the conversation between Roo Rogers, president of Red Scout Ventures, and Cameron Tonkinwise, associate dean for sustainability at Parsons. By this point, we’d heard from a number of huge brands, including Frito-Lay, Starbucks and Coke. All of these were interesting in their own right, but at that point in the proceedings it’s safe to say I for one was feeling a little megabranded out. Rogers and Tonkinwise came to the rescue with a neat analysis of where we are in terms of defining a global “sharing” economy. Rogers is the co-author of the book What’s Mine Is Yours: The Rise of Collaborative Consumption, so knows of what he speaks, while this is also an area of passion for the supremely articulate Tonkinwise. I was hosting this session, so sadly don’t have notes on the many smart things that were said, though I was really taken with Tonkinwise’s challenge to the design community: Think about redesigning objects so they are specifically intended for shared use. As he pointed out, most of the objects that are currently used in the public sphere are lowest-common-denominator hideous, designed to survive nuclear attack but hardly to lift the soul or the spirit. Can’t designers come to our rescue? Please?

[Image c/o DMI.]

October 27, 2011
GE’s Beth Comstock on What Design Can Do For Your Company

Beth Comstock also co-chaired the Design at Scale event, and she gave a 15 minute snapshot presentation on the importance of design to her in her role as CMO of General Electric. Talk about an eloquent advocate for design. Beth is someone who understands the power of design at a fundamental level, while remaining un-starry-eyed about the challenges of implementing it effectively. That involves deep collaboration from all parties within an organization. Or, as she put it, “what business needs now is design. What design needs now is to be more about business.” 

Here are seven ways she argued that design can make a difference. (I have a nasty feeling there might have been eight but I missed the last one.)

1. Design Simplifies
The last decade alone has seen an explosion in the amount of data we’re forced to try and parse on a daily basis. And, of course, things are only getting more complex. A jet engine, for instance (GE’s core business) gives off a terabyte of data. Why not harness that information to provide useful insights and do something constructive for the engine or the aviation business at large? Data visualization may be the latest, hottest thing, but when done right, by designers who really understand the meaning and implications of the data they’re visualizing, it can be incredibly powerful. “The IT dept can’t do that,” said Comstock. “That’s where you need great design.”

2. Design Solves and Surprises
Then she told a story of the design team going into a hospital operating theater to study the anesthesiologist at work, the theory being that you could hardly stop them in the course of their work and ask them to explain why they do what they do. After all, “they’re busy saving lives.” Fair point. However, the design team decided to bring in perspective from another group of people accustomed to life/death situations and being surrounded by a ton of bleeping technology: airplane pilots. Then they were able to apply the gems of insights afforded by a clear-eyed perspective to redesign the OR experience.

3. Design Creates Experiences That Matter
“It’s not enough to have the best technology,” said Comstock. “It’s how you deliver it.” She referenced the fairly well-known story of GE’s redesign of an MRI machine for children (see a video, Fun Hospital and MRI Scans for Kids.) As Bob Schwartz of GE Healthcare detailed at the recent Mayo Clinic Transform clinic, this machine didn’t just ensure a less scary experience for the children undergoing treatment, it also reduced the amount of anesthesia that had to be administered, which is a net win all round.

4. Design Integrates
At an engineering-focused company like GE, the tech teams and engineers rule. “They push the limits of science every day,” she said. What they need, however, is the ability to pull all the various pieces and insights together and this, she averred, is a role for design.

5. Design Fails
Quoting the importance of learning from failure, Comstock referenced GE’s “Hardiman,” a human exoskeleton intended to help man lift 1500 pounds. The only problem? The thing itself weighed 1500 pounds. Nonetheless, she talked of the importance of prototyping concepts and allowing ideas to sprout from unexpected places. And she quoted Steelcase’s design chief, James Ludwig: “design’s role is to create space for naivete.” 

6. Design Has to be Both Local and Global
GE gets a lot of credit for the concept of “reverse innovation,” where products are developed in an emerging market and then taken back to the developed world. As it turns out, Comstock “hates the phrase. It’s innovation as it should be” even as she acknowledges that this is an important new frontier in innovation, and an area where design can make a singular impact.

7. Design Creates a Vision for the Future
“If you can’t tell a story, you can’t sell a story,” she said, talking up the ability for design to map out a vision of what’s possible. She referenced an idea someone at GE had had for an air taxi which resulted in a joint venture with Honda to create a Very Light Jet. Turns out, someone at Honda had been thinking about trying to make cars fly, and together the design teams are working on both developing a new reality and dreaming up a potential future.

[Image c/o DMI.]

October 27, 2011
"Prototyping is a collaborative, improvisational process."

Jake Barton, founder and president of New York design firm, Local Projects, opened the two day Design at Scale conference, organized by the DMI (and of which I was co-chair.) He showed a number of the firm’s projects, including Change By Us, an idea-sharing/matching initiative launched in New York and which has since spun out to Seattle and Philadelphia„ and the BMW Guggenheim Lab, a mobile laboratory intended to “inspire innovative ideas for urban life.” He went into detail about the firm’s process, of which prototyping plays a huge part. I particularly liked his description of the design of client feedback sessions, in which the clients are deliberately left to experience the prototype on their own terms. Any hint of attempting to steer them in a particular direction, said Barton, and the dynamic can turn nasty in an instant. For more of Local Projects’ process and design approach, see also Storyteller, a feature I wrote recently for Creative Review magazine.

September 14, 2011

“Chronic disease management is a team sport.” So said Dr Sanjeev Arora at this week’s Transform conference, hosted by the Mayo Clinic in Rochester, Minnesota. Arora is an liver specialist by training, though a sideline in community healthcare has now become more than a day job. In 2002, he founded Project ECHO [Extension for Community Healthcare Outcomes] in an attempt to handle the very real problems suffered by those diagnosed with hepatitis C in New Mexico. Frustrated that he wasn’t able to do enough within his own clinic (there was an eight month waiting list while many of those with the disease were unable to travel for the many visits necessary for treatment, Arora started ECHO as an attempt to mobilize a network around a disease.

The video above gives the gist of how the program works. At Transform, Arora outlined the importance of collaboration to the new practice. Every Wednesday afternoon, a team of specialists, including doctors, nurses, nurse practitioners and the like call in from wherever they’re located to take part in a video conference. Together, they’ll co-manage the care of up to 15 patients in the course of the call. In his talk, Arora spoke the language of business, of the need to standardize best practices and channel the processes of the most streamlined organizations. Yet, he added, expert clinicians need to implement a quality that’s not necessarily a factor on Toyota’s production line: wisdom. “What makes this different from manufacturing is that every patient is different,” he said.

As Arora mentions in the video, there are now ECHO projects for diseases other than hepatitis C, though he’s also aware of the complex issues that surround trying to scale the program too aggressively. “Don’t start ECHOs for 200 diseases,” he said at Transform. “Just a few diseases account for morbidity and mortality. Do it for those.”

September 1, 2011

“This process has changed so much of the way we look at not only bicycles but also at the process of creating things.” So speaks Charles Youel of Artcrank in this video promoting the bicycle-themed poster company’s collaboration with bike manufacturer, Trek, to make a beautiful looking single-speed bike. Or, as they put it, a bike about art. Great project.

(Video via Doug Powell.)

August 24, 2011
"The big failure of social business is a lack of integration of social tools into the collaborative workflow."

The Big Failure of Enterprise 2.0 Social Business is a great piece by one who has experienced life at the social media-driven coalface. Detailing the problems executives experience when trying to integrate collaborative/Web 2.0 tools into their existing workflow, Laurie Buczek also offers some smart, common sense advice. Real issues arise when trying to tweak old-school, inflexible, legacy systems and the hardwired behaviors of multiple employees, and these should be acknowledged and dealt with upfront. Just pasting another system on top won’t work. Buczek writes:

Focus on what you can control.  Focus on creating a natural collaborative experience.  Focus on providing an easy & intuitive user experience.  Focus on dissolving collaborative islands- don’t create more with social tools. These steps can keep you from falling down the rabbit hole and staying steady on the road to realizing robust social enterprise success while you continue to tackle other longer-term challenges.

(Story via Jen van der Meer.)

July 5, 2011
"Collaboration is quite possibly *the* pivotal dynamic in generating great design results."

In The Case for Competitive Collaboration, Teague creative director Tad Toulis outlines his thesis that competitive collaboration is the means by which robust business of the future will be built. He’s not referring to the “whimsical, feel-good stuff that dissipates at the first sign of trouble” but an “all out, skin in the game style of cooperation that requires real commitment from both parties.” And he has some suggestions for thinking about the design process. Some key quotes:

If you find design problems getting easier—you are most likely repeating yourself.

Love this careful warning that with experience can come laziness or the willingness to fall back on the tried and tested. This doesn’t just apply to designers, and the ability to challenge oneself to do more, better, different every single time is a key skill in today’s marketplace.

Making is an inextricable part of good design exploration. PowerPoint is an abstraction of an abstraction. Things don’t fail quickly in abstract.

A good reminder for why designers are there in the first place. Not to aestheticize existing ideas, but to come up with new ones. That process involves trying, learning and trying again.

Schedules and meetings chew up a lot of ‘finding’ time. The design process needs distraction, a chance to open the windows and let in fresh air. When this isn’t allowed for, ideas become stilted, growing into outsized caricatures of their former selves.

This is key. Protecting the creative process, impenetrable to so many, is critical. Managers should remember that while design may be an imprecise science, it is not unpredictable, and they must have faith that their creative teams will deliver. (If they don’t, well, everyone might as well pack up and go home.)

Remember it’s not personal—it’s about doing what it takes to move the needle in earnest.

A great note on which to sign off.