 All right. Good morning, everyone. Welcome to the UX Functional Group update. I want to start by apologizing for any background noise. We've had some terrible weather here in Florida, and I had to relocate to find reliable internet. So I'll do my best to keep the background noise to a minimum. Right. So keep this short today. First, I just want to intro the UX team. I'm going to talk about what we're excited about for UX, things that we're working on and things that we're looking into for the future. And then just a little bit about the handbook before I open it up for questions. So I know we have a lot of new people coming into GitLab, which is really exciting. And so I just wanted to kind of remind everyone of who the UX team is and who's on the UX team for whenever you need to reach out to us for questions, concerns about an issue or something that you think would be an improvement. So right now we're a team of two UX researchers and seven UX designers. We span eight countries and six times ours. You can look on the team page for our areas of expertise. Unfortunately, Pedro is shaming the rest of the team right now. He's the only one that's added all his areas of expertise. So the rest of us need to step it up a little bit. So what we're excited about, we're actually adding a new UX designer who's been hired and we'll start on June 4. So very, very excited there. It hasn't been officially announced. So there'll be some more details coming soon. As soon as we do get that officially announced, we don't want to out anybody before they've given notice. We're excited about auto DevOps. Obviously auto DevOps is a really important feature for GitLab. And we've been focusing on it since quarter one with UX research as well as dedicated designs from Tori and really the attention of the whole team. So one of the big things that we've done is is tried to make sure that it's a first class feature that users know it exists. So what we're doing to continue that work right now is is working on UX research issue, which is the third link here to really understand how people discover auto DevOps, what they know about it. And what they know about clusters as well, because that's really key in setting up auto DevOps and using it to its full potential. So really excited to work on that research issue and the design artifact for 11. And for those of you that aren't familiar with the term design artifact, what that means is simply it's an issue where we're not implementing the whole feature in one go. We're spending the entire milestone with front end back end UX and product to talk about do discovery and discuss the best way forward. The outcome of that issue, it could be a wireframe for future design to be done in the next cycle could be the whole design and all the problems kind of worked out. It really depends on the issue and the conversations and where that lands. And the goal is not to set up kind of a monolith and decide what someone will be or something will be and then and then just put it together over a few milestones. This is true iteration so it is about really understanding the problem, boiling things down to the first iterative step and then building from there. But we really want to get more of a holistic overview of things before we dive too deep. So actually being developed in this release for 11.0 is our comments redesign. I'm really excited about this one. On hacker news, quite a bit. And through other areas in the community we do hear that that we could improve and our visual hierarchy and our visual design. A lot of people have commented that they have trouble with the comments sometimes they get lost they're not sure where one comment ends and the next begin. So we really took a look at that to try to determine what's the best way to create that hierarchy and bring users through the comments and make it more interactive. So Hazel did a great job working on this together with Victor and some of the front end engineers to really discuss what this should look like and what we could make it be. And then another effort that we are working on the design artifact issue has been worked through and we're actually breaking this up into iterative steps is emerge request widget redesign and exploration. Again, this is not going to be done in one big go. This will be iterated upon. And this is just a view into what we are the direction we're going in. But as new information comes in and we implement certain pieces that subject to change and flexibility. And as you can see there's some inspiration here from the comment redesign in this merge request design and exploration. And this is one of the first big things that G2 has worked on here at UX in the UX team for GitLab and we're really excited to see what he's contributed. So one of the big things that I want to say about this merge request widget is that it has to support multiple workflows. And so the problem has been that there was no way to interpret the best order for users to quickly to adjust the information based on what they are interested in seeing. So again, just like comments, the idea is to create a visual hierarchy and enable users and empower them to digest the information that's most important to them without being distracted by everything else. So something I'm really excited about is UX polish or depth versus breadth, as we like to say and polish is not just about making things shiny changing colors and typography. What really is about taking these features that we've put out there and improving the overall user experience, making sure that it's the best feature it can be that it's useful to our users. And so there's a lot of different areas I think that that we could improve on and that we're focusing on. So one of those is updating UX of notification notifications throughout GitLab. Kind of a hot topic this morning, I know. So those have been set out with banners and toasts and changing the way that we're doing these notifications. It's just a matter of getting them rolled out and implemented within the UI. We're also looking at improving the overall user experience of wiki, the admin area settings as well as the project homepage. So the goal here is to work with each product manager over that area to prioritize and schedule improvements. So they're all we're always chipping away at this and making sure that it's a focus for us. And the last thing I just wanted to touch upon is the handbook with two new designers starting and then kind of meeting with with a lot of new Git labbers, new PMS. One thing that that is painfully clear to me is that the handbook is amazing and awesome and it's like the gateway for everyone into our culture and our company, but it can also be an information overload. There's kind of this rabbit hole effect that can occur where you start reading about something and it links you to somewhere else and you link there and you kind of get lost in that link and so on and so forth until you're not really sure where you started or how you got there. And you can't remember everything that you read. So, I'm working with Ashton to focus on understanding what users expect to see and we're going to do that with some UX research. And the link to the Epic is there we're going to do some card sorts and tree tests, and that will be with Git labbers so please be on the lookout for the UX research study that we're going to conduct in the coming weeks. We'll be looking for volunteers and we're especially interested in both new Git labbers as well as Git labbers that have been here forever, and just kind of intuitively know where everything is, like to see the differences between the two and how maybe we could improve the overall information and architecture of the handbook to make it more effective. And with that, I'm going to open it up to questions. I see that there's some chat messages. Let's see. I'm just going to see if there's anything comment redesign looks great. Thank you. We have an auto DevOps wizard pop up when a new project is created. It's funny mark that's something we've actually talked about in the original auto DevOps research is that we really feel like having some kind of kind of step by step process, a wizard, or even Mark Punsack talked about maybe gamification or some kind of mix of the two to really help walk users through that process because it can be really confusing. So that's something we're looking into. Thank you Tori already answered. Thank you Tori. If I'd only read two comments down. Let's see. Awesome. So are the UX onboarding tasks going to be affected by this research as well. Yes, yes, I'm actually and I didn't add it in there but I am working on an extensive overhaul of the UX section. I'm just going to break it up a little bit more so that we have kind of an overview of UX how we work with other teams with product with front end with back end, how we schedule as well as individual workflows for UXers UX researchers and then some specific onboarding tasks. We'll see how that goes that could help inform how we decide to do some of the overall handbook changes. So is there anything else? Any other questions? Doesn't look like it. Well thank you everyone for attending and please be on the lookout for my handbook UX research. I'm going to get all of you involved. All right. Have a great day everyone. Bye bye.