Day 84- Validation of Ideas- 100 Days 100 Skill Booster Sessions

Very nicely at the end only. Okay, fine. Just a second. Where am I? Okay, spotlight for everyone. Okay, good, good, good. Yes, guys, so today is actually the last session for this first initially research and ideation. What we're doing, right, so what happened is people are bringing out the research. People are valid, people are taking the insights from and people are having lot of ideas. And in the lot of ideas we rated the ideas using the PUG matrix. We used critical thinking methodologies to validate our ideas to see the both ends of it. So all these skills are so far seen. Okay, so today the last skill, what we are going to see is validating your idea. What does mean by validation? How do you validate an idea? How do you know whether this idea has a potential or not? Okay, we evaluated the idea. That's in the day before yesterday. We did it. Okay, we did a matrix. We did an evaluation. That is one part that is okay. But how do we validate certain ideas? There are good methodologies to do it. There are rock solid methods. Like let's say there is a book called Sprint. Okay, we know about this double diamond process, defined test, ideate, prototype. This is like very, very common across the industry. Even manufacturing industries are doing this. Okay. But there are many methods which you can validate the ideas using particular frameworks. Okay, so that's what we are going to see. But before that, what I would like to see is guys, if anybody can share their project ideas, the list of ideas, whatever you have, it would be first better. Like let's say Sharath. Can, can. Can you guys share your idea of your team? Ramraj, Sharat and who else? Who is Kanda? Kanda, your team is mean. You have the ideas of your team. Will it be okay? Anju, can you guys share fast? Because if I keep you with an example, it would be much better and easy to explain you guys. Okay, can you guys share your idea? Okay, I'm just pasting this link in the group. Hold on. Just give me one second. Yeah, parallel. Can you just send me fast guys? Good, fast, fast, fast. Just give me some list of ideas from your miro or whatever. You have your, your projects and everything. Okay, I think Sharath, you have this list of ideas, right? Can you just quickly share it fast to me? Good, good, good. We don't have time. We need to complete it really fast. Okay, fine. It's not allowing more than some characters. So I will limit that. Just limit this. Okay, you sent to me in WhatsApp. That's enough. Okay, okay, that is okay. Okay, fine. So let me share the screen so that we can understand first. Okay, so the day 84, what we going to see is bridging your ideas into prototype. Like let's say validating a concept, getting ready for the prototype. Okay, so next week we will build the solutions completely. But this week we will know how. We will know which idea to build a particular solution as. Okay, okay, you got the idea, you build a solution. That part also we have seen one day in the last seven, eight days before we saw that particular skill set. Okay, but here this is little different. I'll tell you why the skill is very important because many designers out there miss this part. I'll tell you what. See, we have to understand what is the goal first of all for the solution. Many people forget that. They think it is very, very what you call out of the scope or something. Or maybe they don't see the connection at all. Just because the idea is fancy, we take it as a best idea. I will tell you what design concepts ensures the design concepts are practical. It is more usable and addressing the main user need. That is the most most important thing. This is called user centric design. So many products and services guys like let's say when you take a product called Google Glass, how many of you know Google Glass? Google Glass is a good idea, but it is not practically viable as well as cost. As well as there is a product called Microsoft hololens. How many of you know this Microsoft hololens? There are many examples. I can quote you. These products have not become success because it has been developed with a technology in mind. It has been developed with the cost or whatever in mind. But it is not user centric. This has a problem like let's say the big problem had with Meta is a privacy when they launched it actually okay, Facebook launched it several years before. Google Lens technology is not viable. Microsoft HoloLens like let's say the cost is not viable, people can't afford it. So a product should meet the user goal, cost viable, technology friendly as well as it is functional and usable. All the circles should be touched. Then and only it is meeting the whole validation concept. Are you guys understanding this point? In fact, to make this shot? Very simple in this class, very simple. This is a one line. So what how to find out this Jagdish, you're saying in words it is okay, but let's say, let's say if I, if I have to draw a circle, okay, if I have to draw like this. Let's say if I have to Draw a circle like this. Okay. I'm just creating one idea. Okay? Like let's say here it's going to be cost. Many people want to know which is cost, right? Next is. Next is technology, right? The next is business viability. That means feasibility, right? Whether it's manufacturable, whether it's codable. So we need to know whether it's okay or not, right? And the next comes usability. Everything is okay. Is the product usable? Usability. Okay. So these are all the methods what a user centric design has been determined. If people are not able to adhere this, what happens? The product will not get success. Particularly when you follow this. It saves lot of your time resources. By identifying the process flaws in the early stages itself. There is a. There is a flight called Concorde. How many of you know this? Virgin Atlantic has launched in 1984. This flight is called Concord. Concord. How many of you know know about this particular flight, guys? Tell me, tell me. Tell me fast. Did you guys know about this? Nobody's chatting. What happened? Still in the sleep. Sunday Jagdish. Okay. No. Okay. Fanatics type no. If you are not able to. Okay, fine. So I'll tell you. Yes, yes. Okay. Chitra knows it. That's great. So what happened is this particular flight has crashed in 1983 or 1984 because of a very massive crash. Okay? In fact that was the only technology which Virgin Atlantic has developed at that year. And it is surpassing beyond the mach number three and four. So right now what we are having this flight. When we are travel from domestic international, the flight runs at close to one Mac. That means 780 kilometers per hour. That's equivalent to one Mach. Okay? Max speed they call when it goes twice like, let's say 2 Mach. It is like 1500 kilometers per hour. I don't think any commercial flight runs with that speed. If you take rocket, if you take the, the missiles and everything that runs with 8Mac or even 7Mac or even 6Mac and all that means 750 or something into 2 or 3 or 4. Okay, so Mac number is 750 kilometers per hour. So what happened is today it takes like let's say from Europe to like let's say from India to travel to us. It takes I don't know like 30 hours, 30 hours or 34 hours. But when you have a Concorde, okay, which is the Virgin Atlantic flight, okay, the beak will be like this, that flight, car beak. It will look like a bird, okay? It will change its beak and the aerodynamic value changes. You can just travel it in four or five hours. It is five times or four times faster than the commercial aircraft. This is a major technology breakthrough. It's a major technology breakthrough. Okay, but what happened? Because of the testing not done properly, the usability testing not done properly, some accident happened and the entire fight crashed. Government banned that project. We cannot use it till now. Also, people are not very comfortable to do it. Yeah, of course Virgin Atlantic is working on something like an intergalactic planet transfer. And Elon Musk is also working on the mission to Mars. So people are developing the technology now. But they have to keep in mind it is not a problem of what you call that. There is a guy. No, what is that? Virgin Atlantic CEO. What's that guy? Can you recollect this guy's name? Very, very celebrity. What is this guy? Virgin Atlantic CEO. What's his name? Richard Branson. Richard Branson, exactly. Thank you. So Richard Branson, Elon Musk doesn't have any part of it, okay? This is the major part of it. They are visionaries, they are entrepreneurs, they are idea idea creators. Technology people will do technology. Business people will do business usability, Engineers and designers will do usability. But everybody has to work synchronously. That is why validating an idea is the most important part. Major product success comes with this point of a clarity. That is why the skill is very important. And industries don't spend lot of time in doing this. That is why I'm just particularly helping you out with this. And if you are not visualizing this particular step and taking action towards it, your company is not going to have a great product within you. Okay? So you be a designer to ensure this is happening. So we are going to see some frameworks, we are going to validate some ideas, we are going to see some real world case studies as well. So the first way to validate your idea, See, I'm going to tell you five methods. Okay? It's a very, very simple method. First is paper prototyping. No. Pavitra. What is no? What? No. Okay, maybe you're answering for the first question. Okay. First is paper prototyping. See, it is a very, very simple technique. Guys, if you really wanted to know whether your idea is going to work, you wanted to validate it quickly. Check it with the paper, give it to the user, understand whether it's okay or not. Show it to your management, show it to your team, show it to your client. You can get a very, very quick validation. See, for validating idea, you cannot take one year paper prototyping is a day's job. You can able to create a paper prototype and check it out whether the idea is working good or not. This is one way, very, very simple way. Okay, so wait just a second guys. Just a second. Wait. I'm just folding it out nearby. Okay. So that we can get the answer. Okay, so what is paper prototyping? Using sketches or paper mock ups to test layouts or flow with the users. Right? Hey, that is why I'm asking you guys. Please send it out your ideas. Saraj, have you sent it? Oh, you sent it. Okay good. How many ideas you sent, Sharath? Yeah, you can take the first one that the common idea and second one is the. The refined one that the only one idea we are going to pitch. First one, we have almost all the ideas. Whatever the ideas we need to. And that's okay. First one we picked out the ideas based on pug matrix. Right? We put that. Yes, yes, exactly. You got the best idea. Now we are going to validate this idea fast. Okay, that's good. So now I'll take this particular concept as well. Okay, fine. So what is this particular concept what Sharath has given you? Okay, later to put only but in the full industry allergen management software. But it's not got to be a software. It's. We will be doing B2B only but additional feature. Okay, no problem. Fine. So you're going to have a Allergen management. What is that name you said? Yes, Allergen management. Okay. It's like an app or website or chart or. What is this? It will be app only. App. Okay. So to validate the effectiveness of allergen management software with the food industry framework we we can draw on establishing practices related to allergen management. Okay. Cleaning, validation, compliance with the food safety. Here is a summary based on the insights. Okay. Integration. The software must align to hazard analysis critical identifying the thing. Okay, where is exactly the idea can effective allergen management brings? Begins with allergen mapping to identify where the allergens are present in the product environment. The software can facilitate the process of providing a tools and documentation. Okay, great. This is fine. This is a solution, am I right? Yes, yes. Yes. Okay. Okay, fine. Let's. Let's you. What the f. You. Why does this come like this? Okay fine. So this is enough guys. I'm. I'm deleting everything. Okay. Okay. So this is one idea what I'm having in front of me. So I'm just creating one small kind of a software. How does it look like Maybe you can just take a paper, you can cut like a, like a UI what you're trying to say. Or maybe if you're, if you're having a device or something like this, you can paste the paper of that particular mockup and write the options and then you can test it out with your user. This is called a very, very quick paper prototyping way of testing it. You can have something like a base option like, let's say, what I'll tell you is like, let's say, let's say if you want to build this particular UI like this, okay, so what you can do, you can just put. Management begins with allergen mapping to identify. Okay, so I can have two columns. Mapping means I can have a two comparison columns. How do I map this particular parameter? Okay, where the allergens are present in production environment. The software can facilitate this by providing tools for documenting visualizing location, which is crucial for risk management. Okay, fine. So validation result. I can have something like a UI which is having the user ID profile, the battery and other status of this particular device. And this is the parameters in which the, what you call the allergen mapping will be there. This is the first parameter. Okay, this is the second parameter, this is the third parameter. And this is the result. Okay, this is the result. Okay, this is the result. And this is the mapping. What is the end? So what I'm trying to do here is, I'm trying to understand, okay, how do I map this? Like let's say if my user taking this particular allergen test, how it is getting mapped. Like because of this allergy, you get this problem. Okay, I'm just creating a simple UI and what I'm trying to do is I'm asking my user, hey, this is your final result. See, your final result is actually you are like gluten allergy. Okay? Avoid this food. Got it. Very simple. So like this, you have a small paper mock up or something like an idea, quickly you have to test it with your team. You have to ask, hey, is this okay or not? Maybe your team can say, hey, no. The UI elements are spaced very, very, very, very larger. But we have five to six parameters to show in our allergic test. Okay, so why don't you make the icons and pictures and text little small. The usability team will say, okay, when we put five or six items in one screen, it becomes very confusing for the user. How can we make it? Because law of three works everywhere. It's very, very simple to keep one or two or three elements max to max. Okay, so usability team will say no, the five elements we can't keep, we can keep only three. But we can give an option called more will do. Do it this way. Okay, we'll have an option called more here. Okay. When people want to click more, they can click here. Okay. All the highlighting alerting parameters will get in the popped up like this so that the user will be notified. This is my highlighting parameters. Okay, good, fine. So whether it's developable or not, we'll ask the development team. Hey guys. Which is developable or not? Yeah, it's possible. Not a deal. Like let's say your graphics is very high. You can reduce graphics and you can, you can reduce the gradients of the color because we are going to use it in the public. If you use fancy screens and colors and gradients the screen, the software will crash. We are going to use a very primitive screen. Okay, so reduce that colors have only this rgb. So a development team will tell something. Usability team will tell something. Your management will tell. Why are you making this entire app already? Your competitor has this. Finally your management will put a big bomb. Okay, Whatever you did so far will become waste of time. So that's why you need to understand it's a very, very low paper prototyping stage. The reason being it will save a lot of your iterations in the future instead of you building a very, very high quality, close to final solution. And then somebody says this is not going to be a great idea, then you will have to validating the concept is very important. Okay, so you. Okay, even your management is accepting now. And then everybody is accepting. Now comes the user. You will have to give this flow and you have to ask the user, hey, can you just use it? Can you just put your allergic values here? Can I just put your testing here? Okay. Our software will automatically show a visualization where you're going to get the allergic test done. See in the next screen probably it will show a map. In this particular map, the allergy reaction will be visualized for you. And then what happened? This allergic explanations will come here. And after that the relevant doctor which you have to see and the hospital contact will be put here. This is how our system really works. Okay? Okay. This is what is our particular solution. What we have created is going to solve the problem. Okay, My user will test it out. So now give it to your user, ask him to rate it. Hey, did you understand your allergy? Did you get the clarity on what allergy is it having? Were you able to take Decision is it okay? Do you need better you tell me. User will give one feedback, gathering all this feedback, then you validate the idea, then you go for it. Because it is very easier and faster when you do a paper mock up prototype to test it out. Guys, clear in the last few minutes, whatever I explained, is it clear? Fine. Type yes in the chat box if you are okay with this. Type yes. Before we go to the next topic, I wanted you guys to just take one small paper, okay? You take any project. Whatever you guys have in your past, you take any project. I don't mind which project you take. Okay? You can take this allergy project, you can take your college project, you can take your school project also. I don't mind. But what you have to do is you'll have to create a small mock up or a prototype in a sketch pen. Write it down, write a solution. Okay. At least build two to three screens. Or maybe if it's a physical product, try to try to fold that paper and do it. Maybe you can try to create a paper like this and then you can create like let's say Jagdish. I'm creating this kind of a bottle, okay? Like this is my product. Okay. So I'm just pasting out with a cello tape or something. Like this is a product, please use it. This is going to solve your problem. This is how the product should be holded. If it's a physical product, your interaction will be very different. Digital product means you will have interactions, buttons and everything. So think about it. But I need to see some kind of mockup in real world, not just a digital way of just showing it some kind of a physical mockup. Because when people see it with their hands, the perception will be different. If you paste your particular UI and put it in a mobile like this and they will, they will operate it. Okay? Okay. This button seems little bigger for me. Yeah, it's too much. No, this button feels very smaller for me. If I try to press it, it gets adjacent clicked. So how do I manage this? How do I manage this? Okay, so I can space it more. Okay. What are the anthropometric dimension of the fingers? How much space I can give? The usability team will come and tell you. Okay. We'll have to space it accordingly. If you're particularly working in a very, what you call a production based environment, a manufacturing environment, let's say your user is going to use a particular tablet or something. They will be already wearing gloves, so their hands will be little bigger. So you need to give A very bigger UI size. Right? Have you seen in production factories and everything the UI what you will be building is very, very different that the box size and everything will be very different. Because these people are already in a huge cognitive load in working in a factory. You cannot have a mobile like a UI for them. You need to have it big. You need to have it spaced properly. You need to give primary colors. You should. You should not use any much gradients. So based on the environment, based on the client, you try to map one solution. Use sketch pen. Use paper and try to show me fast. Fine. In the next few minutes you guys are going to do a small mock up. A small paper mock up with. With this. With your notepad and pen. And show it to me in your screen like this. Fine. Your time starts now. From that I'll teach you the next concept. Clear? Okay. Good. Good. Good. Super. What is this? Why? Urvi, what is why? What does mean by y? Akash. Yes. Ramra. Yes. Chitra. Yes. Okay. Okay. No. Oh yes. Okay. Okay. Cool. Cool. Fine. Fine. Do it. Do it. Do it. Try it out. You guys have a project already. Please take it that and then try to mock up it. Okay. Maybe if it's not a physical. If it's not a digital product, you can take any physical way to do it. Like you can bring one DAPA or something to showcase. This is a mock up of the product. Be creative. Use the things, whatever you have around you. Okay. Just give me a minute. It just send me one snap. That will be better. Okay? No design studios really does it guys. So learn it properly. Because you should be the one who should take this initiative in your organization to complete it. Okay? Very, very few design studios really take it up with this paper mockup prototyping and test it. Or validate it properly before they give the idea to the client. Everybody's comfortable. Ramraj, were you able to do it? I think Sharath will be okay, right? Because Sharath has a solution. Urvi, were you able to take one project? Tell me. Confirm me. You can unmute. No problem. I'm trying to think about it. Okay. Around me and I'm just trying to think what better I can do with these. Yeah. Better. Better. Better. Fine. Chitra, what about you? You have any projects? Pavitra, what about you? Okay, take any project. If you are confused, I will give you one new also. No problem. Just ask me. Kanda, I hope you are okay. Mekna is already sorted. They have a project. Anju also has a project. A. What about you, Akash? What about you? Okay, very, very fast. You need to do paper mock up. Should be paper mock up. Okay. It should not be a very rough and very neat, well defined solutions and all. Just wait, I'll also give you an example. Okay. Okay. Yeah. Can you send some snaps or something very, very quick. We're finalizing it today. It's okay, finalizing, you do it. Okay, but which bring some solutions fast to me right now. Okay, Just one snap of how people are doing. Can you just show me fast, fast, fast. Hello? Okay guys, can you. Can you just show me what you got? Just send. You send whatever you have till now did. It's okay, fine. Somebody has shared me something. Who's this? Okay, okay. Excellent. Here. Pavitra. Perfect. This is what I'm expecting. Okay, but make it little paper, paper mockup. The reason being excellent. Urvi, I can see your solution. Oh, wow, this is amazing here. Hey, you took some earlier project and now you did this. I could not understand. Okay, this is a direction practical following the calculation without abacus. Oh, that is interesting. That is really interesting. Good, good, good. Fine. Oh, are you referring me? Sorry, yeah, you're. I'm referring your picture you sent me now. Great, Super. I can explain. Yes, afterwards. Yes. Yeah, no issues. Completely fine. See, we just needed a little mock up to explain. What is this thing about? Okay, okay, guys, listen to me now. Stop, stop, stop. Listen to me. So can you just take a picture and send it to me fast in WhatsApp, what you did so far. It's okay. We can do it for like hours together. We can do it for 30, 40 minutes. But you should get the gist of what is happening. Okay, listen to me. Fine. Like let's say if you're having an idea in your mind. Okay, listen to me, listen to me. Just look at the screen now. Okay, if you're having an idea with you, if you wanted to quickly validate it, paper prototyping is the fastest way to do it. Okay? And the next way could be like creating some kind of a mockups. Or maybe if you wanted to do it in a very, very faster way, you can do a method called like let's say a mock up like this and you can create a. A connection. Like let's say if you're building a three screens example like this, okay, you can have a sketch book like this and then you can use some colors. Like let's say if you're creating an option. Just give me a minute. Okay, fine. So if you're having a concept like this, the first Concept. So what is this? Allergy management. Right. So allergy management, what a user will have. So all this validation, research, everything is done. Okay. So you can have a profile P for this. Okay, you're having the, the input questions. What kind of allergic questions we have to ask? Input questions we can have. Okay, and how much questions we can have? 1, 2, 3, 4. Okay. And, and once the people gives the input questions, so there'll be a section which will be prompting to the next one. So you can have a call to action like this. So instead of just telling this as a call to action, I will give one one small color for this very very quick. Okay, I'll just color it. The reason being. So I'll just switch off this blur. Guys, you guys can see it better. Okay. Can you see better now? Okay, you can just create an option so that what people will do, they will automatically know this is a call to action. Or maybe it will, it will prompt them to the next screen. So once they give more, what happens is it will ask some more questions like let's say your date of birth, you had a medical history, you have some previous allergy, you have some, all this, all these questions. Okay. If it, if it feels very, very long, like let's say four or five or six, then we'll have to concise it. You have to think, okay, with the few response, how can I get a better output? Like let's say if I'm giving, if I'm asking a lot of questions, it becomes a problem, right? So you can just cut short. We'll have a three and with that itself we will ask our technical team, like let's say the food allergy team will be there with you, right? Hey, you tell me right now you are asking me to write 10 questions to ask to the user. By the time 10 questions user answers this, they will lose the interest in using this particular app. Why don't you make it just three? Can you give me the top three questions? What will be the determining factor to define the allergy? Then you have to sit and brainstorm. Okay, we'll put this option. First of all, let's put this first option. Okay. The first option is the most vital you have any previous allergy. Second one is this. Okay. The third one is this. You just name it. Okay. One, two, three. Rest is not required. Rest you can put as a. Like let's say optional. Okay, this is a mandatory. You can put the star. So it won't allow the user to fill this before. I mean once you fill this One it will go to the next screen. Okay, you can keep on the next action. You can create a very good hook saying I wanted to find the result. Like let's say you can handle result. You can use a different color, right? You can use the same call to action so that it becomes a easy for the people to understand. Okay, see, look. And then now we are showing some kind of a graph which shows the final user profile. Oh, this is my result. Okay, you're allergic free safe. Okay, you can have a color code to explain. Like let's say you can have a three color code. One is this yellow. Okay, you can have this yellow. Yellow means a little bit. Okay, getting alert. Okay, red. Red means problem. You have to immediately go to the doctor, check it out. Okay, where is green? One second, guys. Okay, so green. Green means you are in the safe zone. See, using this particular method, my user will be able to clearly know that what is the allergic status. He has been there. Okay, so now I took five minutes to do it, maybe three to four minutes. Okay, so what my team will do, okay, user will enter this data. Then the user will find out the parameters here. So what my user will do is to get the result. Okay, so now what happens? You have to give it to the user and check it practically how much time are they clicking for one screen to other screen to other screen? So let's say if this particular screen takes like I'll use another stick. You can use all these materials. Guys, I already asked you to get this 3M posted sticky. Get a sharpie marker. Right now my entire kit is in the office. Okay, so you guys can get this only rough kit I have here. So what you can do is this idea is actually called. You can name this idea. What is this idea? You can have something like a allergic tester. Okay, you can cap this. You can have one more sheet. You can create another concept like this. Because it takes only five minutes, right? To create one one idea. You create multiple ideas like this and show your user which is better. Show your management which is better. So they will tell. Okay, this will take two minutes and six steps. This will take five minutes and six step. This will take seven minutes and three steps. Okay, fine. So totally the user spends ten minutes to complete this. Three screens. Oh my God. Ten minutes is really high. People lose the interest. How do we make it very shorter? How do we make it very shorter? Okay, let's bring AI into this. Let's take another solution. So what we will do is we will have only two screens in these Two screens. What happens is automatically when you scan your picture, whatever the allergy test, what you have using a camera button, I'll just draw one camera button. Okay. Rough camera button. Okay. So it will show like upload, Upload. Are you guys seeing this? Upload? Okay, I'm just giving a small call to action button here. You just upload. You just have to upload it. What happens? This particular tool, the software what you built with your backend team, is going to scan all the data from your medical report and then it will automatically show the graph result. The same color code, whatever you're taking, you can just take a color print of this. You can copy paste here also. You don't have to draw again. Okay. If you're creating a paper mockup, you can use this color printout method. Like let's just say I can have this yellow. I can have this. What you call. Where is this? Red. This is red. Okay. It is giving green. And you can have one small word in the, in the bottom saying AI solutions are 80% accurate. So previously the idea one has got 15 steps or something. Now this particular idea has just only one step. What is that step? Just uploading the picture. That's it. This is the AI idea. Now you have two ideas with you. Okay. Like this. Imagine if you have a five ideas with you. Okay? You just now going and testing it with your users. You're just asking your customer care team, your marketing team, your development team, your testing team, your management, your client and then you're asking. So everybody's very fancy with this AI stuff, right? Oh, one click how people can, let's develop this one. They are saying this is having a potential. You're just validating this idea. Now you're giving this to the software team is developing, people are using it. People are now taking a picture of the medical report and then getting with other terminologies like Lean Startup. Have you read the book called Lean Startup Guys? I would highly recommend you to purchase in Amazon and read. It's an excellent book. Okay. Build, measure, learn, loop. What these people do is like let's say it is by Eric. This guy has written this book and three people have written this book. It's a very, very good book, particularly when you started working in a design studio. Please buy and read this. If you're looking for a job, you're doing your first project. Don't confuse much. Just do your projects and some complete it. Okay? Don't think much. You can just learn the basics and do it. If you're working In a design studio, these things will help you a lot. Okay? Don't go and learn and waste your time. Okay? Measure, test with the real users and gather the data. Learn iterate based on the findings. Build, create a low fidelity mock up and a minimum viable product which is called mvp. See, the reason this book has been written is the meaning itself is Lean Startup being a startup. How do you work lean? How do you work with minimal resource? How do you. How do you create more ideas in a very short span of time which is super usable, super functional, super cost effective, super technology friendly. I told you in the start of the session, right? So these people have really created this method. It's a very, very simple method. You can read that the result and then you are comparing this. Okay, this result, what we got is very very accurate to 99.9%. This result is not even accurate for 60% because the AI model needs to be trained more. So this idea will not work. This idea works. Take it for the development. Look, I. I actually left it in my other place just a second. In one day you can able to decide which solution has a maximum potential and accuracy. Okay, Maybe in the version 2 we can release this so backend team can go and feed this AI model with a lot of data or maybe to create more what you call information around it and then to find the competitor study and then you develop the project. That's it. This is how you quickly validate the idea using the paper mock up technique. Are you guys getting it? Did you guys got it clear? I don't think it is very difficult. But if. If you are not doing it, it becomes very very difficult. The reason is many, many industries skip this. They don't want to do this. I don't know why. Okay. They think it's a time based. They think you build a screen here. That's what design solution also design task also they give you, right? The companies who is asking for the design task to show your only screens and solution. Please don't go and attend these companies, these companies are completely time wasters. They're going to put you in a substandard role. If a company asks your design task in a way, why don't you show a paper mock up? Why don't you show the process? Why don't you show how you evolve the solution. That is the place ideally you wanted to go and work for. By seeing the design task itself, we can understand the quality of the company, what they are doing. It is your responsibility to choose it very carefully or else you will be unnecessarily pulled. Tomorrow you will be just doing the same mistake inside your organization and nobody will allow you to do the process or understand the idea behind it. And it will become a substandard product in the market and it will terribly fail. That is why validating the idea is very, very important. Before you go and test it out. Okay, so what I showed you in the last few minutes is actually called pep and mockup. Okay, What I showed you in the last particular thing is called split A B testing. I'll check whether I have it or not. No, I don't have it right now. You guys can get this, It's a very, very small book. In just one or two weeks you can complete it. Okay, so what that particular method will tell you is you will have to iterate based on the feedback what you are having, give a lot of iterations, measure it and then build a very, very low, what you call viable product. If this is not giving you the required data, build it one more time. If it's not giving you another data, iterate it one more time. Do the cycle again and again until you reach an optimal point. This is what this method is. Okay, you can validate this method. It's a wonderful method. You guys can take it. Mvp. Yes, Sharath. Correct. Because people don't like the costlier product at the start of the place, right? People would like to see the mvp, the minimum viable product. Okay, think aloud testing. Like let's say what is this user verbalize their thoughts during. You're having the same set of audience, same set of conditions. You're splitting the concept like A, you're splitting the concept like B and then you're performing it in the market. 10 users. 10 users. Now you get the result and then you know, idea is better. Let's go for idea. We will keep it aside. This is called split AB testing. Got it. So these are all the methods to do it. Industries follow their own standards. But you guys have to know the basics. And then you adopt to what your industry really follows and automatically you will be getting clarity towards it. Okay, like let's say if I have to find out, like let's say for the paper prototyping I gave you this examples you can have something like grocery app flow tested with the paper screens and sticky notes. I mean I've just given you an example of allergy management because Sharath team is doing that. But you guys can do with whatever solution you got. No Problem Wizard Oz testing. Simulate the backend functionality while testing the front end Front end interface, right? You don't have to worry about traction. This is also one way to do it. Like let's say when you go and ask your user, hey, how do you feel this particular solution is? He will talk about it, note it down, take the example and then improve the product. Documenting the frustration while navigating the app. He will tell like this, right? He will tell many things. Write it down. Okay? This is how you validate the idea, guys. You are not going to validate the idea just by looking at which is the beautiful most visual screen. No, we are not people who are beautifully about HTML CSS coding and everything. You just have to worry about building the solution and showcasing to your user. Your backend team does all these things, but you have to just show a solution which looks little close. I want a little neater solution. This is looking very rough. Okay, get some validation from your concept or your team and develop it properly. Take little more time and develop it. Maybe you can spend another one or two hours to create it in things. We are functional people. We take decision. We help people solve their problem. Softwares like Miro or Figma or anything. Take a printout, okay? And then cut it and then use it properly and then test it out. But anyway, it's a paper mockup. You're just spending little time to do it little professionally. Okay? Okay. And after this, when you say example, Airbnb is early platform testing by manually coordinating bookings. Okay, this is one. These are o testing you can call problem. Aesthetics is a very small part of it. Okay, don't just fake door testing. I have not used this, guys. I just took it from the online. So they are saying presenting a feature without building it to the gauge user interest. The name suggests that it could be some kind of a fake concept where it is not real, but people are going to use it and then get the validation. But in our industries so far I have not used this. We have used. We use paper mock up a lot. We use split AB testing a lot. We use this user storytesting. Don't ask me. Aesthetic is important, functional important. That debate is not the point here. Now I'll teach you in the 95th day to 100th day. Okay? Ultimate ultimate skills. I'm going to teach you with respect to ace. These are like very, very common methods. Okay. We used to gauge the users with the fake users. They're saying, okay, so the example is Dropbox MVP demo video. Gathered thousands of signups. See aesthetics Gestalt law of psychology. We are going to learn this Rasa theory, we're going to go very deep into harm Dropbox. Before launching a product, what they do is they create a small video explaining the important features of this particular product. And then even before the launch of this product, everybody is going to go and purchase that. Their sales skyrocket. Like anything, their products get a very, very big highlight because of that one small demo video. That's why they call it as a fake door testing. But practically speaking, I don't know whether every industry is really using it. Okay, so please be aware. User story testing. Very, very interesting guys. Uber tested ride booking workflows by role playing like a drivers and ride scenarios. This is very interesting. This is what majorly many, many, many design studios will do, including us. So what we'll do is we'll try to understand the situation. We'll try to do a scenario mapping. What does it mean by scenario mapping? Like let's say if you have multiple scenes in your project, in your solution, in your application or whatever. Okay, you try to create that scene same like this in the paper or you take a picture. Mostly our design studio, we will have a lot of this DSLR camera. We'll go and take pictures. Will go and ask the user to hold the product in the hand or use the mobile or whatever. Take pictures, put money rhythm aesthetic will come to it. That's a part of the whole equation. That is not the major equal. Okay, how would you use while sleeping you're using mobile. That's one scenario. Take a picture while driving. People are using mobile. Take a picture. Okay, these are all scenarios. So what is your product going to be used? Where is your product going to be used in various scenarios based on that scenario, you died the problems, you write the solution, you validate the concept and then you go and test it with your users. This is called storytelling user story testing. Because you you okay being a designer, being a fresher. Don't get allude with this aesthetics. Get understand your user very deeply. You will be able to get it. Okay, next is split table testing. I think I told you so. Present two variations of an idea. Analyze the performance which goods which works better. Okay, you need to have a very into the functionality. Help people to solve the problem. Validate your ideas first. Then you can good data to test it out. So you should have a clear validation of why this concept is good. Why this concept is not good. Okay, you need to have a metrics. You cannot impulsive. Impulsively say this is good, this is bad. Just because Ram Raj did. I don't like it just because a build it in a more visually pleasing way. Okay, you need to first get this clarity because Kash did I like it. This doesn't work. Split tab testing comes with a proper metrics and data. I will tell you this is what will happen in many studios. People will. People will go with one favoritism with one people. No, that's not the way. Okay, so e commerce sites tested with buttons placement even without aesthetic pleasure. Also you can still create a product but if the function call to action I think it's very very prominent. Guys, you don't have to what you call very much about it. Okay, so after you create this kind of a methods to do it, you can also validate it with other terminologies and like Lean Startup. Have you read the book called Lean Startup Guys, I would highly recommend you to purchase in Amazon and read. It's an excellent book. Okay. Build, measure, learn, loop. What these people do is like let's say it is by Eric. This guy has written this book and three people have written this book. It's a very very good book. Particularly when you started working in a design studio. Please buy and read this. If you're looking for job you're doing your first project. Don't confuse much, just do your projects and some complete it. Okay? Don't think much, you can just learn the basics and do it. If you're working in a design studio, these things will help you a lot. Okay? Don't go and learn and waste your time. Okay, Measure, test with the real users and gather the data. Learn iterate based on the findings. Build, create a low fidelity mock up and a minimum viable product which is called mvp. See, the reason this book has been written is the meaning itself is Lean Startup being a startup. How do you work Lean? How do you work with minimal resource? How do you. How do you create more ideas in a very short span of time which is super usable, super functional, super cost effective, super technology friendly. I told you in the start of the session, right? So these people have really created this method. It's a very, very simple method. You can read that functionality itself is not met. People will not be able to use your product at all. There is no point in talking. So understand and prioritize accordingly. Okay, fine. The next is pugmatics. We saw it. I don't have to tell you. We saw very deeply in the last few days. Okay, Compare your multiple ideas based on the weighted criteria. Score it, measure it, analyze it. Bring some graphs like let's say hard jar. There is A tool called Hard Jar. Bring the rating from Hard Jar. There is a tool called Google. I actually left it in my other place. Just a second. I check whether I have it or not. No, I don't have it right now. You guys can get this. It's a very, very small book. In just one or two weeks, you can complete it. Okay? So what that particular method will tell you is you will have to iterate based on the feedback what you are having, give a lot of iterations, measure it and then build a very, very low, what you call viable product. If this is not giving you the required data, build it one more time. If it's not giving you another data, iterate it one more time. Do the cycle again and again until you reach an optimal point. Analytics. There is a tool called what you call. There is one more tool. This is what this method is. Okay? You can validate this method. It's a wonderful method. You guys can take it. Mvp. Yes. Sharath. Correct. Because people don't like the costlier product at the start of the place, right? People would like to see the mvp, the minimum viable product. Okay, Think aloud. Testing. Like, let's say what is this? User verbalize their thoughts during interaction. This is also one way to do it. Like let's say when you go and ask your user, hey, how do you feel? This particular solution which we have seen last week as what is the tool? Usability.com these, these particular things are like, let's say it will give you a data what your user is performing. What is vision is. He will talk about it, note it down, take the example and then improve the product, documenting the frustration while navigating the app. He will tell like this, right? He will tell many things. Write it down. Okay? This is how you validate the idea, guys. You're not going to validate the idea just by looking at which is a beautiful, most visual screen. No, we are not people who are beautifying things. We are functional people. We take decision. We help people solve their problem. Aesthetics is a very small part of it. Okay? So don't ask me. Aesthetic is important. Functional important. That debate is not the point here. Now I'll teach you in the 95th day to 100th day. Okay? Ultimate, ultimate skills. I'm going to teach you with respect to aesthetics. Gestalt law of psychology. We're going to learn this rasa theory. We're going to go very deep into harmony rhythm. Aesthetic will come to it. That's a part of the whole equation. That is not the major equation. Okay, Being a designer, being a fresher, don't get allude with this aesthetics. Get into functionality, help people to solve the problem. Validate your ideas first. Then you can build it in a more visually pleasing way. Okay, you need to first get this clarity because even without aesthetic pleasure also you can still create a product. But if the functionality itself is not met, people will not be able to use your product at all. There is no point in talking. So understand and prioritize accordingly. Okay, fine. The next is pugmatics. We saw it. I don't have to tell you, we saw very deeply in the last few days. Okay, Compare your multiple ideas based on the weighted criteria. Score it, measure it, analyze it. Bring some graphs like let's say Hard jar. There is a tool called hard jar. Bring the rating from hard job. There is a tool called Google Analytics. There is a tool called what you can. There is one more tool which we have seen last week as what is that tool? Usability.com. these particular things are like let's say it will give you a data what your user is performing, what is doing and then you measure and take a decision. Okay, and next is my favorite design, Sprint. Go and read this book guys. Even if you're a fresher, get this book. It's there in Amazon immediately. Order it, study it. Okay? Same like design of everyday things, this book is also very, very important. Okay? It's a Google venture actually Sprint. So David Knapp, I guess the author of that book and many people written that, it's not only one people like in two days you can complete this book. If you sit, just two days is enough. Okay? If you're a procrastinator, even if you take two years, you won't complete it. You will get the book, you will not read it. Okay? But if you're an action taker, it's just two days you can complete this entire book. So what is this? Validate usability and feasibility in just five days. Their entire cycle is Monday to Friday. Five days. How do you test an idea? Five days. How do you validate an idea? Five days. How do you validate a particular concept? Five steps. So they have a very, very simple methodology. I mean I can't possibly explain this very detailed, but you can go and read it out. Okay, but this is a method to validate. First is understand, sketch, design, prototype, test it. It's very simple guys. It's not a very big complication. Okay? If you look at design of everyday things, this book, Double diamond process. If you look at lean startup, if you look at design Sprint more or less, it's all same. It's not a very big what you call don't scratch your head. Oh, I need to learn this book. Then interview people will ask me questions from here. What if I don't answer? Don't go into this dilemma, okay? Just these are all methods. Even without this method, you can still design products. Don't think much. Okay? Just take it. If you guys are here, the good reason I'm just giving you this thought process. Go and learn it on your own. Go and understand your users better. Sketch some ideas, decide which is good. Rated average. Make a small paper mockup prototype, test it, create the loop again, do it, document it in your case study. That's enough. Nobody can question you if you are having this clarity. Because this is. This is the process. Beyond this there is nothing. There is a non linear way of doing it. Like let's say sometimes your user will not give the chance for the user to test the prototype at the real time. You'll say it's a confidential project. You can't show it to the user. That time. You can't have prototype. You have to understand sketch design and you'll have to test it with some softwares. You understand, right? Prototyping is not possible. You have tested with the software again. Go and understand. Yeah, there is a risk factor. Until unless the product comes over, we never know what's going to happen. Because it's a confidential project. The moment when I put it in the market, every competitor is going to copy that. Many industries will have a different restrictions, guys. So understand your industry. What are the problem you guys wanted to solve and then take the solution. Once you're understanding this method to validate automatically, you'll be able to create a wonderful solution, guys. Okay. You can take many example. Like let's say. How do I put it? Okay, fine. So like let's say Spotify playlist feature. Use wizard OZ testing to validate user preference or playlist creation. Okay. These industries have used this case study. You can just type out these keywords in the online. Start reading about this case study, you will get some idea. Duolingo's interface. I already told you about Duolingo. How they created AV split testing gamification elements to improve the engagement. Because they wanted to test it which user performs better with this game concept. Can I create it this way? That way which is simpler. Duolingo is a great way of learning, guys. You guys can install that app and try it out. Ideas. Human centric design for medical Devices early prototyping test with nurses refined usability for drug delivery system. In fact, we also designed a lot of drug delivery system in our company. Okay. Few years back and we designed something called this urine tester. We designed this dialysis machine tester, physical products as well as digital products, both together. Okay? We all use this IDEO method. Very, very early stage. We tested out this prototype with the user and then we got the feedback and then we refined it. So any big design studios will properly implement this method to test it. All this consulting design studio, all this people who are like Hariburi. We want only screens. We only want screens. We only want solution. These people doesn't know the importance of it. Don't end up your career like there. If you're already working in some kind of a place like this, red alert. Jump on. Start finding new again. Don't quit your job and do it. Do a proper strategic job search process. Go step by step and then go for the next job properly. Where all these things are taught in a strategic way and they're doing it in an environment. Because if you are. If your environment is doing all these things automatically, you will also do it. Okay? Remember, my mentor always says your environment is stronger than your willpower. You may be a super duper guy learning all this design concept and everything, but if your environment says stop everything, just build the screen in Figma. Go, Go, Go. Do it. Do it. Do it. Evening. Evening. Evening. Send me, send me, send me. In one month you will become a normal you. You'll become like them. Okay? That's why our environment is very important in choosing the big opportunity. Fine. So these are like other methods. I don't know about this case studies, guys, but you can try it out. Zappos validation via this concierge MVP posted shoe pictures online. Manually sourced, sorted them, their orders. I think you can understand this case studies, right? But you can go and read it out detail. Because I have not. I don't have any idea about this. But I know about this one. I've read a lot of case studies and I've seen people. Okay. Particularly in the last. In the last two, three missions before we saw an IDEO case study also in our program. Very detailed. It's an excellent design studio, I would say, which follows the design process properly. Buffer MVP landing pages describes the concept. Collecting email signatures to validate interest. Let's say people are coming to the landing page, buying the product. How do you validate them? How do you understand this is good or not? Have you seen in many Landing pages. When you go in first five seconds. If you're not taking any action, it will automatically ask you for the email and sign up and phone number. Because ultimately their objective is to collect your email id because they'll send you some kind of a offer, this promotional. All these things. Right? So understand that. So they want to check how the users are really behaving. How can we collect this data from the landing page? So based on your business, you think about what is your solution and try to do it. Okay. I would love to give you a lot of real activities, guys. Each and every activity. If I spend 1010 minutes I will take one hour for you to do it. Are you guys ready to do it like this? Ready? No, I can't do it. I have others. We'll do it slowly. No problem. Okay. Just my thought process is to give you the skill and the idea. Okay. And I gave you one live activity. But it's your responsibility. You can try it out with your own project and do it. Nobody's stopping you. You can test all these five methods also. No problem. Okay, read more. You have ChatGPT. Read more about it. Each and every method and process has a different nuances. Test it out. Try it out with your team. Sit and brainstorm. And then use this fugue matrix. And then you decide which concepts really look good. Okay. You can use this role playing also. It's an excellent way. If you're completely stuck, I'll also give you this method. Okay. One go. You'll be able to get solution. Guys, I'm just pasting out in the chat box. Okay. Just use it one go. You'll be able to get a lot of solutions with a super clarity. Okay. Oh sorry. I sent to Akash. Okay. Yes guys, used it out. Okay. I'm going to put it in in your WhatsApp as well. Okay. Use this. Oh guys, I'm extremely sorry. Kanda, you've shared the picture. Oh Kanda. Excellent. Here. Yeah, I'm extremely. So why don't you chat in the chat box here? Jagdish. Excellent. I saw just your solution. Okay guys, fine. Let me quickly show his solution. Wait. Can you see this picture? This is what I'm asking for. If it is a watch interface, you have to cut like a watch. Guys, are you getting. Don't just get stuck with a screen. Okay. Just think about how your product is going to be used in real time. Sometimes it may be a tangible input. Sometimes it may be a C. Some people have read this. Okay fine. Chitra has submitted Babysitter in the city. Okay, that's great. So understanding the idea, understanding the concept. Use some colors, use some arrow marks. Create a very, very small, rough mock up. Sharath. Okay, that's great. Super. Today feels like this allergic level. Oh, that's great. Interesting. Sharp. That's it. So use any, any interactive way, but make sure it is very creative. See, you can use a small method, like let's say you can cut some small holes, you can put some button inside, you can create some colors, you can do some kind of a rope tied up. And you can create many, many creative ways. Guys, it's totally up to you, but make sure this is communicated properly to your user. And you're testing these ideas. Got it? Clear. Super, guys. Take it out. I think you guys got it. Why? Critic validation is critical. I'll tell you last quickly. It activates your reward system automatically your user gets the thing. Okay? Because if you're not able to activate your user's reward system, product fails. With that, you're coming to the end of the session. Watch this video one more time and definitely you will get the clarity. Okay? I'm extremely sorry. Sarat attendance. Okay, please go and mark your attendance, guys. Oh, my God. That.