Showing posts with label Design Process. Show all posts
Showing posts with label Design Process. Show all posts

Presenting the Design Process at Parsons

I was graciously invited by a friend to speak to her design students about the most important thing I learned while studying design: the design process. All other tools I've learned in my short design career have been to support solving problems. The following slides and pictures show a story about how I communicated the design process to freshman and sophomore design students at Parsons.

During the presentation, I gave two examples of previous work experience, describing how I've understood the design process fitting within the work environment. I ended with a short design scenario, asking the students to identify the design problem and propose how they might go about researching, prototyping, and testing a solution to the design problem.



The Perspective of Human Centered Design: What is it?


Human Centered Design has two premises. The first, individuals comprising a culture are the experts of their culture. The second, in order to design a solution for a culture’s problem, the designer is not the expert of the solution or the problem. A culture comprises all the rules and beliefs, tacit and explicit, governing interactions between individuals, thought and action processes, and value systems. An individual can be a part of several different cultures and cultures may also influence one another just as individuals influence one another.

The implications of these two premises set the necessary conditions for a design process that removes the designer as the locus of action for solving and framing a problem. This means the designer acts as a communicator and investigator, discovering a culture’s problem through ethnographic research, interviews and surveys, and cultural probes. The information gathered is synthesized, analyzed, and summarized to be communicated back to the individuals of a culture so these individuals may validate or invalidate how the culture is framing its own problem. This means the human centered designer is also a facilitator, allowing the culture to use the designer as a means to solving their own problem.

Previous attempts at describing the human centered design process and other design related topics:


  • Reflections on Design Research: Framing the Problem, Part 2
  • Reflections on Design Research: Framing the Problem
  • From Neuroscience and Philosophy to Design: Some Thoughts on Thinking and Solving
  • The Shopping Mall and The Design Process
  • Explaining Design to Non-Designers
  • Revisiting Design's Value to Business
  • Design vs Business: What Value Does Design Add to Business?
  • Design Research: The IDEO Way
  • Fourth Order Design: The Underlying Structure of Communities and Moral Obligations of Designers

  • Communicating Design to Non-Designers

    Now that I've almost completed my Master's in Industrial Design, I've been struggling with how to communicate what I do to people that confuse different disciplines of design with each other. Part of what gives rise to this confusion is figuring out the role the designer should play within an organization, as part of a team, as a freelancer, and even as an entrepreneur. The problem I've encountered with clients is the perception of design. They perceive design as its end result, which is aesthetics, feelings, a sense of ease while savoring a well designed experience or interaction. I use the word experience very loosely, and as an umbrella term for products, services, systems of people, corporations, etc.

    Being a designer, I've been trying to frame this problem of client perception in various ways, and I've been prototyping various explanations and I'm going to present the latest iteration:

    Design is a problem solving process that encompasses two major parts. The first is researching and framing a problem, the second is prototyping and iterating a solution. Transitioning from the first to the second part requires synthesis and analysis on the subject being studied.

    Since I'm receiving a master's degree, people tell me I'm supposed to be an expert in something. I'd argue that I'm an expert in a process as opposed to being an expert in a specific field. This process is sometimes called design thinking, and other times people call it human centered design or fourth order design. It leverages anthropology, psychology, and sociology to make sense of the human experience in order to research and frame a problem. For prototyping and iterating solutions, we leverage digital and physical tools: borrow processes from engineering and graphic and product design, to business modeling and service design.

    I've been having difficulty figuring out a role for myself within an organization and how I should present myself because every job opportunity I've had thus far has been from word of mouth, meeting and talking, and occasionally brainstorming to show some of these design thinking tools in action.

    More to come as I spend time thinking about my role as a designer within an organization, and my role in our current society and as an entrepreneur.


    You may also enjoy reading:


    Reflections on Design Research: Framing the Problem, Part 2

    Re-reading my previous post about design research and how I described what it means for a human centered designer to frame a problem in the context of a community, I realized I needed to break down the different steps involved in framing a problem. Just as I did with my previous post, I'll use examples from my thesis to show the different steps, but this time I'll also reference several design texts. This will build up a language to describe design research and its role within the design process.

    A theme in design research is to understand the relationships between different problems. Understanding how problems are connected by using visual mapping techniques can greatly aid in sense-making and communication. Communicating the interconnectedness of each problem, challenge, and opportunity allows for a deeper level of research that will shed light on the root of the problems you're tackling. Designers call these types of problems, wicked problems, because there is no single, simple, or straightforward solution. Instead, the solution takes on the form of a system of solutions, which tackles a system of problems. Sometimes prototyping and testing each solution within a system is a start. However, each solution for each respective problem is not enough, because a solution by itself does not anticipate the difficulties of interacting with other solutions. Thus, a systemic perspective of the interaction of solutions is necessary.

    For example, after I finished my first round of interviews for my thesis, I became aware of three major challenges for the Philadelphia startup ecosystem. These three major areas included a disconnect between mentors and entrepreneurs, a lack of funding in the Philadelphia startup ecosystem, and the entrepreneur's concern with traction.

    I then learned the relationship between these various themes that surfaced after I organized the data I gathered. The relationship is the following: if startups need funding, traction is usually required and having a mentor may prove to be a first point of traction. This is a valuable insight, but was not enough to justify focusing on mentors. Around the same time of these interviews, I came across a report published by the Startup Genome, which discovered two important pieces of information:

    (1) "Hands-on help from investors have little or no effect on the company's operational performance. But the right mentors significantly influence a company's performance and ability to raise money."

    (2) "Founders that learn are more successful. Startups that have helpful mentors, track performance metrics effectively, and learn from startup thoughts leaders raise 7x more money and have 3.5x better user growth."

    These two key pieces of information pointed towards mentoring as a vital opportunity, challenge, and problem that required some sort of solution. Solving mentoring would then indirectly solve traction and funding because of these relationships between traction, mentors, and funding.

    In his book, Exposing the Magic of Design, Jon Kolko presents three major steps: making meaning out of data, experience frameworking, and empathy and insight. Roger Martin, in The Design of Business, calls these same steps the knowledge funnel, when you're going from a mystery to a heuristic to an algorithm. These are all about discovering problems and solutions, and the important part of finding the problem is correctly understanding the relationships between different problems. If you take a look at the example I provided above from my thesis, the example shows the organization of data points into a heuristic, as Martin would call it, and making meaning out of data, from Kolko's perspective.

    Making meaning out of data is the step you take when you've already completed a round of data collection and are working to find themes and structure to interpret the collected data.

    Giving form to the data and finding patterns is messy!


    Organizing and re-organizing the data reveals structures and relationships between groups of data.

    From the previous example about traction, funding, and mentoring, getting to that finalized, clean, and communicable state takes time and requires an open space outside of your laptop. Kolko describes the need for using the physical format over the digital as a way to permit easy manipulation of individual pieces of data. Otherwise, hording the various pieces of collected data in a digital format imposes a file and folder hierarchy that may prevent insights to be gained.

    More examples and thoughts about the design process to come in part 3 of this series.

    To read the current draft of my thesis, go here.


    You may also enjoy reading:


    PLObject: Playful Living Object - User Testing

    A PLObject is an object that is aware of the child’s frustrations, engagements, excitements, and movements. Two semesters ago I prototyped and developed applications for the Emotiv headset, and one such application was a toy and a game for children. The goal was to provide an external representation of the child's frustration in the form of towers that rebuild themselves. When the child became too frustrated, the towers rebuilt. A demonstration explaining the inner workings is here. Check out some of the videos of users testing the plobject.








    The Shopping Mall and the Design Process

    Approached by a certain mall developer, they proposed a project that would have the design team creatively re-envision the future use of the shopping mall and vacant mall spaces. Throughout the course of the project, the design team became aware of the client's self-perceptions, analogies, and words used to convey their ideas and business plans. While collaborating with the client, the project proposal changed. It now incorporated informational design of the client's business language. Information design, a human centered designer's bread and butter, is the process of making sense of the bigger picture and succinctly conveying these ideas both visually and verbally. In essence, it involves storytelling to persuade the client to understand who they are, what they do, and how they do it from a different perspective. The following paragraphs recount my experiences and viewpoint as part of this design team.

    The design team's first step was to dive into historical research in order to understand the origins of the mall and the shopping mall as we know it today.