[SFT 2026] Design Thinking Workshop #3 : Prototype & Solution Refinement

Recording in progress.

you

Good morning friends, how are you this morning? I hope everyone is healthy and full of energy Welcome back to the Samsung Soul for Tomorrow workshop, 2026 Introduce me, Anggita, who will be the moderator for today's session Well, before I start class, I want to know how you guys today Can you give the reaction in the column

Okay, great, this is really crowded, good morning, guys, okay, before we start, there are a few small things that I want to remind you of first, please for your parents, friends, please go to the mute first and don't forget to

for on-cam using the background that has been provided so that it is also cooler on the camera. Well, for those who do not have a name, you can adjust it again for the teacher's parents, please use the format name _ name of the instance. And students, students can use the format name _ name of the team, like that.

then I also want to remind you again for your parents, friends, don't forget to duplicate the Miro that has been shared, now for the link with the tutorial, it's already seen

in the Telegram group that has been shared by the admin friends. Well, this is also not less important, don't leave the meeting first, because the feedback link and also the post text will be shared at the end of the session. Then if there are questions during the material, you can just write it in the Slido that will be shared by the admin friends in the chat column or raise hand, but during the Q&A session later, not now, friends.

Okay, I'll check first, our mentor today. Mas Kusuma, have you been on standby in the room? Yes, good morning, Magita. Good morning, Mas.

Okay, thank you, Mbak Gita. Good morning, ladies and gentlemen and colleagues.

Samsung's participant solve for tomorrow. We enter the third session today, hopefully still excited and maybe you can check the wave first from friends. If you are ready, you can give what? You can give thumbs up, you can give love, come on, the emotes are a lot, let the screen be full, wow, okay, great, okay.

Semangat ya, karena udah semangat aku ijir cell screen dulu sebentar Kita hari ini akan melanjutkan materi kemarin Ups, sudah terlihat ya Nah, kita masuk ke

the next phase where we will learn about Prototype and Test but before we get into the Prototype and Test for friends, let's recap the lesson yesterday do you still remember last week's material we discussed what lessons you have absorbed yesterday

or maybe I forgot because of a week of busyness, I forgot maybe okay Divine Edith, okay nice Edith okay Divine, okay I still remember Crazy 8, what is this if it laughs? the material is stuck, okay I mean

okay what else besides Define and Idiot, what did you guys think about the previous meeting? for friends, the picture, oh yes this picture, the crazy 8, the speed, the speed, 8 minutes okay, the mirror is filled, Define and Idiot, okay

Nice, it seems like you guys and your parents seem to have learned yesterday

We explore the problem and observe with an open mind.

For our project, Ken and Sean from the Grovemade team fly out to Los Angeles to study my environment and how I work. We did the same study with my mentor, Christo, and from both of these sessions, we quickly noticed some overlap and challenges when it comes to note-taking, a big part of our daily work. As a follow-up to these in-person interviews, we conduct a series of online surveys with Grovemade's email list.

We ask questions to learn how people take notes, what their workflow and tools are, and what challenges they face. From all of these, we were able to make the following observations: First, taking notes is essential to our daily work, using notepads or whatever paper is on our desk. Second, we don't have a good way to store our notes, which usually leaves a mess on our desks or are hidden out of sight, out of mind. Third,

People tend to keep important notes for 3-5 days while processing them. With these core insights and many more, we move on to the next phase: Define. Here we make sense of our discoveries and focus on the right problem to solve. While the previous phase was all about expansive thinking, now we're narrowing things down till we have a clear design challenge. I fly out to Portland to review our insights with the Grubmate team.

Here we kick things around and ask ourselves: What are the common insights and pain points? Does this seem like a big enough problem that others face? Are there already solutions on the market? And is this something we're excited about? After much discussion, we land on the following as a challenge we want to address: How can we design a better way to capture, review, and store notes? With a clear design challenge established, we move on to the next phase: Develop.

Here we go back into an expansive way of thinking, now exploring potential solutions. We continue to work remotely, running whiteboard sessions digitally in Miro. For a few weeks, we set time aside to sketch ideas, share research, and add to each other's work. For me, this is the fun part of the process because it's loose, fast, and it's exciting to see possibilities rather quickly.

In Portland, some of Sean's sketches include quick prototypes made of cardboard, old scraps, and 3D printing, which he sends to me for review. One unexpected challenge in this process comes up with the notepad paper stock, and we spend a few weeks trying to find the perfect thickness that would stand up on its own without feeling excessive like cardstock.

This entire process takes several months of cycles to complete. We refine the ideas we like, test them out, then make adjustments to the form and function, dialing in the details of dimensions, angles, and materials. We settle on a direction that involves a set of tools that work together, an updated notepad size from a previous Gromade design, a stand to hold notes, and a divider to store them. Now we move into the last phase of creating the product: deliver.

the implementation of taking the prototype and turning it into a production model. This is the last part of the design process and we're back into convergent thinking. We know what the solution is, now the focus is building it the right way.

This whole process takes months. It's largely out of my hands and now under the care of the implementation team at Grobemade. They finalize the sourcing of materials, develop how each piece will be made and the processes for assembly, determining the cost to make each piece. This slightly influences the final design and price, but not by much since Sean and Ken kept manufacturing in mind as we went through the earlier phases.

After several months, Grovemade sends me the final product, which I'll give a detailed review of at the end of the video. As the implementation team at Grovemade is completing the manufacturing of the products, there's a few more things we have to take care of to get the product ready to sell: naming, messaging, and marketing. Naming is such a critical part of bringing a product to market because it helps define its identity.

For us, we have to name the individual products we've created as well as the name of the collection since they'll be sold individually and as a group. Our criteria are to: fit within the naming conventions of other Grovemade products, communicate what it does, is nice to say and looks good when typeset, and uses words that are common in the market but utilize any distinctions that set it apart.

Just like the double diamond approach we use for design, we follow a similar approach here. We start by writing down whatever comes to mind, then curate the words and phrases we like,

From there, we expand, researching words that carry the same meaning, then combine, edit, and try out sets of words together until we land on these: the note-taking kit, notepad, display rail, and vertical organizer. They might seem simple, but there's a lot of consideration into how they live in the current and future Grovemade lineup, and where they might appear when searching for these items online.

With the names established, we move on to messaging. These are the core talking points to communicate the essence of the products. I take the lead on this because marketing and content is my area of expertise and what I bring to the collaboration. In this step, I try to keep the language clear and direct to answer the core questions we need to understand before marketing. What is the product? How does it work? Who is it designed for? And why is it valuable?

Going back to our research and surveys, I put my head into the mind of our users, thinking of their pain points and goals when it comes to note-taking. The core messaging I land on is this: The Note-Taking Kit is a set of tools to help you capture, review, and recall your notes. Clear the clutter, organize your ideas, keep your tasks top of mind. Now that we know what we'll talk about, we move onto how we'll say it.

The messaging translates into the copywriting on the website and packaging, as well as the story for videos and media we're creating to generate awareness and excitement for the products. Since Grovemade and I have spent years developing an audience on our website,

Okay, so the image earlier, friends, so the process of using Double Diamond, you guys have learned it yesterday and actually you guys have practiced it until the naming phase and also the key message. Well, yesterday you guys made the logo, right?

Actually, this part is already producing ideas into a product that is ready to develop. The concept is already done, you just need to imagine the prototype. Today we will try how you can build the visual into a product.

Alright, so as an illustration, he left from Homemade We, the growthmate. So this problem statement determines how Homemade We creates a space for the solution. And this is your compass, friends. Where do you want to bring the product later? There were four questions. Why, how, who, and what was the other one? I forgot. So...

This is what determines where this product will be directed. And the process of diversity and conversion is important because every time you want to get as many ideas as possible, you must have a diverse thinking. And you convert to get the results that you want to prioritize, according to the impact effort that you have learned yesterday.

So prioritize 1-3 ideas from your idea process, prepare the ingredients and we will decide today. So yesterday you guys have thought about what the shape and process are all in Crazy8 actually. The idea is great in hand, so what's next? Well, we will

Enter the prototype and test phase. What you need to remember, friends, don't fall in love with the first idea. Because it will be misleading, friends. Ideas on paper are like assumptions, friends. You need to validate it. So maybe you're the best.

It's not that easy, Ferguson. If you haven't tested it, you don't know if this product really has an impact or benefit for the user. So what we need to do is from the idea we visualize, that is by doing prototyping. So, to create an idea in a simple visual form, it can be touched, it can be tried. Like earlier, the product is actually simple, the product is like notes, but from a material that

Recycle, and he made several versions so that the paper can be placed comfortably, it can stand up, it's actually very simple, but the process is long.

Because it's not that easy to create a high quality product. That's why it takes a lot of iterations, a lot of trial and error, until you get the most optimal result or the result that you think is the most relevant. So you do tests, tests, tests, tests,

and try prototypes with various corrections, variants, iterations, prototypes, get feedback, rebuild or maybe fix the shortcomings so that you can learn which one is successful, which one is not, and you have to fix it. Okay, where are we? Well, actually we have entered the final phase, friends.

So, in design thinking, we are in the last two steps, prototypes and tests. But the process is not over yet. If we have reached the test, then it's done. No. From this test, we can repeat it to the empathize. We try to target others, for example. We create new features, new development features. We will go back to the empathize. So if you see, for example, you use services,

OTA, Online Travel Application, they have a lot of processes, friends, so if there is a new feature, the product is done, but for example, if you want to add a menu for car rental at the airport, for example, they will repeat it again from MPTX. Is there a need from our users to use a car

car rental at the airport and he will try again prototype, how is the interaction or maybe experience, is it necessary if we are traveling and there is this what is the activity, the tourism activity, we empathize again listen to friends if traveling like to go anywhere to the mall or friends to sightseeing to tourist places

What is the process like? Did you buy the ticket first? Did you prepare earlier? And all of that is because we listen to our target user. Finally, it becomes a feature that you see now. If in the OTA brand, there are events, there are experiences, etc. It's actually part of the process.

to make an idea into a product or even a feature in an application that has been created or even later you make an IoT product for example there are additional features, etc. all of that is based on the process. Okay, let's get into the prototype. So how do you turn an idea into something that can be tested?

Let's watch it first to get an understanding.

Code works. Let's walk through an invention we made here at Kid Museum called a movement dice. Our movement dice has different exercises on each side. That way when you roll it, it tells you what to do. We wanted our dice to be made by our students so they could design and customize each side of their dice. The first step of our prototyping process is making a sketch. Our sketch allows us to see if we like our idea and it allows us to get feedback from other people.

If you don't want to make a sketch, you can also make a prototype as a 3D model in Tinkercad. Here we made our prototype out of cardboard. We liked how it had six different sides for six different exercises.

So we drew our different movements on our dice and then we gave it to kids to test. They liked how it looked and how it worked, but they didn't like the tape on the sides and when they rolled it, they said it was too light and it didn't roll very well. So then we had to think what new material could we use to help fix this problem. So we decided to do some brainstorming

and we went with wood as our material. So we had to then think, if we want other people to make this dice, how are they going to put it together? We decided to make our sides puzzle piece shapes. That way you get cleaner edges when you put them together and it'll be easier to assemble. After we had our box put together, we gave it to other people for their feedback. They liked how it felt, they liked how it rolled, but they thought our dice could be a little bit more exciting. They suggested we add some sound to it.

So back to the drawing board and we decided to add a micro:bit to give it some sounds. Our micro:bit allows us to add sound to our dice so each time we move our micro:bit

It plays different sounds. We tested our micro:bit over and over again because this is our works-like prototype. We wanted to make sure our code worked the way we wanted. We had our code, we had our micro:bit, now it was time to put it in our box. At first we just put it on the inside, but then it was rolling around too much when we rolled the dice. So an easy way to fix that was to just tape it to one of the sides. That way it stayed in place as we rolled our dice. Now we had our final prototype product.

This now allows us to ask questions like, do other people know how to use it? Does it work the way we want to? And do we like how this looks? Throughout this prototyping process, we tried a lot of different things and tried new materials to get to a product we were happy with. Don't be afraid to try new things because that's what the inventing process is about. Keep on making. Yeah. That's how simple we want to make the activity. So,

The process was first sketched, then made a prototype, then imagined, then made a prototype in the form of a cardus. But after getting feedback, it turned out to be too light from the cardus. And only connected with tape and often released.

Therefore, the feedback was changed to wood. The wood was made of wood, it was firmer, stronger, and the shape didn't change much.

there is a bump but it's not fun, so it's finally sampled microbeats to give a sound so it's attached to the microbeats inside so that when it rolls down there is a voice to make it more fun that's the process that you guys actually will get through along the way, later you guys make a solution and make it a

you should go through the prototype and test first before you really launch your final version

or you iterate it several times first, then tweak it until you find the most suitable one. But it will definitely take a process again, repeated again and again. It won't stop, but at least your MVP or product that you want can be live and can appear first so that users can use it.

The prototype around us is analogous to bread, friends. So we have a bread shop. Well, that's our team. If earlier in the video, it was explained that he was a product designer, marketing, manager. So this process is what

gives an engine for the ideas we want to make. So this Roti shop makes new products in small and cheap portions before they are mass produced. As if we usually give Roti shops a display of a few items, maybe one type is maybe three or four. If you go to a coffee shop, it's usually like that.

The second is the customer is your user. So you usually give a teaser, maybe you can see if for example in a bread shop or sometimes there is okay we have new bread, new taste can be tried or we have

Cookies, for example. Cookies can be tried first. Or a simple ice cream, gelato. We can try it first. The taste, is it suitable for our taste? That's it. So...

this roti sample is the prototype so the customer will see and feel with their own intuition, whether it is held, felt, or seen visually, the intuition will try to explore whether this prototype is in line with their needs

So the simple form of this product is to test the assumption to the real person. So people can really feel the benefits of your product. Prototype makes our assumptions can be tested to people before we make a big investment. For example bread, do you like it? This taste, we make bread taste

Nasi Padang, for example. People like it, right? Or nano-nano noodles, for example. People like it, right? Well, we test it first. If they like it, then we launch it. Full scale, we produce it mass, for example.

because it will reduce the risk of greater loss because it doesn't work or doesn't break their solution and for long term, friends, less effort too because it has been tested in the beginning and only focus on other areas, for example marketing, production improvement process, etc. Why do we have to make a prototype first?

So the process of visualizing ideas, one of the goals is to validate the solution. Is it relevant? Does it answer the user's problems? And how do they interact with your prototype? So you need to observe again. Is there feedback?

That's the goal, so the second is to learn fast and easy. So by finding weaknesses while still prototyping, it's still easier for you to change, fix, not after the product is done. What are the examples that we often find? If you guys have heard of recall product or recall mobile, there is actually a mistake

This is production, friends. If there is a mistake in the oil injection or something, it usually happens in some car factories. They will pull the version of 2000 something, and it is replaced with the one that has been improved. Actually, that's part of the process too.

There are mistakes in the first version, we fix it in the second version, that's part of the iteration process. It can be because of engineering mistakes.

process. So what is the purpose of why we need to do the improvement continuously, iterative continuously, one of which is to convince stakeholders, that is, to make it easier to explain ideas to judges, mentors, and school staff later, friends. So if you have made a sample product, make a visual form in a prototype format, friends will be able to present

with a simpler way because there are tools to help imagine if it's just a picture, especially if you only use AI pictures like this I use an AI picture, what is this? Samsung is out of breath, for example like that

Now you have to be able to make it so that people can see the button, if you press it, it will light up. Oh, there is a component, a chip, there is a USB 3.0 plug, there is a power button, etc. What will it look like? That's the function of making a prototype.

What we know to make a prototype can be two phases First low fidelity or low-fi If you heard about low-fi, high-fi, low-fi

Love Fidelity or the real raw or still rough The material can be from paper, pens, sticky notes, can be simple and rough visual, very fast and easy to make, the process, the function is to test ideas and concepts If you saw the video earlier, he made the sketch on paper, that goes into Love Fidelity

then we make the high fidelity version, the material can be digital tools, modified, mirrored, or you make the mockup with the production of one, you guys tried to test it first, he made a single one in the first video, then the visual is similar to the final product display, so what is drawn and what was produced in real time is more or less the same

Usually because using a CNC machine, the accuracy is usually very high. The sizing and so on. And this process takes more time. Like we had to go to the workshop, cut the wood first, cut the iron, the metal first, then assemble it, assemble it. But the function for the detailed interaction and presentation test is easier.

there can be a touch, holding it, oh it looks like this, we test it, put it on paper, it turns out to be able to hold it better that's the function of making a prototype at the level of fidelity or we make it visual, visual until it becomes a real product there are 5 steps you can choose from the prototype to

from the selected idea to the prototype ready to test, so yesterday you have made several options, then you choose one, finally you create the crazy eight, the purpose is to determine the product first, choose the solution that is most suitable for the selected idea within your team, you can use Impact Report Matrix, you can access from the feedback user side, so it depends on

your team's capability. Then the second is you make the planning sketches. Yesterday at Crazy8 you made the rough sketches for the flowchart or requirements or rough sketches. And determine the scope, focus on the most crucial feature for you to test.

For example, in the section of the order feature, if your product is digital. Or if yesterday, from my example case, make an IoT to measure air quality. Maybe measure the PM first, or measure the humidity. That can also be any indicator you need to test first.

then you make the prototype, so from my sketch, try to make a component if you are an IoT, make the component first, you can buy it if you are free to use Arduino or whatever then you assemble it so that the function works, then you just have to make

the prototype cover, you can use 3D print, you can use cardboard first or you want to make it from paper, paper that can be shaped first, that's okay too or like before, make it from wood, from bamboo, make it first so that there is a shape

from apps is easier because it's a digital product you just have to make it online want to use Miro, Figma, AI, that's it then prepare the test scenario what do you want to test? do you want to try the feedback feature? do you think the wording is clear?

or how to use it, do you understand the exploration, how to sign up, how to order, for example, or it depends on what the feature is, if the product, for example, does he know how to turn it on, how to choose the function, how to change the function, do you understand, for example, we have what, yesterday, the case was

For example, air purifier, how to turn it on, then the function of the buttons, understand or not, there is a fan, there is a speed, there is an automated, then there is a smart home feature,

for example, connected to a cellphone, do they understand? so you arrange the scenario in the form of a checklist do they understand the process? make sure every step you take to make a prototype is more directed and save, the purpose is to save, don't skip the sequence of these 5 steps

So first determine the product that was made, so based on the impact effort yesterday you already understand the impact effort, which do you think is the most feasible for you to make a product? The consideration is the cost and, in addition to the impact and effort, the cost and timeline, how much time is needed for the team

and learn, maybe you have a limited budget, what can you make? choose the most affordable and the resources, skills, tools, materials that the team currently has so you don't have to force yourself, oh I have to make it using 3D printing if you don't have it yet, don't force yourself to order 3D printing or you have a limited budget, don't force yourself to

with good wood, for example, use what is around you first, right? maybe you have from the lab at your school, right? there are materials that you can use again, right? or from the cardboard, I used to make IOT for this cage, right?

my desk and I made a ladder cage, there was a thermometer and the temperature was from the cardboard before the original material was made using plastic materials so try this impact effort to help friends, which one can I build first? I make it first, using available resources

The more you guys get into this, high impact low effort, it's good. It means you can directly make it. Or low impact low effort is still okay. But if it's good, for example, the idea has been well received, the product is already, what is it, the possibility that this will be cool, for example.

will be implemented, it means entering this quadrant, major projects, but usually long term. There is a phase when you make it, maybe it's still here, it will go up later, so high impact, maybe it can move again until it finally becomes a major project. If high effort but low impact, you should avoid it. Because it will make it difficult for your friends to spend more budget.

Okay, the second is sketching. If you see the video, it was made by sketching first, just like you made Crazy 8 yesterday, so you need to brainstorm. So that it's more concrete, it's easier for you to discuss, "Oh, I made it like this, what do you want it to be like?" We combine or can choose one.

What is the purpose? That is to predict the problem. So from the sketch, there is a potential error, a gap that the product is not visible, the product is visible earlier. Maybe the flow is like this, it's wrong, if you want to be good, you can use the button first, so that the registration is easier.

then the third is easy to iterate, so you can delete it first from my sketch or repeat it so that the flowcharts are more directed, so the flow is also clear and you will know the needs or requirements in each part, how big is it

By drawing this, it becomes easier to iterate, it's easy to make, easy to change, even if it's wrong, it's just thrown away without much loss. So it's not the stage that you have to implement with more advanced tools.

The third is to determine the scope of the prototype. If without a scope, making features at the same time is long, so it's expensive, sometimes the feedback is scattered everywhere, because all the features are available there in the same time, so the feedback will be long, wide. "Wow, this is less like this, less like that, less like this, less like that." Finally you are distracted and not focused on your main solution. So we need to give scope.

It's not the same as Merta, if you look at the current apps, it's not the same as Merta from the beginning, there is a process, the main function is one, then the next feature is added, and so on. But each feature has the same process through the previous desenting.

The main focus is to take people first, the second focus is to take food, the third focus is to take packages. Remember, for each feature you need to give feedback. Because the audience can be in the same environment but the needs are different.

One needs food, the other needs to be delivered, the other needs to be delivered in a package. So focus on one of the most crucial features first, tested, the rest can follow shortly. The main thing is for you to

These people are the same, they are the drivers who will do the task. But the needs are different because the user has different needs and goals. So if you want to test the features, look for a product, for example, just for the search, login, payment, and profile, you don't need to make it first. So focus on the search feature first.

The fourth stage is, from the image you make the production, the prototype, so adjust the purpose first, then you focus on the most crucial feature, focus on the most valuable part, which is still full of assumptions, you need

make it more detailed, the more complex the prototype, the longer it takes to make it and the more common the feedback is so try not to be too detailed, so instead make it like this, like a screenshot, maybe a sketch that hasn't been seen yet, the color and this is okay, later on we will make it in high fidelity, but you don't have to activate all the features first, the main feature you want to test first,

If you want to order, the order will be activated first. Then the search feature or sign up feature will be step by step until it becomes the whole of the feature that you want to offer.

What you need to remember is that the rough prototype is more valuable than the beautiful one, which is already good but has never been tested. The design is really good, because it's just a mess from the internet, but you don't really understand the function or the feature of solving the problem or not.

There are 6 types of prototypes that you can choose and you can be quick to assume your product. The first is the paper prototype, this is clear, which you draw.

the sketch up earlier. The second is the roleplay service. Well, this is like last week, friends, watching the video, which is actually a roleplay service because there is a service design process. Then the second is the storyboard. So you guys, yesterday, actually, Crazy8 is similar to a storyboard. Because the process of your storyboard, sorry, the process of defining

whether it's the use or the process, it goes into the storyboard. So the purpose is to create a series of images that tell the user's experience. The fifth is digital mockup. Digital mockup that you can see now, a lot on the internet or in tools, for example using Figma, using Miro, using AI, well, all of that can

it can be turned into a clickable prototype now so it can be interacted and measured now Wizard of Oz is a term, so it looks automatic when running the manual of the team so it's like the prototype can move but it must be moved by hand or there is already

the button can be turned on, but we use the center button, so it's like it really happened. That's the Wizard of Oz, it's amazing. The prototype has just been able to operate, but not all of the features are on. The sixth is the physical mockup, so the model can be made from cardboard, clay, etc. until it finally becomes

If you remember in the first project, it was the one that made the shopping cart prototype. At first, from the shopping cart, it was added this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this, this,

I can imagine that the needs are more simple, more simple, and finally made with separate frames so that later it will be immediately lifted, there are hooks for things that don't need to be put in the box.

So, the example is like that. The main purpose of the prototype is to validate assumptions quickly, not visual perfection. So, it's more like validating whether this is actually needed or not. So, it's more about the functionality, not visually good, but the function doesn't work. Okay, let's break first, maybe, Ms. Gita, or is there still time? There's still time, 4 minutes left, sir.

Maybe break first, okay? After that we immediately have the next material. Okay, thank you very much, Mr. Kusuma, for the great and super insightful material. Well, friends, how is it so far? Can you give a rating from 1 to 10, how much do you understand the material just now? 10, 9, wow cool, it means you understand it really well.

Hatam 6 6 7 Okay I continue, friends Thank you very much for giving a rating By the way, if you already feel tired, because you sit for a long time, you can really stretch first To drink, so that the body is more relaxed again Because we will break for about 5 minutes Now, be careful not to leave the Zoom application or on YouTube, friends on YouTube Now, for friends or parents who are still

Stay on Zoom or YouTube, we will refresh our brain first through the exciting icebreaking session. Now, friends, ladies and gentlemen, please type the answer through the chat column on Zoom or YouTube. Okay, what are you playing, sis? Wait a minute, friends, I'll share the screen.

Well, today I invite you to play "Describe me in two words" The way is really easy, later I will show you one picture, you can answer using two words that you think most describe the picture. Well, for example, there is an ice cream picture, later you can answer cold and sweet, like that. Okay, ready? I will continue, the first picture.

What are these two words? Two words that describe the sentence. "Diaduk enak gurih" true, it's delicious for breakfast, it's really chicken porridge. "Diaduk enak pedes" it's hot. True, the debate of porridge being stirred and not being stirred is like the never-ending saga debate, friends.

I'll continue to the second question, the answer is the answer is bubur, yes, it's easy, yes, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy, it's easy,

Okay, great, UniPTB, no, fried chicken, right, that's not the University of Indonesia, right? I continue again to question 3, let's go, what is it? Dr. Daniel, wow, doctor, yes, right.

Heart, doctor, doctor, well, usually doctors, the answer is a stethoscope, yes, this is a tool that is used for doctors, yes, a stethoscope, friends, heart, ears, and throats, right, okay, I continue again, question 4, is this what is called Dubai Cui Cui, is it wrong, is it Dubai Cui?

Mochi Dubai, not brownies, sweet and sweet, true. Matcha, this is not matcha, this is kunafa, guys, the name is Mochi Dubai, my favorite. Great. Not Nexstar, sis. Bapak, Bapak again, no, no. Okay, this is Dubai chewy cookie. This is food, if you scroll TikTok, you will often find a food vlogger who reviews like that. Continue. Now,

Oh, this is too easy. "Walking, walking, wheel shoes" Are you ready yet? Oh my God, this comment is really exciting. "Wheel shoes, wheel shoes, machine shoes" Machine shoes? "Wheel shoes, walking shoes" Yes, that's right, this is a wheel shoe, guys. There are black, pink, and blue colors. I complete all the colors. Okay, let's continue, friends. Is there any more? Okay, there's still more. What is it?

this is not a friend, it's an animal, come on, the front is C, friends, if you read it, it's a cow, a capybara, it's true, it's hairy, it's hairy, it's fat, it's fat, it's not cute, it's not a snake, friends, this is a capybara, okay, the comment is really random, there is someone who answers this

Okay, I'll continue again, okay? Is there still any? Oh, last question, friends Describe yourself Come on, self-love first, princess Yes, that's right, handsome, handsome, handsome, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful, beautiful,

hungry, oh yes, you're hungry, let's have breakfast first, try to eat a lot of food, this is really diverse, yes, it's beautiful, smart, okay, let's continue, friends,

Okay, because the ice-breaking is over, let's continue to the material, oh yes, before continuing, I want to test it first for friends who are still excited, you can give the reaction emoji, love, thumbs up, free. Okay, still excited, if so, I'll return it to Mas Kusuma Utek, the material expert, Mas Kusuma?

Okay, that's really fun. Do you want to continue? The guess is funny. It seems like it's just the duration, right? Okay, let's go back to the material. But...

To help our fans, here is Kel. We built this.

Last year, we got a special email. The senator's father is a farmer in the mountain village. Their cows are raised in the mountains. Every day, he has to go up to the mountain to check on the cows and find them. It is very tiring. A few years ago, he even broke his leg while looking for them. They tried cow GPS tracker before.

But the products on the market had problems. We called them to ask more and found that the tracker they bought had very large arrows. The real location and the location in the app could be off by an entire mountain. But here is what confused us. We tested a similar tracker ourselves. Yes, the battery size is absolutely fake. But the real location and the app location were only off by 10 meters. So why was theirs so inaccurate? We went to his home and tried hurting Kels ourselves.

♪♪♪

After running around the mountains for a whole day, we found the reason. The phone signal is very weak in this mountain area. Most Cal trackers send location data through 4G to a server. Then the server sends the data to the user. This means if the Cal starts in a place with good signal, the tracker sends the location successfully. Then Cal moves to a place with poor signal, the phone cannot get updates. So the location on the phone can be very far from the real location.

and cows move over a very large area. Wow, they climb really far. When we got back to the studio, we started working on the solution. This is the system we built. It has 5 parts: a color tracker, a gateway, LoRa relay stations, a walkie-talkie, and a mobile app. So how do we solve the weak signal problem in the mountains? We cannot build cell towers, but there is another option called LoRa. LoRa is a long-range, low-powered communication protocol.

The bandwidth is low but enough for location data. When we visited before, we tested all our base stations and the gateway. Our tracker first sends the location data to a relay station. The relay station sends it to the gateway. The gateway sends it to the server. And finally, it reaches the user's phone. This solves the problem of poor signal. But here is another problem.

When you are in the mountains, your phone also has no signal. So how do you receive the cow's location? Let us show you the core of the system, the walkie talkie. It also uses LoRa, so even without forged signal, you can receive the cow's location and guide you to find it. And with this device, you can even ask: "Cow number 1, where are you?"

Just kidding, we added AI voice feature inside. So now if I ask, where is cow number 7? Now let's talk about the tracker. We used a nylon shell and a metal buckle, so even when cows fight or scratch, it will not break. We also added numbers on the shell, so it is easier to tell the cows apart. To detect accidents, we added accelerometer inside the tracker. It can detect the cow's movement and alert you if it acts strange or leaves the group.

You can see it in the app. The uncle can also ask the device about the weather so he can bring the cows back in time and avoid danger in the bad weather. Mountain roads are easy to slip on so we added an SOS button to the device. Press and hold it and the family will get an alert on their phone. They will hear an alarm sound and see his location in the app.

At the end, we even made a bullnose shape shell for the tracker so we can spot the cows from far away in the forest. But in real use, it was not very practical, so we removed it. Then we took the system to his house, installed the gateway on lower relay stations in the right places, put the trackers on the cows, and now we can finally start founding cows.

After testing everything, we marked the locations in the mountains with the uncle. Then we went home. It was a great experience. Thanks for watching. See you next time.

Okay, this idea is not endless, it's a bit too much. Okay, if you see, the idea is simple, but the practicality is quite complex. Making a tool to sweep cows. The problem is actually from one of their viewers on YouTube.

because in their village, cattle often lose cows in the grass fields because the hills are quite steep and the method of finding them is tiring, they have to be sent sometimes they eat time every day and the risk of losing their livestock is permanent because they don't know where they are, they disappear. Well, if you look at it, they make

prototype first, with GPS, solar power, and also what was it that was installed on the tractor, installed on the cow's calf, there is also a slow-meter, right? So focus on testing whether the range of signal transmission, battery life, and physical durability against extreme weather can be this, what?

can last a long time, used in all fields. And earlier it was shown that there was a broken one, there was one that didn't work, finally replaced. Well, that process is the use of prototypes. Just now it was made of tin, it was broken, finally it was not necessary, it was given tin, just a scratch.

and the result, you see there is a stack of call trackers, light, energy saving, and it uses a battery of 60,000 and directly integrated into the cellphone then can be monitored in real time with the walkie talkie earlier and from the daily search, now in a matter of minutes you can find out where the cows are, whether they are gathering,

what is it? breaking or splitting, so it's funny, that's how a design thinking helps the process of making this, the process from the problem to a prototype, from the prototype to a testing, through the testing process and the result has a useful value or impact. Now in the modern era, friends,

you can also use AI if the product is digital or maybe make a sketch of the fidelity first, you can also use 3D if you want to make the product real

it's possible to do it now so you can design it first using Figma, VIO, Vercel, Replete, Lovable, Miro and now it's quite easy, you just need to describe it through text maybe make the UI frame or make the wireframe first if we used to have to work for hours to make the minutes

AI can help make the sketch or IoT hardware can make a picture of what the shape is like, it can be made directly. The flow chart, the function, can all be easily broken down through AI.

And we can also brainstorm with AI, whether you want to use any model, whether you want to use ZGBT, Cloud, Gemini, make the draft first, the flow, the list of features, what are the things that need to be tested. If you are confused, you don't need to open the book again. Now you can ask chatbot AI to help you make the scenario.

But what you need to know is that you guys are still the pilot. So AI helps to speed up the process, but the decision, whether it's from the design side, validation with the team, all the iterations until the outcome is from you. We as humans, we as humans who

determine the decision whether this is okay or not. For example, if you want to make a promo, make a simple wireframe, an hour-long reminder application, and then you also mention what the screen is like and what the main button is like. Well, if you can detail it. Even now you can

make a brand guideline, for example, the color, you have made a logo yesterday, now you want to apply the brand guideline, what color is it, if you can give the hex code, the AI will adjust it later, that's it, friends, you can test and do it for testing, using the prototype. Okay, the question, the first quiz, what is the main purpose of making prototypes in thinking design?

can write in the chat what is the purpose of making a prototype? B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B

After the prototyping step of the design thinking process, we are arriving at the last one, dedicated to validation of our previous activities. Usability testing is all about verifications of our designs, but also assumptions we made in the previous stages. Is the target group of users able to perform tasks that solve their problems through your prototype? Are the assumptions you made during defining and ideation stages correct?

Is the functionality of your prototype clear to the testers? Those are examples of very high-level answers that you need to acquire during usability testing activities. As I already explained in my previous videos, usability testing is a method of testing the functionality of your product/prototype by observing real users as they attempt to complete tasks through it.

A typical usability testing session would require from you preparation of tasks or goals list which testers would need to perform through the prototype. An example of such a task can be creation of an account, purchase of an item or whatever else your product offers to its users. During testers' interactions with the prototype, you need to observe them thoroughly, which allows you to spot any blockers and issues with the logic, interface or core concepts.

Apart from simply observing, it's a good idea to prepare a list of feedback questions, which will allow you to expand the amount of useful information. An example of such a question can sound like this: Was the process clear for you? Is there anything missing in the presented process? If you had a magic wand, what would you add to the presented prototype? List of

Tasks and feedback questions for usability testing is typically referred to as study plan or script. Apart from the mentioned, it's a good idea for you to include in your script the purpose of the study, some background on the product, and questions to learn about the participants' current knowledge of the problems that the prototype aims to solve.

To make your usability testing session unbiased and scientific, you should follow the same script in each user session. Assuming that you have your prototype ready to go and you also prepared a script for your study, you need to find participants for it. I think that's the most difficult and time-consuming step for most aspiring UX designers. Because first you need to find your target group representatives and then somehow convince them to spend time on your study.

Conducting your usability testing sessions online through conference calls definitely will help you on that front, because you don't need physical location and participants don't need to spend time commuting. Then, most likely you will need some sort of a carrot that would convince them to join your study. Good practice is to offer something like a gift card. Okay, but how can you find them?

Here with the help come various social media platforms like Facebook or LinkedIn. You can look up for interest groups that your target group should be interested in. Then enroll to those groups and post about your study. You can also utilize extended advertisement targeting functions and reach with your study this way. Nowadays more and more designers use dedicated platforms to conduct their usability testing studies. Primary argument for that?

is the speed increase and process simplification. Because you don't need to find and schedule meetings yourself and you can conduct them asynchronically. Unfortunately, those services are generally quite expensive, but most of the time they are worth that money. After the study, it's time for analysis of what you learn and application of your findings to the next iteration of the prototype.

If the situation requires it, you may need to go through all or some of the design thinking process steps multiple times. But thanks to that, the chances for success of your project increase. It's also easier to acquire funding. That's why many startups use a design thinking approach for that purpose. If you want to watch the videos dedicated to the previous stages, you can click on the playlist here. Or if you want to learn something else today, you can click on the video here.

Okay, if you see the process of doing the testing phase of the prototype that you have made, you can reach out to the other audience, right? From your personal account, you can reach out again or you can look for your friend's segment or for example your target is an application

for children, for example, the target is actually parents, so you have to use logic too, right? can be parents or teachers, because maybe if children, maybe if games, yes, but if something that helps the learning process, it's just maybe both need it, from the child, from the parents too, or from the teacher in the class so make sure you validate and iterate, so remember, validate and iterate

So we can test whether the feature we make with the assumption that we can solve their problems, whether it is really proven or not. Well, for example, what is proven that needs to be

improve. Well, that's the iteration part. Maybe the appearance, maybe also the functionality. The placement only affects the buttons, if in the application the button, even the call to action, the words, the writing is influential. Easy to understand, or misleading, or less understandable, it can be misleading, the sentence or the question.

the sentence or call to action. So that's why it's important for you to test the test again and again. And how did this solution really reach your users? There are two ways. I'll clean up the screen first. Okay, there are several ways, there are two. If you remember Nielsen Norman, Norman who made the book in our first session,

The only way to get UX design right is to test. So, the process, the product that is usable is

From the point of usability plus utility. Usability is how easy the product is to use. Can a user do this task without confusion or frustration? The key word is easy to use. Is it easy to help them use it? The second is utility. Is the product really needed by the user? Easy to use but

but it's not needed, it's the same, it's wasted, friends. So the key word is "users are needed". So these two things that when we do the test, are users really needed? So to validate and improve, to iterate. So always remember usability and utility.

According to Nielsen, there are five components of usability. The first is learnability. How easy is it for users to use the product when they first try it? If they don't ask a lot of questions, there are two possibilities. Either confused or not comfortable asking or it's okay. They can understand without us having to explain too much.

For example, if you sign up, it's clear that you can use an email, you can use your phone number, or you can use Google Sign Up. It's clear, right? Without it, you need to ask a lot of questions. But if they are not clear, how do you register? Well, that means there is something that needs to be approved, friends.

The second is efficiency, how fast the user feels the task on the product. The faster the bottleneck, for example, the loading time is long, the error, for example, and it's not yet registered or not yet registered, it will be a drop-off later or the user will not return.

This is very common when friends play games, for example when you play games and suddenly the server error, finally it's not efficient actually, the game becomes inefficient because it lags or because it's too heavy, so the experience decreases. Well, that affects efficiency.

The third is memorability. So after the theft, do the users still remember how to use it? This is important because it affects retention. Will they use your app again or not? If yes, they usually don't need to remember to repeat it. But if it's not enough, they will try to take a theft.

"How was it yesterday?" or ask again, "Why can't I log in again?" or "Why can't I click this?" or "Tap this menu?" he forgets. So it's important to be easy to remember. So there are behavior factors, studies, like yesterday in the video that our first friend, so there are behavior studies that

Helping users to follow instructions and follow the pattern as it is. Now, there was an error earlier, how many errors happened and how easy it is to fix. Usually certain apps can be an error, for example, there is a server gateway or the link is dead, not connected.

server, it can be an error and the same at the end it will be a drop-off so you need to fix it if you find an error, find a bug, there is no perfect one, friends, whatever product you want, there is no perfect one, you definitely need to test and iterate so that we can solve the error or the bug if the product is real, what else is it? it's broken, so it's included

or not, not functioning as normal as the initial instructions. The fifth is satisfaction. So it's important for us to see, to observe whether they are satisfied using this product, with features that meet their task.

So you need to ask how do you think, do the apps help? What is the help in terms of what? So you need to ask probing questions too. Okay, so these five components are lenses when you observe the user trying the prototype. So make sure you can observe these five usability components. Okay, so to do the testing, there are things you need to prepare.

The first step is to determine the goals first, what testing are you going to do? If not, it will spread everywhere, friends. So what you want to learn from the test, choose the most suitable method. It depends on what you want to test later. Make sure it's relevant. Will this method need to be

It needs to be tested in a qualitative or quantitative way, or there will be certain tools that can be used. Then determine the scenario and task, the task earlier, if you want to log in, register, sign up, separate one by one. Okay, the first task is actually to create an account.

The step-by-step method is A open the application, B click sign up, then click using email or using Google sign up, for example, using Google email. Then they can't finish until they finish creating the account.

The third is metric determination. This is very important. Usually the key is in the metric. So you have to know the success rate, both from success rate, time, and satisfaction. He made his account successful, but it takes time.

It takes half an hour to make it because of loading, loading, loading. So the user is not satisfied, "Oh, it's been a long time since I made an account. Is the server slow or what?" So you need to determine the metrics when you test testing. Because this determines whether your app is successful or not. Or your solution is solving the user's problem or not.

The fourth, prepare a prototype. And this is what you will repeat later. If it's already a matrix, make a prototype. Then adjust it, you can use certain tools, like Maze, Userberry, etc. to test the prototype which is a digital product. So adjust the scenario and task in there. Then recruit the participants.

This is sometimes we are wrong too, we can do whatever we want with the participants, those who are close to us, neighbors, friends, it's not wrong. You have to make the cluster. Remember, the first one yesterday was empathize, so make the cluster first. This feature is aimed at who? Audience A, B, C, User A, B, C, personal, what are you like? Well, that's what you select, you have to filter first. Choose participants that are suitable for the target user, then schedule.

Actually, 5 participants is enough for you to test at the beginning. But the more participants, the better. But 5 participants usually represents as long as it is in accordance with your personal opinion.

The test format is an example, for example, the scenario, the task and the method are like this. The scenario is, imagine you are a student who often leaves the bus at school in the afternoon. You want to try the home alarm application so that you don't miss the bus today. The task is to show how you set the alarm clock.

back to this prototype, let the participant try without help. So you just look at it, okay, we already have the application, try to show how you set up the return hour on our prototype. Well, let him

the audience that we test, try first explore, try whether they understand or not, well, we just have to see it first while recording, making, oh, he's pressing something else, right? when we make that feature, what is it? he went to another menu, not to the alarm menu, for example, well, this will be our benchmark later

The metric, so can the ease be achieved? What is the success rate? What is the speed of time completion? That's calculated, friends. How much is the comfort and satisfaction scale? 1 to 5. Or what is the system usability scale?

You need to calculate that. Okay, if you made a sign up earlier, it only takes 3 seconds to finish. That means it's okay, it's still okay. But your target is actually 2 seconds and it's over. For example, like that. It doesn't take long because you can immediately use Google Signup. Or use other features that speed up the sign up process. For example, like that. Well, it's all measured.

So when testing it doesn't necessarily mean, "Okay, oh he understands." "Good, good, good." Not like that, friends. You have to have the calculation, your notes, whether the metrics are achieved or not. Okay, continue. Well, then we already have the audience, how do we conduct the testing session? Well, for example, you guys, please be quiet first. Thank you, ladies and gentlemen, thank you, friends who have been present. I will conduct

testing application A. We ask you to try this application first. The purpose is to explain the A, B, C first. I will give you time, that's it, minutes, for you to try to explore first. So, just give it to me. So, remember to meet first. Second, explain the scenario and the task.

For example, I asked the staff to do what they did, and then asked them to think out loud during the process. So let them know what they're talking about. I'm confused, where is this?

Well, let's just let it be, try it first, sir. Look at the application, maybe you'll find it later. How to sign up. So let them tell you first. Oh, the font doesn't look that good, the writing, right? That means you need to note that there is a need for improvement in the font sizing. Or, oh, I'm confused, what do you want to sign up for?

Sign in. Oh, so there's a typo error. So we need to change the call to action. We need to change the copywriting. Watch and note, don't interrupt or give directions. So let it be. If they think out a lot about us, try it first, sir. You can try it first, if there's any problems, just tell them. But you can't intervene.

What is the purpose? We get important insights during the process of trying. So remember that what is tested is the prototype, not the participant. There is no wrong or right answer. All feedback is valuable because the purpose is to improve and iterate our product further.

This is what often happens, tips on difficult situations when testing. The participant is clumsy, how to use the cellphone, because it's not used to it, because the brand is different. Try using Samsung. The technique is clear without directing the answer. So, they are directed, "Oh, open the on/off button first, sir, so that the screen is open."

Then give a limit Sometimes I ask this girl, "I can't do it" Well, that means you have to give a limit Give a time limit, if it's too long, it's too long, one person can be very long It can be a day later if you don't meet

the limit is okay, this has been tried three times, it doesn't work or it can last for 5 minutes, try not to finish it, find the sign up, that means there is something that needs to be improved, this bag failed, but the information is valuable because later you can improve, okay, it means there is a mistake, we set up the sign up button, we need to change the position, the button, or the naming, the call to action,

or error, sorry, fix it for a while, then continue the session calmly, this is very common because suddenly clicked, not connected, the name is a prototype, clicked, not connected, or not yet a feature that we want to test, later you can explain, this one we haven't tested yet, for example

But if there is an error, you can say, "Okay, let's fix it first. We'll deploy it first."

This process looks easy, but in practice, they will be frustrated. Whether from us or from the user. I'm so confused, I'm so difficult. Some people are so emotional, how can I not use the application? That often happens, friends. So you also have to be patient when facing your customer.

because basically that's what will happen later on the field, so you see a lot of people who are impatient, you have been deployed or launched the application, then the rating is 1 or 2, because there is an error or improvement that you didn't fix first before you released it, so there is a function, usually beta test first, beta test is for the purpose of

public to market, you can review first, you can test first until it really comes, or there is no bug or no error. Now, if the product is real, how is it, if the shape is a

hardware, it's actually the same, they just need to explore first, oh do you know where the button is, oh you know how to turn it on, how simple it is like you guys, this is AC for example, it's also tested, friends, how to turn on the AC, the button is understood or not, sometimes there is no, what is it in AC, there are many buttons, sometimes there are those who don't know what the function is for, there are fans, there are

to cool down, to warm up. In the AC there are buttons that sometimes not everyone understands. So we test first. After you test, summarize everything, collect all the insights, the observation notes, the metric numbers, the success rate, the time, the SAS, and the quote from what they say.

You need to record what feedback they give spontaneously from your users. So that's the quotes. It will be your insight. Then, which priority do we need to solve first? From what we've tested, it seems that users are still in trouble when they want to use our feature. Why? The journey seems too complex.

Well, you need to improve in the next iteration, so you need to get back again, prioritize which is the most crucial. If he, for example, if the sign up application is not yet available, how do you want to access the feature? So you solve the sign up first, the registration. So,

You classify it, for example, high prevents the main task, medium disturbs, but there are other ways. Low, cosmetic problems, I mean, the problem of the mark, can be marked. The third is iteration, so fix the high findings, you group them, you solve the issues first. Later in the next prototype, you test again.

One iteration is equal to a higher level of solution. So every time you do an iteration, your solution becomes higher level or firmer. Every time you do an iteration, you will find a new insert. But make sure you have a limit on how long you want to do the testing.

Remember, we want to capture all the insights, then do this iteration 10 times, 20 times, if the pattern is the same, that's it. So remember to focus on the iteration that has an impact. For example, this is an OTA application.

Well, you know. So, the comparison before and after UT. So there is feedback, adjust the architecture of information to make the visual change more visible when looking for a flight. And feedback B, make the display with more flight options so that users are not confused to separate the more detailed mascafe line. Well, if you look here, the before,

before there is a search for a flight and a flight selection so only these two features are influenced by the user experience, friends, imagine if you open the application, there is a home, there is what, there is what, there is what, there are so many and sometimes we need to do tests, there are some that we need to improve, there are some that we need to add, listen to the voice of the exit, for example, I was confused when

choose the flight with an unread date input and besides that you have to do some scrolling because it's not that visible to all the options available in maskp so this is in the breakdown, friends, if you see it, I'll show you while I'm drawing it, if you see it in the blue

if it's on the first screen, the display is immediately date, this is the return, there is a button, what is it called? there is a action button, or what, then it is replaced more after testing, it turns out that you only need the date first, if it returns, it just needs to tap here, an addition will appear,

Then from the maskapai, it became longer because it needed a breakdown. I want to see the comparison. People want to compare when they see a plane ticket, right? Not to choose directly where, but to be breakdown first. That's why the more the display is wider, the easier it is to read. This one is longer compared to this one, which looks like two maskapai.

this can be 5 in one screen this one is simpler this one is more expanded that's the function you validate and get feedback UT or usability testing usability testing from your user imagine, friends

Okay, let's continue. There are cases that are usually done in Google Design Sprint. We usually have feedback that we summarize. So many startups

to develop a product that is immediately available for months without knowing the market really wants the solution. What Google does is make a design sprint. So, for five days, they make a prototype, make the facet, the front in one day, then test it to five users the next day.

and the result is that the big idea is easily validated or stalled in a week before the code is written so before they develop it, the idea that is too big can eventually shrink and be validated or even it doesn't make sense, let's launch it first

So this saves time, maybe they will invest, so it will be easier for us to prevent things that are not wanted. So the focus is on what we want to make first, which really has an impact and has value. Well, let's watch first, how is the design sprint process?

Hi, I'm Jake from GV and this is a super fast intro to our sprint process. The big idea with a sprint is to build and test a prototype in just five days. It's kind of like fast forwarding into the future so you can see how customers react before you go to all the time and expense of building a real product. Every sprint starts with a big challenge, a team of about seven people, and a clear calendar. On Monday, you'll create a map of the problem and choose one specific target.

On Tuesday, you'll create solutions to your problem. But instead of a shout-out-loud group brainstorm, you'll work alone to sketch detailed, competing solutions. On Wednesday, you'll pick the best solutions. Instead of endless debate, you'll use a structured decision-making process. On Thursday, you'll build one, two, or even three realistic prototypes.

These prototypes are just a facade of a finished product. You can use tools like Keynote, Marvel, and Envision to create fake apps and websites. Or, to quickly prototype hardware, you can use a 3D printer, or modify an existing product, or just prototype the marketing materials.

Finally, on Friday, you'll test your prototypes in five one-on-one customer interviews. You'll find obvious patterns. Some solutions will work, but some won't.

Either way, you'll have clarity about what to do next and a great start on that big challenge. To learn more, check out our book, Sprint. It's got detailed hour-by-hour instructions and it's packed with stories about startups like Slack and Medium and FlatAction. Good luck with your Sprint and thanks for watching. So, I see the short version of the design is higher, so it's more direct to the prototype and test phase.

so in the research phase it will be slower but in 5 days you can immediately find out what the product is like, you can see it too, the digital prototype uses tools or even if you make it non-digital, you can use 3D print or packaging

can still be applied for you, the purpose is to get feedback and iteration whether it can really have a useful value or not. That's it. Okay, quiz! I hope you're not sleepy, friends. How many participants are enough for a qualitative test to find the majority of usability problems?

5, 100, 1, no need because there is already AI, I change it to AI I just ask AI I hope it's not too much all right, okay is it correct? correct thank you for answering friends yes, so it's correct A, friends, 5 participants is actually enough

for usability problems. But remember, you can also use clustering, you can use more than 5. Okay, let's do the hands-on first. Let's continue with the hands-on first. Okay, now you try to

make a prototype and analyze testing using the lens that we mentioned yesterday you learned in the first session, namely there is discernibility, visibility, viability, and responsibility. Now, friends have duplicated this, the mirror, maybe I'll change the screen first, wait a minute.

if you haven't duplicate, duplicate first, friends, you can copy it too so what you need to do, friends, we will make a digital prototype first but if you already have a case that you make a physical product, you can also make a sketch or make a design later on the AI

what you need to do is create an opportunity problem yesterday, you try to write it first then you put the ideation of the solution, like yesterday I, this is an example of the garbage problem, flooding, how to monitor the environment from the local people to the reporters, access to the neighbors to deal with the garbage, now I made a brief concept product

So you can make a brief first. Well, I made one reference guide. Actually, the more, the better. What is the purpose? More to get color references and also the appearance. Well, you can open this later.

what the output results are like, but this can be done because I use Miro, I generate using Miro, but this is paid, friends, if you want, friends, just enter this idea, the problem of the opportunity and the solution, for example, using Gemini, CGPT, or cloud, or Persplexity, friends, just copy paste the problem, then ask to make a product brief, yes,

product briefing, this is an example like this, if I run it, there is already a structure, maybe I will change it to a basic initial, maybe the product briefing, friends can use other AI, so later enter the problem, the opportunity, you write

then the solution and the design reference, the design reference you just need to copy paste the link take reference or take design reference from this website for example

This is an example. So if we call it in the industry, it's called PRD, friends. So you can make a problem statement like Bali facing garbage management, garbage management problems, and affecting the budget during rainy season. So there is a lack of monitoring system, coordination between the residents, and...

The goal and structure is to create an outcome that is expected to improve the reports, available access as a resource, and reduce flooding. So this is the purpose. And we can also define the user, like who is the use case, target Bali citizen, then the trash condition citizen, resource, and the other coordinates, there are three stakeholders.

the solution is the monitoring, reporting, access feature, and the mechanism to enter the system, the relays, etc. which is not included, so usually if we make it, there is a boundary, so we set it out of scope, this is an assumption, sorry, it doesn't look like it, I'll move a little

There are some assumptions that we can define. What is the purpose of having open questions or assumptions to challenge our product? Can we really deliver or not to the user? If you can, you can make it using lovable. You can join lovable here because I use

you can use the same lovable or you can use other tools, there is bolt, there is what you want to use in cloud code for example, that can also be done, but I can't teach it, so you can explore how to do it, maybe I'll give you an example first, friends, if you open this, it's already the website, friends, I share the screen, the screen, and this is only using lovable

this is clickable, but it's just landing page if you want to create the next page, you have to generate again the function hasn't worked yet but this one on the main page is already clickable you can use other tools too, apart from lovable but there is free credit so you can generate 2 or 3 times the page whether it's apps or

apps or website. That's it. Now, if the way, friends, you can enter the PRD, which was the product brief, you copy it, then it's generated here, friends. Yes, enter it here. Or it can be in the form of a document, yes. You save as PDF, then you enter it here. If you have a better reference, just attach it directly.

in the form of a file design or you can use a connector if you want to connect to the Miro, you can directly Miro it's more advanced, friends, using MCP, but if you want you can directly prompt it and then attach the design reference, you can link it or you can attach the PDF form

Later, Generate will make it like this, friends. I made it earlier. Same. I can also change per section. Okay, clear enough? Try it first. Experiment, please friends. Let's try to make the prototype first. The time is 15 minutes, friends. To try to make your prototype version.

Okay, let's try it, friends. Can you help, Ms. Gita, if there are any questions first, maybe check from friends. Actually there is still 10 minutes, Mas. There is still 10 minutes for Q&A. Okay, it's okay, we start early, so that later if there is a problem. Okay, I give you 15 minutes to try making a prototype first. Okay.

Silakan, kalau ada pertanyaan langsung di chat ya teman-teman ya. Let's go. Ayo semangat teman-teman, dikerjakan. Sekali-sekali nyobain AI-nya ya.

Well, friends, if you're done, you can be informed in the chat column. If there are any questions, you can also be informed. Later, Mr. Kursuma will answer it. Well, that's it. Thank you, friends, Mr. and Mrs.

♪♪ ♪♪ ♪♪

♪♪ ♪♪ ♪♪

Is there anyone who has finished? You can immediately drop it in the chat column, friends. Mr. and Mrs. There are those who have finished. Great. Okay, you can share later if there are those who have finished. That's right, you can share in the chat column, Mr. Kasuma.

♪♪ ♪♪ ♪♪

There are so many of them, I hope there are no problems like yesterday.

There's still 5 minutes left. Cheer up, friends, parents! Yeah, like a Mamiro.

♪♪ ♪♪ ♪♪

If you have any questions, please drop them in the chat column, guys. Show your cool works.

Thank you.

♪♪ ♪♪ ♪♪

I will explain the paper and there is a challenge later, I will explain it at the end of the session, so stay tuned, don't leave first. Cheer up!

♪♪ ♪♪ ♪♪

♪♪ ♪♪ ♪♪

♪♪ ♪♪ ♪♪

Hi, the time is left, two minutes, friends, let's go, let's speed up again, keep your spirit focused, later there will be a show by Mas Kusuma, one person for the presentation, yes, that's it, two minutes again,

♪♪ ♪♪ ♪♪

♪♪ ♪♪ ♪♪

5, 4, 3, 2, 1, okay, happy, slams up! Where's the sound? Is there anyone who's done? There's someone, bro. You can share the screen, maybe.

Okay, nice. Can you explain what you're making? Ari, can you open the mic? Okay.

So what I do here is based on the problem of the damage of public facilities that can affect the activities of the community and endanger safety. Therefore, I am innovating to create a website for public facilities reporting, where I can report the damage of public facilities from photos and locations, as well as monitoring the status of improvement by the community and the government.

Okay, let's see what the results are like. Like this. I made it using Loveable. Can I scroll it? Okay. Report, verification, repair, complete. So this is the website. The landing page. Okay, nice. But that's already...

Have you connected the sign-in page yet? Just like this. Oh, not yet. Okay. Oh, but there's already a display. Yes. That's great. Okay, great.

interesting, you can share the link later so that friends can see it too share the lovable for other inspirations so later like this friends when you develop a prototype with lovable the appearance can be a website or even an app you can share it on chat maybe, Kak Fahri, the lovable thank you, who was the other one? you can, the one who raised hand

thank you, Fahri, for sharing. this is for example of friends. Yudan, please. please. that's great, fixity. that's great, cool, Fahri. cool. oh, Yudan can't open the mic. can you share the screen? can you check if my sound is heard? yes, yes, it's in. okay.

Can you explain? So, the problem or opportunity that we or I raised is, first, from the problem of slow network, second, limited spec device, third, what is it called? The third is not knowing the ability of each student

Okay.

The first thing is the understanding, there is a presentation here, oh, it increases, it will increase after answering from the assessment, this is for customers. Can the teacher access it too? The teacher hasn't tried it yet, I just prompted it earlier. Interesting, this is the dashboard.

Okay, nice. This is really cool. Can I share it? Sure, to everyone. Later I will share it. Later maybe friends can share it to the class manager too, to Gita who has successfully made it using lovable or other tools can also be. Earlier someone asked using Vercel, you can also use VO.

That was really cool, from the student to the teacher, so both of them have been done. This is the interface. Okay, how is it? So what's the name of the program? Oh, it's done. You can stop soon. Thank you, Yudan, for sharing with your friends too.

Now, there are two interesting examples, Ms. Gita, for you to inspire. Maybe some of them haven't been done, they can be an inspiration too. Okay, that's really cool, friends. Ms. Fari, Ms. Yuda, maybe other friends will have cool results that can be shown later. Okay, I will continue to this session because of time limitations. Can I, friends, Mr. Ibu, raise your hand?

Or if I can't, I'll read it from Slido too. Is there anyone who wants to ask? Can I raise hand? Okay, I think I'll read it from Slido first, maybe while you guys prepare questions, like that. Wait a minute. Well, here's a question from Kak, oh this is the top comment, it's from Kak Aquara.

May I ask, in this section, what is the prototype that is expected by the jury or jury and what are the certainties of the prototype? I'll go back to the team, what are the criteria from the selection?

Maybe this can be asked to each admin in the Telegram group, friends, if there is a question like that. I read this again from Kak Elza. "Kak, our product is a mini reactor with machine learning and a dashboard, the calculation of the reaction results, can the prototype be used in materials that have not been innovated?" What do you mean, what do you mean by materials that have not been innovated?

Maybe if you're here, Elza, you can open mic first. Yes, Elza, can you explain more detail, maybe? What is the material that hasn't been innovated yet? Yes, that's on-cam, please, Elza. So, our product has the material innovation. So, with the material innovation, it can produce more valuable results.

But for the synthesis of this material, it's a complicated process. So, can we prototype it without material innovation? But the important thing is, what is it about machine learning and others?

So when you make a prototype, it can be from the previous priority first, you make a pack effort first, which one do you think can be done first? If the material innovation is core, but it seems to need more effort, you make it a longer strategic project, but what you can test now, like machine learning and others, you do it first.

So it's no problem if you add it later. The important thing is the prototype process, you focus on which feature is easiest to make and can be tested immediately. Is there any additional questions, Elzan? Thank you, sir. That's enough.

Okay, remember to prioritize, friends. When making a phototap, prioritize first what you can develop immediately. Okay, please, there's more. Okay, this is from Sultan Habia, can I have another one, friends? The recent one. Wait, I'll check. Open mic or read it directly? Yes, you can, Sultan. Hello, sis. Oh, she's on chat, sis.

Here, sir, may I ask, for example, have you made a mobile and app look-up design and prototype for the hardware later to be embedded in a link or inserted into an image? That's it, sir. The second is, if you have made the real prototype, because it needs documentation, the report later, friends, in what?

make this later you can imagine what the picture looks like but if not, make it first

flowchart, the function, then if there is a prototype image, you can use a link, or like the sketch earlier, what kind of planning do you want to develop? If it's normal, someone can make it using 3D too, if the hardware is in the form of CCCC that does have the features, that can also be done, but if it doesn't exist,

You can just take a photo of one side, for example, a product for IOT that has a sensor, for example. Well, you can take a photo of the component from above. Okay, thank you. Oh, there's a Sultan. Thank you, Sultan. Thank you, bro. Maybe I'll just answer the question that was asked in the chat.

It's okay, I'll just answer it quickly. If it's still in the form of a paper from Maria, is it still in the form of a paper or is it already in the form of a prototype? Well, if it's a prototype, there should be a physical form, if it's hardware. But if it's a digital product, you make the lovable or make the digital prototype.

because it's clickable, actually the one in lovable is already live, but the features haven't been developed yet, like Tahrir made it, but the sign up feature, the sign up is already there, the contact or what, the right corner is not connected yet, for example, or the one that Yudan had earlier is the same, the one that hasn't been finished, the one in the teacher's section, but it's okay because it's already visualized, the appearance

Then from Zafaria, for example, can a product be made on a smaller scale? Yes, if the hardware is from a small scale, so that it doesn't leak. So make a small size first, at least the features and this are visible. If there is a button, there is a screen, or a sensor, so that the video is made.

The prototype with the material, if you can start with the small one, you can. But if the cost is the same, make it small and big, it's better to just follow the size of the reel. Because 3D printing has the same filament cost. Whether it's a lot or a little, it's the same. The calculation is one time to make the savings. Okay.

Can we use software for the phototaping? Yes, you can. There's an example from Google. There's an example from Google. Whether it's a digital product or a real product. Like the one we made coffee with. Or this one can be used for 3D printing. It's the same. The process is the same. Okay, I'll return it.

Okay, that's enough, friends, for this session. I'm sorry if there are any questions that have not been conveyed to Mas Kursuma because of the time limit. Thank you very much, Mas Kursuma, for the valuable knowledge and experience that has been shared with friends today, to Mr. and Mrs. too. It's really insightful. Can we give applause to our mentor today, Mas Kursuma, friends? The reaction, clap your hands, clap your hands.

Thank you. Thank you. Okay, before we end, don't forget the important moment, which is documentation. You can turn on the camera first, prepare your best smile, let's take a picture together first, come on, wait a minute. Okay, I'll count 1, 2, 3, 1, 2, 3, okay, for the next slide, 1, 2, 3,

Okay, thank you so much for those who are already on-cam. Once again, thank you, Mr. Kusuma, for this amazing material today. For Mr. Kusuma, if there is another agenda, you can really leave. If you want to stay with us until the end, you can. Once again, thank you so much, Mr. Kusuma. Thank you.

Actually, you can make it a reflection, you just need to generate a question that you want to ask to do the testing. But the phase is according to the material, how to do it. That's all, friends. I'm sorry because of the time limit, it can be practiced at home. Thank you, I'll return it to Gita.

Okay, friends, we have arrived at the end of the workshop, but don't go out first because we still have one link form that needs to be filled, namely for post-test, for feedback, and also absences at the same time. Wait a minute, I'll share the screen first. Well, friends, can you scan this barcode for the filling of feedback, post-test, so at the same time, for the filling, can you?

fill it in first before leaving Zoom, and don't be too lazy to absent it. For the post itself, there will be a keyword inside. The keyword is "prototype". I repeat again, prototype. P-R-O-T-O-T-Y-P-E. Later, you can fill this keyword in the column requested in the form.

Then I while explaining too, Mr. and Mrs. related to the previous challenge and also there is a paper, yes, for friends, Mr. and Mrs. There is something exciting, now there is a meet the innovator challenge, this is the time for you to show off your team's compact, make a video, sorry for a moment, friends, not fullscreen, well, yes,

Okay, I'll repeat it, so for my fellow students, there's something exciting, now there's a meet the innovator challenge, this is your time to show off your team, make an introduction video that shows who is doing what in your team as long as you develop the innovation, this is a must, friends, when making the video, there will be

three necessities that must be followed first is follow and tag Instagram @samsungindonesia the second can use the collaboration post feature with one of your team members and the last is the account is not private, friends, so don't just make a video and make sure that the above three things are fulfilled like that, the most important thing is that the four best videos will have a gift

saldo e-money total 4 million rupiah pretty good right for buying this gelok get 1 RT so don't forget to join this challenge then for friends who asked about the paper

can be continued, can be perfected again because the deadline is on the 26th to 29th of July for the template, it's still the same as when you registered, so there's nothing that changes, friends, like that. Okay, Mr. and Mrs. Friends, before we close the

today's session I want to say thank you very much, I'm always excited from beginning to end if there was something that was not right from me, the team and also from others, please forgive me, hopefully what has been learned today can be directly practiced for your own concept paper and don't forget to scan the barcode first for post-test and also feedback before you go to

recording stopped

Thank you.

Friends who are present in this session on January 11, I will stop for the boom. Happy weekend everyone, tonight we continue.

Don't forget to fill in the feedback and postage in the chat. The keyword is "Phototype"