Chiang Mai Dapps Meetup/7th July 2020 - The Importance of Design & Acid Test for Product Development
Chiang Mai Dapps·Tue, Oct 27, 2020, 12:00 AM
Transcript
so I'll tie it into that work done so like I have sort of I'll give you so like that some real-world stories match with the points and then I would like to go through another rather than exact same process well I will I'll give you guys a big project to use that same methodology on and you guys can help fill in blanks and then after that I think there's a few people here who we can maybe go through another iteration of your own project or something so the first thing that understand is that so I was an industrial designer and I did a mental device designer which is necessarily very safety focused because you don't want to kill your patients people that are painting that business and in fact like they're the reason that the first one is essentially a protocol from Leeds the European national standards body and explain it's this big ass document but it just says read to this whole thing if you want to be able and follow the protocol if you want to be able to have your product available in Europe and those are actually followed in both that can't see anything is basically an American standard for human factors engineering but the I see you're basically shows for 18 so not into it so just kind of promise one big fat thing like this is that essentially before there's a point of time before they had the standards and asked people and made people comply with them before they were able to really sell the products in the country is that basically there would be a design process where there would be like a doctor and you say there's a problem with my patients and let me talk to an engineer and then the engineer will like help give some like input like this is what I think is important to make this product to help the patients and the engineer ago I got here was important and then they would get to the patient and then sometimes the patient was down because the engineers wouldn't actually test the devices with the patient's using them so or there would be a category error that started some very big called USERRA which means that the patient or the doctor or whatever would essentially use the product wrong and then cause harm to the patient so in these standards there's three package classifications of products which go under class 1 2 and 3 and it's just a severity so class 1 is like the highest athletic it anything that will kill you if it stops working later or if it malfunctions seriously then later pacemaker class 2 is things that will cost maybe might kill you total cost of your harm so those are the things that worked on those really human talents machines and some machines perineal dialysis basically anytime something's going into your body and coming out it's like doing such it and coming back out so there's always gonna be like a suitors for your harm and the ancient cultures so once you pass up once you're in this zone you need to and you look at these this process it's essentially it's pretty much common sense in a way but it's just a standardization it's something for regulators to point to and say this is very easy to go and so and so it looks like so this is what the process is like it's like fun essentially what you're trying to do is you're trying to manage your risk so that because essentially when you start that you don't know you don't know what's bad so what you do is you sort of research which is either primary or secondary primary it's like watch them do their thing secondary is your computer obviously one is better than the other ones more cost-effective but can you sort of left right a little bit of paper but it's actually what you're trying to do is you're trying to like expand your knowledge base what is risk and what you need to focus on and then eventually come to this point where you have enough research information where you have and you understand your own personal or business positives business and you apply that to this problem that you really understand and then you create concepts in order to like just mentally figure out that's a good idea yes paper this is plant whatever but it's just a way to like quickly get feedback from other people to understand what the view is called also so with development phase basically you've done a bunch of different ideas of different concepts then you choose one and then you start developing it and the way you do you don't develop it by just doing it because you'll definitely see what happens so what you as you do call rats and you divide it into distinct points of areas of concern because if you have your electronics here watery stuff here you have your mechanical stuff here if you make your product from the get-go all these food things all sandwiched onto the same prototype when one thing goes wrong you're probably get what's called spooky action so you won't know what went wrong well it doesn't work anymore where four nights so that's why they call rafts where you try to separate the things as much as possible from each other so that was one thing race it doesn't regular things and then after that you call and that's because all this doesn't mean anything until unless it actually helps home so then testing you have what's called two different types called summative and formative in backwards order but four note is they test that inform where they run and some of it is or forward of is does the product in its final form meet your work product goals which is called verification versus summative which is does your product and users goals which is validation does it meet your goals verification of cost manufacturing build even blah blah doesn't work like blah and then after you if you're sure that operatively can verify that all of your needs are met at some point you have to just show that the end-user can use it by themselves or whatever your particular needs are and then that it is effective for the reasons that were using and that's essentially what policies so to put it into more concrete form when I was working at used to we did a parenting or hemodialysis machine essentially your kidneys fail it takes off the blood cleans it but we were doing that you would go you would plug into the Machine you would go to sleep and then while you were sleeping it would do the cleaning process so is it's not a new technology but it was a technology an old technology a new set which is pretty important because now you have to do some of the testing of the end user so what we did is like this man you think there's this business idea or for this product because right now the problem is the patients have to go to a place like to a special renal dialysis center and there's nurses involved and to sit there would it be great just like so in order to do that definitely understand the trick was called that your research to create what are called design inputs so who's using it figure out why they're using in when they're using it was the context that you're using it and then all these details inform what is here are the underwater you know a lot of are they like you know it does this traveling playing a lot so they're gonna be like yeah think about it - well the seals be good when they're losing pressure you know you have to understand all those things because eventually gives it something of testing to say oh yeah you know you do realize the patience of travel you know they're not the reason you're giving them this machine so you've got to make sure that this machine that you're designing the electronics mechanicals can withstand depressurization and box and that means but that's why it's so important to your research beforehand because if you get all the way down here and then you spent like if you cannot wait at this point you really pissed so these are design inputs and they are the direct these creative you're about verification measurements and as you do primary research then you can create my name is so once we did much research we looked like nurses top the nurses which filled out like patients then you decide you know who's using and how they're using and when they're using or whether using it whether you can then you start then we did the concepts that we just did a bunch of drawings to kind of Excel our customer to it and but that's interesting I think that the last thing I would add is that throughout this process there's prototyping happening through all the way from the beginning that it's not just like we made a prototype here and then it worked or it didn't work it's like if you make prototype here and you test it at the end to make a prototype here here they're here until we refined exactly what is you don't know in order to the idea with rafts and prototypes is to narrow down the variables that you're focusing on to what's essential so if you were if I were doing a prototype for mass that was in concept development stuff and even in the development stage and the concept stage whatever you create a prototype it should be the prototype should be answering a singular question or it should be an amalgamation of many different answers from senior questions so like if I were doing this analysis team basically what it looks like is kind of this boxing thing and it has these doors but essentially what we did is we would break down the devices different pieces and mock up just this door we don't we don't try to make multiple versions for every question we have quite a mess about does this door open it close we just made the part answer to a question yeah because you're trying to separate we're trying to narrow your focus to give a very clear answer to understand it's like it's like making function function as small as possible so you look at it go awesome but if you have a function that's this big that's tentative things we've got one part that works you look awesome that works but then there's all this other as we go wrong that's a horrible way to go so it's the same thing you want to make at least invisible products you want to make a prototype of a answer we won't see another question and then eventually yes when it comes to like testing we created full versions but they were all had this very strong basis yeah so actually four hinges yeah I was that we had some we're going to do some weird or portage so the doors here that way it's but that's just so that's that's a solution to us to a specific problem that was about after using the device find out that that was a problem versus wait here going to be really cool we had you know four wave doors that's awesome why no but like you need to have like a reason for your yes so so then you walk the cats over the Doge they picked up DOS that's where we test and then wow so when it comes to this this so in the map device world what you're doing is you're creating you would create a protocol in order to reduce to remove any sort of bias that you could introduce you but the point is to have documented proof that give to regulator this week doctor to say that went through all these steps and and you made a test based off of all this information whatever project I wouldn't really follow this exact same process because the key thing for me is that this is a process that is developed in order to reduce risk when it comes to things that are saved in critical because you need to have the aside to say to follow the process the process process and one of the main things I do is because the biggest thing with project is that I have to be really concerned about people basically getting confused so that's the biggest thing of test scores to make sure that it's very clear what they're doing and that there's ramification for vision just make sure that that people it ought to be like perfectly happy but they need to be not losing sleep over their critic so your your your goal of this process is the same goal that is to reduce concern is to say that we've gone through this process and we ourselves can be confident that tested through the novel the way I can use all time so that I feel confident you know publishing this thing where it's really hard to predict you know so the natural path is the one major thing so if from the research section I would definitely have basically at least two big takeaways and that comes with the concept and you find it but you need to have a very clear distinction of those grandma whether it's a engineer and then you're also based on that and a context use it and the motivations you have a very clear understanding of what is phenomenal path nominally they always do this eighty percent eighty times any time that's time they'll always put this like this but as long as you can make your safeguards if you know that now the path is then you can create safeguards when they you're often but if you have no idea they're always going to do you're not making a consumer product or making an engineering product for yourself you're creating a product that does everything or has no clear path so that it's the user normally an engineer has to create your own path for what they think is important but a real unusual cause you sing but you know you need to really nail that down otherwise just gonna really always get if you're always gonna get pulled every time ya got a future you're exponentially making your product which you signal path for exchange is that 90% of users eventually the money is that the idea of that you know kind of follow so that's like this that's I think there's a certain cutoff point where your rationalization should stop you're talking about that and it's up to the point where there was money because it's a divergent pathway because there's a major and tater someone's making money it may not be the customer want but like stop your nominal path there once you've yes for the so really understand is that there's a very distinct difference in exchanges and you can call there's an exchange which is you understand okay [Music] so okay so there's a primary secondary first of all primary always great to do primary because it's something that so definitely research otherwise you're just otherwise you're racing all of your decisions on base all the information that's available to everyone else which means you have - do you wanna do - regardless and it's it's a shady stuff foundation to say that you made your the last six months of work decision based on some one last thing this was told to me very sternly by so when you work these companies you have a dedicated mom because all these estimators might say Johnson Catelyn give a but this is the super stage where device it comes to prototyping or just anything is that any time you say the word just like oh you just have to do this no do not say just any time you say just you are implying that it's super easy and that you can do it so if it's just you just do it so the preneur who learn is about meetings was anybody said that there is a problem pay attention really close before going to the best specific word yeah so but anyways the point of that is if you're saying just you need to prove it that you can do it which means you need to make a prototype yourself
Automatic transcript — names and jargon may be misspelled.