Reflection 3: The Design Cycle Deconstructed

When people hear that I am in D-Studio, they often ask, “What does that entail?” “What is design thinking?” And in all honesty, I am continually finding new elements to add to my response each week. From the process we experienced in class with regards to the upcoming Sauder re-opening, my group and I added on to the design thinking process. We added a “share” component at end of the “ask”, “try”, “do”, process, in order to include the collaborative aspect that we believe design thinking entails.

This idea of “share” falls very much in line with Schon’s analysis of “Design as a Reflective Conversation”. However, upon considering the numerous projects we have taken on in D-Studio, in addition to my experience in other areas, I have begun to formulate a new idea of the design thinking process. In order to truly understand how design thinking differs from the typical way of thought, we must first have a common understanding of the traditional way of tackling a business problem. Typically, one identifies a problem, considers the objectives, considers the constraints, and looks for a solution. In relation to the design thinking process, the elements of “ask” and “do” are evident. Although not explicitly stated, there must also be a period of “trial” (try) unless the solution is evident. However, I believe that in the design thinking process, this “try” period can lead to new ideas and objectives that may have not been previously defined. Idea generation can sprout from one particular train of thought, yet can expose new and fresh opportunities. I have found it hard to “buy into” the “Ask, Try, Do” process for two primary reasons:
1) These three simple steps do not address the additional possibilites that design thinking often spurs
2) Ask, Try, Do are elements that are arguably the fundamental pieces for traditional thinking, meaning that there is no difference between the two processes

How would I alter the process? I do not think that design thinking can truly be summarized in a flow chart or process cycle. As can be seen in the reading, design is largely a function of personal/collaborative reflection, meaning that design is highly dependent on the individuals in the process. I believe that we all run through stages of “Ask, Try, Do,” however, not necessary at the same time. The beauty of teamwork is having the ability to “ask” while someone is “trying”, or “try” what someone is “doing”. Being at the same stage of the process at all times is to say we are all approaching the problem in the same way; we are hindering new ideas and new ways of thought to be discovered.

Consider the image below as 3 people continually circulating in the design process, linked, but finding points of intersection at various moments.