Episode #21: (A) Affinity Diagram - #dddAtoZ

Hi, welcome back to my channel, Miky is here, sorry, sorry, this is a new device, new device, okay guys, maybe you know it first, this is a podcast session on the spot, it's easy, the sound is clear, so I'm Tri from Gojek, please introduce yourself from here. Hello, I'm Heikal from Ticket with my head product, hello, hello, I'm Rian, product designer on Ticket too. I'm Anga from Teeet. I'm Evan from Gojek Research. I'm Raufan from Ticket.com. I'm Barry from Ticket, Heikal's friend. Okay, so here is Gojek, there is Ticket, there is NAF, Jobatical, Sun2B, yeah, I know it. Okay, we want to discuss DDDA2Z, so we want to discuss from A to Z, what topic can we discuss? Well, this is the first design, sure, we start from A, then we have polling, it says Avinity Diagram. Well, what actually Avinity Diagram, maybe from me first, yes, later I give to the research team that usually use it very often in Gojek, Avinity Diagram, Actually, don't be too curious about the name, the point is just tools or framework for you to organize a problem, so you find a lot of problems, then you organize, then after that you know what you have to do from that problem. If you think about it, Evan, from Gojek Research, how? Well, basically like I said earlier, Avinity Diagram is like a method for how we can understand what the problem is actually, because from each person there are many points, points from different teams, from different users, maybe the problem in different points is given differently. Well, from that Avinity Diagram, it's like a method that we use to solve the problem and we can know what the big problem is, and actually from all the problems, what is the point, and we can also prioritize the problem after we solve it. That's how big the picture is. Okay, let's try to start right away. For example, you get a challenge to make a general transportation application, right? Sure, before we start, when designing, you usually find out what the problem is in general transportation. Now let's try to ask here, what is the problem when using general transportation? My problem is because the report has to be transited from several stations. From me, I also don't know where the transportation route is. The space is too narrow for large people. Yes, for me, the schedule and the capacity. For me, the security. For how long I arrived at the destination, it's not sure. Okay, I'll go back. What was that, Ben? Sorry, it's not clear. I don't know when I have to arrive. When you arrive, right? Oh, ready, ready. Okay, now, for example, we arrived here. You already got a problem, right? One said, report, if you want to go to Angkor, right? I said report. The second, the route is not clear. And then there is the one who said, the biggest problem, the space is too narrow in Angkor. And then there is the one who said, the schedule and capacity of the passengers are not clear. And then, Ravan said about security, safety, I'm worried, right? And then the last one, Berry said, it's not clear when you want to arrive. Well, that's from some, what's the name of the inside that we already got, the problem. It can actually be gathered. For example, for example, what is talked to Berry, the same as the one talked to Evan about the schedule. Well, the next step, Vinitidagrem, is that we write here, the inside, the inside. Write in the post-it notes, one by one. And then it's out, 7, right? 7 or 6. And then after that, the inside that is gathered, we gather, which one is similar? Maybe Evan wants to add a process in the gathering. Well, there was a problem earlier, if we can see, what was it just now? Try, try, try. Report, route, it's not clear. And then the space is too narrow, the schedule and capacity are not clear, the security, it's not clear when you arrive. Well, if you're here alone, we can see there are some red things in the design. First of all, like the report, the space is too narrow, the security. That we can, like, the comfort from the one who uses the facilities. Then the problem of schedule and capacity, and it's not clear when it arrives. If the schedule is when it gets up and how many hours it is. That's more to the problem, maybe information and the problem of infrastructure too. Yes, that's what we mean, we have two big gaps. The security and the second is the information and infrastructure. That's what we mean. Okay, so we already have two big gaps, which is information and security. Okay, well, we have two big gaps, right? After that, what's the step? Evan? Well, next, from the problem itself, we are looking for the main problem from the comfort. What is the most, if we, for example, research, we interview users or ask random on the road, survey, what is the problem that comes out the most? So we know that the comfort of the user is, for example, the accessibility problem. Or the problem earlier, because of the report, because we have to go anywhere first mile, the last mile. That's what we're looking for, what's the main problem. Then from there, we prioritize the most frequent, most out there. So we know the magnitude of the problem, how big it is. Okay, that means after collecting it in prioritization, right? In prioritization, okay. Well, for example, after prioritization, that means you already know what's the most painful, what's the most necessary to be solved, right? Well, in the affinity diagram that is in the book, just enough research, basically you imagine that there are three levels. The first level below is post-it notes. You have to imagine the six points that the problem is called, friends, friends, one by one, you put it in the sticky notes, right? In post-it notes. There are six, right? Well, you collect it, it's called observations, it's in the first layer, the lowest layer. So observations, from observations, we get six or seven problems, right? Or insights. Well, the second, in the upper layer step, level two, level one below, then the upper level. From the problem you found, you have to draw the insights, the point is the conclusion, right? From the bottom, you have collected it. Earlier, I met a big theme, collected, then information and comfort. Then it became an insight for you in level two, that oh, a lot of people feel less comfortable to climb the anchor. That's the first insight. The second, oh, information about the anchor is often not clear, that's the insight. Well, after that, we simply enter the next level, the last step, which is to make, what is it called? Action items, or in the book it is called design mandates, right? So, from the insight you got, you have to think, oh, maybe if the insight is like this, what should I do? Well, now we ask each other again, friends, the design mandate is to make an application, maybe because you get the insight, the information is not clear, the schedule, the capacity we don't know, how many anchor, what is the name, the course, then the second insight, the second about comfort. Comfort means, what was the name, the bank is not enough, and it's not safe to anchor. Well, now we ask, after you, the designers know the insight, guess what solution you will make, what is the design mandate? In the design mandate, for example, there was a problem earlier, what is it? The schedule is not clear, so in the design mandate, we have to make clear information about the schedule that can make the user easier. That's one example of the design mandate. Maybe one of these, there are two scheduling, there is the right router for the router. It's different, bro. I don't know if it's a report, what is the access, can you show more clearly, more clear? I can't pause, bro. Why is the design mandate here? So you can just guide the front to determine what is the take-aways for the next step in the project that is being worked on. Well, maybe the user, because he had a problem like that, maybe the solution is to make the schedule more complete. The estimated time rival, when, to know, okay, how long do you take the transportation, and what facilities will be there, and what is it? That's the most important info from the problem earlier. Let's go back again. Okay, then maybe from me adding, for example, there was a talk about security. Oh, that means you in the app should have, for example, an emergency button, for example. When you are in an emergency, you can press the emergency button, for example, call the police, for example, like that. You can do it, right? Just like that, practice doing affinity diagram, so basically you, what is it? You're collecting this problem, right? But when you gather it, it's not clear, it's not the same group, the problem is different. Well, after you gather it, you organize it, oh, this problem is similar to this, this is similar to this, and then after you organize it, you look for the insights, oh, that means the summary. This is for this group of problems, and then after that, you look for the design mandate, the design mandate means the action item to solve the inside-inside, you get it. Well, now I want to ask, because there is a lot of practice here, right? Maybe Keraofan, who is very often implementing affinity diagram on ticket.com, please. What is it? Well, actually, what I often do in projects that I work on on ticket.com, it's just like a weekly checkpoint. Well, there, sometimes, actually, it's not directly implemented from this affinity diagram method, so sometimes after we gather the problems together, then group the problems together, then look for the solution together. Well, that's usually not only the designer, so all the stakeholders of the project are invited, starting from Team F, back-end, then the PM is sure, and all of them are involved in the project. Maybe now we go to the tips and tricks. Do you have tips and tricks, so that the problem-solving session runs smoothly? If you were from Ravan, you invited everyone involved, engineer, product, so don't just be a designer, so that it's more successful. Maybe from Heikal? If it's from me, what's the trick? How is affinity diagram more successful? Oh, so that it's more successful. Well, actually, there is research on the user, so sometimes if it's just from us, it can be just assumed, right? But if we interview some users, look for the problem from the real user, the problem is getting closer to the real problem. Probably from me. Maybe from Evan? If it's from me, like the others also invited users to research and listen to what they think is the most valid source. Because they solve their own problems, and in that process also look for variations. If the user can be random, like from various sources and characters, criteria, and also invite people like Ravan said in the PM, the developer, it also has a very significant effect. Because they will work, and they will know why they have to do something and why something is chosen. And they also have empathy towards the user, that something they work on will have a significant effect. Do you want to add more? Just add more, yes, that's enough. I think it's good, don't forget to document it. Because usually if you just go through it, you will forget it, so don't forget. If I use remote, I use a mirror board, so I use a post-it, it's like online whiteboard, and not a post-it type. That's a very good tip, what is the name of the mirror board? Mirror board. Mirror board, okay, that's cool. Okay, that's good, guys, the name is mirror board, right? That's for those who usually work remotely. Okay, what else? What is it? Maybe tips, usually when you interview people, there are a lot of data, right? There are a lot of insight. Are there any tips to help solve the problem? First of all, we look at what is written on the post-it notes. Then at the beginning of the session, each person can write. Write all the problems, then paste them on the post-it notes. That's the first session, just put them on the post-it notes. But after that, we think about what the problem is. So we invite people involved, "Oh, this problem is similar to this one." So we paste the post-it notes on top of each other. So we know, "Oh, this is the problem, this is the problem." So it's a mixture, and when... So it's like validating, right? For example, checking, "Hey, do you think this is the same as this one?" So there's a discussion there, like, "Oh, this is the same as this one?" Or maybe, "Oh, no, I think it's the same as this one." So one room is already one frequency about the problems that we determine. Okay, maybe the kids want to add Mas Berry. Tips, discovering the problem, finding the solution, and solving the problem. If it's on a ticket, usually, because we're very specific about the business. OTA, for example, if I'm on a flight, looking for the problem, usually it's just outside the application, outside the application stability. So, for example, the stakeholder is important. Like, for example, business, team tech, or board of directors. Usually, we invite them to look for the problem. Then, in the cluster, to know, "Okay, the problem is here. The problem is in the application." Or, "The problem is in the airport." Or, "The problem is transportation to the airport." So, the output is finished in this diagram. We then know, "Okay, what's the big picture?" Then, each of them will have another page. For example, "Okay, the designer, the scope is just a product. Solve the problem of the product." But, for example, the marketing, you know what the marketing problem is. Or, for example, business people will know, "Okay, the problem is in the business." The solve is like this. So, actually, this affinity can be used to find the solution and to find the problem that is wider. Okay, that's it. Thank you, thank you. Thank you, Mr. Kanek. Well, I want to say one more thing. Maybe the last question, for all of you, the designer of this business, right? Okay, find the inside or solve the problem. Okay, that's one thing. But, how is it actually, you have an idea to change that into a real-time design? Ravan, maybe you have an idea? So, in the project that I'm working on, usually, it's back to the beginning. So, there are two weekly projects. One is with all the stakeholders. The other is with the only team design. Usually, we are the only team design. So, we are the only team design. We are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. So, we are the only team design. Okay, that's all. Please prepare the questions for the next group. I, Tree, Hekal, Rian, Angga, Evan, Ravan, Berry, Pandit, Unduduri. Thank you for listening. Bye bye, Assalamualaikum. Bye.