Category Archives: Design Thinking

IDEO Shares Design Thinking Toolkit for Libraries

After it’s groundbreaking work in bringing design thinking to the field of education, what was next for IDEO? Libraries!

While librarians across the different spheres of the profession have paid more attention to user experience, the virtues of design thinking as a method for identifying and then developing appropriate solutions for challenging problems is rarely discussed in the library literature. One exception – my 2008 article on design thinking that appeared in American Libraries. The new Design Thinking for Libraries: A Toolkit for Patron-Centered Design could change how librarians respond to design thinking as a method they can use to improve their libraries.

What may have been off-putting in the past about design thinking from the librarian perspective is the possible association with business. It was perhaps perceived as a business driven process. Librarians and business don’t always mix well. You know…libraries are not businesses and shouldn’t be run like they are…resisting the corporatization of libraries. Whatever your position on that observation, let’s agree that business can offer some potentially good ideas that librarians may want to adopt. While its true that many of the examples of what IDEO can do with design thinking have a business orientation to them (such as the shopping cart project), what IDEO is offering is unrelated to business. It’s about design. The Toolkit makes clear that what really matters is the value of design in developing thoughtful solutions regardless of the environment in which it is applied.

There are three components to the toolkit.

The first document is the core component that goes into depth about what design thinking is and provides details on each phase of a design thinking process. What’s presented here is slightly different than the key areas of design thinking one discovers in the video that covers the shopping cart project (empathize; information sharing; deep dive; prototype; evaluation). Rather, it is based on Tim Brown’s classic article on design thinking that appeared in Harvard Business Review. That breaks design thinking down into three components: inspiration; ideation; iteration.

For those new to design thinking this will be of little consequence. Over the course of the toolkit, the reader is introduced to all these component parts in one way or another. What’s great about the toolkit is the level of detail it provides on how to conduct the different parts of the design thinking process. Whether it’s a brainstorm session or creating prototypes, there’s practically a step-by-step approach to getting it done.

The second document is an activities workbook. This is chock full of resources that would be helpful to support a design thinking project. It’s got worksheets for everything from icebreakers to creating prototypes to obtaining evaluation feedback. I wish I had this workbook the first time I tried a staff retreat based on design thinking practices.

The third document is a “quick guide” for those constrained by time (who among us isn’t these days). It’s a condensed version of the full blown toolkit. This might be useful for introducing colleagues to the ideas behind design thinking, but to really get a design thinking project underway, it will require a more serious investment of time – using the toolkit and activities workbook.

No doubt, with the growing popularity of ethnographic studies in academic libraries, some of the toolkit content will be familiar to librarians, but this new IDEO toolkit will really enable librarians who want to establish design challenges for themselves and their patrons to finally make great use of the design thinking process. While it may take some time for design thinking to enter into the mainstream of librarians’ conversation, I think this guide will play a significant role in bringing more attention to the benefits of the design approach. I don’t doubt that come a year a two from now, librarian conferences will be featuring more than a few presentations on design challenge projects.

Exploring IDEO’s Design Kit

If you are a librarian who is embracing design as a methodology or strategy for giving your community members a better library experience, you owe it to yourself to spend sometime exploring IDEO’s Design Kit. This totally free package of resources mixes text and video to deliver support and instruction to non-designers who want to incorporate design practices into their work. There are also ample case studies to help you understand how the design techniques are put into action.

I just finished reading Tom and David Kelley’s latest book Creative Confidence – lots of great ideas and insight into what contributes to creativity – so I was curious to see what David Kelley had to say about creative confidence in under two minutes. Kelley’s video introduction into methods for building your confidence in your own ability to be creative, did a fine job of sharing the book’s key points – quickly. Every design kit video I watched was under two minutes.

One of the design processes that serves as the core of the kit is HCD – Human Centered Design – defined as a creative approach to problem solving that starts with people and ends with innovative solutions that meet their needs. It means designing from the perspective of the people you are trying to help. HCD consists of three phases: Inspiration; Ideation; Implementation.Libraries are getting into “making” activities in a big way and that’s an important part of the HCD process because you have to make things – that’s where prototyping comes in – to find out if the inspired ideas can lead to workable solutions. Above all, the people with the problem are the ones who have to embrace the solution. The important thing to know about HCD is that anyone can practice it. You don’t need to be a designer. You just need to start with the people.

There’s a lot to the toolkit site and you learn how to navigate it by poking around and exploring different areas. You might find it easiest to start with the three main areas: mindsets; methods; case studies. Drill down and explore in each one. This will give you a better idea of what the kit has to offer and how it’s delivered. But no matter how you tackle it, you can’t go wrong. No matter what path you follow in the toolkit you’ll be gaining lots of new ideas to share with colleagues.

And if your HCD process takes you into some ethnographic research, well there’s a new and free “Simple Introduction to the Practice of Ethnography and Guide to Ethnographic Field Notes It’s a good starting point for familizing yourself with the practice of ethnography.

If IDEO Was Hired to Design a Library System

One of the early design thinking influences for me and other librarians was the Maya Design Project for the Carnegie Libraries in Pittsburgh. In 2004 the Carnegie Library moved into some unprecendented territory when it hired Maya Design to totally rethink and redesign the library from the user experience perspective. This being the early days of the Blended Librarians Online Learning Community, we were tremendously interested in learning more about how design was being used as a technique to understand user needs and expectations, and how the design process was being applied to the work of reshaping that library.

We were also fascinated that non-librarians were invited to do all this work. That type of work would seemingly fall within the domain of librarian expertise. What did the designers know about libraries and those who used them? What special skills did they bring to the project? The answers came from Aradhana Goel, one of the MAYA Design experts leading the project. As our guest for a Blended Librarians webcast (unfortunately the archive is no longer available) Goel gave us some great insights into the design process as she shared some visuals and explained how the designers were taking a systematic design approach to understand the customer journey at Carnegie. We learned that designers like Goel didn’t need to be library experts. They only needed to be experts in the design process and using it to improve the library experience. That said, Goel emphasized the importance of working closely with subject matter experts.

It was a great learning example to understand the value of design thinking for “reinventing the customer experience”, as Carnegie Libraries described it. What if we could take what Maya Design did for just one library and instead ask a design firm to apply its design thinking process to the entire ecosystem of libraries. An interesting idea no doubt, but given the breadth and depth of that system, inclusive of all the different types of libraries and many different member communities it almost seems like an overwhelming and impossible project.

But according to an article in the New York Times about some recent projects by IDEO, the design industry’s most globally recognized firm, there is a movement from designing specific products and services to tackling entire systems and re-designing them from the ground up. In this particular article, IDEO’s work for a Peruvian entrepreneur to design a low-cost network of private schools is profiled. Though IDEO has experience in helping some health care and education organizations to re-design their operations for efficiency and a better user experience, the Peru project is far more ambitious in its scale. IDEO needed to design every component of the school system, from the buildings, to the classrooms to the teaching training and even what happens in the classrooms. In the three years since IDEO began the project, it now includes 23 schools.

It got me to thinking, what if IDEO was asked to build a library system from scratch, using no preconceived notions from the current system. Whatever it ended up being, I imagine it would probably be radically different from the way our libraries work now. Two things would happen at the start.

First, the team that IDEO would assemble to work on the project would have one librarian. Everyone else would represent different disciplines such as business, anthropology, marketing, engineering, health care and more. IDEO often brings together a truly diverse squad of individuals to bring many different perspectives to a project. One librarian would bring some expertise, but would eliminate preconceived notions about what the library should be or a host of reasons why certain things wouldn’t work (e.g., “But how would we get the books back to the shelves…”).

Second, the research process would be user centric. The team would probably have less interest in talking to the librarians, except as subject expertise is needed. They would primarily seek out individuals who use libraries as well as those who never do. Observation, conversation and journey mapping are techniques employed to gather data to inform a deep dive about library use. Out of that process would emerge ideas for a library system that would break the mold of the traditional model.

It’s hard to imagine exactly what a design firm like IDEO would come up with for a completely new library system. Perhaps it would be less fragmented than our current structure, and we’d have public, academic and corporate libraries working more as a system, sharing resources and offering more interchangeable services. Library facilities might undergo some dramatic change in ways that would make them more intuitive to the community members and less reflective of librarian practices. IDEO might see a natural fit between libraries and publishing, thus encouraging more libraries to serve as vehicles for writing and publishing.

What I do know is that IDEO would spend time prototyping new versions of any library system they’d design, and that would give both librarians and community members the opportunity to weigh in on how well that system met their needs. While we may never find IDEO tackling the American library system, it is possible that we will see individual libraries connecting with design firms to guide them in totally rethinking what it means to deliver library services. Then again, what if IDEO taught librarians how to do their own systemic redesign? I think more us would discover that design thinking is a path to improving the quality of the library user experience. That would be rewarding for both librarians and their community members.

Experts Chime In On Design Thinking And Design

One of the questions often asked of design thinkers is how it differs from the practice of design itself. Based on a series of questions and answers with four leading design thinking experts, the answer seems to be that design thinking is a process for better understanding problems in order to achieve good solutions. It is more about thinking through a problem in a systematic way with the goal of arriving at a workable solution. Design, on the other hand, focuses on improving experiences in an intentional way. What else do these top thinkers have to say about design and design thinking?

DMI Review, a publication of the Design Management Institute, featured interviews with A.G. Lafley, CEO of Procter & Gamble, Don Norman, executive and educator, Tim Brown, CEO of IDEO, and Roger Martin, Dean of the Rotman School of Management, in its Summer 2013 issue. You can find the home page of this issue here but depending on your affiliation you may or may not be able to access them without a fee. You may also be able to find scans of some of the interviews with an Internet search (e.g., I came across the Martin Q&A). It’s rare to find all four of these experts sharing their insights together in the Q&A format, so this is a good find for those who want to learn more about design thinking.

Here are some highlights from the interviews:

Lafley: “Design thinking is about using your whole brain.” “Consumers usually cannot tell us what they want, but they can respond to stimuli. Through an iterative process that involved consumers with early stage concepts and product prototypes we got to be really good at designing better consumer experiences.”

Norman: “Design thinking is a process of determining the correct problem (as opposed to jumping to a solution). After the correct problem has been determined, then it is a process of working toward an acceptable solution.” “Anyone can do it with training and practice.”

Brown: “In business, design thinking can be described as an approach that uses the designer’s sensibility and methods to match people’s needs with what is technologically feasible and with what a viable business strategy can convert into customer value and market opportunity.”

Martin: “The fundamental principle is balance of opposing forces. Design thinking balances exploitation and exploration, reliability and validity, analysis and intuition, and declarative logic and modal logic.”

Each interview is fairly short so if you can get your hands on this article you’ll find, without a significant time investment, more than a few interesting insights into both design thinking and design.

Small Details of the Library Experience May Matter the Most

There’s a new book garnering attention because it brings a new perspective to design thinking. What makes it stand out is that it’s a really small idea. Micro-small in fact. That certainly has a refreshing appeal when what usually gets hyped are really big ideas. This approach may be of value to librarians in helping them to think small – and we’re unaccustomed to hearing that sort of advice. I have to admit to being guilty myself of suggesting that it’s the big idea that helps our libraries get attention. If we intend to design a library experience based on achieving totality, it makes sense to consider all of the individual, micro-design elements that ultimately contribute to the total experience.

In his new book Microinteractions Dan Saffer encourages us to focus more on the small details that add up to the bigger moments of our user experience. In other words, the success of the outcome of the product or service is in the details. The microinteractions are the small elements of the overall process or service that can determine its unique features that make for a great experience. Microinteractions include functions such as silencing a cell phone, filling out a webform as part of a larger process (e.g., requesting an article from the library), or any small component of a larger experience. Saffer shares a good story about how a cell phone alarm ruined a concert because its owner didn’t know that the phone issued a time alarm even when set to silent mode. The design of that feature is perhaps a good one but its existence, or how to override it, certainly wasn’t clear to the phone’s owner.

There are four parts to the microinteraction:

1. A trigger that initiates it; something the user has to do such as pressing a switch or choosing an option.

2. A rule that governs the operation of the trigger; when a light switch is turned to on (the trigger) the rule states that the light stays on until the switch is set to off.

3. Feedback that the rules generate; visuals, sounds or sensations that let you know the rule is operational – such as the light that goes on when the switch is flipped or the visual cue that informs you the form was submitted.

4. Loops and modes that make up the microinteraction’s metarules; think of them as smaller helper functions that support the microinteraction, such as a sub-function to change the location for a function that provides a weather report.

As we go about designing different elements of our library services and products how could a better understanding of microinteractions and their part in the success or failure of a more involved experience help us to improve the total library experience. While I imagine that what Saffer mostly has in mind is our experience with interfaces and technology design – and that appears to be the case based on the examples he provides in the (free-to-read) first chapter. What I’d like to contemplate is how we could apply the microinteraction process to various areas of our library operations. For example, try applying it to a face-to-face reference interaction.

First, we need a trigger – something to get the community member to activate the service. As we design the microinteractive pieces, let’s remember delivering a superior experience is the desired outcome. What about something physical, such as a smile, big greeting or eye contact (or all of them) that sends a trigger to signal the initiation of a service process. Second, we need a rule and it should be natural for reference librarians. The rule would state that the librarian stays engaged with the community member until the request for information is resolved. Unfortunately, the micro-design missing in the reference interaction is follow up; we rarely know if the assistance offered actually solved the community member’s need. Third, the feedback generated by the rules would be verbal in nature, with the librarian providing oral feedback to let the community member know how the interaction is proceeding and where it is headed. And fourth and finally, the metarules would focus on demonstrating a research skill as a microfunction that supports the microintereaction.

You might be questioning if this application of Saffer’s microinteraction methods helps us to improve the total library experience. But if we can regard many of our routine activities as microinteractions within a much larger system, you can begin to see how designing each microinteraction in the individual service or product can eventually add up to the totality of the library experience, it makes a difference. It may also be easier to get there by focusing staff energy on the design and effectiveness of each micorinteraction that is incorporated into the total library experience. Perhaps the most valuable outcome from this new book is that it will get us thinking about service interactions – and designing them – in a whole new – and micro-detailed way. That, I think, is why Saffer’s work is sure to gather more attention.

Design Thinking For Our College Students – A Better Higher Education Experience?

One way in which design thinking is promoted by its advocates is as a system for solving difficult or wicked problems. Much of Roger Martin’s classic work on design thinking, The Design of Business, lays out an approach by which businesses can overcome the weaknesses of purely analytic or algorithmic processes for problem solving. In higher education we frequently describe critical thinking as an important outcome for college students, and advocates of information literacy discuss the necessity of helping students think critically about the retrieval and usage of information – and how it contributes to the scholarly communication system. One way in which students can develop higher level critical thinking ability is in solving difficult problems. So it would seem to make sense that helping them to better understand and use design thinking would be a valuable component of higher education. There is little or no evidence that design thinking is currently integrated in to the learning process anywhere within the typical undergraduate college curriculum [NOTE – some design and business programs would be exceptions but this is often more the case at the graduate level].

So I was intrigued to come across an article about design thinking in the fall issue of Review of Education Research. I could recall few if any articles about design thinking in the literature of education, and I immediately wondered what ideas and suggestions the authors, Rim Razzouk and Valerie Shute would be sharing in their article “What is Design Thinking and Why Is It Important?” [NOTE: available only to subscribers]. The basic premise of the article is that current pedagogical approaches are inadequate to prepare students for lifelong learning. No matter what career direction a student is headed, he or she must be an effective problem solver. After pointing out the growing interest in design thinking in the world of the business the authors state that:

Helping students to think like designers may better prepare them to deal with
difficult situations and to solve complex problems in school, in their careers, and
in life in general. Current educational practices, though, typically adhere to outdated theories of learning and pedagogy

The first half of the article provides an in depth literature review of design thinking, so for that reason alone it may be of interest to those seeking a nice survey of the basic concepts and theories. In identifying the characteristics of design thinkers, Razzouk and Shute do a good job of demonstrating that those are qualities we want in our college graduates:
* ability to visualize
* human centered
* ability to develop multiple solutions to a single problem
* systemic vision
* ability to clearly articulate ideas to others
* effective in teams

While the authors do a good job of thinking through how design thinking could benefit college students, the article is thin on providing concrete examples of how and where that would happen in the curriculum. They mostly offer general suggestions:

Associated activities could be designed in a way that requires students
to generate ideas/solutions, receive support for their emergent design thinking
skills… Educators can support their students in developing these skills by providing them with multiple and varied opportunities to design and create prototypes, experiment with different ideas, collaborate with others, reflect on their learning,and repeat the cycle while revising and improving each time. In summary, the premise is that by improving students’ design thinking skills through having them apply processes and methods that designers use to ideate and help them experience how designers approach problems to try to solve them, students will be more ready to face problems, think outside of the box, and come up with innovative solutions.

While I agree with the authors that integrating design thinking skills into the curriculum would definitely benefit the students, I imagine that influencing other faculty to embrace their idea would be difficult. Given that few faculty would even be familiar with design thinking, it would be quite a challenge to get them to accept an entirely new approach to learning that would require them to abandon many of their current practices. I have advocated in the past that Library and Information Science educators should look more closely into design thinking for ways to integrate the ideas and practices into the preparation of future librarians. For the most part it has fallen on deaf ears, and I expect that these authors can expect the same results.

Despite the odds against having the higher education establishment accept design thinking as a viable foundation for a 21st century education, I hope the authors will make an ongoing effort to get other faculty to hear their ideas. As the authors put it, “Helping students to think like designers may better prepare them to deal with difficult situations and to solve complex problems in school, in their careers, and in life in general…If we are serious about preparing students to succeed in the world, we should not require that they memorize facts and repeat them on demand; rather, we should provide them with opportunities to interact with content, think critically about it, and use it to create new information.” I think that’s an educational philosophy that many academic librarians would support. I will be following up to see if the authors are able to gain any traction with their bold proposal for educating college students as design thinkers.

L-Schools and I-Schools Should Take A Closer Look At D-Schools

According to the Wall Street Journal (watch the video) D-Schools are hot and B-Schools are not. The WSJ is acknowledging an important trendh within B-Schools that has been growing in popularity for a few years. While it’s true that a few forward thinking business schools, most notably the Rotman School of Business (U of Toronto) and the Weatherhead School (Case Western) have integrated design thinking into their curriculum, the vast majority of business schools are still offering the same traditional courses and career paths for their MBA students. Moving to a design thinking influenced curriculum makes good sense because more businesses are making use of design thinking and looking to hire those who can bring more of these skills to their companies. At my own institution, the Fox School of Business includes the Center for Design and Innovation, where the faculty are exploring the intersection of design and business, and exposing the newest MBA students to the design inquiry process, a variant on design thinking.

While the video does point out that some B-Schools are providing a mix of design thinking and business thinking, it emphasizes that D-Schools may be the new B-Schools. Students who may have opted for an MBA in the past now want to be designers – especially designers who work at companies like Apple, Google or Facebook. They want to mix their business knowledge with the problem solving methods used by designers. The Stanford D-School is probably the hottest D-School right now, and perhaps it’s no surprise that there are many connections between the school and IDEO. I have participated in several of the D-School’s one-hour webinars, and have learned some great things about design thinking from their faculty members.

It’s great that business schools are recognizing the value of design thinking – and that business people are recognizing the value of attending D-Schools. Perhaps now is the right time for L-Schools (Library) and I-Schools (Information) to take a closer look into this trend, and consider how to integrate design thinking into the curriculum that prepares future library professionals. I made this suggestion in a post a few years ago, and there was a mixed reaction – everything from “Who is he to tell us how to design our curriculum” to “Sounds like an interesting idea” to “I’m already doing this”. The lack of enthusiasm for my suggestion was likely owing to a lack of familiarity with design thinking. Courses on library instruction, human-computer interaction or usability studies may include some elements of design, but it would be completely different to integrate design thinking philosophy into the curriculum – so that every graduate has internalized the design inquiry process as a problem-solving methodology. As a result of that post, I was asked to participate in an ALISE conference panel focusing on design in the LIS curriculum – thanks to those faculty who were open to the possibilities. Clearly there is opportunity here. To my way of thinking, the first LIS program that successfully merges design thinking and library science will establish a distinct advantage in the field. As a starting point, take a closer look at how B-Schools are integrating design thinking into their curriculum and why they are doing it. Even better, make a visit to the Stanford D-School.

This post is not intended as a critique of our LIS programs. There are great programs turning out high quality graduates. I do think the LIS program that breaks new ground by integrating design thinking and philosophy into the curriculum will establish a real advantage over the programs that stay the course. We need LIS graduates with those traditional skills that prepare them for library work. We have a greater need for students who are savvy problem solvers. With the wicked problems confronting the library profession, we need colleagues who can design elegant solutions. Design thinking skills could help our future librarians be the kind of problem solvers and decision makers that can tackle any challenging no matter what area of librarianship is involved. That’s what design thinkers do – they figure out what the real problem is and design a solution. Perhaps some L-Schools and I-Schools will seriously look into the D-School trend, with an intent to use it as a model for future curriculum development. If the goal is to create better libraries, should’t it start with how we prepare future librarians? In the meantime, is it possible that more libraries will just start hiring D-School graduates? I think some already are or will do so soon.

A Manual For Design Thinkers

One of the knocks against design thinking is that it’s too much about thinking and too little about taking practical action – getting things done. I wrote about this reaction, which calls into question the value of design thinking, and suggested that we needed to focus more on the design approach as a practical method for putting our design thinking tools and techniques to work. In seeking out more ideas on how to accomplish this I acquired a copy of “Designing for Growth: A Design Toolkit for Managers.”. I believe the book has lived up to expectations. Of the numerous books and articles I’ve read about design thinking, this one is the best at providing a concrete approach to applying design thinking in your practice. Yet in many ways the book sticks to the blueprint for design thinking, albeit broken down into more steps with a variety of techniques organized into “ten tools”.

Let me give you an example. In the classic IDEO method, the first phase of the design thinking process is to be an empathic designer – to put yourself into the place of the end user of your service or product. As was famously said about designers in the Deep Dive video by David Kelley, “We not experts at anything. The only things we’re experts at is the design process.” The video then goes on to illustrate how designers go out into the field to study the existing experience and learn from the experts – those who either create or use the product or service. The second tool in the Toolkit is Journey Mapping. This is an exercise the design team conducts to create a graphic flowchart of the customer’s experience as he or she interacts with the products and services provided by the library. The whole point of Mapping is to deeply understand things from the point of view of the end user. What’s the first tool? That’s another thing I really liked; it’s visualization. The authors, right off the bat, emphasize the importance of visual communication throughout the design process. There’s a chapter dedicated to each of the ten tools, and the one on visualization even has some sketching tips.

Many of the steps, processes and tools discussed in the book really connect back to the basic fundamentals of design thinking. The difference is in the way the ideas, practices and techniques are organized around four phases of the design process: (1) What Is? (2) What If? (3) What Wows? (4) What Works. It’s interesting that steps one and two are all about discovering what the gap is between the problem and potential solution. Again, that’s classic design thinking. What Wows is all about prototyping, and What Works is about implementation and evaluation. It’s all there. That said, I see this book as being somewhat different from others on design thinking. Others, like The Art of Innovation or The Design of Business, are more like straight read throughs. This book really is more like a toolkit. You just use your hammer or screwdriver when you need it to get a job done; you don’t take out every tool in the box. Likewise, if I just want to invite our community members to work with us in developing a new service, I can just make use of the chapter on customer co-creation. It offers me the steps I need to follow to get this done successfully. While some may come away with the impression that the book is a bit on the busy side and that there are many possible distractions within the book, I tend to prefer the many sidebars used throughout the book. They may be a bit of a distraction on the first reading, but then you discover there’s lots of practical advice and ideas found within those sidebars.

If you want to get a taste of the book Designing for Growth, you may want to read an article based on the book, “Learning to use design thinking tools for successful innovation” that was authored by Jeanne Liedtka in the journal Strategy & Leadership (Vol. 39 No. 5, pgs. 13-19). It is behind a paywall, and your library may or may not provide access (NOTE: it can be “rented” for $3.99 via DeepDyve if that option works for you). When librarians ask me to provide more practical ideas for how they can implement design thinking in their libraries, I’m going to point them to Designing for Growth. I think the authors are on the right track when it comes to moving potential design thinkers from thinking to doing.

From Design Thinking to Design Process

Since writing this post focusing on Bruce Nussbaum’s essay about design thinking as a failed experiment I have come across other posts and articles referencing the essay and commenting one way or another on the state of design thinking. One in particular titled “The Short Happy Life of Design Thinking” authored by Damien Newman was published in the August 2011 issue of Print magazine (sorry but this article is not online), and though it’s a rather short piece I thought it did a good job of capturing the essence of the main critique of design thinking: design thinking doesn’t actually get the desired results. Newman writes:

And here lies the difficulty with the term “design thinking”: It didn’t offer an actual, repeatable process but rather defined how a designer should think, a kind of mind-set that would set in motion the process of design. Design thinking alone didn’t have the results that the simple process of design did…Organizations that bought into the concept of design thinking were not getting what they wanted, which was to produce better, more innovative results.

Newman then goes on to share the story of a new social change project called Common, described as a community for the rapid prototyping of social ventures. One of their ventures is Common Cycles. Newman’s point is that Common is an example of a post-design thinking organization that brings together experience, intuition, creativity and collaboration. Newman believes this is a good example of the transition from design thinking to design process. As I read Newman’s piece I was puzzled between the difference between design thinking and the design process; they seem quite similar in the components that define them. Then I had an experience with the design approach – which is similar to what Newman describes as the design process – and I now think I see how the design approach is similar to design thinking and perhaps is even based on the same principles – but which gives a more practical process for putting it to work on designing solutions.

Here’s what happened. About two weeks after writing the post about Nussbaum’s article I had a great experience in which I participated in a two-day design process workshop at Temple University. This is a development about which I’m quite excited. It is part of a larger effort to integrate more design approach-based education into our B-school curriculum. Most of the activity is coming out of our Center for Design and Innovationwhich is led by Youngjin Yoo, who was previously at the Weatherhead School of Mangement at Case Western University. I previously wrote a post about the book Managing as Designing, a book that evolved from a conference on design in business held at Weatherhead – and which contains a chapter authored by Youngjin Yoo (which I subsequently realized after writing the post). I’ve since had several conversations with faculty leading the effort at the CDI, and we recently collaborated by having our incoming MBA students conduct a design project (about wayfinding) here at the library. Back on June 16 and 17 I attended the Center’s Business is Design workshop, facilitated by Yoo and James Moustafellos, an architect, designer and entrepreneur (and also faculty at the B-school). I thought I knew a good amount about design thinking, which was discussed in the workshop, but I really learned even more about it, primarily the hands-on aspects of the design process.

Here are a few highlights of the workshop:

* Develop a design attitude as a process for innovation – the process should be an iterative one in which we should be asking ourselves “can we make this better?” and being deliberate about taking action to try to make it better. (an exercise using pieces of paper to simulate a design process and express the attitude)

* Technology is not always the path to innovation. Listening, observing and working in teams is another means to achieve innovation. Constraints such as time or resources move the process forward as they force us to be deliberate in our thinking. (a small group activity involving intense listening and shared observations)

* We use design to deliberately shape the behavior of the user (anecdotes about urinal design with the goal of keeping these areas cleaner). Great design can achieve far better results than text-based signs.

* Empower the organization to get everyone thinking and sharing ideas. Move from the old mainframe/dumb terminal paradigm to the personal computing paradigm where everyone is empowered (of course there is the struggle between innovation and control).

* Systemic experiences emerge from the design inquiry process – composed of five questions:
* What are the problems?
* Who are the stakeholders?
* Why are these needs/issues important?
* What are the solutions?
* What are the resources?

* Use the design approach to move from things to action. Move from nouns to verbs. A library is a thing. Transforming people is an action.

To reinforce many of these ideas the workshop challenged us with many design approach activities. I’m not going to provide those details for two reasons. First, this is already a long post that would become even longer, and second, I am hesitant to divulge too many details that would take away any of the surprise elements for those who may take this workshop in the future. I will say that the second day of the workshop revolves a major project that requires the participants to go through the design inquiry process in a very hands-on way. In a combination of field study – getting out to observe, listen, ask questions, record data, etc. – and team-based workshop exercises (e.g., creating personas, experience mapping, etc) the participants gained a great understanding of what it means to go through the design inquiry process.

When I registered for the workshop I thought it would simply reinforce what I already knew about design thinking. It did much more than that. It moved me from just seeing design as a way of thoughtfully developing solutions to a process in which we have to engage ourselves in a mental and physical way. This is why Damien Newman’s article resonated with me, which it may not have without the design workshop experience. Now I understand what he means when advocating for moving from “thinking” to “process”. I believe there is value in understanding design thinking as the way in which designers approach their work, but it is more powerful when we acknowledge that we also must engage in the design inquiry process when we want to produce the “better, more innovative results” that Newman describes. I plan to continue my involvement with the Center for Design and Innovation at Temple University because I believe there is much more yet to be learned about the design process. I would encourage you to seek out similar opportunities – and encourage your colleagues to join you.

Design Thinking’s Guru On Leadership

Bruce Nussbaum is ready to get off the design thinking ship, but one of its original captains is still strong at the helm. I’m talking about David Kelley, described in this recent interview with Fast Company as the principal guru of design thinking. In this interview Kelley doesn’t comment on Nussbaum’s decision to move on to something new that he calls “creative intelligence”, but focuses on how design thinking applies to leadership. To motivate employees and enable them to achieve workplace success, a good leader can improve by applying some basic design thinking processes.

Here are a few of Kelley’s insights into “leadership by design”:

* The main tenet of design thinking is empathy for the people you’re trying to design for. Leadership is exactly the same thing–building empathy for the people that you’re entrusted to help. Once you understand what they really value, it’s easy because you can mostly give it to them.

* The way I would measure leadership is this: of the people that are working with me, how many wake up in the morning thinking that the company is theirs?

* I’m trying to get people to remain confident in their creative ability. In order for them to have that kind of creativity, you have to be very transparent. Understand them and involve them in the decisions being made. Even if the decision goes the wrong way, they still were there and saw how we decided to do this and so they’re behind it.

* I don’t think people do anything out of fear very well. So I think the only choice is to have them intrinsically motivated.

This is a worthwhile read because I previously haven’t thought much about the IDEO approach to design thinking as a touchstone for better leadership. But I like the ideas that Kelley shares. What is more important than having empathy for those we work with everyday? How, as a leader, can I achiever greater transparency? How can I encourage creativity and innovation within the organization? As always, Kelley gives us something to think about beyond the traditional perceptions of design.