O que é DESIGN THINKING? | Bootcampinho UI/UX Design

Are you really thinking about your design or are you just repeating ready formulas? In today's class, we're going to talk a little bit about what Design Thinking is, which is basically this thought-out design. Or at least it should be, right?

After all, how should we go about the design? When we talk about thinking about the design, it's important to remember that the process has to be more important than the tools. What do I mean?

Understanding this process, understanding what is being done has to be much more important than, for example, using Figma, using Adobe XD, this is just a detail in your project. When I talk about tools, when there are… All these UX Design tools too, like persona creation, qualitative research, quantitative research, user flow, user whatever… a lot of little processes, little tools, more importantly than knowing all these things is for you to know what to do and why you have to use each one of them. When to use them, in what way, so this process is very, very, very important.

And a very important point in this whole process is that you need to have a very clear objective, that is, when you say, “I want to solve a problem”, you gotta have it very clearly in your head what problem do you want to solve, because from this problem you will be able to come up with insights, research, all the rest of this tangled design process that we usually see as being cute, with little lines, everything straight, it actually is a mess of going back and forth, move it, don't move it. . .

anyway, I'll teach you with a more linear process, since you're learning. But know that many times this Design Thinking goes into one step, then it shifts back to another and with time you will start understanding this malleability of when to go and when to come back, what to do, what not to do, but, mainly, focus on thinking the design. Understand what you are doing, why you are doing it and not just copying a bunch of things without even knowing.

For example, there are a lot of courses that say “Ah, this is Design Thinking, in this stage you'll do the persona, you do this, and this, and this, in this step that, that and that. And then the person memorizes it and doesn't even know why they're using it, what they're doing, why they're doing it, okay? I always instigate you guys with the following: throughout your process of learning design, keep this question in mind: If all the tools, if all the “frameworks", for example, design thinking, is a design framework that someone created and it helps you think about the design in stages, but there are several other tools, there are several other processes, for example, personas, someone also created it.

If all tools, including tools like Figma, Adobe XD and all the frameworks, ended today. Would you still be a good designer? Would you be able to do design if you didn't have anything ready out there to copy, and to follow?

If the answer is no, it's a sign that you have to remain studying processes, and studying how to think about design. And this is the hardest thing to learn in design because it's very easy for us to copy what's out there, but more important than copying, and I'm not saying that you shouldn't use what there's out there, but mainly use it and think about why you are using it. What are you doing, what is your objective and if it makes sense for your project.

Because it makes no sense for me to tell you "do that, and that and that", and maybe that doesn't make any sense for your project, okay? So, always question the rules, the norms, the laws, the tools, always have critical thinking, even to what I'm telling you guys here, okay? So, as was said, Design Thinking is a design framework, it is basically a structure that was thought out on how you can create the design.

And to better explain to you what this Design Thinking is, since it will guide our course. . .

So, it's ONE design process. There are others. Why am I explaining this one?

Because I use it a lot in my daily life. Normally, I adapt them depending on the client, depending on the project, depending on what I need to do, and that's cool, because you don't have to follow it strictly. And it's cool to know, because Design Thinking is being used a lot, not only by me, not only in a company, in several companies out there.

And it's a process that, in general, I believe has a very nice logic and it gives you. . .

It teaches you to start thinking about design from itself and then over time, please continue researching, continue studying this process and understanding which is the best process for each of your projects, okay? So come with me. I'm here with this structure, which is what people usually call a double diamond, which is precisely these two pretty diamonds here, see?

And Design Thinking is usually built on top of this structure. What do I mean? Look, typically, you will start with an assumption of the problem.

Remember I asked you guys, as a challenge in the previous lesson, for you to find a problem to solve? So that's your problem assumption. I have a problem assumption: people don't donate stem cells because they don't know how to donate it.

For example, this is my problem assumption and I'm going to try throughout this process to solve it from there. How am I going to do this? In Design Thinking, following a linear path, without comings and goings, it works as follows: the first step is the discovery step, that is, you will discover and understand the problem.

What do I mean? The goal of this phase is to learn as much about the product and issue as possible, including trying to find things you didn't even know existed. Do you see that here, this [diamond line], increases?

This stage here, discovery, it is a stage that it encompasses, it grows, you see? And this stage grows because that problem assumption, for example, I thought that people didn't donate stem cells because they didn't know how to donate it. I'm going to talk to people, I'm going to research, I'm going to see everything related to this problem.

I'm going to try to discover things that I didn't even imagine that I didn't know That phrase was a bit strange, but OK… Your goal is to try to explore as much as possible, far beyond what you think you know. It's going beyond, it's trying to break the prejudices that we have, because we have biases. There are things in my head that I believe.

And you also have other things that you believe. As much as you want to get rid of it, you're not going to get rid of it. So your goal is to try to go far beyond what you think you could go, okay?

And that's the discovery phase. You have to find out as many things as possible so at the end of this step you have several problem assumptions, for example, people don't donate stem cells because they don't know how to donate it, maybe another assumption is that people don't donate stem cells because they don't even know what stem cells are, you know? Like, there could be several other derived problems that you didn't even imagine could exist, because in the next step, which is the define phase, your goal is to align the objectives and central problems.

What do I mean? You're going to take all those assumptions of problems that you had and you're going to arrive here at a definition of the problem, that is, you're going to see all those issues that you found out were also a problem and try to understand, "okay, what is the real problem here? Could it be that the problem I had initially that people don't donate because they don't know how to donate is the actual problem?

" "Could it be that the actual problem really isn't that people don't even know what stem cells are? " As you've done a lot of research, talked to a lot of people, anyway. .

. You'll be able to combine these problems. So this first phase is a comprehensive phase and the second is a convergence phase, that is, you will combine the problems to go back and try to find what that real problem is, that central problem.

Usually, I didn't mention it here, but in the discovery phase, some common tasks are, for example, creating the briefing, doing research, analyzing products, competitors, user research, quantitative and qualitative research, we will talk about this during the course. Each of these steps in detail, okay? So, there are several things that can happen in between.

In the definition phase, some common tasks are, for example, consolidating this data, all those surveys, organizing these surveys, defining objectives, defining what the real problem is, because at the end of this stage, you must have defined what is the real problem that you are going to solve, because from this problem that you defined, you will start to enter this part here of idealizing. That part of figuring out your goal is to find as many solutions as possible. What do I mean?

You will do several things here in the middle, for example. You will test flows, you will sketch ideas, you will create wireframes, you will brainstorm… You will try to come up with as many ideas as possible. Again, it will comprise your ideas for you to try and solve this problem.

I have a problem here, what could solve this problem? It could be a crazy idea, you could make a flow, how would the user do it? How would the user think?

Try to talk to more people: “How would you do that? ”, “How would you do that other one? ”, “What tasks do you expect?

” Try to cover your ideas as much as possible, generate many ideas to be able to solve this problem, because at the end of this stage you should have several suggestions and ideas to solve the problem, because from all these solutions that you generated, you will go forward to the next stage, which is the prototyping stage, that is, you will take all those ideas that you generated and you will really start to generate prototypes, that is, you will generate a functional structure of how to solve that problem, you will select one, two, three solutions… three of the best solutions or just the best solution that you believe in, because from that, you will generate a working prototype, for example, you will generate a prototype there in XD, in Figma, of how to actually solve this solution. And the cool thing is that the process does not end here. You will do several things.

Until you align with the developer. Often times, at this stage, you also make technical decisions, talk about what is possible, what is not possible, because finding the best solution is not necessarily, "Oh, it's beautiful for the user", but there's no actual way to make it work. Often it is not viable.

Not only for technical reasons, for budgeting reasons, time, but for limitations of craziness actually. Sometimes the idea is too crazy and it just doesn’t work out. Sometimes, in some cases, the crazy idea is the best one, but in others, it may not work and going out of your way too much is not always the best solution, okay?

You need to validate and that's what you're going to do in this other phase, which is the testing phase, that is, after you have those prototypes, those solutions to the problem, you're going to test. That is, your objective in this step is to validate the solution, you're going to validate those solutions. You're going to talk to users, you're going to do usability tests, you're going to try to understand if it works, or if it doesn't work, because your goal in this step is to have a new problem assumption.

This here [the testing stage] will generate a new assumption of the problem and the whole process can start over. Of course, the way I explained it, it's a totally linear process. It might be interesting, “Oh, I made some sketches here”, maybe you can test directly with the sketches, for example.

Or sometimes you're here in the discovery phase and when you're going to define it, you see, “Wow, I lacked data for my research, maybe I have to go back and do a little more research". So, that's what I say that this process is not necessarily straight, linear. In the course, we will make it a little more linear, but be aware that many times in real life it is not linear and you may need an extra step here and there.

Over time you'll acquire this feeling, and if you want, you can use a totally different process if you want as well, okay? But Design Thinking is cool because it always puts the user at the center of the problem, that is, everything will start from these surveys, these conversations, these things you do with the user, you will test it later with the user and all of this will help you to think better about the design. And just to reinforce, the design has to be “thinking”, that is, if you don't think the design, it is as if you took a bunch of templates, ready-made layouts and just copied them.

Because if it isn't a thought-out process, there's not even a reason for you to go through this whole design process, if it's just for you to repeat the steps without even knowing why you're doing it, okay? In today's class I want to recommend you guys a book that is really cool, which is called “The Design of Everyday Things”, by Don Norman. He is very famous in the area, like, when you enter the area of ​​UI/UX Design it's really cool to read this book, this Don Norman is one of the guys who basically created the user experience.

This book "The Design of Everyday Things" is nice because it brings a really nice notion about how to think about the user, about how you can do all this design process having people at its core. It's a very short book, very easy to read and I highly recommend it, okay? And don't forget, of course, to see the additional materials for the class.

And before we finish, I couldn't finish, of course, without our incredible Alfred's Challenge. Alfredinho said to me: your challenge today is to create your project's Briefing. Remember that we saw in the last class what the briefing was?

How do you create one? So, my suggestion is, go to our Notion template, come here… on "Course Project“, click on “Course Project”, also, if you want, you can change it here, put the name of your project, now that you know what you will do. And here is the project briefing.

So, fill out a briefing, and understand what the scope of your project is. Your objective in this class is for you to create the scope, what are you going to do in your project, what is the size, what is the deadline, until when do you intend to finish it, for example, who are the people involved, everything neat, everything listed, what is the briefing for your project. .

. Because from the next lesson onwards, we will start to develop and really dive into this Design Thinking process and then the classes will get a little bit more challenging, okay? So, let's start this Design Thinking in the right way?

Do you really want to know what we will do next, how do we get started, how do we put these processes into practice? So, click on the card on your screen, because on our next lesson, we're going to start talking a little more about the discovery phase.