 All right. It's the top of the hour. I'm going to go ahead and get started. I welcome everyone to the GitLab functional group update for UX. The deck is linked in the calendar invite, and here's the agenda today. We have a lot to cover, so I'm just going to keep rolling through. I don't want to keep you here too long. So quick overview of the UX department. I know that we have a lot of new team members joining on a daily basis. So this is a quick view of the UX department. Each UX designer is dedicated to a specific stage of the product lifecycle, and they work directly with PMs and engineers to understand the roadmap and the direction of that area. To see where each designer works, you can check the team page. I've linked to those in the top of the slide. We also have two dedicated UX researchers, and they're dedicated to specific stages of the product lifecycle as well. Our O'Donnell covers Ops products, and Catherine Oqpara covers research for dev products. Just as with UX designers, the goal here is to work alongside PMs and engineers to anticipate and drive the direction of the product through UX research. I wanted to say special farewell to Hazel Yang. You can see Hazel's influence throughout GitLab, especially in our beautiful illustrations and icons. She'll be greatly missed, and you can still chat with Hazel in the GitLab alumni channel or catch her on Twitter. So you may have noticed the UX team is growing quite a bit, as with the rest of GitLab, and the UX department is undergoing a reorganization soon. So the current structure looks like this. If you want to get out your magnifying glass, or you could click on the link. Right now we have a dev Ops split, and research remains on its own, but each of the researchers specialize in a particular area. So we've filled our open positions for release and verify, and our new team is going to start, I believe on November 11th, so we'll announce details of that soon. And we previously filled our monitor team opening, but with Hazel's departure we have a need to backfill. So we currently have these two vacancies, one for the monitor team and one for secure. So we love referrals, if you know of UX designer we should talk to, please encourage them to apply, feel free to ping me directly and ask for more details if you need them. So with our growth, did someone want to ask something? Sorry, I thought I heard something. All right, moving on. With the growth of our team, we have put together a UX vision. You can click on the link here to take a look at it. As we grow and move into dedicated teams, we need to maintain a shared vision for the user experience at GitLab. We need to remain connected, and to do so we have to make sure that we all have the same goals. So this vision sets the tone and direction for all of our efforts, and it keeps the department focused on our ideals, even as we work on different stages and aspect of GitLab. I would think of it as a guiding set of principles. Every UX department will have its mission statement that drives the vision. Google, Airbnb, they all have their flavor of the UX strategy and vision. This strategy and vision should always reflect the values of the company, but have actionable ways they are implemented in the experience. So this actually goes deeper into things like workflow, stable counterparts, and the fact that everyone can contribute. So I'd love for people to take a look at this vision and this document and leave your feedback for us. So a quick recap of Q3. As we run straight into Q4, we added headcount in the middle of the quarter and said farewell to Hazel, which stretched us a bit, trying to get in that third hire and a backfill. So we only reached 66% of our goal on this OKR. The good news is that our pipeline is quite strong, and we have many good candidates in line. We reached 100% on our security dashboard OKR. It was a real stretch for the team. I don't want you to think that because it was 100%, it was easy. We had to push really hard to get there. And I wanted to put a special thanks here to PMM Cindy Blake for assisting with the comp analysis, and to Andy Volpe who came in brand new to the secure team and face this challenge head on. And once again, this was another stretch for the team. This OKR, getting these components put together to ensure that moving forward the CSS and component system that front-end is building has the proper standards. Each UX designer contribute to making this happen on top of their individual group responsibilities. We only missed documenting one component, and that's currently in progress. All right, Q4. So we have a lot of cool things coming up. The first Q4 OKR is create a seamless cluster experience, identify three additional ways users can create manager clusters, and we want to draft a proposal for an MVC. This will fall under the Configure Team. So UX in addition to the Configure Team are well on their way towards this, just wrapping up product discovery phase for the group level clusters. Implementation will be happening in 11.5, and we'll be working on how the experience for group level cluster, excuse me, will transfer to instance level clusters in 11.5. That's a lot of clusters. And you can read these notes also in the speaker notes. There's links to each of these. So this is one I'm particularly excited about. We actually have already completed a competitive analysis for version control tools for designers in GitLab. We want to identify ways that GitLab can leverage open source, our own tools to assist designers. So enterprise designers work on a variety of platforms. The market has exploded over the past decade with the majority of designers moving from using desktop software to cloud-based platforms. This move is largely based around the need for collaboration between designers and other departments. GitLab is the single first application built from the ground up for all stages of the DevOps lifecycle for product, development, QA, security, and operations. Teams work concurrently on the same project. A significant missing piece of this lifecycle is UX design. So we've completed a competitor analysis and have identified an MVC. You can click the links here and take a look. And huge thanks to G2 and Andreas for assisting, putting together this comp analysis. Sorry, there's good questions coming in. I'll get to the questions here in just a moment. Huge thanks to G2 and Andreas. They really worked hard to get this comp analysis in very quickly. We want to move fast on this one. And lastly, the UX department is cross-collaborating with the front-end department to build out maintainable, scalable CSS components. So we'll enable engineers to utilize reusable components, and that would have a significant impact on our speed of development and the consistency across GitLab. So an 11.5 antebellentory are actively implementing CSS, and additional UXers will be assisting over the next few months. Okay, so questions. And it looks like there were some questions coming through. So I'm going to jump to the chat. Feel free to jump in and ask questions as well. It looks like Seth asked right now, Amelia, is the UX designer focused on monitor? Would this change with hiring Hazel's backfill? No, this would not change. So this would be another UX designer to work alongside Amelia. And the reasoning there is the workload that we anticipate. Part of adding headcount to UX department was the goals that we have for Q4 and into 2019. So we took that into account when deciding where to add UX designers. Absolutely, Seth. I'd love to make this into a blog post. That's an excellent point. So I'll go ahead and make sure that I work with marketing on that. I think that this would, it is a huge thing I'm really excited about. Let's see. Why is your already signed in in red? I'll take a look at that offline. I'm not sure what that is said, unless you want to speak up. Is it something important that I should address right now? No, it's absolutely not important. Okay. All right. And let's see. One note about the blog post. Two things, like if you have a document that you want to have public and allow people at GitLab to edit, you can use like file publish from the Google Docs menu and put that URL in the document. So external people can access it. And you don't have to work with marketing to publish something. You can just publish something. Okay. It used to be this understanding and explaining this, not especially to you, but to the whole company. Like the content team writes your blog post. They write their own blog post. If you want to do a blog post, just write the blog post. Very much encouraged. Thank you. All right. I'm getting on that perfect. Are there any more questions, any more ideas? I'd love for everyone to chime in on the honest. I think that, you know, the more people we can get thinking about this, the better off will be. And I just also wanted to say to everyone that I will be on vacation next week. I'm going to be hiking in Moab. I will be completely unavailable. I don't think I'll get any reception out there in the middle of the day. I'm going to be on vacation next week. While I'm away, Tori will be the point person for all UX questions or concerns. So make sure that you reach out to Tori. And I'll also add that in our UX channel. And I'll add it to the company call. So everybody is aware. Pet peeve of things that we should redesign, ship that we haven't been able to schedule yet. Oh my goodness. Yo, that's a loaded question. How are you going to ask me that? I think that all of the work that we did on, on auto dev ops, we did a lot of research in Q1 and Q2. And now we're working on clusters here. I think there was a lot of really good insights that came out of our UX research that we could focus on and push out there. They're ready to go. They have data to back them up. And it's just been a struggle with everything that we're working on in that area and that space to get them priority. So not one thing comes to mind, but that whole area. You want me to, I can, I can definitely, you want me, you know what I'll do afterwards? I'll find it and I'll link it in the product channel. How's that? So nobody has to watch me searching for it right now. Unless you want to make the entertaining. Okay. Perfect. I'll put that in the product channel. All right. There's no more questions. I think Sarah, I put a few things on here. I think the bigger theme is we're doing awesome in this like super deep functionality, like the security dashboard for the, for the CISO, like awesome. I love the designs. I think what's, what's really important is also like first impressions, like paths that everybody hits when they, when they start using GetLab that those are like, those are perfect. So we're not striving for perfection really deep in the product, but an initial path is like, oh, I have to leave my email twice, even though the next step is registering. I'm not sure maybe that's the best practice, but I think it's an, it's a relic from our past when we didn't confirm email initially. So, so stuff like that, like we should make sure that we don't forget our front doors, like we're building out room after room after room in the company. Let's make sure that the facade facade, maybe a bit of a load of words, but, but that the interns also looks great. And I'm not sure because we're splitting up all the teams and we're saying, hey, you're doing, you're doing monitoring, you're doing security, et cetera. Like we, it's like, there's other people who's, who's paying attention to like the front door is there, is that everyone's responsibility? Is it your responsibility? Who, who, who watches that? The most popular flows. Yeah. And I think there's a really good question. That's something that Mark and I have talked about in depth. And that's a concern. We are seeing large gains in productivity and in focus from UX designers being embedded in teams, but you're absolutely correct. There's, now there's almost, we don't want to create silos where we're not seeing how people transition from one area to the next. And I think that's something we could address in a couple of ways. One, obviously I should have my eye on that and that should be something that we're discussing between ourselves at our UX, what we call surfacing the areas we're working on, looking for areas of overlap and opportunity. But I think at a higher level that, that almost needs a dedicated person or a dedicated team. So that's something I'll add to my. Maybe it, now that I, now that I say it, my concern, which I've had for a time now that I say it out like we actually have the managed team, which is responsible for like user sign in and log on and things like that. So maybe the UX special, the UX specialist focused on managed states should be, should be have an eye on this. I like that. So that's a great idea. Yeah, so to Sid's point about the security dashboards for CISOs, I have experienced with what draws people in at the front door. And, you know, I've worked on a lot of security products in the past as well. So Sarah, let's collaborate and I will give you my feedback on the kind of front door facade kind of things that draw CISOs in and all that. That's fantastic. Excellent. Kathy, I'll add that to our next one to one. I think that's great. And I agree with you said I think managed stage is, is the perfect area for that. I'll, I'll get with the, the team there and start talking about how we can do that. Chris recently put together a really good user flow on his team. That was, was really, really helpful to see the overall flow. I know that Jeremy was, was very excited about it. And that's something I think we can use in other areas to start surfacing this, but especially in the managed area. That sounds cool. If someone has it, then feel free to post it in the Zoom chat. Okay. There's a Pedro has a, as a question, I think in the chat. Sure. I'm looking for you, Pedro. Pedro, can you just speak up? I can't quite find it. It's the last one, but I can speak up. So for the competitive analysis, we looked at UX pin. Cause I don't see it listed. So maybe we, we had a reason for not including it. I don't know if there was like a, I don't know what it is. I don't know that we looked at it and specifically cut it out. But if you think it's relevant, add it in. Absolutely. This is a work in progress. We just wanted to get it out there as fast as possible for things like this so that we could have people surface, maybe areas we missed or other opportunities that we just didn't see yet. Awesome. Yeah. I will suggest it. Thank you. Yeah. Fantastic. So I want to say that I find that this, this was a great, after you create materials and hopefully you're, some people are noticing that I'm trying to steer up as much conversation as possible. I'm actually thinking about renaming the functional group updates to group conversations because we don't want to end with a presentation and then no questions. So feel free everyone to chime in and bring up small stuff, big stuff. It's fair game. Yeah. I think that's great. Thank you. It's really been good and some great surface. I'll do a lot of follow up after this. Chris, if you're on the call, can you link to the user flow that you did, the user journeys? Not sure if he's on. If not, I will definitely share it in the general and make sure that everyone can see it. There it is. Perfect. So it's the billing journey map flow. I think doing more flows like this across the application or will be so helpful for us to see that the different areas and make sure that we're seeing everything. Cool. Hi, Sarah. I have a comment unrelated to the past 10 minutes. And I like to talk in that type. So I'm going to interrupt. I appreciated how you mentioned Hazel departing earlier in the FGU. And I know there's been a lot of talk in various places at Gillab about transparency and the termination, voluntary or involuntary. So if, you know, this is a thing to talk about departing folks and FGUs, I think it's a great place because you can, you know, show us some slides as you did and recognize the work and encourage other FGU presenters to do the same. So not a question. Just. Oh, thank you, Victor. Yeah, that was, I didn't bear my eye putting that slide in. I got to be honest, but, but it was nice to be able to see her and put it up there and share that with everyone. So thank you. I appreciate that. Fantastic. All right. Well, if those are, if there's no more questions, I'm going to go ahead and let everyone go. Thank you so much for attending. And if you have anything further, please reach out. I'm always available. Awesome. Thank you. Bye bye.