 All right, it's the top of the hour, so I'm going to go ahead and get started. Welcome everyone to the UX Functional Group Update. Today should be a little bit shorter. It's only been three weeks since my last update due to the holidays, my last FGU got moved up a little bit so it's a shorter time span. The first thing I want to cover is that there's been a slight revision toward 2018 goals, at least for quarter one. We did some rearranging in order to focus more on areas that are closely tied to get lab strategic goals for 2018. We'll still be working on the other efforts we described in our last FGU, but that'll be more part of our day-to-day, not a special effort. So first off, we want to be DevOps for Kubernetes, right? So that means evaluating the install experience, the cluster experience, auto DevOps and operation workflow. So our first KR update takes a close look at our installation process. So we'll start with user testing to establish a baseline time for our current installation and identify opportunities for improvement. Make changes, retest, rapidly repeating the cycle until the time can't be improved. Our guesstimate right now is that we could probably push and improve it by 50%, maybe even more. But as we get into that, we'll be sharing the user testing videos, the results that we have, and then the changes that we plan on making. Secondly, we want to establish operations engineers as a first class citizen. So until fairly recently, we have been really developer focused. And in order to make the intersection between development and operations powerful, we really need to understand operations as well as we understand development. So with this KR, we're dedicated to understanding the needs, wants and perspective of operations engineers. The end goal is to establish a solid dialogue with this group so we can build out a set of tools they just can't live without. The final KR here, complete the pattern library and UI repository remains the same. And you can see details about that KR in our last functional group update. So some accomplishments, even though it's only been three weeks, since our last update, we've managed to fill one of our two open UX positions. We'll announce more about that new hire once the process is a bit further along. We've also been working on a 2018 vision. So Dimitri has been working closely with Mark Ponsack to tell the story of GitLab's 2018 product vision. Still work in progress and you can see the latest iteration on YouTube. There's a link right there for you. And so far, 10.5 is looking really, really good. 40 out of the 48 issues are already UX ready. So that means the UX is complete and ready for front end, back end to get working on those. So that allows us more time to devote to okay, our vision issues that we're already working on. So challenges. So obviously we did some last minute updates to our KRs for this quarter. So that does mean that we're starting a little bit late. And that gives us a bit of reduced time to reach those goals. So pretty confident that we're going to get very far on those. We're going to hit the ground running. So hiring, while we have hired one designer, we do still have another position open. And that means that we are understaffed still in using existing resources to review and interview candidates. Anyone here hiring knows that that can be really time consuming. It's a temporary constraint. We're confident that the remaining position will soon be filled. So hopefully that's something that won't pose much more of a challenge but the next FGU update. Priorities. So we do have some priorities that come in outside of deliverables. UX has been asked to give input earlier on for product vision issues, which we love. That's something we really want to do. We want to get more involved earlier on in the process so that we can use research and our specific set of expertise to help drive better solutions. But these often fall outside the current release. They're not part of our deliverables. So we have to balance that with the deliverables for the release, as well as any high priority or time sensitive issues that come in. So that can be a bit of a challenge. I think we're doing pretty well right now, but just keeping that in mind as we move forward. We also do have a lot of requests for UX design and research. Again, these are usually not scheduled. Something that someone just has an idea on or a question about. They want our input. Ideally, we'd love to jump on these and start iterating right away and generate some ideas on how to solve them. But we need to make sure that we're meeting our current obligations. So I've asked the department to concentrate on the highest priority issues first and just use your best judgment when answering requests on unscheduled issues. That way we don't get off track and miss deliverables because we get too deep into something else. That doesn't mean you shouldn't be asking for our help or pinging us. Don't want to discourage that at all. Just be aware that there may be a little bit of a delay in response. But if you feel it's something important, feel free to message me directly and ask me to take a look at it. I'm always happy to do that. And then I wanted to put a huge thank you out to PeopleOps. The whole team, of course, but I've been working closely with Celesta, Chloe Nadia and JC for interviews, candidates paperwork. Celesta has been doing a great job of sourcing and trying to find me just the best candidates from all around the world. So I wanted to say thank you so much. I know that they are understaffed and doing the best they can and they're knocking it out of the park. So thank you so, so much. I promise I keep it short. Any questions? Check in the chat. Big thanks to PeopleOps. So I'll give it about five seconds. And then I will let everyone go. Gonna have a whole 20 something minutes back. My math is terrible. Five, four, three, two, one. All right. Thanks, everybody. I'll see you in the team call. Bye-bye.