[MUSIC]
In this lecture, we are going to learn about design thinking.
What's the origin of design thinking, what it is, why do design thinking and
how it can help.
So let's start with the origin of design thinking.
So in 1916, Herbert Simon said that design is a way of thinking and
we shouldn't just let design be just one of the step of the process.
And then, in 1991,
Rolfe Faste suggested that design thinking is a method of creative action.
And then in the same year, David Kelley,
who is sometimes considered the founder of design thinking made the first
commercial application of design thinking by launching his company IDEO.
So that's how kind of design thinking come into being and
now it is being applied to many industries, including software.
So our goal would be to focus on how design thinking can be applied especially
to the software industry.
So what is design thinking?
Design thinking is a process of creative problem solving.
So as you can see the key word is creative and it is for problem solving.
It is designed for solving problems which are wicked.
So another definition is methodology for creative and
practical wicked problem solving.
So a couple words that are highlighted here are creative, it's a practical,
and it is for problems that are wicked there are very weird in nature.
And we don't know the outcome,
sometimes we don't even have data to prove what is the right solution.
So in those situations design thinking could be a valuable approach and
then here's how the CEO ideal defines design thinking.
Design thinking is a human centered approach to innovation that draws from
designer's toolkit to integrate the needs of people,
the possibilities of technology and the requirement for business success.
So it's kind of the three circles, human desirability,
business viability and technical feasibility.
And to the union or the intersection of that is what brings innovation.
So how can we come up with a solution that is needed by the individuals, so
human desirability that makes business sense, so business viability.
And it can be implemented which means technical feasibility, so
that's what design thinking is.
Now let's go through the steps of design thinking.
So the first step in design thinking is to empathize and
what that means is to go to the user, talk to the user to understand their work.
And come up with what is the real problem that we need to solve.
Once you understand that then you define,
you clearly define what is the problem that we're trying to solve.
So whatever you learn in the empathize step about your users,
based on that you'll define exactly what you're going to solve.
And then once you defined what you are to solve,
you come up with multiple solutions to solve that problem.
So instead of just going on with one solution,
try to come up with multiple solutions.
And then pick few solutions that you are going to further explore.
And then to explore those ideas, you create prototypes.
That is the way you can bring your idea
into life in an inexpensive way.
So once you create the prototype, then of course you're going to show it to the user
and see if it actually solves the problem.
So it is this short cycle innovation process to continuously to improve
your design or your solution.
And when you are going through this process,
it's not a waterfall process as sometimes people
consider this as a waterfall process, where you just go step by step.
Actually, it's just a way of thinking about different steps but
you can go back and forth between each of those steps and it is generally,
done as a cross functional team.
So you have everybody of your team be part of this whole journey.
Now, let's take a look at each of these steps in a little bit more detail.
So, empathize like I said, it's the process or it's the step where
you actually go and learn and understand the world of your users.
So the question is, why empathize?
How does it help?
So the idea is that we all have bias or
filter on any given situation or a problem.
So if you show somebody a situation, everybody will interpret it differently
because each one of us have a context that we have created over the years.
So how we think about a problem, what we hear is very
different than what our users see, think, or hear.
So we really need to go to them and
work with them or watch them to really understand what are their real problems?
So by doing this step you actually understand what is the real problem
that user is having.
And you don't use your filter to understand that.
So how do you do empathize?
Well, of course you go where the users are.
You talk directly to the customers and users.
You watch them work or the best is to work along side them or do the work
that they are doing so you understand their pains, you understand their needs.
And you understand their work.