 Good morning, good afternoon. My name is Sarah, and welcome to this month's UX Research Functional Group update. So, since the quiz format was well received in my last update, we're going to play again this month. The rules of how to play are available on this slide for those of you who haven't played before. After each of my questions, I'd like you to try and guess what the answer was, and you can do this by answering your guess into the chat window. You can only guess once, and you must have answered your guess by the time I finished my countdown. ac mae'n amlwg am ymweld â'r rhaglen y rheswm y UXT. Mae'n amlwg am rheswm i'n amlwg, mae'n amlwg am fwy o dweud a'r ysbytau yn ddych yn ddod am fwy o gwaith ymlaen. Fe oedd y cwestiwn y nifer 1. Mae'n dweud yn ymddangos arall o'ch cyflawn a'r hunain i'r cadw yma i'r YRX research yw'r cyfeirio. Mae'n ymddangos i'r ymddangos i'r cyflawn o'r cyflawn o'r cyflawn o'r cyflawn. Felly mae'n gweithio'n amser o'r ffordd. Felly mae'n gweithio'n gobeithio'n cofnodi'r yswrdd y ddechrau i'r labiaidd. Felly ond y ddechrau i'r ddechrau i'r ddweud. Rwy'n ddweud hynny'n gwneud. Yn 3. 2. Mae'r ddweud hynny'n ddweud hynny. Mae'r ddweud hynny. Nid yw, ti'n gweithio'n gweithio. If you said C, 17, you'd be correct, I've spoken to 17 candidates, and I'd like to give a quick shout out to the People Ops team for finding me some great people to talk to. So question number two. So this is an illustration of our new persona, and he is responsible for managing and maintaining his company's GitLab installation, but what are his pain points? OK, you've got three seconds left to answer, two seconds left to answer, and one. So the answer is E, all of the above. So why are these pain points? So this persona actually introduced their company to GitLab and subsequently they're now responsible for managing and maintaining their company's installation. Basically they're the go-to person for anything GitLab related. However, they do this in addition to their day job, as they're typically an engineer who has taken on some added responsibility. And the problem with this is that they don't always have a lot of free time to update GitLab or configure it. So they fall behind with updates because they can't keep up with the frequency at what GitLab releases at. And also because they're not a sysadmin, they're sometimes not very confident in how they've set things up. So processes like automatic updates, creating a backup and so on, they're worried that their setup isn't secure or as efficient as it could be. And we can help them with more tutorials and guidance in the areas that they're struggling in. Another common suggestion is the ability to trigger these processes from within GitLab's interface. And this persona is also responsible for onboarding new users to GitLab. So they've got a lot on their plate. They really want their colleagues to adopt GitLab, but again they're struggling to find the time to demonstrate GitLab's extensive features to them. So if their colleagues can't understand the benefits of using GitLab and the impact that it will have on their workflow, then it ultimately slows down adoption. And we can alleviate this problem with things like a walkthrough when users log into GitLab for the first time on my next question. Now I'm going to give you a bit of background before you answer the last two questions. So I conducted a card sort with some of our users and a card sort is a research method used to help organise the information architecture of a product. And basically each user got a set of virtual cards on and each of these cards is a piece of content from the sidebar. So for example one card had tags written on it and another card had pipelines written on it. And users were asked to organise the cards into categories that made sense to them and they could create as many categories as they wanted. And the second step was to then label those categories and they could call them anything they wanted them to. And when you analyse a card, so you're looking for common patterns, you're looking for when people organise and label a group of cards in the same way, you could then apply that structure to your information architecture. Now for this question, users organise cards into a new category that we don't currently have in our sidebar at a project level. And they gave it one of the headings detailed on the slide. So which one was it? We have three seconds. Two seconds to answer. One second. OK. If you said A, wiki, you're being correct. Wiki is actually a category which already exists like you had a bell. And you can add it to your sidebar by changing your project settings. If you said C, insights, you would also be incorrect. Insights is a navigation item within GitHub's interface. It was actually B statistics. 58% of users who took part in the card saw it was like a new category called statistics added to the sidebar. And some of the items they would like to see within this category include activity, cycle analytics, contributors, members and charts. So my last question for today. So what happens when users are confused by a piece of content? Well, you end up with less common patterns and more unique categorisations of that card. So at the content on the slide, which received the highest number of unique categorisations, two, one. If you said A, tags, you'd be wrong. If you said B, snippets, you'd be right. So snippets had a whopping 48 unique categorisations. So that's 67% of people that categorise snippets differently to one another. So why is this? Well, the category headings are people used actually gave us some insight into this and I'm going to read a couple to you. I don't know. I don't know. No idea. Ambiguous. It's useless. Do not use. Really used. Now users could access a brief summary of why snippet is from the card description. So we can safely assume that they have a basic understanding of what a snippet is. So it's not the terminology we're using to describe the content. It's just as simple as that they have no idea where to put it. And that's possibly because they're not using the feature. So for a future study, we need to dig a bit more into why they're not using snippets. So that's all my questions for today. Thank you for taking part. My next quiz will be in the new year and I'll be introducing some prizes for taking part in the functional group update. So stay tuned. Come back next year and please take part. In terms of what I'm working on at the moment, I'm currently writing a blog post into the kinds of research that we do at GitLab. I'm also doing some research into how issues are sorted on the board view and how they're visually displayed across GitLab and the kind of things that users need to see on an issues board versus our list view. I'm also hoping to expand our personas even further. I'd like to include a non-technical person. Does anyone have any questions? Sarah, are you considering broadening the research beyond just the interface of GitLab but also researching the installation, the updating, the onboarding, getting a trial, stuff like that? Definitely. I would definitely love to do that. I definitely think from what we've seen a lot of the time, we could touch down with this persona such as onboarding new users and having walkthroughs and things like that. That is something that I would love to be involved in. Cool, that seems a good middle ground to start the onboarding of new users. Any last questions? Thank you very much everyone. Enjoy the rest of your day. Thanks for the game.