 So I guess a good start will be looking back at your PowerPoint presentation. There were some feedback from the presentation that perhaps we can start from there. So when I did look through the slide deck, so let me just scroll to maybe I can share screen so that we all looking at the same thing. Let me see share. So this is the slide that I believe most of you have seen from your previous presentation. So looking at this particular slide, we can start from there. So initially when I had a chat with Michelle, we were the one thing that she did point out was more what is the problem that you are trying to solve, which is, I guess we're referring to why people are not coming back after a day of running at least one job. That kind of the conversation that that's how we started you know what what why it occurs what is, is it normal, you know what is what did they do basically. So, while we're talking about that. I was thinking very similar to Galaxy Australia in the beginning. We use language like the user. Right. It's like one person, but it's actually not one person because this user can be different type of user different role. It's just that it could be the same person but doing different tasks as well. So that kind of lead us into adopting this. The Alexia life science data cycle as a framework to give us some understanding and insights of whether you are a person working on at different stage working on different things. So you where it's Galaxy seat within this cycle basically that's what our UX team wanted to know. So, so it's pretty hard when we say what is the problem we're trying to solve we really want to say what problem are we wanting to solve for which users. That will be giving us more, more context in that way. So moving along if I can also said so what about scope and scalability. So, what we found is usually when we have user journey mapping layout which I'm going to share with everyone how it looks like and how it lead into agile practices and also user story. And then from there we need to then prioritize what tasks what is the law hanging fruit, you know what can we do now and what can we do in the future. That's our thing. So that is what we want to, I guess that is what user journey mapping can provide us the scope of you know what we want to do. And then we, yeah, then we talk about the agile method, which is to us is whatever user research data that we get it, it's really allow and helping the team to create user story to then put it in bad log to then implement him. Not just not just the user story makes sense but it's also allowing the team to line up things that when you want to, when you're working on certain component. And if they're all related is good to kind of group them all together and implement them together so one push, then all these little problem would get sorted. And that's really it's something that is useful to have to have a story coming out from the user journey map with this one. So user journey. It can be anybody like I said, it just understanding each person where where they are at what stage and what so to or things that they're the touch point and the different pen points they're experiencing during this entire cycle. And it's very important to understand the persona. So, like I said this one persona could be having could be playing different role at different time. So, but it's still good to have like a person in our mind, when we're thinking of certain function or certain solution we want to design for them, and allowing us to then interview those user that fit that profile, and to get you know more relevant information out from them. So for example, if we said the persona is a PhD student, then you know we will look for all PhD student to interview, but if the post persona is the lecture, or the bioinformatician senior by information for example, then we will interview those people. So it just help us. So usually, when we at Galaxy Australia, when we want to talk about a user story, we have to be very specific in for a senior bioinformatician, I want, you know they want to do this or you know I'm a, I'm a PhD student and I want to do this, so that I can achieve something. So you know so that story tell the developers, as well as designers to understand that you know this is designed for certain people, however saying that we using user journey mapping, we'll be able to tell designing and developing one solution normally can help multiple persona, not just one. So that's the benefit of having them all visible. So that everyone is not going to have assumption or guessing. The next when we're talking about the yep the scope is yep that is correct so we will know I usually like the odd number. Because if we have even number when you come to a point to being 5050 and that will be quite difficult to help us to make a decision so normally if it's an odd numbers. Now in regards to, you know, people say well five users that can represent everyone, but from my experience that will be as you go along and interview more people you will start to see the pattern, you will start to see this actually belongs to the same group of people and then you group them up. So, and also the more user you interviews the more data you need to analyze or take longer time. So, once we interview up to five people, six people you start to see there is pattern emerging, and that will help us to then identify who is who playing what role. And let me see is there anything I need to answer here. Yep, no. Yep community of practice that is correct. Next one we want to talk about the content. Yep, so this is a good one Michelle about. Yes, soos. Normally it is seems to be highly subjective and it's correct. However, it needs to actually apply in context. We are not randomly asking people to randomly doing the sous survey at any point of time, but it's always follow on from after we test with them on certain thing but whether it's a features, whether it's the page, or mock up, we then ask them to do a sous survey. Based on that experience just happened, and they will be scoring based on what they just experienced. So, that means, yes, we are asking the same 10 question every time. But it's in that context so we normally attach those data behind whatever we were testing at the time. And very important this is a very important exercise. I've introduced to bio comments, because previously, they have done quite a bit of, because we have a user engagement team. So they have engaged with users, however, they don't really have a framework or method to collect and store this sort of. I guess it's very high level, but it gives you a very good indication on whether have you done. Well, as it is now, and have you improved or actually you have done that badly this time, you know, so it is very good to, you know, give us this kind of instant feedback. It's just a very quick and dirty way to give you feedback, really. So the next one is, yep, this is the user journey mapping process, we want to understand at each point doesn't matter what role you are. You will have to have a planning stage, like for even for designer ourselves, you know, we got to plan how do I want to start doing this design what do I need what software do I need, you know, that sort of thing who do I need to work with. So all these are planning stage and then collect stuff at the process that sort of thing so this cycle really can apply to a lot of a lot of petitioner can actually apply this method. So likewise, being a life science researcher also fit the bill in that way. So let me have a look at the feedback. So it says sounds like our onsite interview prevent us from only understanding the journey from a single communication channel and will instead show us where the user journey actually start. Yeah, before the user open up galaxy. Yep. That's right. So from the minimum maximum number these underscore what is the mix of remote interview versus onsite interview. I don't really I don't really understand that second point so Michelle if you want to maybe elaborate a little bit about what is the minimum and maximum numbers listed underscore. Sure. So, under the assuming we have five user interviews. What number should be onsite versus remote all of them in general or ideally maybe all of them. It doesn't have to be it can be all of them off site could be all of them face to face could be you know some online and some face to face because doesn't make any different. We use mirror board. In the olden days before before pandemic, we used to use whiteboard and sticky notes and see the user in front in the room with us and just you know put sticky notes on the whiteboard. Today, a lot of things are digital dice and so we just will use mirror but which was the same like a whiteboard. I will share with you how that user journey met look like, and we send the link to the user. We all online, and they can just in in real time typing putting their notes on to the mirror board. I will show you that screen in a minute. So yeah in regards to physical thing yet can be offline online doesn't matter. Yes, so we do have already. We do have a lot of user research. Not sure about website analysis analysis. However, we, I must say we being I joined by a comments last year. So it's a very short timeframe. However, we have achieved a lot with Galaxy Australia we have many at the time. She was the UX designer only working on Galaxy. So she was trying to do more user research and more UX type of work. However, there were missed. I think people easily misunderstood user experience designers actually UI designer. So she ended up doing quite a lot of like you know doing design, but without any evidence supporting you know why are we doing this why why. How do you make decision that this design work is it based on someone's opinion is that based on someone's, you know, subjectively decide. Yeah, I like this design, you know, so on. But since then I joined spend a bit of time educating the team and also the mainly the stakeholder as well as the decision maker in regards to user experience practices. And because we get it right. Everything we do had evidence behind it, and it's not based on my opinion is not based on because I'm a designer so you know I think this look great. It's purely based on how users understand what we're doing what understand the design and is that really helping them to either navigate or finding things that they need to find. That's really is the objective so in regards to aesthetically, we can make the previous website. If people kind of not sure how to navigate visually looks great, then it's actually not functional and it's not functional so therefore, you know that's not what UX is about. Yeah, so in regards to since I have joined, we started having a central location to store all of our user research data, and not only just galaxy but also all the other projects that I'm involved with within bio Commons. And that way, many being the UX designer can also see how the other platform work and at what point even those user actually do use galaxy. So you know it's one of the journey. We try to them landing onto galaxy Australia. So to her, it's really good to have the UX designer overarching seeing the whole thing to have that understanding and insights. And great this outcome measure measurement particularly when using. Okay. So yeah, in terms of the century click tracking. Yeah, do you want to elaborate that point a little bit. Oh yeah. This is just to say that having or seeing some of the data that's stored centrally on the user interviews the user personas that might have been created for galaxy, or just generally speaking I think would be helpful for the different companies to to see and have access to as opposed to necessarily starting from a blank page and doing all you know our user interviews from scratch. Does that make sense. Yes, yes, yes. I think that's a very good point to make as well so yes entry more like some sort to like Google analytic where it tracks what's the users that the activity, the user make within the site. However, you know, like, like we know it's just that is is quantitative and we, we don't know why and, you know, but we have figures. So yeah it is good to married the sort of user research with the quantitative data to give it more insights that's definitely would help. And, okay, so user engagement should be multiple engagement type based on product service doesn't need to be to be and maybe possible to have an existing standard user engagement value in biological science like maybe possible in other fields industries. Yeah, so user engagement should be based on products and products or services. It's the reason being the stand sorry that so it do happen as this exact, sorry, exacting standard user. Okay, yeah user engagement dust do need to be engaging with the same with the right, I guess with the right person or group of people. It's not going to give us good insight or clear indication if we're talking to the wrong people. And that's what lead back to lead back to we need to actually have persona in our mind that would then help us to do the engagement. Um, yeah, okay, suggested engagement type for a galaxy finding a history running a job. However, we running a job shouldn't be considered alone because job may not be may not have run successfully. So should include planning for errors. Yeah, yeah, that's right. So this is this point is a very interesting one but let me have a look at the feedback how many user did something in a month. What portion of user ran a workflow. Is there a heat map on the site to see what portion are being kicked or user import workflow user running tutorial. Okay, so to me, quite a lot of the a beside the first one how many user did something in the month. I think the second and the last point. They are. They, I think they can be tracked by having you know something like a century some sort of, you know, to that you can track whether you know hit map that sort of thing is fine if we want to get that that kind of data. But the first question is something that we will have to be interacting or engage with users to actually find out that you know what how many user did something in a month but what something what is it. Is it just come in, actually run a job, or is it yet is it coming in to find what they had done last time, and then they left, you know, that sort of thing so it's, it's, it's hard to find this sort of data by using technology at this point of time but we can definitely do it when we actually have that right persona in mind and include those as part of the question to ask them. And yet when it comes to user research and user interview. It's very very important to know how to design the questions, which I think later on we're going to touch on some of that point. Okay user persona. So overall I said possibly that user in a biological science often have a lot of pain point that they have to get over and so by the time they get to galaxy even a tiny bit of frustration is too much, which is true. I will show you the user journey map in a minute. So high end meet range and newbie so high end is people who are very senior and like Carolyn Hawk for example, she is a very senior researcher, but they are not going to be the hands on people. They, but they are the one who set the agenda that is correct. And so if people feedback to them that you know galaxy is very frustrating to use, then that's not going to look good to us yet. So what we really want to please in this case is the newbies and the meet range people because they will be the one who feedback to the high end user, which is a decision maker that they should be using galaxy. Carolyn Hawk for instance, because she's not she's not the one who use galaxy, but she have heard good things about galaxy. So we need to make sure people keep saying good things about galaxy to her. So we really need to please the newbie and the meet range. So let me see is there anything I need to give me I need to answer with the feedback if you're doing you know me every day you're not going to be using galaxy. Will you use HPC instead because of, for example, once you have that in your own environment is easier on your own system. That proven to be true today. When I interview a lot of senior bioinformaticians due to I was working on the TSI project. And access to really senior bioinformatician who is helping people like Carolyn Hawk to do data analysis or genome assembly. That's our job. They do, they do not use galaxy. However, if we make galaxy good, then they will want to use it. So it's just a matter of really having more chats with them, doing more exploration with them to see how we can help them. So there, from their view, they do see galaxy as a good tool for the startup for people who wants to become bioinformatician they will recommend. Yeah, try Galaxy. They're pretty good. They got a lot of support and things like that. But once people start to know how to do stuff, and they will probably teach Galaxy, but that's what we want. We want to keep them. So this is where the opportunity for us. How do we keep them? And so can we get some of the user retention number for Australia and EU to compare contrast. Best line would tell us that we have different types of user between the two. Yeah, I think, I think there will be something that I'm interested to see as well. At the GCC in Brisbane, I had a chance to talk with some of the EU team, particularly someone from working in the hospital space. And I don't use Galaxy, so I have no idea. And yeah, they were saying that, oh no, I always want to customize. So then I just, I then realized that is that they are another type of users that Galaxy has, which is, you know, they're completely on their own. Galaxy so it can be actually customized more than, for example, Galaxy Australia. So the idea Galaxy user may in fact be an entire, entire lab, not just a single scientist. Yeah, yeah, it could be. And it's, but it does require quite a bit of a studies to understand exactly how many departments are there, we in the lab, and then we can deliver to help each department. So yeah, it can be as big as we want it to be really. So the next slide will be talking about technical work or something. So I feel that entire site redesign are not usually necessary to generate high return. Yes, correct. The majority of what involves is usually in the planning and coordination, not a complex non-ante technical implementation. Yeah, that is very true. So yeah, and then user interview. Yeah, I do that. I just mentioned that, you know, Galaxy is for beginners, a lot of the senior bioinformatician to think that for high end user, they will use Galaxy as training tool, which is, I would say, 95% of the time that's what I heard, and actually have seen. Okay, so we want to we want to see some quantitative analysis on Galaxy Australia during the community go where it will be cross team cross functional. Okay. So we will try to see if we can get there the sharing the quantitative analysis. As I mentioned to Michelle previously is we, our study was studying on the Galaxy Australia interface. And if that if you find that could work and would help with different if you are using the new UI, then yeah I'm happy definitely happy to see if we can somehow see if we can cross check the quantitative analysis whether it will be helpful. So come back to the redesign. Yeah, no, I definitely don't think most of the time we need to redesign everything, unless it show us a very good evidence showing that, you know, we really need to redesign because nobody is touching this page, something seriously wrong here. Then, yes, we will have to do something. However, very often we'll find when we're talking to user, particularly aside, like aside like Galaxy, it has traffic. But it's which area do we want to improve. So we will talk with the user to then eventually we found out sometimes just the labels. Sometimes it just the icon. It makes sense to them. So, you know, just simple improvement, simple hint and things like that to help them that would really help. I will also show you some of the things that we found. Another interview source. I feel strongly that on site interview shed a lot of lights yes on on challenges user user face for for software in a biological science field that we should allow to interview on site as well. Yeah, so I did a few study basically following around following the researchers around for a week. I went to Sydney, went to Brisbane, went to museums and follow around follow those researchers around and also buy information to see how they work. So I have some ideas. So by the time when I interview them, you know, sometimes people are nice. They're nice. So they will look at the using the site and they will give you some really nice feedback. But we really want to get into the negative side thing because you know knowing all the good things not going to help us we really want to want them to tell us the problem. And so when you are face to face with them, you can see the body language, you can you can sense that whether they're just saying it because they're being nice. And yet so often people do say one thing and then do another. My experience was one time doing a user interview on this is for another site another project. Ask them about, you know, this is a very, very long and big table on the web page. And we asked the user, do you have any problem using this data. And they said no it's very good it's very easy to find see everything is there so we said okay so how do you find what you want. And they will use the browser command F to find what they want because the table did not come with a search tool or a filter or sort. So they just use command F and that's how they find them. And that's when we went okay, okay, there's a problem here but yeah but they accept it is a was fantastic is no problem yet. So, that's why it's very important to look at them how do they do things. All right, could we find a way to see what to they were using before they got to Galaxy. Okay, so we can. But we need to know who are we talking about. You know, it's different persona they come from different. They come from different pathway and you know but we can definitely find out where they come from this is why we have that data lifecycle to help us during planning. What do you do, but not everyone doing the same thing during planning stage. If it's Carolyn Hawk, she will be doing very different thing compared to Kate, who is a senior by information that work for Carolyn Hawk. So, you know, yes, we can definitely find out what to what they're using. Can we hook up century to get user journey information similar to what Australia is doing. We can explore that if century has if you know you got you if you have expert in using the application to know how to set the setting I'm very sure we can some we can get some I wouldn't say 100% but we definitely can see if we can modify it a little bit. Who is Wendy back and has offered to have new be experienced from other people to fantastic look if we have access to our one or two or three types of persona to interview. That is really a bonus. This is one of the biggest challenge for use UX designer is to recruit users to interview. And this is very good news if you have access to them. So to the designer connecting the work by comments is doing to measurable outcomes sounds like it will help them produce more quantitative data for us as well. Yes. So yeah, that would be good if we can work together if we can supply you the quantitative data. Any questions so far or is it okay the way it's going. Anyone. Oh, I would say, I think, at least a couple things one is anyone that has feedback to feel free to type it in and I will add it to the slides and some of the other galaxy hubs have not seen this before. And I would say on the from the US galaxy team were really excited and only a 15 minutes left to see some like real life example of a galaxy Australia user journey for instance, or, you know, the actual names of some of the user personas that you guys have found from your search or something that was used in a real scenario, since we're theoretical. Yeah, thanks. Sorry. Yeah, good, good. Yeah, I just want to follow that up. Yes. So yeah, how about I guess I don't want to go through all these slide but what I'll do is I show you I show you how the user journey map looks like. And what we did was we literally this is mirror board. So we'll create this board and we have the cycle, the stage up on the top so we got the planning, if you can see. Planning, collecting process analysis and preserve share and then reuse. And then we on the on the left hand column, we want to know what sort of job need to be done at the planning stage at the collecting stage at the process stage and and go on it and apply throughout and then the touch points. What do you use do you need the contact someone do you need to use email do you pick up the phone. Yeah, do you physically have to travel somewhere. So all these we want to know. And then we want to know what is the objective what do they want to gain. In the planning stage. What do you want to achieve you know so for the senior bioinformaticians say I want to know the brief. It's very important for me to know the brief so that you know I can produce you know quality outcome and things like that for instance. And then during collecting stage, you know what do you want to achieve. If it applies throughout, they will then step us through walk us through their journey. And then during planning stage, you encounter any pain points you know any frustration that you think is a challenge, you know appear all the time there's a situation so again they will walk us through every stage. So, for example, planning stage and might say, from one of the disease researcher, they are not buying from my teaching, they would say, it's very frustrating when they find a piece of sample, you know, a piece of ear for example, and they will need to bring it to a sequencing company to get its sequence. And then what they found out was that there's a long queue, for instance, so that's going to delay the project and things like that so we want them to tell us although, although the initially the project manager saying, how is that help us. So we want to know this because that's the journey from the users, things that is hidden we didn't know about. But during this process they're planning the collecting and then the process, and then the analysis that is when you can see, galaxy start to appear there. And you can see that they're already gone through quite a lot before they get here. So if they get the analysis and then preserve and then share and small pain point more frustration. And then that is when we know, oh, okay, we're going to make it a bit easier for them because they're already quite frustrated. You know, that's that that kind of thinking. So as you can see this one is an, for example, we're interviewing bioinformatician from an institution. And then we also in the end asked them how do you feel after during that planning stage after you have gone through all these you feel pain this way. Do you feel that you're hopeful? Do you feel that it's helpful? Or, you know, productive or neutral or frustration or stress as you can see here. These are the words they put on the user journey, likewise for another bioinformatician and things like that. From this data, we then analyze it unpack it will then create something like we store all of our research in Confluence. And we do a report. So this is for the UX designer. This is our space. And so we can use this information to do presentation, or we can also print it out as a PDF as well. So here we want to talk about why do we do this thing? What are we doing? Why do we need to do this user research? Because we want to understand the data lifecycle. And then we also before we start interviewing the end user, we actually talk with the team and stakeholder decision maker and get them to tell us what were the pinpoints and area for improvement of Galaxy Australia. They tell us first, you know, they will have assumption. That sort of thing doesn't matter. We just put them on mirror board against sticky notes. And then these will then help us to frame the issue so that we can we can then test this assumption and we can then ask the user what did that tell us about our services. You know, it frame so that we know we're not going to be off track and ask random question. So there's actually something that we want to find out. So from that, we will then use user journey mapping. But this at this stage is no we don't have like an agenda when we do user journey map that gender is literally want to understand. Where did you come from? What did you do? And then where do you want to end up? Yes, this is the participants. So we pick five people. No, it actually not paid is we only can get five. And so this is high level characteristic of our participants. So we will say bioinformatician and then research analyst and computational biologist and PhD student. And then from there we have another another document to show the drawing of the persona but that is really for the team to share just so that people can remember. You know, like I said, are you super hero so people can say all the the spider man and you know the Batman so rather than trying to remember names and things like that. So there's many different ways to create the persona. But let me just skip through very quickly. So this then we start with talking about 10 points that we say we want 10 points no 10 points I will have no job. So, 10 points so Galaxy to create 10 points across the research life cycle. So at the planning stage, there is missing tools, this lead to the user being unsure of whether their tool of interest can be installed on Galaxy. This often will require the tools team to look into the matter and this create a time lag and uncertainty for the user as to whether this is a visible option. And then at the process stage issue with the tool search and users said to the tool search is broken. And additionally, there is concern that also older tool will not be compatible with more modern data. And also too often just didn't work and were broken and one user also stated and unsupported live type file type. Let them to have to convert the file using a tool outside of Galaxy and then put it back into Galaxy and that's quite annoying. Yeah, and then at the analysis and analysis stage user said the issue with memory we limit associate with tools is a pinpoint tools not working as expected and having to troubleshoot. Or one thing is the error message not being clear. People do find it's okay to have error but if the error message not making sense or not telling them why and what else can they do. It's kind of like, you know, it's not helpful. And then additionally unavailable and availability of certain to was reported as an issue at this stage as well. So, yeah, if to if to sometime not working and not there you know it's going to create this uncertainty that I'm not sure whether it is not there or it is not working. Yeah, so the the history this is Galaxy history are creating pen points, particularly at the analysis stage. It was referred back and Alice stage is that stage is in the life cycle. So it's this area, like we said, that is when Galaxy appear. Yeah, so the his the history what sort of is what sort of pinpoint well is selecting the wrong data. The issue with selecting the wrong data from the history therefore getting a result that is wrong and is confusing to the user. There also doesn't, if a user doesn't rename files in their history, it can get very messy and confusing, which is, I'm sure, if you haven't noticed already this has been actually mentioned quite a few times during the GCC as well. It was noted that found them convention as step as deep learning curve for people. Yeah, so if it if people come find the file. You know it's it's very annoying and that all come down to you know how do we make sure people name their files correctly. Okay, so I'm not going to go through every point but we have this report happy to share I got PDFs as well. But I just want to highlight a few things like this, for example, you know, at planning stage, the data size data transfer movement and security issue were listed as concern. Additionally, there are report blocker is obtaining resources with researcher not knowing who is who to contact about obtaining resources. That is from the planning stage, and during the GCC I mentioned, you will see at even though at these various stages. Galaxy if people want to use galaxy at the planning stage. It does pop up, but we need to solve this problem. So then it will pop up more often. And if we come part of it, you know become a touch point and that's what we want. But yeah, so this report will show you what we found this is really good. And what I want to quickly jump down because now we've got six minutes is what this is also a list of opportunities. These are the opportunities from the user telling us, you know, what do they would like to see so these are very valuable. And then we have what I want to show you is, and yeah, what I want to show you is our recommendation. Right. So all these we got user telling us what opportunity they want to see. And then they also give us some good question about, you know, tools, we choose, how can we be more efficient in the tool we choose to wrap. What process do we use currently to prioritize this but I think this is an internal question. This is a recommendation. So we, we on the mirror board. Once we identify all these challenges and problem right here. So initially, we put them all sticking out. They're all over the site. So we said pen points these are all the sticky note on galaxy to pen point for the history panel all the sticky note here. We work with the stakeholder and we work with the decision matter in galaxy Australia and we say okay now we want to prioritize these are the pen points. How do we prioritize this, then they will help us to move across. So for example, we will say, and the pen point for short term, short term, what can we do right away. We will pick which pain point from the tool from the history from the information and data and then put them here so that we know okay that short term. Easy. That's easy. All hanging food we can do it now. And then we will have medium term one and then we have the long term one. Right, this is with the stakeholders so they can make that decision we you can only provide you so much and then you can decide when you want to execute them. Now, we then also make some recommendation. So the recommendation is from some UI improvement side of thing once we can see and identify the pain point that body language and things like that from the users for instance, and we will then make a recommendation here. So feel free to have a look but I can email everyone or provide you. I don't know if you have confluence access, but I can definitely email you the PDF. We can look at our recommendation. Now some of this point we already sorted. Right, so that particularly the short term one. And if, if cameras here or carrots here, you know, they will definitely point out which one we already executed. So there are still some midterm and the long term one that we haven't tackle. Yeah, so, so that's basically the report which I have a PDF of now, in terms of also an on this is ongoing running user research question and we want to keep collecting data of our user. Every person that we've met or interview what not we send them this link and get them to give us the information what domain they come from. Do they like this off online platform. How do they read them things like that. This is also some data that we can share. And then we have or else. Yeah, no that's it. And yeah, so that's it. Yeah. That's all I got so one minute to go. No, no time for question. Maybe in the last couple of seconds. I think this would be awesome to see this PDF copy of the report that you were displaying. It sounds like there's a lot of very valuable findings from your user user research so we'd love to take a look at that and then also be able to kind of I think pull some of the pieces of the process from that as well. For any iteration of this that we might do on our side. And then I think to, it would be great to see that form that you just showed at the end. I think this might be useful. I think it would be great to collect information and feedback from users on kind of the US and the galaxy main side. So we'd love to distribute this as well. And possibly at you based on Bjorn's comment in the chat. And then maybe since I am talking already, I can ask maybe one question if you have an extra minute. A little bit about how you convert these findings and how you take these findings and put them into the development cycle. Can you speak a little bit to that about how these recommendations kind of turn into action in terms of becoming addressed or fixes being made. Yeah, so. Alright, I have a bad track here. So because we were working with we being the UX designer working, as you know, with small team, so working with Cameron and Garrett and also Nigel. And so they will have to make a decision on the weather is the short term and long term. So what happened is, for example, if they pick to say, okay, we want to fix the tool search is a short term thing, we can do it in the next screen. So then this will then add as a ticket in the backlog. And it's, well, sometimes we have a be a. The person will have to write the user story in it. So that way is that user story come from it has to be something to do with the user journey mapping. So that then fit into the story. But for the more medium term, for instance, it may be either relying on, you know, the global side of thing, or if it's maybe technology or a, yeah, or authentication, for example, you know, relying on the third party, then it may be a medium term, but it still will be end up in a backlog. Okay, that's helpful. Any final questions I know we're a little bit over time. There's something on the chat and we have a look. My question is a bit, we are running a lot of in person trainings and is there anything. So is there anything that we can distribute during our in person trainings to these users or is there anything that we should talk with those users. So essentially, we have a lot of trainings and a lot of users that we train. What are these, let's say, most important 10 points that we should ask our users to enrich our data sets. Right. See, that's the key word that enrich your data set. Yes. But how to do that. Yes. So yeah, by using this question and that is not going to help you because this is this question is designed to understand our user type. But if you really have it sound like you do really have a burning question you want to find out the answers. So you literally, I'm happy to work with you, we can come up with not much five question that will help you to gather data that's going to actually be useful, you know, not not asking them. Do you find this easy that sort of thing that's not going to help you so you really is the matter of designing those question, but doesn't have to be many five is quite a lot. And because your burning question is how. What was that about improving the data set. Is that right beyond. Yes. So is there kind of, I don't know, a sheet of paper which we can distribute and people need to fill out something or is this the form that you showed that we should just send around and ask people if they can fill out those form. Is there something that we should stand behind our users and watch what they are clicking and then fill out those data. Right. I'm just pitching you the idea that the global galaxy community has I think access in the in person trainings at least to a lot of different kind of user groups. And we could use it to enrich your data set. Right. I'm just not sure how to and I would I would need to have an introduction from you. What are the key points that I need to observe or or which of those materials that you have shown here. I mean we cannot give them everything right this is a little bit of overwhelming, but maybe the top top 10 questions which we could give them and really ask them nicely to fill it out. Those kind of things I think we can do easily. Yes, that's right. I think yet what what I'm showing you if whether it's a form or journey map or what anything else it's it's the method. So, like, yes, it definitely will you if you have, you know, you obviously have the capability to have a lot of users engagement. However, we really want to know we're not going to just give them a form but we don't know what's the form going to help the information and collect how is that going to help us. So it is the matter of putting in some effort to make sure the piece of paper or the form we send out, you know, that is going to generate some useful data for you to answer that question that you have. Right. So, like, yes, definitely I can create a form, but you're not going to you won't be using this form, but we'll create a form that looks like this have only five or three questions. Those three question is the question that we will design to make sure it's going to provide you the answers you want. You know what I'm saying. Yes, but I guess it's not me that one. This right so the global galaxy or you in that sense I mean the UX team, whoever that is wants to have that right. Yeah, but do we know what it is that we want to know. Yes, exactly. Yes. So if we do know what we want to know, but we don't know the answers and that is exactly the, the question we're going to design. Yeah, to come up and then give it to the user every time you do your training you give them those five, three questions, and then it will give you the quantitative answers. Yeah. Great. Excellent. Thanks. Yeah, I know we're a little bit over time. Thank you so much for this presentation. I think there's going to be a lot of valuable feedback we can take back and also I'm really excited to dig into some of those resources that you shared towards the end. So thanks so much for your time. Thanks everyone for joining our call. And we'll see you at the next one. Thanks for having me. I'll send you the PDF. Wonderful. Thanks so much. Thanks. Bye bye. Bye bye.