How to know what you're users really want - Chris Bradbury

what's up it's Denver good morning everyone good morning welcome to uh my talk I am Frank bring Kemper I work for oasis.app and I'm gonna be talking about setting users up for the next Bull Run something all of you are obviously very excited about uh a quick disclaimer if you are here because of the news around the oasis.app's multisig please see our Blog the automation will be immutable soon yes that's a short aside uh so yeah I I said it before I'm a foreign I'm a product manager at oasis previously I was with the maker foundation and at Oasis uh we're we're building uh this so always installed app you can check it out we're a team across uh yeah the whole uh world uh about 30 people and uh you can uh yeah you can find who's on our team on our about page uh we have a lot of like uh long-standing D5 experience in our team um so yeah that's that's the Oasis uh but what am I gonna talk about today uh so I'll I'll start with a quick lightning intro uh to the jobs to be done framework uh then I'll talk about how to apply the these jobs to be done framework in defy and how how to therefore set up users for the next Bull Run and then uh how we're applying that within oslab itself so starting with this jobs to be done framework if you're you don't have any idea what this is that doesn't that that's okay because I will uh I will make it very simple wait yes okay so what are jobs to be done so a job is just shorthand for what an individual individual uh really seeks to accomplish in a given situation that sounds quite obvious maybe but um if if you uh if you look at it from an example it's it's uh it works the best so there was this construction company uh a couple of years ago and they were making a construction for the elderly specifically like 70 plus people who were looking to to live somewhere in Detroit uh in a in a little a bit of a smaller um yeah smaller house and they were doing everything that they can to listen to their their users so so the elderly uh to hear what they want so they wanted for example uh out of the focus groups they heard that the users wanted um that the floors didn't have any any bumps and and stuff like that so that they could roam around in a wheelchair if if that's needed um but uh that that didn't help them increase their sales so how uh it didn't matter how much they listened to their their users to um yeah ask them what they wanted nothing helped and then they started thinking a little bit differently um about well it's not about what we built it's about like the job that the our user is trying to achieve and what is this job in the case of like a building construction for the elderly uh it's not that uh that you have just the house it is that you move your life uh from like a big yeah big Countryside aside home uh to a smaller smaller place area so so what uh did this company do they made sure that the moving was arranged they made sure that um that if you had extra furniture that wouldn't fit your new house that that would get sold for you um they would make sure that the financials were easy to understand for for the elderly so it's it's thinking about much further than just uh what should we build uh it's it's about uh like making sure that you're building um for something that a user really wants so the questions you should ask yourself if you're uh using the jobs to be done framework is what experiences will help customers make the progress they're seeking in a given circumstance that's the first one and what obstacles must be removed I think a great example of this one is uh with Uber um Uber they they like introduced that you like uh obviously that getting a uh from one place to another is now easier than ever um and they completely like remove the need to hassle for the the money after afterwards uh completely integrate that like that that was a very big obstacle for uh taxi users and now everyone uses Uber because it's so easy uh and the third question is what are the social and emotional and functional dimensions of the job and uh what you need to think about here is uh for example in the case of the construction company um like moving out is is a huge deal so uh you need to make yeah reduce the anxiety levels of your users and the same holds for defy uh like if uh if you're doing very scary huge transactions then maybe you want uh your users want the ability to simulate those transactions uh to make sure that it's really according to their need um or there might be other ways how they would like to have their anxiety alleviated so how can we apply these jobs to be done framework in in D5 well for example with oasis.app we started as the front end for the maker protocol but being affronted to a maker protocol doesn't say anything about what you do to a user like it's it's really just using the lingo of the protocol and and putting that in front of your user no user no new user will understand that only the real core users will understand what you're doing so uh we're not anymore the front end for the maker protocol we are for example this is one of the jobs that we try to optimize for we we try to help the user optimize their position and protect them from the worry of losses so um that that reframing of um like of what you do uh helps Focus your user experience around this this job to be done of the user um so answering some questions the questions that I posed earlier so for example what experiences will help customers uh make progress they're seeking in a given circumstance well for example in D5 they need to you need to show insights instead of data you don't need to just block the the protocol data to the user because again no user will understand it you need to make the user help the user um yeah give them the insights that they need based on the the protocol data so for example showing the profit and loss instead of the collateral on debt uh because yeah in some cases what what does your depth really matter um in a leveraged position for example uh if you only care about the the profit and loss that you're making what what obstacles must be removed well one one thing uh I think is a really good example of uh like a job to be done style um um like Improvement is a uni swaps permit too uh and what what uni swaps permit 2 is doing is trying to abstract away the need for approvals uh or at least abstracting the need to approve every single token in every single transaction that you're doing because that's really really annoying obviously and then what are the social emotional and fictional dimensions of the job um when a user has opened a position for example that that that can have been very terrifying uh you you don't just want to say say transaction completed like that that no user will will be happy when they see that uh that they're like okay transaction uh completed but did it work did it do what I wanted to do so you can say something like hooray you opened your position that's so awesome something like that it obviously the tone needs to be tailored to your users as well um but yeah like this is uh this is how how you can think about it so what are their the product roadmap consequences of this job to be done style framework for example when you're trying to apply it uh to um set the users up for the next Bull Run well first of all try to abstract away protocols and lingo as much as possible so like why does a user even need to know that you're using the maker protocol if you're using email uh do you know that you're using SMTP I think maybe in this room even like uh 20 know that you're using SMTP uh but like for those who are unaware you're using that but you don't care because you just want to send an email that's it yeah so also less focus on features more on use cases I I will come back to this in uh in in one minute so don't just uh if a feature if users start asking for for things uh don't just blatantly build what they ask for but try to understand the job that they're trying to achieve with that feature that they're that they're asking for because maybe you have a much better idea of what to build than than the user also kill features that don't contribute to the job to be done so if you have have features that are uh uh yeah for whatever reason not um yeah not contributing to optimizing profits and protecting from losses and that's your identified job then you should definitely kill that feature so what is oasis.ap and how are we applying this uh this jobs to be done framework well our mission is to be the most trusted place to deploy your capital in D5 and we do that with uh two main jobs the one is the one I said before so help me optimize my profits while protecting me from losses and the other one is help me earn a predictable yield on the assets that I own um and and these two jobs are what we focus on in our products uh so for example we have uh the the multiply product um and you can see that like we we also still need to abstract away some lingo um but uh the the idea of multiply is that it's leverage like trading uh whilst like the the maker protocol itself and the Alpha Protocol itself they don't uh yeah they don't allow for leverage uh or well they allow for leverage but not not on their front ends so we've built this leverage uh like trading product on top of the maker and Ava protocol we built stop loss so if you open a position uh you can immediately set up a stop loss trigger at a price that you that you like and uh by this we are the biggest um like automated stop-loss protocol in D5 with over 200 million being protected today uh using stop loss uh we also have uh Oasis Boro uh that's to to get liquidity uh you can also set up a stop loss there um and you can borrow for example against wbtc at a rates of 0.

75 um and then thirdly uh we have always earn uh where you can get get yields on uh on your assets um and we this is like the the most the the product where we try to abstract away the protocol the the most it's still not not completely there because we we also want to help users understand where their Capital actually is instead of just putting their Capital somewhere um so this is like a fully self-custody uh position what you can do here for example in in this case is you can get up to 10 times exposure on reptek eth um using using other so in one transaction uh you deposit eth and you choose the multiple that you want to get so for example you can get a if you want 5x multiple on your website Keys you can get that uh yeah so so that's uh really briefly what's how you can apply the jobs to be done framework and by applying this you will eventually set up users for the next Bull Run so uh I think that's it thank you all for listening if there are any questions in the room feel free uh to ask me and if not you can catch us at our booth we have our booth uh yeah over there any questions yes the before offering a risk analysis in the interface a risk analysis of the interface itself yeah uh yeah we currently don't offer simulations uh well we we offer like assimilations in terms of what um uh like how your position will look like but we don't yet simulate the exact transaction so so the transaction gets um uh like we we estimate the guess and thereby we show if it will succeed or fill um but we're uh we're also going to look into uh yeah making it possible that you can actually see where your assets are going in every step cool I think that's it so thank you very much foreign thank you