 Okay Hello everyone We have encountered some issues, but as Designers and researchers we are accustomed to this basically we have iterated So I Am Sasha ten asset good to see so many new faces I am a product designer and the researcher I am one of the co-founders of the web three UX user research panels And I am leading the UX design and UX research for the threshold network Which was formerly known as keep network and new cipher I am also part of the team who is building tbtc Which is the first fully decentralized bitcoin to ethereum bridge I like to say about my job that is to transform extremely complex products into palatable bits I've been designing for around 10 years now and I've been in the ethereum space since 2018 My goal is to make explorative research part of All of the web three products okay, so Today's talk is about a new collaboration flow between designers developers and business developers It's a critique brought to the way things are currently handled. We'll try to go together Over what could be the issues of the present building process How they affect the product lifecycle and we will explore how might we collaborate better from the start and how to be more inclusive Today's talk is an open conversation. Hopefully this subject will set the wheels in motion And I would be happy to hear any ideas suggestions on how we better The proposed approach So the future of web three UX Why do we even talk about this? Is there an issue? So anecdotally 70% of the user experience of a web three protocol or that is dictated by the smart contract Smart contracts are usually not upgradeable. So the experience should be flawless from the start If you're not familiar with how this could be translated to then Um The user experience in web three is made of the entire user flow and user journey The number of transactions until the goal is reached Which in web two e-commerce means the number of clicks The gas spent by the users And the displayed information so What is the current ux situation in web three? The products are extremely complex and difficult and the development teams are more focused on solving the problems Which are localized at the smart contract Um, and there are many levels in between the smart contract and the user. So this is what's happening The development team meets decides how to uh, how the protocol or that will work. They write the smart contract Um, and afterwards they send it to the audit. Usually there are multiple audits done in average two to four And after the code has been audited and fixed it fixed the development team decides to bring the design to the table So basically design is brought when all the user journeys all the user interactions All of the interaction experience has been set in stone and there is no way to go back at this point So there is a tendency for technology to lead the product versus the other way around this means that There is a high likelihood of over-engineering and unfortunately ux becomes the a by-product Tech people do not have the priority to put themselves in the user's shoes Which is not really an issue unless the entire experience depends on them So this is the current flow and let's check. What are the downsides of this flow? So The teams are siloed, which means there is zero collaboration any findings from research design research That require redesigning the experience is impossible because the smart contract has been audited and fixed so there is no turning back Design can improve the experience only by adding explanations and ux writing gimmicks um Design unfortunately can only cosmetize the product. It cannot fundamentally improve the experience product building time is longer because everything is cascading And onboarding and retention of new web 3 users is low Due to the unfortunate and clunky experience and steep learning curve so We learned why most of the ux resides in the smart contract We learned the current situation in the ethereum product building And the issues of the current flow. So how might we improve the state of web 3 ux? So first of all, we all need to be open-minded and flexible to replace our common behaviors This means stepping out of our comfort zones by changing this piton track The deliverable The deliverable is the user facing product not the technical not the smart contract not the back end product So Having a goal a target to get to a desire ideal outcome is a great place to start from So This is not the product This is the product So let's try to find out about a different way of thinking First of all, I would like to start from a process that has been proven to work very well. This is the double diamond process the double diamond which was popularized by the british design council in 2005 um This process is based on a diverge converge process developed by the linguist Bella Bannaty This methodology suggests that a product process should have four phases discovery And definition which together make the explorative and divergent phase And then development and delivery which together make the iterative and convergent phase So explorative design helps us do the right thing Iterative design helps us do the thing right This is my mantra and I think this should become everybody else's mantra So What could be a flow that respects the two important phases in a product development cycle? And it can also respond to the web three environment needs So this is a product flow I am proposing that follows the explorative and iterative phases And which I believe with it would definitely improve a lot the web three product development So what let's break it down So in the explorative divergent phase everyone is brought to the table from the start design development and business A designer will facilitate stakeholder interviews and each team will map out their requirements The user needs technical constraints Business goals, they are all considered and taken into account User journeys are created based on each team's insights and requirements EVM constraints security issues User needs pain points KPIs and business requirements All of these elements are incorporated in a high level user journey map That will mark each step a user needs to take in order to achieve their desired goal The user journeys assumed needs and pain points are probed in explorative research by speaking to real people This is a very impactful moment In the process since we are moving from merely assuming things to actually spending time and observing the people Who will in the end use our products? So in this type of the process We're testing our ideas and this may be the moment in which we might need to pivot We might find out that maybe this is not the way to go so Afterwards all of the unearthed insights and findings will be incorporated into the new user journeys So research has been conducted assumptions have been probed Findings had been incorporated in the into the new user journey And all of the stakeholders have validated them now the interactive phase can start So the new user journey is validated with the users and with the stakeholders now are now becoming the backbone of the project Based on these documents and artifacts the development team and the design team can start working in parallel The design prototype and smart contract writing is a very important step in which the two teams will need to have constant check-ins and will need to accommodate each other's findings. So basically The design team will test the prototype will have some findings They will communicate them to the smart contract developers the smart contract developers We'll incorporate these findings into the smart contract And then they will find solutions. Of course, maybe some technical solutions won't won't be necessarily perfectly Answering to the new needs that have been discovered. So they will also Communicate these new issues and findings to the design team So there needs to be a constant back and forth in between these teams and there needs to be constant collaboration between the design team and the development team so The benefits of the proposed flow Are the following the team is fully integrated and not siloed There is constant collaboration and back and forth between the design team and the development team There are shorter building times and of course more time for research and testing So if this sounds like a good approach, I invite you to adopt the methodology And adapt it to your organization We need to think of this proposal as a work in progress which will be shaped up By our experiences and needs. Let's consider this our explorative phase If you plan to adopt this methodology and implement it in your organization, please let me know what were your struggles Which parts of the process worked and which didn't What did you have to do to adapt it to your own company needs? What were the struggles or Of challenging the status quo. Did you encounter any any resistance? All in all, I would love to hear from your experiences with this process because the goal is to evolve it into an adaptable, adaptable and helpful process to the entire web 3 space So some great news from the threshold network and the tbtc team My team was convinced about the benefits of this new methodology So it was decided to adopt it and implement it into our product development process starting 2023 And this means I will also share with you my experiences of adopting and adopting the process Some thoughts from my colleague Doug who is a great supporter of UX in our organization Um He's talking about this methodology and he says there is no hoping and guessing only principled aligned movement that values the user above all else And some more good news. Um threshold network has open source its entire UX research and past UX studies. Um, you can find Here user research guidelines all of the past studies that I've conducted for keep and threshold network And different helpful artifacts Never forget this. Love your users. Thank you Thank you Sasha amazing presentation. So there's a few minutes left. Maybe somebody has questions Yes, I always have questions. How long would you expect this to take? On average, I understand that's an exploration by nature But do you have any intuition or feeling for how long you would take an exploration versus iteration? So you mean explorative phase what like, okay, so generative user research should take two three weeks at most Which is not a lot and it's very Easy to implement the findings afterwards. So you need to start with this it can take even less than that but the most time that it takes is finding the the Participants that are meeting the user profile that you're trying to to build for Yeah So it doesn't add to the building process. It's actually um It shortens it because you know what to build from the start and you know what people are needing and you know if your ideas are actually viable and I don't know responding to the market need Yeah, I have a question. Thank you Basically on the face of integrating users What's your proposal for test net versus main net? Of inclusion of the users because we realize that when users are on test net and we when we are on this kind of user testing the users as they are not Integrating with real money or real assets their concerns are way Beyond the when they are on main net, but when you are on main net You should have already a functional solution that should work. So what's your take on that? So I think it's best to to Do usability tests on test net? But try to make it as real as possible Like what you're testing will be mirroring your product that you're deploying on main net And the thing is that if you're giving the users test net tokens and everything and they will go to To the entire experience at some point. They will Forget that they are actually testing So you will get Very good insights. You will find what's fear for and scary for them because basically we are designing for fear So I really I'm I'm a big champion of testing on test nets Yeah, okay. Thank you. Yeah Yo, great presentation Is the generative research supposed to align with the spring cycles that a that a product team might have or is It something that goes like again like in parallel and doesn't have to Match up with agile I think it it should be part of the sprint cycle or it can be agnostic of the sprint cycle So you would like start up a come like a regenerative research campaign Even if it's even if it's outside of the cycles of the product. Yeah. Yeah, exactly. I think it should be in parallel Okay, cool. Cool I have a question. Yeah, I want to ask how do you reach out to the correct personas How do you find them? and how many Different personas are you considering to make a research? It's very difficult in my point of view so We don't have a huge pool of participants. So first of all, I think we should Stick to the most important persona that we have And then after you're building your user profile and you know who you want to build for Then I think you should use a screener and also web 3 ux, which is our user research panel It actually started from this need and this hurdle that is very hard to find participants so Yeah screeners and then a pool where these people are and try to Invite them. Can't wait to talk about this more after the conference. Okay, sure Amazing. Thank you so much Sasha. Thank you all You