Okay, we're gonna do a do over in here, so whatever I told you a while ago, I'm gonna say it again, but this time with this one over here. So that's my Twitter account over here. I'm really looking forward to the conversation that we're gonna have. Okay? So we're ready? Alright, perfect. Okay, let's do take two here. Hi everybody! How's everybody doing so far? Good, good. It's been a long day, but I hope that our conversation for today will really be, you know, instructive to you and to your projects. My name is Jeb Rosario. I am a user experience specialist here in Toronto. And as you've heard in my mini-spiel a while ago, today we're gonna be talking about design discovery, which is really that first mile in the design process. And we have already gone through some really great sessions on how to operationalize design discovery and user research. And today I'm just gonna be showing you that framework, that founding framework, that hopefully will help you get really acting upon discovering the project context, the problem to solve, and most importantly, aligning it to what your users and your business needs with respect to the project that you're building. Sounds good? Alright. So you've heard this already, but I'm gonna say it again because, you know, I'm too much of a creature of habit. The first few days of pretty much any new project is typically exciting. The client is here, the executives are excited, the team has been assembled and we are just ready to take this ship on the road. But then somehow, somewhere a UX designer pipes up probably at the back of the room and says, we should do UX research. We really need to discover the right problem to solve so that we can build the best digital product or service for our client and their users. So that's supposed to be a good thing, right? Absolutely aligning everything, making all the ducks in a row in one line. That's supposed to be a good thing, building everything according to spec, according to plan and most importantly, according to what your users needs, right? It's supposed to be a good thing. So then how are you gonna be explaining or how do you start to explain the confusion some teams have when it comes to doing project discovery or UX research or worse, the resistance that some teams have when it comes to this process. Today, we are going to talk about good design discovery by way of effective UX research. My intention is to provide you with this starter framework to really get this process on the road so that you can build digital products that people love. So here's our agenda for today. Here's our agenda for today. I'm gonna begin with a little intro on what design discovery is, what's its intention really be. And then we're gonna go through the design discovery jetpack, which is really this collection of methodologies that you could use, mix and match in order to really build that targeted discovery process. And then we're gonna be finishing with some special concerns and questions in design discovery and then we're gonna be wrapping up from there. Does it sound like a plan? All right. So design discovery is that first mile in the design process. This is where we try to understand the design problem at hand in order to table a strong and solid solution. It is composed typically that design process of a double diamond. It's typically conceived as a double diamond where on the left side you've got product definition and on the right side you've got product execution. And there are some things that we do within the process to really inform both the definition and the execution phases. All to make sure that we are really building the best thing for our users and that design discovery happens between initial insight and the plan. So how many of you are familiar with this model, the double diamond model of design? Raise your hands. So this is a model from the, final mistake is from the British Design Council, I believe. I may be getting the facts wrong but it's definitely from the UK. And the intention of that double diamond is to really just provide a map of the things that happen within a typical design process such as you begin with that initial insight like I have a problem that I want solved or I have a big idea and how am I going to be following through that from a very strategic standpoint as in the first diamond. And then once you've come up with a plan you are now going to be moving on to the execution phase which is really in Drupal parlance, it's really where development kicks in. So how many among you here can really say that they are user experience practitioners? Raise your hands. So I'd like to have a show of hands. So could you just give me a sense of who and what you're working on in your respective companies? Any takers? Yup, front end design. Anybody else? So in summary, the point of this double diamond is to provide that initial map towards the process and we just really want a zero in on that first diamond in the process because that's really where all the design discovery, all the planning, all the user research, that's really where it all happens. And I'm going to go through those methodologies in a short while but have a look at that first diamond and all the activities that go on in there such as understanding the market, customer empathy, product strategy, ideation, etc. The goal of product definition is to make that plan really concrete. You want it to make it very solid so that you know what to do, the moment you try to bring it from idea all the way to execution. Okay? So that's the double diamond in a nutshell and let's now move on to the second phase in this presentation which is how do we really conduct this effective discovery phase? When it comes to really doing this discovery phase what usually comes to my mind is okay, we're now on some kind of a fact finding mission hence that inspector Closol thing at the beginning of my presentation and it's really all about understanding what problem you have at this point and how you're going to be setting the cycle in motion to really understand the challenge that you've got in a very targeted way. So by using the term jet pack in the design discovery jet pack what I'm really referring to here is the right set of UX research methods to get discovery done. And when I say the right set, I'm not just simply referring to the appropriate methodologies but also the right scale of methods because one of the biggest temptations for some teams at least is that your stockpiling way too much on UX research methods such that it starts becoming a little bit too bulky, there's too much to process, there's too much data that has to be dealt with but at least when you're trying to be a little bit more lean and trying to be a little bit more actionable there's probably something to be said about keeping it lean at the beginning and then when you find that you really want to scale up the understanding of the problem at hand, for example if you discover something surprising about your customers or your business halfway down the road he would be able to course correct and actually follow through on those surprising insights. So the most important thing when it comes to really understanding any kind of process that you will be reading whether it is through someone like Don Norman or Jared Spool or some guy or girl on Medium.com is that the process that they tend to advocate worked for them and the same disclaimer is also applying here such that the process that you're going to see worked for me in the sense that this is really a reflection of the patterns the methodological patterns that I have had throughout my time as a UX practitioner but in order for you to really get the biggest bang for your design bug for your strategy bug, you want to make sure that the methods that you see in here you're thinking about them and you're trying to tailor fit them according to your process that's the best way to make sure that you're ensuring the long term success of the product or service that you're building and that's exactly what we're going to be doing within the next few slides. So far so good? Are we going on a pretty good pace, not too fast, not too slow, just right? Amazing. So usually I find that there are three big ticket stages when it comes to doing project discovery. There's client side research where you try to understand everything there is to know about your business, about your client and then you move on to user research which is really now all about okay, we now know what the business needs we now know what they really wanted to achieve with this new website project that they're trying to do, well who are they really deciding for? So this is where user research is really going to be of biggest help this is where we go then to get out of the building to really understand who is it that we're deciding for and then once you've done all those processes the first step and the second step we are now going to be taking everything that we know and start presenting it to our clients' stakeholders and say this is what we've learned, this is how we can start solving the problem through synthesis whether it is internal synthesis or collaborative synthesis with your team. So that's a 20,000 feet point of view of doing design discovery and I'm now going to begin with that first big ticket phase called client side research. Client side research as we've already hinted a while ago is really all about understanding what your clients or your business really absolutely needs. We do it because we want to probe your project's business context so we know what to optimize for for example or design with this new product or service offering and usually I find that with websites especially websites for e-commerce or something the typical objective is okay well we want to be able to increase sales to optimize conversion etc etc those kinds of business goals are what we try to get a good handle on as early as possible during this client side research thing and there are some activities that we do in order to really get that thing done. So before I continue is everybody familiar with the list of activities that I have over here? Are you more or less familiar with these methodologies? Is there anything that you want me to elaborate a little bit more in detail? It's more about me being mindful of time that's why or should I talk through everything? Who has a preference? Talk through everything, raise your hand. Selective, raise your hands. Okay. Let's go for both. How many of you want to know about stakeholder interviews? Let's just go through everything. Stakeholder interviews, this is really about okay this is the first meeting with your client. This is the first interaction that you've got with them and therefore okay what do they really stand for? What is their brand all about? What is their business? What do they really want to achieve as a result of engaging with you as a vendor or as a service provider? And then as soon as you have that good first first interaction with them you build some more relationships with them and try to understand what their business is all about to which then you move into competitive analysis which is now about understanding okay so this is this business over here there's probably some other related businesses that they are competing with that they're also in the ecosystem with so for example in the case of Google there's gotta be another company that produces browsers so Google, Mozilla and the rest can definitely name them and by doing competitive analysis you're really essentially trying to find the good, the bad, the ugly and many other stuff that would help really inform what are the things that really work for them what are the things that cannot work what are the things that we can take away from etc etc so that's competitive analysis and then heuristic evaluation is really now this more structured process in which there are some usual usability standards that we want to take into consideration is the product that we have really up to par at least during that initial scan in the usability standards and then you also do primary and secondary research which is trying to understand the people and also are there any kinds of literature available what was the press that this company has had before and then you also dig in through analytics just to really get a good feel of what their website traffic is especially in the case of websites content audits which is really that list of all the content pieces that the company has and then finally metrics which will come organically through the conversations that you will have with your clients because they will tell you okay we're going through this project because we want to optimize for X we want to increase Y etc etc so far so good secondly as soon as you've done all that business side research you now go on through user research which is now really about the people that you are designing for and the selection of activities that you're seeing over here this is really just a subsection of a very very very rich field called user research and I'm just really going to show you over here the big ticket items that tend to happen in my practice at least when I help clients build websites so for example you've got personas which is really that composite picture of your users and I've put a very important qualifier there which is scenario driven personas because at least in my view the big problem with some personas is that they tend to be just a laundry list of demographics and bullet points rather what we want to do is to drive that empathy piece and really answer within that persona document well okay Janet what does Janet need from us what is that relationship that we want to build with her what is the thing that she needs from us as a company and how can we as a service providing company can address whatever it is that she really wants solved so it is that situational look at the people that you're designing for that really unlocks the potential of personas beyond just simply descriptors of this is Janet she is 43 years old she lives in Richmond Hill or something because you don't really get anything beyond that kind of thing especially if you're trying to understand what is going on with her life that would want her to switch to our product or service etc usability testing is meant to really just tease out the initial challenges with the product or the service that you've got so usually usability testing tends to happen across the entire project life cycle on one hand you can do it as early as possible just to benchmark the challenges that you've got what you have to work around with etc etc and also you try to do usability testing throughout the development process just to really level set and benchmark okay the issues that we have set before we have identified before okay they're starting to get solved right now we're now getting really good clarity and good stuff in here so usability testing is meant to really just benchmark the thing and also assess how it's working through and through and then card sorting and tree testing those are information architecture techniques that you use to really understand for example what will that navigation structure really be and usually we're pretty much happy campers when we say home about this cool service offering blog, contact us that's a pretty simple IA structure but as you and I know especially if we're working with really big ticket clients we know that it's definitely go beyond five major categories so what will that categorization scheme really look like and that's exactly the job of card sorting entry testing job stories is from Clayton Christensen where it's really all about what is the job that your users are trying to get done and we want to pay attention to that so that we can really design the product or the service according to that unique pain point many other research methodologies is needed and finally once you've gotten all those information all those details both from your users and from your business you now want to start presenting what you know and get the process of solving the design problem really started so in my world it typically happens like we now say to my clients here's what we've learned about you the client and we want you to know that these are the things that matter to them they really appreciate for example the recipe pages that you put in this magazine website they really love it if you do all these contests et cetera et cetera so we try to tell them that the good and the bad we don't really say bad but we try to tell them what are the things that we can really improve on and then once your client has really gotten a good feel for it you can now start saying okay we can now start really thinking about what's the technical architecture what might be the features that we really want this website or this mobile app to really have in the future and then how can we really operationalize in that how can we really do good on that and that's the job of your design documentation whether it is a user flow document or wire frames or even creating an interactive prototype either through envision or action or something and then also some research presentations just to really say these are the things that we've known about our users and this is exactly what we can do to solve their foremost challenges now every project is different there are some extra considerations that you want to pay attention to especially if you're now going content presentation and this is especially the case for websites that tend to be a little bit more about the functionality where you have to do something in order to really get the biggest bang for your buck like for example if you're a marketing company and you really want to drive lots more lead generation and a lot of conversion for your products and services then that would really mean putting a little bit more effort on the discovery process the methods that you really want to use so I've given you some more activities that you could consider depending on the type of depending on the type of design practice if you wish that you're trying to really understand for example if it's information architecture if you really want to understand the structure of the site do more card sorting and tree testing if you really need more user research you've gotten some more methods there content strategy some initial discovery methods that could really work for you and also visual design there's also some mood boards really trying to understand what is the visual style that we want to go for what's the feel or the color schemes the fonts that we want to use and what I normally recommend is that it's very tempting to have just one user experience practitioner whenever possible if it's possible to spread competencies out such as you've got a dedicated visual designer and then you've got that user experience designer slash information architect or if you can even invest in a content strategist that would be fantastic because at least the load is shared among the team but the point of having these add-on activities really just to say actually go a little bit more beyond the standard selection of user research methods because our problem is a little bit more specific and therefore it may warrant extra discovery a little bit more methods just to really get to the problem at hand sounds good? can someone remind me of the time? 10 after 4 alright perfect so we're kind of on track which is a surprise a little bit outside of schedule but we're now here on the third and the most important part which is really the thing that I'm excited for in an ideal world design discovery is going to be going smoothly it's not going to be like full of drama or something it's just going to go as straight forward as possible but as we've seen a while ago design discovery really depends the success of design discovery that is really depends on what would really be what would really be the right methodologies to attack the problem that you've got and therefore we want to account for those specific instances within organizations within clients so that we could make sure that design discovery really happens in the most productive way possible our goal really is to make that process your own and so let's begin with that first and really big ticket consideration called relationship between UX and Agile this is a mine field let's be clear this is a mine field in an ideal world Agile and UX are going to play very well in an ideal world you would really have UX research and design really fit into that sprint schedule and there will be no issues that sprint schedule that your product manager has worked so hard for it's just going to go smoothly and that and everybody's just going to sing a happy tune because everything's just going to going as planned but the problem however is that in a pure strong capital A Agile process the challenge is that UX research and design becomes shoehorned into the process it gets forcibly fit in there sacrificing the deep contextual thought that's really needed to do contextual user centric user centric design and I've got an example for you to really just make that make that a little bit more more tangible so YAMP Digital an award winning agency down in Australia kudos to them they were able to make this UX and Agile thing work as you can see over here if you look at feature A that blue dot over there where the start blurb is you can see it prototype development test launch sprint one sprint two sprint three sprint four it was just cascading pretty nice they managed to make this thing work now let's say for example that we are going to be turning down the lights on this presentation have you noticed why is research such a forlorn and lonely box over there at sprint one okay so lonely okay so lonely what if by sprint three you discover something new what if you discover that there's there's got to be a change in direction somewhere that you really need to account for and so is it the end of the world then okay I mean I'm pretty sure that it's not but this is one of those conversations that ux designers and add in and pure agilistas are having like how do we really ensure that these kinds of that these kinds of situations can be accounted for especially if you discover something new and surprising for your for your for your users and this is exactly the core of a page lobheimer of the nilson normal group was saying that a pure strong agile process forces forces designers to really be a little bit out of their element at the expense consistent user centric thinking and designing however we also need to make sure that there is a way for us to deal with it and if you want to make sure that ux and agile can really play in that good sandbox very very well we got to ensure that some compromises can be made as well so some companies were able to do this by doing this thing called sprint zero where you do a lot of that upfront research strategy and initial designing even before the formal sprint one two three four and five happens you're really dealing with the hard stuff out of the way so that you can just devote that sprint cycle on the on the features the user stories et cetera et cetera and if you go on to bit.ly slash ux jetpack I have given you some resources in there about two companies here in Toronto in the form of sprint zero one of them one of them has really been very very big on lean and agile and their own sprint zero process their own discovery process really leads towards user stories which I think was a very interesting innovation so definitely have a look at that and so sprint zero is really just meant to get that hard stuff out of the way and I hope it's something that you would be able to consider whenever you have to whenever you have to be in an agile environment and have to just get this user center design thing on the road so that's the first question and now let's now move on to the second which is now about the role of data in product design so just a little gut check are we going too fast too slow just right or anything pretty good okay I'm kind of racing against Simon here because I do want to make sure that we still have time for some interaction with some things that we do need to look into here but we're gonna let's move along over here when we talk about data when we talk about data we're largely referring to all client side information that is used to understand your business's context so for example we're talking about analytics customer logs CRM info service calls among many other things that your client has in terms of hard numbers et cetera et cetera and I want to show you a diagram that I really really liked these are some data sources and UX research methods at Canada Post full disclosure I don't work there I tried but no dies I don't know if someone from Canada Post is here but anyway as you can see over here there are two really striking things in this chart the blue the blue boxes refer to largely qualitative methods whereas the orange boxes are more quantitative and if you really look at the types of data sources and methods that they have you'd probably notice that they're more interested in evaluating assessing the performance of their products and services rather than understanding the problem at hand so the character of the methods and the sources over here tends to be more evaluative than generative now as a quick aside just to make sure that our jargon and our definitions are really up to par when we talk about generative we're really talking about understanding the problem space whereas evaluative we're trying to prove or disprove hypotheses we're measuring impact et cetera and typically evaluative research happens when there's already something out there on the road and then generative is when okay we're trying to redesign something or we're trying to build something from scratch from a web perspective generative research tends to be the flavor of fresh builds or redesigns whereas if that thing is live already it now skews towards evaluative okay this is important because this will really tell you where Canada Post is already comes to their design processes they've recently redesigned their website and their mobile apps so it really makes sense that they're now trying to understand okay, are we really achieving our targets et cetera et cetera contrast that with my own UX practice as an in-house practitioner or as a as a consulting partner to some companies where sure I do have quantitative methods for sure I definitely look at analytics I look at my competitors I look at service logs but then when you look at the blue the blue boxes here you'll find that the qualitative methods in here are really more about okay who are the people that I'm really designing for it's really more about that exploring the problem space which is really emblematic of my own practice which is because I'm helping clients really build something from the ground up or redesign something my own research methods necessarily skew towards the generative side but if I'm now really taking care of a new website that's been launched out there it does make sense that I would have to say okay, I really need to make sure that the bounce rate is not over through the roof or else if my bounce rate is 80% I should get fired okay or something I mean whatever but you know the drill okay so neither approach generative or evaluative neither of them is right or wrong okay but it points to the need to make sure that you are really contextualizing the research methods and data sources that you have according to the problem that you're trying to solve according to the situation at hand and the best way to really ensure that this is happening is to have a decent selection of quantitative and qualitative methods with you mixed methods research as they would say to make sure that you've got a decent picture of the issue at hand of the problem that you're trying to solve so that's number two the role of data in product design okay and now I want to go through the third which is the role of accessibility in product design I'm going to make this simple okay I'm going to make this simple as designers developers strategists researchers creative technologists whatever you call yourself we have a big role in ensuring that the products and services that we build are going to be are not going to be posing as a barrier to the people who use them it's all part and parcel of being human of being a good human that is and so our role is to make sure that the people who are dealing with our products and services are not feeling left out because I've noticed especially when I was reading when I was reading a Toronto Life article on someone who was talking about her experience as a blind person in navigating the city of Toronto she was really saying that the mere fact that someone seemed to have designed something that she can use felt like she was whole again so notice what she just said over there because majority of the products and services that were built in this world were thought and conceived with an able-bodied person in mind now that she has this challenge she kind of felt left out and we've got a very special opportunity to make sure this doesn't become the case for someone like her so here's some quick design wins that we can really look into to make sure that we are building the right and the most accessible products and services and I'm just really going to zero in on that last point over here because this is where we designers tend to tend to really get very much carried away so here's a footer okay, here's a footer and at first glance there's nothing really like so bad about it I would actually say that with the exception of one thing the colors are pretty much on brand on style okay but then the question is how do you explain that about elephant right atvertize menu and so what I did was I ran it by a color contrast checker and it did say that it failed and I should mention that one of the guilty things about us designers is that we sometimes prioritize aesthetics over functionality which is this and so this is like this priority reminder for me and for my other colleagues but no just because it really looks pretty just because you can put it as a dribble shot okay doesn't necessarily mean that you can actually get that thing on the road we still need to make sure that it's according to standards one of which is this color contrast thing and the thing is we can actually solve this we can actually make sure that this doesn't become an issue and that we can we can make this better whenever it shows up so that's accessibility and now we go on to the fourth and final pointing here which is that very very common thing which is come on Jim research again you're taking forever to do this thing why cannot you be faster so there's a common there's a common concern I've noticed whenever I do my work that research is this is this bottleneck it slows everything down people cannot move forward because you're not done with your research or anything and to me there are really two sides to this issue you've got a timeline problem which for sure I concede some of us designers and researchers can just get so carried away with our understanding people that we just stockpile on those methods but then the bigger problem for me at least is the relevance problem which to me is the root of all the issues that research has in terms of really entrenching it in the product development process here's the truth there's really this huge chasm between good UX research and organizational strategy and I was really reminded of this the other week when I was talking to I was talking to a director of service design and she was really really hammering on the on the research methods that that she had in her company and sure she was still able to talk about how this is relevant to her to her to her boss but I also thought about how my other colleagues approached UX research and they just seemed to say oh we did contextual inquiry and then we did ethnography then we did more user interviews and stuff so it suddenly becomes this laundry list of all research methods and discovery techniques but then the question then that we should be asking or like I should be asking myself this well what's in it for the company so what if your personas were really the most dribble worthy thing ever what if it was really the most well-designed thing what good is your statistically significant A-B test if we cannot really demonstrate that hard line that connection between the insights we've generated and how it's going to benefit the company and so one way that I've tried to mitigate that challenge is to make sure that I always generate the oh moment when I share my UX research findings and let me just share with you a story of how this actually worked a couple of years ago I was redesigning the website of the Canadian Jewish news and at that time I was still in the throes of the so-called persona placement format which is really just that laundry list of demographics and characteristics but the moment my team started talking about UX research in terms of well you know Janet really appreciates the recipes that you've got and they looked to the CJN to be this particular this particular thing the moment we tried to talk about our personas in terms of their relationship with the company in terms of their emotional connection and how important the CJN is to them the moment we were able to establish that relationship the more our client was saying oh tell me more about it oh that is how we want our editorial strategy to be really going moving forward we want to ensure that whatever we write is actually something that would be resonating with the people that we are writing for so that kind of constant connection is what we really want to drive when it comes to doing effective UX research because really Erica Hall in a very recent but very very well argued article called thinking in triplicate said in a very only as human centered as the business model allows what this means is everything that we do as designers and developers really happens within the purview of a business infrastructure we wouldn't be able to do this job if for example you know we wouldn't be able to do this job without that client you know paying us I mean it's funny I do know of a UX researcher that says that all my behavioral as a big company that she works for I mean back role may sound like a very facetious term but the truth of the matter is that only confirms the relationship that we have as workers service workers digital workers with the companies that we are working for so the challenge then is not just to become user defenders alone we definitely need to make sure that we are representing the interests of our users but we also need to make sure that in the process we are not neglecting what our clients need so it's that move from human center design to value center design as Erika Hall says that the biggest bank for design and research is but can really be generated and that I think is a very very worthwhile thing to work for so far so good so to cap this conversation we've talked about design discovery a very very quick overview of it and it is really this first smile at where we tried to understand the customer and the business needs in order to build the right thing and consistent with the term jet pack we are not trying to stockpile way too much and make that that set of techniques too heavy and too bulky for us but we want to make sure that we start with something that we can work with and then scale it up according to what our project needs if you only have to remember one thing I hope it's this good design is good problem solving and considering that we are now in a day and age where design where products and services are increasingly being fought at the experience level it does make sense to make sure that UX research and design can be bought in and recruited to our camp think of this as you go go for work on Monday think of all the things that you will learn today and to borrow at Drupal North and I'm really looking forward to the conversation that we're going to have make sure that you represent your users and your business and go out there and build digital products that people love thank you it's 4.30 so I don't know if I have time for questions but let's take a couple let's take a couple okay if any questions for any questions for me I'm sure there are I mean I was rapid firing over this I don't know if my comprehension is really spot on but don't make me feel lonely here going once going twice going fries this is not an option team non? really? yes Susanna thank you Susanna that means a lot coming from the dear leader of evolving web thank you Susanna a couple of years ago I was the user experience team of one the sole UX practitioner at a not-for-profit organization they were redesigning their website it was a move from Drupal 6 to Drupal 7 so they were looking to me at that time to really just okay Jim we really need to make sure that this information architecture for this particular toolkit that we have can be a little bit leaner so what I did there was to really do a lot of heuristic evaluation and a lot of user testing and was actually funny in here was that I was still a very new practitioner at that day at that time and I was saying ah I am the UX person in here I have all the knowledge in the world of course younger heuristic and everything I said I initially said oh we should do we should do advanced search we should do advanced search I was really coming up with all these these great mock-ups about how advanced search can be deployed but then when I started doing user testing when I started really understanding what are what the users of that particular not-for-profit service is that's when we started that's when I started describing yeah advanced search is not going to work it's all about making sure that the labels are clear that there is a much leaner information structure to use and that it's not onerous to use it can scale across devices so that kind of shift from I am the genius designer all the way to okay I actually have to respond to what my user tests has been showing that is one example of how discovery processes can really can really help you redirect your project direction and also your design decisions and I'm very happy to tell you that we were able to launch that I mean they already redesigned their website yet again but that following through on user insights and being able to respond to them and be able to tell my clients this is what your customers need and for them to really trust me with those recommendations I think that's a really good thing and it speaks to what really could happen if you have that close collaboration between yourself as a designer as a developer as a researcher and the client that you're serving cool alright thank you so much I've heard you had a few issues earlier I did you're gonna work something out and so I mean luckily luckily I overrehears this thing so I kind of know what to say there you go okay I'm just gonna pop in this okay so just so you guys know this is the end of the day there's no big announcements or anything other than we hope to see you guys come back tomorrow looking forward to it another big day but it doesn't start until 10 am so you get to sleep in and maybe be hung over after our after party which is again at rec room make sure you guys get your gift certificates and let's head there ASAP because it's rush hour on a Friday it's gonna be a while thanks guys have a good one


Not a problem. Open UV editor and make another window for the shader. Click new, name it normal map, click on the simple object, click new, shift A, S, image texture, click on the picture and select the normal map you've just created. Drag color into normal, press shift A, S, normal map and drag it over to existing connection. Left click, make sure that's the only one selected. Go to cycles, bake and change it from combined to normal. Check selected to active and set ray distance to something like 0.5. Click the detailed object, then shift click the simple object, press bake, you're done. The detailed object should be sculpted or copied from the simple object. Anyway, I hope that helps. Thank you so much for watching. If you enjoyed this video, please don't forget to like and subscribe. Hope you have a fantastic day and I'll see you around.