Foresight 20/20

Last week Brandweek had an article about Design Thinking, and I'll have to say it was a bit misleading.  I'm not going to nitpick the article, but I would like to address a few points that I think are valuable to understand about the topic.

I should start by saying that I am a proponent of Design Thinking, just as I am a proponent of Business Thinking, Legal Thinking, Engineering Thinking, and Political Thinking.  All are approaches to solving problems that have evolved to ensure rigor and best practices in their respective professions.  Where it gets interesting is when a problem in one discipline benefits from an approach used by another discipline.  The current buzz about Design Thinking is an answer to the business world's need to innovate.  The current processes used to guide businesses don't lend themselves well to doing something new that can't be measured by current benchmarks.  Designers regularly create new solutions that have no benchmarks, so taking a page from the way they work should be helpful to achieve these goals.  And it is. 

What gets misleading is when the distinction is blurred between an approach that is used in a discipline, and the work, skills, and deliverables expected of professionals in that discipline.  If a business person uses design thinking to develop an innovative business model, the outcome is still a business model and the profession is still that of a business person.  It does not mean they should be called designers, as they do not possess the skills required of a design professional.  If a designer uses business thinking to make their designs more relevant to the business, they are still designers.  The article references people with design backgrounds who are now in marketing roles.  That would be called a career change. 

Finally, it is misleading to narrowly associate tools with disciplines.  The article associates ethnography with the way designers learn about consumers, and suggests that focus groups are more for business goals.  This is just not true.  Ethnography is a research tool, and is used when a deep understanding of consumer values is necessary to solve a problem.  This could be a business problem, a design problem, or a pure science problem.  If we are truly employing design thinking methodology, we are less worried about what tools we are using, and are instead doing whatever is necessary to achieve our goals.

I don't know who first coined the term Design Thinking (I've heard it was either Tim Brown of IDEO or Roger Martin of the Rotman School of Business), but Roger Martin's article is still the best I've seen in terms of defining the value of design thinking to a business.  His article on Reliability and Validity is well worth the read.  Reliability vs Validity.doc (42.00 kb)

Nov. 13 - Update today from Jess to clarify the attribution of who first coined the term Design Thinking:

As far as origins, Peter Rowe wrote a book called "Design Thinking" that came out in 1987. Not sure about earlier usage, but I'm skeptical of either Brown or Martin being the originator.  Here's the Google Book result for Rowe's "Design Thinking"

http://bit.ly/rowe_design_thinking

I recently wrote about how good design embraces constraints.  In the comments, Kelly asked how we should go about focusing a client on the possible design constraints upfront in the process.  This is a good question, and the extent to which you can identify all the constraints upfront depends on the extent to which you are looking to improve the existing offering, or you are looking for a breakthrough.

In my experience, if you are looking to improve on an existing offering, the real constraints typically consist of tangible boundaries that are easy to identify.  These would be things like current manufacturing processes, distribution channels, category definition, and organizational structures.  If the new design needs to fit within these constraints, the designer should be made aware of them in the beginning.  It is then part of the designers job to creatively work within these constraints.  For example, if I am a company that manufactures padlocks, and I am improving my current product, the constraints should be easy to identify.

On the other hand, if you want to develop a breakthrough innovation, it is necessary to understand that one of the most important outcomes of the project will be to indentify the constraints.  In this case the real constraints tend to be less tangible, consisting of things like the consumers' culture, and macroeconomic regulations and conditions.  Any of the constraints listed above would be self-imposed.  Back to the padlock example, if I want to develop a breakthrough innovation, defining my company as a padlock company would be unnecessarily limiting.  I could redefine the company as a security company, and a whole world of options opens up.  The real constraints for how consumers perceive security would need to be indentified as part of the project, before potential solutions are explored.  Once potential solutions are explored and selected, the next set of constraints needs to be defined.  These would be things like where, how they will be made, new organizational processes that will be needed, which categories will now define the offering, etc.

The point is that regardless of the type of project you are undertaking, the constraints should be identified before the designer starts designing anything.  If we are trying to do something truly new, we should be aware that defining constraints is part of the process, and we should be prepared for the reality that current constraints may not need to be imposed on future offerings.

I talk a lot about consumer insight: how to learn from consumers, how to derive insights, and how to translate them into useful criteria to guide decision-making.  I realized that I don't talk so much about how this connects to the design process, and I'll be mixing in more of that from now on.

I've often heard clients talk about holding back on the constraints because they don't want to hinder the creative process.  While the intention is good, nothing could be further from the truth.  The creative process depends upon constraints.  Figuring out how to manage constraints is what creativity is all about.  Having a blank slate to design whatever inspires you is what fine art is all about.  It may be fun and interesting, but it most likely won't help to achieve your business goals.

Next time you're working with a designer, remember that it's your job to let the designer know about all the constraints to the process ahead of time.  Along the way some of these constraints may be challenged or made irrelevant, and that's part of the creative process at work.  If you don't do this, the designer will create their own constraints, and what gets designed may not be relevant to your business at all.  At that point everyone's time has been wasted. 

Also remember that you don't need to decide what the answer is, and have the designer just draw it up and make it pretty.  Design is about problem solving.  Problem solving needs constraints.  Otherwise it's just decoration, and that's a different task altogether.