metacool

thoughts on the art & science of bringing cool stuff to life, by Diego Rodriguez

Designing at the Boulder Digital Works

Bdwlogo

I'm happy to announce that I just joined the board of the Boulder Digital Works (BDW).  At this time back in 2004, I was busy helping the Stanford d.school achieve lift off, so it's really cool now to be part of another design education startup.  And now the idea of a design curriculum combining business, technology, and human issues is much more accepted in the mainstream, which to me makes the focused mission of the BDW even more exciting.

As John Maeda recently noted, the missing partner to STEM (Science, Technology, Engineering, Math) is IDEA (Intuition, Design, Emotion, Art).  As a person who was trained on both sides and now works and plays across STEM and IDEA, I feel strongly that our education programs need to combine both in order to create the T-shaped people that can go out and make a difference in the world (Principle 6).

Finally, as a native of Boulder, BDW gives me another excuse to get back to the place where I came to love and admire the fine art of driving in the snow.  Can't wait.  Hope the board meetings are in February!

19 August 2009 | Permalink | Comments (1) | TrackBack (0)

| |

Brad, Conan, and me

What do us three hunks have in common?  The answer is easy and natural:  we're all (former) proud owners of a Ford Taurus SHO. 

Mine was an 89 with a chalky black finish.  A good car with a fabulous, fabulous motor. The best device ever conceived by mankind for laying some patch.  On a cold Oregon winter highway, in the dark and in the wet, I could shoot huge rooster tails of sparks out from the slipping studs of my winter Michelins on steel wheels.  Oh, the romance.

Sadly, the Taurus brand isn't what it used to be.  Years of being the default choice of rental agencies will do that to your brand equity.  And at a personal level of branding, to admit in public that you loved an SHO is something akin to admitting that you used to play with GI Joe dolls. But hey, it's all true.  I'm not afraid to say that I loved driving my SHO, and I hated parting with it.  The day the truck came to my house to take it away, I made sure I was away for the afternoon so that I didn't have to be a witness to the act.

At what point do you release yourself from brand snobbery and just live your life, do what you want, buy what you want, consume what you want when you want?  Hopefully one of the outcomes of this big economic reset will be a relaxing of our emphasis on brand value, with a shift toward intrinsic value. I think there will be more freedom to be you and me, with more acceptance of those of us with strange tastes or less appetite for consumption (I drove my SHO for 12 very good years -- and only one clutch).

I mean, look how happy Brad looked as he peeled out in his new whip.  Isn't that what it's all about?

14 August 2009 | Permalink | Comments (1) | TrackBack (0)

| |

17: It's not the years, it's the mileage

If you're going to reach innovative outcomes on a routine basis, you need to match the right team to the opportunity.  Part of that means understanding Principle 7 so that you know what type of problem you're tackling, the other part involves understanding what kind of experience you need on your team. 

When it comes to answering that last question, the right kind of experience profile depends on whether you're looking at a high or low variance situation.  Examples of low variance situations are flying a 747 from San Francisco to Singapore, operating on a heart, or serving up burgers at In-N-Out.  In each of those situations, we desire a predictable outcome delivered with a low degree of variance from a predetermined standard, and in this context, the right experience is expressed in terms of having done the same thing many times before.  We want a pilot who can fly the 747 on, well, autopilot.  We want a surgeon who has done hundreds of the same operation, and learned something from each one, not a surgeon who has done one hundred different surgical procedures once.  As such, experience is really about tenure in a role, with relevant experience having a direct correlation to years in the role.  

In a high-variance situation, where we are expecting an innovative outcome, but have little to no sense what the right answer might look like, we need a different definition of what "experienced" means.  In this context, we want people who are experienced with the process of innovation -- in other words, people who have gone through the "understand - build - test" cycle of Principle 4 many times.  We want folks with a lot of mileage under their belt, in other words, but that mileage need not be strictly correlated with years at work. 

For example, one of the reasons why Honda cycles its production engineers through its various racing programs is to increase their innovation process mileage; designing a new component for a mass market automobile takes several years, so between the time an engineer graduates college and turns 40, they may have only shipped three to four designs to market (if they're lucky).  Contrast that with a race engineer, who faces the challenge of optimizing a race car for a different track configuration every two weeks for eight months, as well as managing an arc of innovation for the entire car over those same eight months.  During that short period of time, they may experience 10, 15, even 20 cycles of "understand - build - test".  So when it comes to picking an engineer to go figure out the future of mobility, which one would you choose, the "I've shipped the same thing to market three times" person, or the "I've done 20 cycles every year for the past  four years" individual?  By my reckoning, in this world an engineer age 26 could have 20 times the relevant process experience as a person 14 years their senior.

Mileage really does matter when it comes to understanding the art and science of bringing new stuff in to the world.  Many of the hottest Web 2.0 apps are springing from the agile fingers of lads barely past drinking age who are in fact hoary veterans of the coding wars, having been engaged in hacking kernels since they were eight.  They have a tremendous amount of relevant mileage under their belt, and have a skillset that's perfectly tailored to the nimble world of innovation on the interwebs.

I'd like to propose a metric for assessing the innovation prowess of an individual or of a team.  It looks like this:

innovation experience index =  [market ships] / [years of practice]

In other words, how many innovation market ships have you experienced over a given period of time?  And of those, what's your profile for incremental innovations?  For revolutionary innovations?

It's all about mileage.

This is number 17 in a series of 21 principles of innovation.  I really welcome your feedback, questions, and ideas.

12 August 2009 | Permalink | Comments (4) | TrackBack (0)

| |

Joi Ito on innovating with agility

Awesome post from Joi Ito today, talking about innovation process and government policy.  An excerpt:

Generally speaking, it's probably cheaper and faster and more effective to make a prototype than to make presentation deck. It's also probably easier to test something on real users than to do lots of marketing and guessing. My recommendation to just about anyone with an idea is to just build the thing, iterate until you have some user traction, then pitch angel investors based on that traction. This is very much in line with the old IETF motto of "rough consensus, running code."

Joi's thinking is well worth a read (us usual, I'm not telling you anything new there).

When it comes to innovation principles, I'm a bit of a wooden stake looking for vampires these days, but in Joi's thinking I see the following at play:

  • Principle 4
  • Principle 9
  • Principle 10
  • Principle 15
  • Principle 17
  • Principle 21

Speaking of which, I need to heed my advice and ship the last set of principles.  Now.  I'll get on it.

11 August 2009 | Permalink | Comments (1) | TrackBack (0)

| |

Who designed the Porsche 917L Martini "hippie" car?

1893544329_9f2c410dfb_o

This Porsche raced at Le Mans in 1970 and captured my imagination as a boy like no other race car.  Beyond being a member of the ultra-gnarly 917 family of Porsches, this car sports a paintscheme like no other.  Campaigned under the brand umbrella of Martini, those iris swirls were as arresting then as they are now, and are what lended this particular car the sobriquet of "hippie". 

It's a beautiful design that's stood the test of time, and I'd wager it is a flexible one, too; if this pattern were printed on the side of resuable shopping bag from Whole Foods, none of us would bat an eye.

Here's where I need your help: I know that the design team behind the hippie graphics was headed by Anatole Lapine.  Somewhere in the cobwebs of my memory I have a vague recollection of reading that a member of his design team was a graduate of the Stanford design program.  If you have any information about this, could you please send me an email or leave a comment below? Design mysteries are few and far between, and this is a fun one.

By the way, it's Porsche Week over at Unabashed Gearhead Gnarlyness.

photo credit: Kelzone

10 August 2009 | Permalink | Comments (0) | TrackBack (0)

| |

Deep Glamoring...

6a00e553bc525688340120a4c85820970b-800wi
I just posted a piece over at DeepGlamour:

Top 10 Most Glamorous Cars, 1945 - present

I have a feeling not everyone will be happy with my opinions, so please don't slash my tires.  But don't fret, there's no M Coupe on the list. 

Let the debate begin!

05 August 2009 | Permalink | Comments (3) | TrackBack (0)

| |

Maira Kalman on the American Message

As far as this art and science of bringing cool stuff to life thing goes, Maira Kalman really nailed it in today's NYT.  You have to see it all.  It's the triple distillation of pure awesomeness.  Here's a quote:

Everything is invented.
Language.  Childhood.  Careers.
Relationships.  Religion.
Philosophy.  The future.
They are not there for the plucking.
They don't exist in some
natural state.
They must be invented by people.
And that, of course, is a great thing.
Don't mope in your room.
Go invent something.
That is the American Message.
Electricity.  Flight.  The telephone.
Television.  Computers.  Walking on
the moon.  It never stops.

I simply love what she's created here and am totally inspired.  Many thanks to my friend (and great innovator) John Lilly for pointing me to this.

Have a great week, everyone.  Go make a dent in the universe.

And no moping!  Always ask yourself, "What would Travis do?"  Just do it, that's what.  JFCI!

02 August 2009 | Permalink | Comments (2) | TrackBack (0)

| |

metacool Thought of the Day

"The next time you see somebody driving a Ferrari, don't think this is somebody who is greedy, think this is somebody who is incredibly vulnerable and in need of love.  In other words, feel sympathy, rather than contempt."
- Alain de Botton

31 July 2009 | Permalink | Comments (2) | TrackBack (0)

| |

Hyundai is the New BMW

Yesterday's announcement by BMW that it is leaving Formula 1 as part of a brand repositioning focused on sustainability and viability leaves a market niche open for driver's cars. I actually agree with BMW's move based on long-term societal trends, but for the next 5-10 years I think the "Ultimate Driving Machine" niche will still exist and be a profitable one.

So in to the market vacuum left by BMW, I hereby nominate Hyundai as its successor. If you are laughing at that suggestion, take three minutes to watch this inspiring video of Rhys Millen setting a new Pikes Peak hill climb record in his Hyundai Genesis (albeit a modified one):


Great performance brands are forged in the heat of competition. Hyundai, your forge master is Millen.

30 July 2009 | Permalink | Comments (1) | TrackBack (0)

| |

My favorite new web destination

The Book Seer

Metacool The Book Seer

I really like this site.  From a functional perspective, it doesn't do anything that Amazon doesn't try and do for me.  Based on a knowledge of what I've read, it dishes up future reading suggestions:

Metacool Book Seer result

The list of book recommendations it cranked out here is very good, almost as good as what Amazon would dish up, because it does in fact use Amazon to generate the list of books to be read (though unlike Amazon, The Book Seer doesn't know that I already have three of these in my possession, especially the last one by Jeff Zwart, which is particularly gnarly and a treasured part of my stash.  But I digress).

The difference for me lies in the beard.  That beard.  Oh my, what a beard!  The kid in me just can't get enough of typing words in this gent's mouth and having him soothsay a future arc of literary interactions.  It's so Monty Python, so retro yet right here, so not Web 2.0-ish.  At the end of the day, The Book Seer makes me feel good by injecting a little dose levity and eccentricity in to my week, and one could do a lot worse than that.  By comparison, Amazon is cold and clinical, and is always trying to sell me something.  Helping me find a good book in a fun way feels a lot better than being on the receiving end of multple cross-sell offers crammed down my throat.

It's a great example of Principle 3 in practice.

28 July 2009 | Permalink | Comments (0) | TrackBack (0)

| |

What's up with those principles, and a request for help

Diego Rodriguez metacool Principle

Over the past few months I've been writing up a series of 21 Principles.  We're now 16 principles deep, with more to come soon.  The feedback I've received so far has been very helpful, and has helped to push and improve my thinking in multiple dimensions (that would be Principles 4, 5 and 8 at work).  For those of you new to metacool, I have a running roster of these principles on the right side of this blog window.

These principles are intended to underpin a general theory of innovation.  They are not meant to be principles of design thinking, though some of them are obviously closely related to the theory and practice of design thinking.  Inspired by the simplicity work of my friend John Maeda, I'm trying to figure out what I think and know at this point in my life when it comes to all things innovation.  Hence my working through these principles in public in a messy kind of way (that would be Principles 9 and 10, with a little dash of 14).

So here's where I need your help, in triplicate:

  1. What is missing?  When it comes to innovating, what situations or dynamics or practices have I not touched on yet?
  2. What is wrong?  How am I being dumb, silly, foolish, pigheaded, idiotic, unintelligible... and just plain wrong?
  3. What resonates?  What matched up with something you've experienced in your life?  And if it did, would you be willing to share your story with me?

Please leave me a comment or shoot me an email. 

As always, thanks for all your help and for the conversations!

21 July 2009 | Permalink | Comments (4) | TrackBack (0)

| |

metacool Thought of the Day

"In business, it's not how many ideas you have.  What matters is how many ideas you translate into products and services."
- Henry Chesbrough

20 July 2009 | Permalink | Comments (0) | TrackBack (0)

| |

Jacek Utko and Principle 3

Here's a great view in to the design process of Jacek Utko.  He's managed to take things that are "dead" and turn them around so that they're remarkable, moving, and cool.

I'm always amazed by people who are able to take a moribund category and turn it in to something wonderful.  There are so many examples of this in action in our world:

  • selling commodity products:  Zappos
  • helping people eat when they don't have time to cook:  Dream Dinners
  • financial planning and tracking:  Mint

And so on. 

What ties of all of these together?  As you can hear from Jacek Utko's talk, it's all about a commitment to really living Principle 3.

17 July 2009 | Permalink | Comments (2) | TrackBack (0)

| |

Running with your innovation radar on

I really dig this interview that Helen Walters recently conducted with Alan MacCormack.  In it, MacCormack uses the metaphor of a radar system to express a way of viewing the world that is quite consistent with behaviors I've seen expressed on a repeated basis by creative individuals and innovative organizations alike.

I particularly like his emphasis upon establishing "innovation radars" to tap in to high-variance information streams that will help you see and understand what is coming next.  For example, MacCormack talks about taking R&D funds and spending them on external organizations via mechanisms such as research grants.  In that example, the notion of information streams comes to play not in the grants themselves, but in the array of grant applications you'll receive as a result of announcing that you're giving money away; the resulting stack of applications allows you to see future trend patterns emerge without having to leave the office.

In his book Weird Ideas that Work, Bob Sutton expresses a similar idea when he suggests using job interviews as a way to gain new information about how the world is working.  Imagine the difference between viewing a lineup of ten job interviews with prospective employees as a task to plow through and seeing each of them as an opportunity to learn something new from a (potentially) interesting person.  All of this is about finding creative ways to put Principle 1 in to action.

I was extremely fortunate to spend four semesters studying with Professor MacCormack at business school.  I learned a tremendous amount from him, and consider Alan a leading researcher in the world of bringing cool stuff to life.  He's a true guru of innovation, and I'm always inspired by his insights.

16 July 2009 | Permalink | Comments (0) | TrackBack (0)

| |

Leading from behind

BusinessWeek just ran a good article about Mozilla's development process for Firefox.  As readers of metacool know, I'm a big fan of Mozilla, and look to them as a living example of many of the organizational trends that will become more widespread over the coming years.

I particularly like the idea of "leading from behind" mentioned in the article:

How Mozilla channels those efforts is a model for a growing number of companies trying to tap into the collective talents of large pools of software developers and other enthusiasts of a product, brand, or idea. "There's structure in it," says Mike Beltzner, who runs Firefox. "But at the same time you allow people to innovate and to explore and [give them] the freedom to do what they want along those edges—that's where innovation tends to happen in startling and unexpected ways."

At Firefox, Beltzer calls it "leading from behind." His team makes only the highest, direction-setting decisions, such as the date each new version of Firefox has to ship. It's up to Mozilla staff and volunteers to meet those deadlines through a process of identifying specific tasks that need to be done and accomplishing them. A system of recognition has formed among volunteers, who can be designated as "module owners" and given authority over certain areas, such as the layout.

Mozilla is a wonderful example of Principle 12 in action.

02 July 2009 | Permalink | Comments (0) | TrackBack (0)

| |

Once, and the triumph of heuristics

On a friend's suggestion, I just watched the DVD of the film Once.  I really liked it.

It's a musical.  A musical!  But not in a South Pacific kind of way, with big production values and mountains of dollars behind each scene.  Rather, the music is just there, and it is written and performed by the actors.  I found the result incredibly moving and poignant, and meaningful in a way that a slick, over-thought production could never be.  There's such value to be had in taking talented people and letting them do their thing, and taking what they do on the spot and accepting it for what it is.  Not perfect.  Not probably as good as it could have been on paper, but unique and meaningful in a way that would be impossible to replicate any other way.

Artful.  Authentic.  Inspiring.

For me this is important because I'm increasingly wary of the over-intellectualizing of things and processes where talent should in fact reign supreme.  If the results are good, why try and distill out an algorithm?  Heuristics rule, man. 

You know, at the end of the day, most good stuff happens because someone good and talented sat down and worked really hard and kept on trying even as things kept breaking.  Brilliant marketing schemes are the result of hard work.  Innovative business models just happen... by being in beta over and over and pounding away.  Heuristics rule.  And sometimes you just get lucky. 

I'll bet on luck and talent any day.

01 July 2009 | Permalink | Comments (2) | TrackBack (0)

| |

More on teams...

30 June 2009 | Permalink | Comments (0) | TrackBack (0)

| |

16: Grok the gestalt of teams

If you're going to get innovative stuff done in the world, odds are you're going to do it with other people.    If you haven't looked out the window lately, we're living in an ever more connected and interdependent world.  If there ever was a time for lone inventors to thrive, this is not it:  smart, action-oriented, high-EQ, multidisciplinary, interdependent teams are uniquely positioned to take on the broad, systemic challenges so in need of innovative thinking today. 

So if you're going to do remarkable stuff, you've got to learn to grok the gestalt of teams.

There's an entire literature on effective team roles and dynamics that I won't go in to here, but based on all my years of battling on the front lines to bring new stuff in to the world, here are a few of my favorite insights in to behaviors that make for exceptional teams:

  • Build it out of T-shaped people:  an effective innovation team is composed of people who are really good at what they were put on earth to do, but also share a common way of getting things done in the world.  We want depth: an engineer needs to be an engineer's engineer, and we want the MBA to be capable of unlevering a beta in her sleep.  But we want breadth, too.  We need them both to not only get along, but to thrive in a symbiotic relationship centered on getting stuff done.  In my experience, what adds that breadth to a team is a group of individuals who are versed in the ways of design thinking. 
  • Know thyself, and let everyone else know, too: a high-performing team is no place for posturing or secrets.  If you're good at something, we want to know so that we can you let you be the lead on that.  And if you're not so good at something, we want to know that too so that we can help you get better, or keep you from wasting time on that front.  The way this happens is for individuals to be proactive about disclosing this information through the course of the life of a team.
  • Be friendly, because the networked world is your oyster:  imagine how powerful your small team could be if it were part of a vast network of experts and people wanting to contribute to your success, if only you'd ask.  Well, guess what?  Via the marvels of modern technology, you're already there.  Need someone to hack some code?  How about a coder in Bangladesh?  Need an expert on nanotubes?  Find her on Twitter.  Need some help with that marketing plan?  Why not befriend that VP that occasionally strolls by your team space?  The network your team needs to hit the remarkable zone is already there waiting to be asked.  Be friendly and invite those folks in.  Because they want to be on the team, too.

These are only a few points.  What matters to you when it comes to being part of an effective innovation team?  I'd love to hear.

As the cliched saying goes, "there's no 'I' in team"  (and you never want to be at the receiving end of the saying "there's no YOU in team", but I digress...), so get out there and grok the gestalt of teams.  Be the team, good things will happen.

This is number 16 in a series of 21 principles of innovation.  As always, your comments, thoughts, and ideas are most welcome.

29 June 2009 | Permalink | Comments (1) | TrackBack (0)

| |

The Twitter thing...

I've started using Twitter again.  I first began using it about two years ago, but did not manage to make a habit of it.  But now I'm back on, and I'm really on.

I'm hoping that my Twitter stream acts as an extension of what already goes on here when things are running right at the metacool blog.  I promise I won't use it to update you on the type of breakfast my dog just ate (I don't have a dog).  I guarantee you I will focus on the art and science of bringing cool stuff to life, because at the end of the day all of this material has to come from somewhere, and I only have one brain to offer up (on a good day).  Compared to this blog, my Twitter stream will be more concise, more cryptic, less considered, and will arrive on a more frequent basis.  It will also be made up of a lot more questions than answers as I poke around for insights in an extroverted kind of way.

I hope you can come along.  On the right side of this screen you'll find a new readout of my Twitter activity. 

On Twitter you can find me under the name... metacool.

19 June 2009 | Permalink | Comments (1) | TrackBack (0)

| |

metacool Thought of the Day

"What is it that confers the noblest delight? What is that which swells a man's breast with pride above that which any other experience can bring to him? Discovery! To know that you are walking where none others have walked; that you are beholding what human eye has not seen before; that you are breathing a virgin atmosphere. To give birth to an idea -- to discover a great thought -- an intellectual nugget, right under the dust of a field that many a brain -- plow had gone over before. To find a new planet, to invent a new hinge, to find the way to make the lightnings carry your messages. To be the first -- that is the idea. To do something, say something, see something, before any body else -- these are the things that confer a pleasure compared with which other pleasures are tame and commonplace, other ecstasies cheap and trivial."

- Mark Twain, Innocents Abroad

18 June 2009 | Permalink | Comments (3) | TrackBack (0)

| |

How will it look through time?

I love this video because of the way it illustrates the necessity of considering the passage of time as we think about bringing new things in to the world. How will it look through the day? How will it look after 10 years? 20? 50? 200? How might future generations feel about the work we've done today?

As this video aptly shows us, Philip Johnson considered these questions in the design of his Glass House. For me, this is further validation of the importance of Innovation Principle No.3.

08 June 2009 | Permalink | Comments (1) | TrackBack (0)

| |

Once again, why having a point of view matters

Metacool_neverbarefoot

For an wonderful example of why it is so important to have a distinct point of view when one is trying to bring something new to life, look no further than this: 

Never barefoot

It's a daily dose of chutzpah, wit, and inspiration.  The depth and breadth of expression to be found in the design of something as familiar as a pair of shoes provides this challenge to all of us:  couldn't that thing you're doing be made even just a little better or more meaningful?  Why keep doing the same thing without first asking why?  Why look like everything else on the market?

07 June 2009 | Permalink | Comments (0) | TrackBack (0)

| |

15: Celebrate errors of commission. Stamp out errors of omission.

When we attempt to bring new things in to the world, we will make mistakes and screw things up.  That, along with death and taxes, is a certain thing.

So, for individuals trying to make a difference, or for organizations trying to be innovative on a routine basis, a fundamental question must be asked and answered:  do we want to reward smart thoughts in the absence of action, or do we decide to celebrate the act of trying, even when it takes us to places of failure?  I say that we need to err on the side of errors of commission.  Doing must be more weighty than thinking or talking.

In the words of Bob Lutz:

Errors of commission are less damaging to us that errors of omission... taking no risk is to accept the certainty of long-term failure.

Obviously we need balance, and not everything can be about charging in and apologizing later.  It's good to listen to what the world is telling you and course correct as you go.  But a bias for action, and ways of rewarding action and penalizing inaction, will lead to remarkable things happening over time.

We must celebrate (and learn from) errors of commission and stamp out out errors of omission. 

This is number 15 in a series of 21 principles of innovation.  Your feedback is most welcome.

04 June 2009 | Permalink | Comments (1) | TrackBack (0)

| |

Leading tribes, cultivating movements, part II

Julia Kirby of Harvard Business Publishing has just written a lovely post about the Stanford d.school CIA team behind the push to turn part of downtown Palo Alto in to a pedestrian zone.  It's titled Starting a Movement, Learning to Lead.  Here's an excerpt:

So you tell me: is Creating Infectious Action a course in leadership? To be sure, it doesn't focus on individuals' leadership journeys. There's no competency model at its heart. But what is leadership all about if not creating a vision of something different and better, getting people excited about it, and mobilizing everyone to cooperate in accomplishing it? If you can go out there and create infectious action, I'm inclined to call you a leader. And if you can't, you probably shouldn't call yourself one.

I asked Captain Hughes what he'd do next with the toolkit he gained in Creating Infectious Action. Beyond Palo Alto and pedestrians, would the course have a lasting impact? "I've always said that if I ever get to be a General, I would definitely change a few things," he mused. Like anyone down in an organization, there were some procedures and policies--like aspects of the Army Physical Fitness Test--he thought were downright silly. "But now I think maybe you don't need to be a General," he said. "You just have to get a little movement going. Then you start getting people on board."


As I wrote in my post about Seth Godin's recent talk at TED, you can't manage a movement, but you can lead one, even cultivate one.  So yes, Creating Infectious Action is a course about leadership, where leading looks a lot like cultivating a garden. 

Man, what a great team.  This makes me so happy.

01 June 2009 | Permalink | Comments (1)

| |

metacool Thought of the Day

CIMG5723

26 May 2009 | Permalink | Comments (0) | TrackBack (0)

| |

Please help us kill gas in Palo Alto! CIA 2009!

8794709

A student team from our Creating Infectious Action (CIA) class at the Stanford d.school needs your help:  they are trying to create a movement to transform part of downtown Palo Alto in to a pedestrian zone.  Here's their idea:

Imagine this: University Ave-- from High to Cowper-- transformed into a pedestrian-only urban park complete with outdoor restaurants, street performances, community events, trees and gardens, and bike-friendly infrastructure.

This Initiative seeks to do more than just block University Ave. We aim to tear up the road and create a unified and truly beautiful community space. Cities all over the nation and Europe demonstrate the success of Pedestrian Malls. They revitalize business, encourage alternative transportation, and reinforce a sense of community. It's an all-win situation.


I like how this team has used the design thinking process to end up with the creation of this movement as a goal.  Given a short but sweet design brief to go "Kill Gas", this team spent a lot of time hanging out with business owners, store workers, and citizens on the street in downtown Palo Alto.  They prototyped various solutions, and kept learning as they went.  They ended up with several very interesting design directions, and picked the pedestrian-only urban park as the way to go.  I think they were wise, for two reasons. 

First, this direction, executed well (which we'll see -- the quarter isn't over yet!), has strong potential to knock it out of the park across what I consider to be the three key principles behind creating infectious action:

  1. create a remarkable offering:  a pedestrian-only zone in Palo Alto!
  2. weave sticky stories around the offering:  "tear up the road and create a unified and truly beautiful community space"
  3. identify communities receptive to points 1 & 2, then light some small fires, and then spend time pouring gas on those fires:  this is where you come in

Second, I think a pedestrian-only zone in Palo Alto would be a Good Thing.  I grew up in Boulder, where part of Pearl Street was transformed in to a pedestrian mall when I was a kid.  A few decades later, it's still the beating heart of the town, a fun place to be in touch with the community.

Here's where they need your help:  if they can gather 1,000 pledges of interest by May 27, a former mayor of Palo Alto will take their multi-stage implementation plan before the city government.  As I write this, they have 883 887 supporters and four days to go.  It would be awesome to see them blow through the 1,000 barrier in a big way. 

If you would like to support this team and their cause, you can do it in one of the following ways:

  1. Join the Facebook group Palo Alto Pedestrian Mall
  2. You can sign their online petition here
  3. Or send a text message to: 67463

Last but not least, please print out this flyer and stick it on your front lawn or in the back window of your car.

Thanks for helping this remarkable movement catch on fire!

If you use Twitter, please consider tweeting this blog post to help spread the word!  And if you blog, a post mentioning the movement would be much appreciated!  Mahalo.

4889975

23 May 2009 | Permalink | Comments (0)

| |

14: Failure sucks, but instructs

Since you will fail when you take on the challenge of bringing something new in to the world, it's useful to adopt the mantra of "Failure sucks but instructs".  Repeat that mantra a few times, and then hark back to Raney's Corollary:

"you only learn when things start breaking"

None of us want to fail.  But when we do, we have a choice to make:  we can choose to learn from the failure, or we can choose to avoid dealing with what the world is trying to tell us.  Time and time again, history shows us that innovators who get stuff done are also the ones who best learn from their failures, which may be legion.  Think James Dyson cranking out thousands of vacuum cleaner prototypes, the Wright brothers crashing their kites and gliders over and over, and even the rational marketers at Amazon hypothesizing and testing across multiple web platforms each and every day.   Each is a lesson in the power of success driven by cycles of failure coupled with learning.

Failure sucks, but instructs.  The wisdom is out there.  Can you accept it?

This is number 14 in a series of 21 principles of innovation.  Your feedback is most welcome.

20 May 2009 | Permalink | Comments (0)

| |

Paul Bennett & Egill Helgason on design thinking, Iceland, the future of the world economy, and a whole bunch of other important topics

I'd be posting these videos even if Paul Bennett and I weren't colleagues at IDEO, so rich and fascinating is this conversation between Paul and Egill Helgason, the host of the Icelandic show Silfur Eglis.  Design thinking is a central theme of their time together, and they touch on many important topics of the day, including transparency, community, and how we might move ourselves out of this mess.  It's definitely worth a listen.

And don't worry -- it's all in English!  Enjoy.

19 May 2009 | Permalink | Comments (1)

| |

Innovating under our noses

I saw two cool things today which renewed my faith in the ability of us all to innovate anywhere.  There are tons of things right under our noses which would benefit from a rethink.  Today's examples come from two organizations that usually go by their three initials.

The first is Apple's brilliant rethink of "banner" and "skyscraper" ads in the online version of the New York Times:

Metacool Apple NYT ad

In these ads, the PC and the Mac guys on the right interact with the Apple Customer Experience banner on the top, and then with the bald guy from the Sopranos in the "Hair Growth Academy" ad on the left.  It's funny, witty, clever, and catchy.  And it's the first web ad I've clicked on in, well... forever.  It's a nice example of an incremental innovation, and I'd love to see the resulting web metrics.

The second piece of inspiration is the Intern Auction being held by Crispin Porter + Bogusky on eBay:

!BSm4bFQBGk~$(KGrHgoOKisEjlLl5Pu2BKEFIhWvTg~~_1 

Not only is it a fun way to raise awareness of CP+B's intern program, but it also provides a market check on the value of an internship to clients.  Just to be clear, the auction is to buy the services of the intern, not to buy the internship itself.  I wonder how much more the internship would sell for in that latter mode?

Thanks to both the NYT and CP+B for an making this an inspirational Monday.

18 May 2009 | Permalink | Comments (3) | TrackBack (0)

| |

Leading tribes, cultivating a movement

This is the second of my favorite talks coming out of this year's TED conference.  Seth Godin takes us through his ideas about leading tribes.  I think he does a fabulous job of describing a different way of leading, a way that seems like the perfect fit to our highly networked, interconnected, and (potentially) interdependent world.

His three questions at 14:15 are priceless.

You can't manage a movement.  But you can lead one, even cultivate one.  Don't be a sheepwalker -- try and lead the tribe that matters most to you.

12 May 2009 | Permalink | Comments (0)

| |

metacool Thought of the Day

I saw this video clip earlier this week. I love it.

In it I see the following principles we've been discussing over the past few weeks:

Principle 1: Experience the world instead of talking about experiencing the world

Principle 6: Life life at the intersection

Principle 8: Most new ideas aren't

09 May 2009 | Permalink | Comments (1) | TrackBack (1)

| |

13: Do everything right, and you'll still fail

Odds are your innovation efforts will fail.  Bummer.  Big, big bummer.

It's tough to bring something new in to the world.  Your chances of survival improve with a process informed by design thinking, but it's very likely some key factor -- across desirability, viability, or feasibility -- will not quite be there, and things will go pear-shaped. 

This doesn't mean we shouldn't try to win, to make things happen.  Quite the opposite: because the odds are so low, it means working even harder, pushing as much as you can to get things right.  I don't know about you, but I really hate failing.  It feels bad when it happens from a big-picture point of view; I have no problem with a prototype failing (that's a good thing, per Raney's Corollary), but I loathe the idea of something failing at a systemic level.  Yuck.

But acknowledging that failure is a likely outcome enables us -- if we work with the end in mind -- to make a leap to a more productive state of being.  That state of mind is the focus of Principle 14.

This is number 13 in a series of 21 principles of innovation.  Your feedback, ideas, and comments are greatly appreciated.

07 May 2009 | Permalink | Comments (1) | TrackBack (0)

| |

12: Instead of managing, try cultivating

Leading people to innovative outcomes has much more in common with the successful cultivation of gardens than it does with traditional, top-down, centralized, command-and-control management techniques.  Whereas the later is concerned with efficiencies, coping with scarcity, and always being on top of things, cultivating is about embracing variance, abundance, and the idea of living at the bottom of things.  A leadership model based on a cultivation mindset can be found in the following four defining behaviors of cultivators of innovation:


1) Being at the bottom of things

Flourishing gardens come from being at the bottom of things. Instead of pursuing the traditional management goal of being on top of things -- with the lucrative by-product of being at the top of things -- the leader-as-cultivator makes it their job to live simultaneously at the bottom and in the middle and on the edges, dealing with things that might seem like plain manure to outsiders. 

It's not lonely at the bottom. The bottom can be a messy place, but it is the wellspring of success when it comes to fostering creativity. With plants, as with people trying to act in creative ways, you can't tell them what to do, but you can try to support what they need to do, matching essential resources to tasks at hand. This is not traditional, I'm-the-heroic-boss leadership. Instead, the creative cultivator takes satisfaction from tending to the health of the overall garden, and wisely leaves the kudos for smelling great and looking good to the roses.


2) Trusting what is there

Creative cultivators trust what is there. A wise cultivator resists the temptation to "dig up the seed as it is growing", as it were, to check if people are being creative enough. Many breakthrough innovation initiatives are stifled by linear project timetables more appropriate to incremental efforts. The paradox of cultivating innovation is that confidence in outcomes is itself an enabler of innovation; a wise gardener knows that roses are the best authorities on the creation of rosiness, and until they bloom, only checks in to see if they need more food and water. Furthermore, creative cultivators trust that the right answers -- though not necessarily the ones they would have thought up themselves -- will emerge from their gardens. So much about what makes a creative organization tick is tacit; it is about what's there and what it creates in an emergent way, rather than what a few brains wish to have happen via explicit processes and goals.


3) Embracing the ecosystem

By their nature, gardens are part of larger ecosystems. Healthy gardens readily accept inputs from the outside world.  Rain, seeds, nutrients, soil: we needn't worry where they come from, we just care about their integrity and how they help us grow good stuff.  Encouraging variance -- the generation of weird or unexpected ideas -- is a key goal for someone cultivating a creative culture. Anything that encourages variance through the cross-pollination of ideas from outside sources (very much the function of bees) should be reinforced. And as we're sadly seeing out in the world, gardens without the benefit of bees soon stop producing.

Thinking about the long-term health of all stakeholders in an ecosystem is also a signature act of a cultivator. Innovating is a long-term endeavor and requires a great deal of patience, investment, and fortitude. Actions that value short-term productivity over the long-term health of the garden and its larger ecosystem are not conducive to lasting success.


4) Taking a bird's eye view

Finally, creative cultivators do all of the above while simultaneously curating the garden from a bird's eye view. Managing a portfolio of creative endeavors requires knowing how many plants a certain piece of land can support and then pruning or culling as need be.  As Principle 9 states, sometimes you have to prune (or kill) ideas and projects.  Doing the most with the resources at hand, listening to what works and what doesn't, and guiding growth to be something unique and wonderful – that is the essence of strategy, and of gardening as well. Most importantly, by taking a bird's eye view, a creative cultivator creates the context for plants to grow in accordance with a strong vision of how the garden should evolve. In organizations, this means having points of origin that can inspire individuals to be creative in certain ways, and not others, and to innovate in the right directions.

Taken together, these four ways of leading should help innovations flourish.  Instead of trying to manage innovation, we must move to a model of leadership that's all about cultivating it.

This is number twelve in a series of 21 principles.  Your feedback is most welcome.

06 May 2009 | Permalink | Comments (2) | TrackBack (0)

| |

11: Everyone needs time to innovate

Given all the challenges we face in the world, we need to everyone to innovate.  Everyone is potentially creative and able to bring something new in to the world.  The idea that there two types of people: "creatives" and everyone else, is but a myth, albeit a damaging one at that.  Up and down an organization, everyone needs time to innovate.

If you're sitting at the top of an organization, or in a position with a high degree of gravitational pull, you need time to innovate.  To get the most out of it, your time spent innovating should take the form of helping other people grow and setting things up to be successful.  Your innovations will deal with setting the stage in the right way for the right things to happen, and with architecting systems, teams, and structures so that appropriate behaviors emerge given the innovation challenge at hand.

If you're working on the front lines of an organization (where some might describe you as being at the "bottom"), you need time to innovate.  Because you are doing the critical work of the organization, you're the most in touch with the people who benefit from its offerings.  You can use the tools of design thinking to start making a difference today in how you make those people feel.  Figure out what they need that you're giving them, make some prototypes, and start testing them.  Cycle though that and improve the way things get done.  It takes time, but the potential benefits are enormous.

Note well that I'm not saying that everyone should be creative all the time.  Far from it: we need people to be executing when they should be executing.  Land that 747 safely, mend that broken leg, receive that shipment of returned goods, and file that tax return.  But for the critical questions of how, let's give everyone more time to make it all better.

This is the eleventh of 21 principles.  I really do appreciate your feedback and ideas.

04 May 2009 | Permalink | Comments (0) | TrackBack (0)

| |

10: Baby steps often lead to big leaps

When operating in the realm of the blank sheet of paper, where assumptions about how things might work outstrip the things you know will work, baby steps are a way to learn your way to success.  Granted, a big leap can also get you to your end goal, and will do so very quickly if you're lucky, but a leap into the darkness is very likely get you hurt.  Smaller steps allow you to assess the best path forward as you move forward, recognizing that for trailblazers, the path is of your own design. 

Baby steps are appropriate at the start, middle, and end of things.  This applies equally to individuals, teams, and entire organizations.

As obvious as it may seem, starting something is essential to its completion.  But often times people can't accept the challenge in front of them, and so they find myriad ways to avoid doing something:  budget reviews, scoping meetings, taking sick time, eating pizzas, buffing that feature on your last project, surfing Facebook... all fine ways to delay dealing with reality.  By taking a huge problem statement and breaking it in to smaller chunks, baby steps make it easier to get going.  If you're stuck in foggy, uncharted waters, you can spend a lot of time trying to to shoot the stars to chart a course, or you can raise the sail and move a bit, then reassess and move a bit more.  Baby steps help you get going, fast.

In the messy middle of an innovation initiative, baby steps allow you to quickly explore multiple directions in parallel, rather slaving to polish one idea before you know it is The One, or even The Best One We Have Now.  Big leaps make for expensive bets. Baby steps, on the other hand, are by their nature cheaper to pull off, so you end up spending less money per unit of learning, and that learning comes sooner.  And it's easier to kill off ideas when they're expressed as baby steps, because there's no huge sunk investment tempting you to spend more time and money in order to save the project or your career.  Most important of all, per Boyle's Law, baby steps increase the frequency of feedback you receive, because you can bring  a lot of baby step prototypes to quick meetings.  You learn a lot this way.

Many "overnight" innovation successes are actually the result of years of baby steps which added up to a big leap.  That  E Ink screen in your Kindle is the result of years of incremental innovations in the marketplace that took the technology from something best suited to department store signage to its current form, which is a truly remarkable breakthough. Those years of patient baby stepping at E Ink allowed them to accumulate a huge amount of explicit and tacit knowledge about how to design and make these displays; the more they learn, the harder it will be for others to duplicate their efforts with one big leap.  Baby steps can also lead to capability growth.  If you look at the product launch history of a firm like Honda, you see a steady beat of incremental product launches scheduled with presidential election regularity.  Every time Honda launches a new Accord, they not only put a better product in the market, but their people and systems evolve as well.  Stack all those launches up, and you can see why car companies that default to a "big leap" strategy are not doing so well.  Finally, baby steps can open up unforeseen opportunity streams in the guise of real options.  The folks behind Guitar Hero and Rock Band didn't set out to create the world's biggest ever living room music entertainment system -- they were just MIT guys interested in making the music performance experience more accessible to all.  Via fourteen years of patient experimentation and baby stepping, they got there, big. 

Baby steps often lead to big leaps. This is the tenth of 21 principles.  Your feedback, comments, and ideas are most welcome.

29 April 2009 | Permalink | Comments (2) | TrackBack (0)

| |

next week: the CIA conference!

6a00d83451b75569e20115704bd1f6970b-pi

24 April 2009 | Permalink | Comments (1) | TrackBack (0)

| |

metacool Thought of the Day

"Success is the ability to go from one failure to another with no loss of enthusiasm." 

- Winston Churchill

24 April 2009 | Permalink | Comments (0) | TrackBack (0)

| |

9: Killing good ideas is a good idea

So that brilliant idea of yours isn't the only version of it under the sun, but that's okay (Priniciple 8) you're pouring everything you have in to making it real because you believe it is the one and true answer to the problem at hand.

A this point, killing that good idea could very well be a good idea.

It's easy to fall in love with an idea.  And when we're not mindful of process, and spend our energy worrying about whether we'll be successful and on budget and on time (not that those are bad things, they're very important), we can also fall in love too early with an idea, simply out of fear.  The mental or organizational dialog goes something like this: "This one is good, and we're in a rush, so let's go do it.".  Early closure is the enemy of innovation.  Better to move fast through lots of ideas early, throwing most of them out in the process, than to hone down to one in the very early days, polishing it to perfection in the vague hope that it is The One. 

Killing ideas also reserves energy so that there's enough left over to actually bring the very best ones to market.  In work, as in life, you can't do everything, so deciding what you won't do becomes as important as deciding what you will do (while always maintaining a bias toward the doing).  In a discussion about why Apple never shipped a post-Newton PDA, Steve Jobs said "If we had gotten into it, we wouldn't have had the resources to do the iPod.  We probably wouldn't have seen it coming."  At the end of the day, you never want to be low, slow, and out of money or time.

So go look at  your portfolio of ideas, and then kill a few that aren't going to be remarkable in the way they go about making people happy and creating value in the world.  You'll be much more innovative as a result.

This is the ninth of 21 principles.  Please give me your feedback and ideas.

22 April 2009 | Permalink | Comments (4) | TrackBack (0)

| |

8: Most new ideas aren't

Most new ideas aren't.  Someone, somehow, somewhere already thought up the essence of what you're thinking about.

Which is all the more reason to keep plugging away.

Accepting that someone else already had your idea is liberating, because it frees you up to learn.  It moves the focus from what's going on in your head to what's going on in the world.  Much of innovating is actually about stealing ideas from one context, connecting them to other ideas, and putting them to work in another.  Where can you find analogous experiments or successes or failures that can inform your own work? Remember, before Facebook there was Friendster.  And before the iPhone came the Newton.  You can choose to live ignorance of what came before or what is happening in other parts of the world, or you can dive in and embrace all their hard-won lessons as your own.

Best of all, standing on the shoulders of giants is a free activity.

At the end of the day, if someone else has already had your idea, then the goal shifts from having ideas to making them real.  Innovators ship, dreamers don't. 

So what's keep you from making your idea real?

This is the eighth of 21 principles.  Please give me your feedback and ideas.

20 April 2009 | Permalink | Comments (3) | TrackBack (0)

| |

7: Develop a taste for the many flavors of innovation

In music there's a big difference between Mick Jagger and Maria Callas.  If you're a pilot, hopping a bush plane around Alaska requires a different skill set you need to grease a 747 on the runway in Hong Kong. 

And so it is with innovation:  it comes in many flavors, and the ability to discern those flavors and proceed accordingly is a foundational of skill of individuals and organizations who are able to achieve innovation outcomes on a routine basis.

This is most easily explained using a 2 x 2 matrix.  I promise this is the only 2 x 2 I will be using in the course of this ongoing discussion of innovation principles:


Ways to grow metacool

No matter where you want to go tomorrow, today you and your organization sit at the lower left vertex of this 2 x 2.  So, looking up the vertical axis, you start with the offerings that you currently deliver to the market, and then range up to things that are new to you. Then, looking out across the horizontal axis, you start with the people you know, and out at the end of the axis you have people (or users) you don't know at all.  The four quadrants of the 2 x 2 then fall out as follows:

  • lower left:  existing offerings for existing people
  • upper left: new offerings for existing people
  • lower right: existing offerings for new users
  • upper right: new offerings for new users

Three different flavors of innovation are defined by these quadrants:

  1. Incremental Innovation: you seek to deliver improvements to offerings you already sell to people who you understand fairly well.  Your capabilities as an organization are designed to deliver these offerings to these people.
  2. Evolutionary Innovation:  one aspect of your offering (either unfamiliar people or an unfamiliar offering space) is changing as you seek to bring new something to market, forcing you to evolve away from what you know.  Your mainstream organization will be only partially equipped to successfully innovate here.
  3. Revolutionary Innovation:  the proverbial blank sheet of paper.  Everything is new, as you don't have a history with the offerings, nor do you understand the people here.  Your mainstream organization not only is not equipped to innovate successfully here, it won't even see the value in innovating here.

For each type of innovation to work, different organizational structures, metrics for success, development processes, individual skillsets, financial structures, even seating arrangments and reward structures must be put in to place.  Just as you wouldn't take a 747 to reach an Alaskan fishing village, so too you wouldn't try to go after a revolutionary innovation outcome using a team and structure built for incremental outcomes.  But it happens all the time, ergo the need to develop a taste for these flavors.  Innovation efforts are more likely to fail due to flawed architectural decisions made during their genesis than because of a lack of effort or luck on the part of the participants who put that architecture in to action.

There is no value judgment being applied across these three flavors of innovation.  Though "revolutionary" innovation is the flavor which captures the imagination of the public, incremental innovation is what keeps the lights on and your brands relevant in the short term.  But revolutionary innovations are what lead to breakthroughs that build value for the future.  In reality, a healthy organization must maintain a portfolio of innovation initiatives across this landscape if it wants to stay healthy for the long haul.

I am the last person to claim that this is a definitive model for understanding the landscape of innovation.  But in my experience it is simple enough to be used in practice, yet not so simplistic that it yields erroneous outcomes.  For more depth, please reference the following paper authored by Ryan Jacoby and yours truly.

This is the seventh of 21 principles.  Please give me your feedback, thoughts, and ideas.

17 April 2009 | Permalink | Comments (2) | TrackBack (0)

| |

6: Live life at the intersection

Innovative outcomes result from living life at the intersection.  This is true not only within the confines of innovation initiatives, but also at the level of individuals, teams, and organizations.

Innovation needs to happen at the intersection of desirability, viability, and feasibility.  These three elements make up the legs of a proverbial stool called "it'll work in the world."  Too many innovation initiatives focus on only one or two, much to their detriment.  For example, creating something without regard for its feasibility out in the world is not unlike designing a bridge without regard to the existence of gravity: it might work, but the likelihood of it being a reliable, safe, means of transport will be greatly diminished.  And while it might be tempting to "really be creative" by ignoring constraints, a wiser approach is to view constraints as liberating.  Look at any bridge by Santiago Calatrava, and you'll see desirability, viability, and feasibility all coexisting in a glorious symphony enabled by constraints.

Calatrava is great example of what happens when an individual lives life at the intersection.  He is a prototypical "T-shaped" person, combining great depth in engineering, architecture, and sculpture with the breadth that comes from a design education and a life lived, well... getting stuff done.  

Teams and organizations engaged in the art and science of bringing cool stuff to life need to live at the intersection, too.  A team of experts ("I-shaped people") with no means of communicating will get no where, fast.  A team of generalists ("hyphen-shaped people") with no means of building and executing will suffer the same fate.  Diverse teams of T-shaped people are uniquely able to communicate in ways that support the generative application of their areas of expertise.  The end result is innovation.

This is the sixth of 21 principles.  Please give me your feedback, thoughts, and ideas.


16 April 2009 | Permalink | Comments (1) | TrackBack (0)

| |

5: Anything can be prototyped. You can prototype with anything.

Prototyping is the lingua franca of innovation.  It externalizes internal thinking in a tangible form, rendering it more intelligible by others and the world.  The good news is that, though it has its roots in the creation of physical things, when taken as a mindset and a methodology, as a way of finding solutions, prototyping can be applied to any domain.  Anything can be prototyped, and you can prototype with anything.

Anything can be prototyped. Prototypes aren’t just for physical products. I routinely see people prototyping services, complex experiences, business models, and even ventures.  Really, anything can be prototyped: before filming Le Mans, Steve McQueen took a film crew to the French race a year earlier, shot an entire movie's worth of stuff, and then threw most of the exposed stock away.  He knew that they best way to learn how to shoot a great movie at Le Mans was to first shoot a rough movie there. His camera people gleaned deep insights into camera placements, mounts, and techniques which put them in good stead when it came time to shoot the real movie. And the value of the tacit knowledge transfer involved cannot be underestimated: rather than try to explain to new camera people what he wanted, McQueen could point to actual film clips and say, “This is good.”  Prototyping leads to speed as a process outcome.

You can prototype with anything.  You want to get an answer to your big question using the bare minimum of energy and expense possibly, but not at the expense of the fidelity of the results.  It's not only about aluminum, foamcore, glue, and plywood.  A video of the human experience of your proposed design is a prototype.  Used correctly, an Excel spreadsheet is a wonderful prototyping tool.  GMail started out as an in-market prototype.  A temporary pop-up shop is a prototype.  Believing that you can prototype with anything is a critical constraint in the design process, because it enables wise action, as opposed to the shots in the dark that arise from skipping to the end solution because zero imagination was applied to figuring out how to run a create a prototype to generate feedback from the world.

A wise person operates with the worldview that anything can be prototyped, and we can prototype with anything. 

This is the fifth of 21 principles.  Please give me your feedback and ideas.

15 April 2009 | Permalink | Comments (1) | TrackBack (0)

| |

4: Prototype as if you are right. Listen as if you are wrong.

To make change in the world, we must constantly engage in a yin-yang cycle of prototyping.  This implies a commitment to two behaviors:

  1. Prototype as if you are right.
  2. Listen as if you are wrong.

What is a prototype?  A prototype is nothing other than a single question, embodied.  In a way quite similar to the scientific method, productive prototyping is about asking a single question at a time, and then constructing a model in the world which brings back evidence to answer your question.  In order to believe in the evidence that comes back to you, you need to prototype as if you already know the answer.  A strong belief in your point of view will push you to find more creative solutions to the question at hand.

Once your prototype is ready for the world, it is important to listen as if you are wrong.  You (and everyone around you) must be willing to respect the evidence that the prototype brings back, whether you life it or not.  You must also go out of your way to put your prototype in to the world.  Hiding it in a closet is only cheating the process, and ultimately, yourself.  My colleague Dennis Boyle, who is one of the world's truly great design thinkers and a remarkable product development guru, has a saying which we like to refer to as Boyle's Law.  It goes like this:

"never attend a meeting without a new prototype"

This serves to both push and pull.  It pushes you to prototype earlier and with more frequency, because you want to (and have to) meet with other people in the course of life.  And it pulls you toward a more productive state, because you can't have a meeting without having a new prototype, which means that you spend less time talking in pointless meetings and more time doing productive explorations.  Doing is very important.

There is an important build on Boyle's Law, which goes by the handle of Raney's Corollary.  Coined by another one of my colleagues, Colin Raney, his corollary states:

"you only learn when things start breaking"

The goal of a prototype is not to be right, but to get an answer.  That answer is what allows you move forward with wisdom.

When we engage in both of these behaviors, prototyping as if we are right but listening as if we are wrong, we engage ourselves in a continuing cycle of do-try-listen.  When faced with the challenge of bringing something new in to the world, this cycle leads to concrete results that have a better chance of changing the world, as they are born of lessons from the world.  As such, I much prefer the word "prototyping" (a verb) over the word "prototype" (a noun).  It is about doing.  Prototyping is how things move forward.

This is the fourth of 21 principles.  Please give me your feedback and ideas.

14 April 2009 | Permalink | Comments (3) | TrackBack (0)

| |

3: Always ask: "How do we want people to feel after they experience this?"

Too often we focus all of our energy on designing the thing, and forget about the people who will use it.  As we approach any design effort, we must step back and always ask: "How do we want people to feel after they experience this?"

Part of the challenge lies in taking an "ecosystem" approach to the human experience.  It's relatively easy to think about the experience of the end user of the thing you design, but what about the experience to be had by the person who sells it?  How could we make that better?  Who will service it?  Who will retire it?  Who will market it?  Who will provide training and education?  A comprehensive look at all of their needs will help (but not guarantee) a better overall experience for the end user.

Another part of the challenge lies in thinking about usage through time.  We often design for those few moments that make up the core value proposition.  But what about all the other experiences?  How does it feel to start using it?  What does mastery feel like -- is it exhilarating or boring?  How does using this expand our human experience?  How does it influence our environment?  What does it feel like to extend one's relationship with the offering?  Does it help someone get to a state of flow?

There are many examples where designing for the entire experience has made for success in the world (here's a list of "well done" vs. "not so well done"):

  • Apple Store vs. Sony Style
  • Dream Dinners vs. Hamburger Helper
  • Trekking in Bhutan vs. in Nepal
  • Disneyland vs. your local amusement park
  • World of Warcraft vs. Second Life
  • Mint.com vs. your credit card and bank statements

As Lance Armstrong would say, it's not about the bike.  We must keep asking "How do we want people to feel after they experience this?"

This is the third of 21 principles.  Please give me your feedback and ideas.

13 April 2009 | Permalink | Comments (2) | TrackBack (0)

| |

2: See and hear with the mind of a child

If experiencing the world firsthand is about wisdom, then being open to what that world tells you requires cultivating the un-wise mind of a child: open, curious, fun-loving. 

Being open and curious takes practice. 

Having an open mind requires one to suspend (or at least defer) judgment.  This is an acquired skill. 

Curiosity must be fed: when asked by a classmate of mine how we should best spend our time preparing ourselves for a life spent designing stuff, the great design guru Sara Little Turnbull said, "Great designers are great readers."  In other words, you must feed your curiosity, because it grows stronger as it is fed, and the cognitive foundation set by that curiosity is what enables one to recognize patterns and make connections across disparate elements of complex systems.

Having fun (especially as you work) requires energy and time.  But it’s worth it: fun shows ways forward other than the drab grey of the mundane, and it can shake us out of the path of an obvious solution.

Without the mind of a child, one can’t see or act deeply.  We must see and hear with the mind of a child.

This is the second of 21 principles.  Please give me your feedback and ideas.

11 April 2009 | Permalink | Comments (7) | TrackBack (0)

| |

1: Experience the world instead of talking about experiencing the world

The signature behavior of people who routinely achieve innovative outcomes is that they constantly seek to experience the world instead of talking about experiencing the world. 

Instead of only reading someone else's market research summary, they go in the field and shop across the category in question.  That way they can get a feel for all the intangibles which are lost in translation, as language, photos, and even video are imperfect mediums.  Honda's innovative rethink of the pickup truck came from Saturday mornings spent in the parking lot of Home Depot.

Instead of taking someone else's diagnosis of a problem at face value, they seek a second opinion, and the deliverer of that second opinion is their own person.  When there's a problem on the production line at Toyota, they don't wait for a PowerPoint to circulate with photos and diagrams of the bug in question.  Instead, everyone concerned walks over to experience the bug firsthand.  And then they ask:  why, why, why, why, and why?

Instead of spending sixty minutes talking about what might be done, they build four 15-minute prototypes to immediately jump to the lessons that only come when you start breaking things.  At the Stanford d.school, we hold "Iron Chef" prototyping sessions where small teams receive a problem statement from the audience (show me a way to run fast on the Moon!), and then they prototype the hell out of it for five minutes.  And invariably they get somewhere interesting that would have been unreachable via conversation and hand waving.

Instead of only reading second-hand source or searching on Google, they go to the place and talk to people and see the sights.  Talking to a person living on a dollar a day is much different than reading about it, as important as that background knowledge is.  Experiencing the Mona Lisa in person is something quite different than viewing it on your MacBook.  In order to understand what was really going on in Dubai, Joi Ito picked up house in Japan and moved there.

To truly start living as a design thinker, experience the world instead of talking about experiencing the world.

This is the first of 21 principles.  Please give me your feedback and ideas.

10 April 2009 | Permalink | Comments (8)

| |

David H. Liu Memorial Lecture Series in Design at Stanford

The David H. Liu Memorial Lecture Series in Design starts up again next week.  The speaker roster is truly amazing, and they should be an awesome experience. 

If you're anywhere near Stanford on these dates, I highly recommend stopping by.  Do check the series website for any room or date changes.
LiuLectureSpring2009_v3_1

09 April 2009 | Permalink | Comments (0)

| |

Simple Pleasures

In this age of economic swirl and uncertainty, quality is more important than ever.  As people decide where and how to spend their precious dollars, I think they're going to vote in favor of things of high quality, and hence greater meaning.  It's a good time to be a design thinker who intuits quality, and the great news is that lessons in the do's and don'ts of quality surround us each and every day.  It's relatively easy to enroll in a continuing education course in the art of bringing good stuff to life -- all you have to do is to be mindful in your daily journey.  They constantly surround us, these simple pleasures.

When I feel something is of high quality, I literally feel it -- my world calms down, and I experience an emotional response which is not unlike the feeling you get upon settling in to a champagne jacuzzi.. ah, this is nice, this is good. I can look at a high-quality object for unreasonable amounts of time, entranced by the quality of the details that make up the whole, as well as with the whole itself. Paying attention to quality is of prime importance to those of us dedicated to bringing cool stuff to life; knowing what goodness feels like is a key enabler of having a strong point of view, and it also keeps us from settling on the mediocre or the convenient. It's good to look and to know.

And what do I mean by quality? I'm not talking about process control and six-sigma methodologies, as much as respect them when used at the right time and place. Nor am I conflating quality with high prices; the realm of yuppie-driven quality is a place where price and opinion leaders combine to dictate what's hot and what's not to a club of self-selected consumers, and the value proposition there is nothing if not hollow. The quality I speak of has to do with materials, fit, proportions, workmanship, and care of assembly and upkeep.  It is unavoidably a function of what something is in the world.  In short, it has much more to do with the visceral (it looks and smells right)  and behavioral (it works right) elements of design than it does the reflective (the meaning is right).

Taken in mindfully, life offers us a continual flow of lessons in quality.  No matter if you are experiencing the built environment or nature, taking the time to really look around will deliver a constant stream of opportunities to think about quality.   Because this isn't about money, I don't think you have to be in a high-zoot environment to see interesting stuff.  Sometimes a lack of quality can be as instructive as its presence.

Just the other weekend I made a quick trip to my local grocery store, and happened across two wonderful chances to feel, hear, and see quality at work. 

The first was this charming 1959 Porsche 356: 

356

It was in beautiful shape, likely restored, but not over-the-top perfect.  I spent a few minutes sitting across the street so that I could admire its proportions in profile.  Why am I the only person admiring this thing?  Come on, people!  An open driver's-side window allowed me to admire the deep red leather interior, as well as the creamy steering wheel, a color combination which works wonderfully.  I waited long enough for the owner to come out (by which time I was distracted by the bike below) so that I could hear the motor start up.  It cranked up immediately, with zero smoke or stumbling, and its exhaust note was a smooth mix of metallic crispness and baritone song.  It's educational to experience a machine in good tune.  Quality.

Parked right across the street was this bike:
Jitensha

What sublime aesthetics.  I love the way the metal fenders exactly match the arc of the wheels, the artful way the side marker lamps are positioned, and the highly considered color scheme.  Everything is just so.  I find bikes fascinating because they are endlessly customizable.  Cars, and to a lesser extent, motorcycles, must meet regulatory concerns to be considered roadworthy, but with a bike, you can go to town and make it just as you see it in your mind's eye.  Without any badges in evidence, I couldn't ascertain the make of this bike, but looking at the compontents and accessories, I'd wager that the owner is a frequent shopper at Rivendell and Jitensha, both local purveyors of (extreme) quality bicycle paraphernalia.

The simple pleasures of quality: feel it, imbibe it, know it.

08 April 2009 | Permalink | Comments (0)

| |

A Harvard Business Review Debate: How to Fix Business Schools

110-how-to-fix-business-schools 


I'm participating is something new for me, an extended online debate.  I'm a panelist for How to Fix Business Schools, which is being hosted by the Harvard Business Review.  Here's the blurb:

Are our business schools up to the job? Many critics have charged that the values imparted in MBA programs contributed significantly to the ethical and strategic lapses that led to the current economic crisis. Is that fair? And if so, what needs to change? How can business schools regain popular trust?

For the next several weeks Harvard Business Review will be discussing these and related questions in the HBR Debate: How To Fix Business Schools. For this online symposium, we’ve invited an impressive roster of experts to lead the debate—and to try to come up with solutions.

So there you go.  This should be fun: I can't wait to see what many of my co-panelists -- many of whom are former professors of mine or individuals whose writing has been a big influence on my own worldview -- have to say about the debate topic.

If I write anything particularly meaty or inflammatory I'll make a note of here on metacool.

02 April 2009 | Permalink | Comments (1)

| |

Yet another thought on prototyping...

1901 Glider Kited

Thanks to everyone who gave me input on these thoughts.  I particularly like this build, which was related to me yesterday:

As you make a prototype, assume you are right and everyone else is wrong.  When you share your prototype, assume you are wrong and everyone else is right.

01 April 2009 | Permalink | Comments (1) | TrackBack (0)

| |

« Previous | Next »

Categories

  • designing
  • innovating
  • leading
  • marketing
  • meta metacool

search


About

Subscribe to this blog's feed

    follow me on Twitter

    Favorite Posts

    • A million reasons why...
    • Mo Cheeks and a fundamental question of leadership
    • Innovation Lessons from Garage Majal
    • From Obama to Pink to Oprah
    • Shinya Kimura and the primacy of doing
    • A tribute to friends and friendship
    • Strategy that makes your hands bleed
    • Quality in a switch
    • Travis Pastrana and the future of the world economy

    on the nightstand

    • : The Great Bridge

      The Great Bridge

    • : Porsche - Origin of the Species

      Porsche - Origin of the Species

    Principles for Innovating

    • 1: Experience the world instead of talking about experiencing the world
    • 2: See and hear with the mind of a child
    • 3: Always ask: "How do we want people to feel after they experience this?"
    • 4: Prototype as if you are right. Listen as if you are wrong.
    • 5: Anything can be prototyped. You can prototype with anything.
    • 6: Live life at the intersection
    • 7: Develop a taste for the many flavors of innovation
    • 8: Most new ideas aren't
    • 9: Killing good ideas is a good idea
    • 10: Baby steps often lead to big leaps
    • 11: Everyone needs time to innovate
    • 12: Instead of managing, try cultivating
    • 13: Do everything right, and you'll still fail
    • 14: Failure sucks, but instructs
    • 15: Celebrate errors of commission. Stamp out errors of omission.
    • 16: Grok the gestalt of teams
    • 17. It's not the years, it's the mileage
    • 18: Learn to orbit the hairball
    • 19: Have a point of view
    • 20: Be remarkable

    CC

    • Creative Commons License