GitLab CI/CD UX Team, 3 Jun 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Verify & Release By weekly UX Meeting | 3 June 2020

Description

No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).

A

So welcome everyone to the very fine release, yaks team meeting and yeah I'm extremely excited to have this session, particularly today, because we have fun UT member joining video. This is our bi-weekly, a meeting where we meet as this team of product designers in my 35 degrees, and we have a standard template here for the meeting which we kind of like go over through so um I place. The effort fYI the read, only item about the family and friends day. Thanks, hey enough for posting that first and that's some exciting news.

A

So next up next Friday, it seems to be like yeah we're gonna have another day off, and let me just jump to that. Your stage, part of the conversation who I'm your item is the first.

B

Yeah, let me just a fight.

B

Yeah, so I just wanted to share that at the testing room we just finished our first category maturity score /, so it's a based on the old process, so I wouldn't say that this is like a good example. Moving forward at all, to be honest, I mean there's, definitely useful things. I learn a lot of stuff about my category. The category that I was testing. I've learned a lot of things about the product, but yeah like the process.

B

As we know, change and it's gonna be use different criteria, but I still feel that there was like useful stuff and, like I, think that we yeah we run it in a way that actually allowed us to verify that what we did. It's the right thing for the customer, so I think that that that was a good approach, regardless of the method and I. Think that yeah I'm happy that we were able to move that category to viable. It was compliant, and now it's viable so yeah I'm, happy about that.

B

But yeah if anyone's gonna run that process soon, I yeah feel free to reach out and I can provide my input again. It's gonna be based on what I did on the old process, but I think there's still a lot of like learning things about like how you set up your scenarios.

B

You know I realized that, like the first call that I had was like sloppy but as I move forward with the calls like I got like new small strategies on how to make sure that I was getting what I needed out of customers when, like validating the the scenarios. Just one example is like when you start reading the scenario by people like right away, start jumping doing things. You know and I feel out that at the first goal, but then I realize that that the second person was gonna.

B

Do that as well, so I told them like hey, please don't do anything until I finish reading this scenario, you know and that's something you don't know until you go on you tested right like until you do that exercise. I feel that I can give tips on that. If you are gonna run these even if it's good the new process and yeah I just wanted to share that proud that we did that and happy that we were able to move one category up in the max really scale.

A

Thanks for sharing and yeah, it seems like that went pretty well smooth interesting. We had some well I, would say different experiences in general and give up a different stage group, so it I'm happy that you've been able to validate them, which we wouldn't even give it a level up. So thanks a lot for sure. Yes, as ones that, if anyone had would be having any questions, feel free to reach out I hand over to your guests.

C

Yes, yes, so in release management, we're making out user stories for environments in deployments discussing this topic in or I think Baker sessions, so Jackie and I have identified a bunch of a few Xbox and what we call UX features for environments and deployment, so they're all listed in this first ethic that are linked here and I'm currently in the process of making user stories for environments in deployments deployments more granular, so jackie identified a bunch of high level user stories, we're not calling jobs to be done because they're really like specific and I'm breaking them down into even smaller stories.

C

So, just a request, slash heads up, if you have anything in your stage or any issues that you've seen that overlap with environmental deployments, please let me know or just feel free to add them to this topic, because yeah we'll take care of them even if they belong to you, or at least it's nice to know any questions or the condoms there I'll jump to the next one, which is similar, I'm also tracking you, except and UI polish issues in an epic for monies management.

C

Just so I have a better overview of how many items we currently have. These are the ones that I had identified so far. They are not like categorized by category or anything like that. So same thing, if you have in your stage group overlap the items that you think are interesting to release management. Let me know I've been here: I have a goal to work on at least one UX slash front and issue per milestone now, so this is just part of a an exercise to see how.

B

Many of these exist.

C

In on these management, and not a lot but I went through all the issues: labeled release, management and yeah- these are the ones I did find that message. Peace, mrs. Fisher, said there's much more around.

C

D

Quick question relating to your first Jenna point here, which is regarding UX bugs. So how like you Xbox, are those issues that are labeled, UX and bug and are not referring to any UX depth issues exactly.

C

So there are not you, my polish, because my polish is just like correct implementation or whatever styles or things that can be improved. The new, except is really good things that were created from technical depth and UX bug is just above that touches the user experience. I think this is also related to the conversation we had about King the Xbox labor rights that we had a couple of weeks ago. Yeah.

D

So I, like I've, got a little bit lost on that conversation. I think we had it somewhere, but it is not fully clear to me when you would assign UX depth like a bug is wrongly implemented because of like like there's like technical back there or like a bug, is like it's programmatically, not correct, thus creating some problem right. The new exdeath would not like that would be a separate, separate bucket right. Okay,.

C

D

C

I also see this is that these are front end. Bugs that touch the you. Are they wax that's how I'm also going over them and I. Think it's also too hard. This question, you know just go over those issues and decide if they are you I polish. She likes that bug whatever, but these are just what we're calling wax bugs, because it's just a bunch of UX issues and some of them include bucks, and we also have a different tactic for UX feature requests, so everything the only environment doesn't have legacy.

C

Let's say everything that isn't you so that's yeah.

D

That sounds good in terms of like do we have this document it in the handbook nope. No, then I suggest that we perhaps make an addiction there yeah.

C

It said to me when you erase the you left a comment to one of the issues right may be asking: what's the difference and I was a bit like, should I go ahead and add this to eat it into the handbook right now because anyone's in a book with handbook, we just have like a mullet fullest list of labels and what did what they mean? We don't have like. You know anything like like a place, a placeholder for you, except, for example, it's everywhere in the end book.

C

So maybe that's that's a good opportunity for us to just write down what the you ask that is, and when to use a UX bar, etc. Like.

B

You asked that should be analogous to detect that, in the sense that it's usually that it's created in a sloppy way, and then we look back at it. You are like oh I mean just tell me what it's supposed to do, but it's not right. You know, but still it's serving the purpose I did that. That's how I will define them like separate, like anything that it's a actual UX mark or like an actual yeah. It will be something that, like it's, broken and I, think everything else that feels like wrong.

B

Ux is just you expect, am I wrong about that for ya.

D

I think there's a debate to be to be had there and I think it's perfect if we, if we include that in the merge quest to be created because it's it's such a like it is like I, would love to refer back to the handbook page on this on the triage issues, looping back into my next point on the agenda, because it's sometimes pretty hard to go off from just a label description as to what exactly this is, and now we're talking about label combination, which is not possible to be explained in like a label.

D

Explanation so yeah, like I, think you have like a salad point. On the other hand, I would say, like you, except I, would often thought of myself like hey if this creates user confusion. If this has like usability problems, those kind of things, though, like easily fall, or at least leaning towards the bucket of UX, that, if that you know like is it is doable like if that is filterable related to your definition of you, accept versus you like that bug, that is to be like I think it it can, but maybe not like.

B

I think what I was pointing at like tactically right now is that, since my beginning, at gitlab, I have never attacked anything as you explore like I. Don't know how reason is that label I always do inner bark or you accept, or both right yeah like for me, a bug is about regardless, if it's a technical, front-end or like if it's born you're experiencing that bug in the front end right, like it's impossible, not to like seeing the impact of your experience. So for me any bark is a UX bargain.

B

That's what I was trying to get at almost trying to poke holes at the idea of shoe? Should we really do? We really need the UX bar.

C

Also, when we think about, for example, white college right, we need to remind ourselves that it's really related to pajamas as well. It's like all those stylists and all this, the nitty-gritty of the UI that should be implemented or styled in a way. But it's not and I completely understand the combination.

B

That's a great point because, like sometimes I see things I don't even know if I want tell the pajamas people like hey this component is wrong or, like I mean, let's start by saying that not everything uses gitlab UI right like so there's things like these are no using good love. You I, I think we're responsible to go on, say like hey. We gotta fix these and the option in those cases is either using the TWI component or fixing it it matches. Whatever.

C

Ui or pajamas, but, for example, if it says styles from the page layout right those days and evening then the evening in the code base itself. So, for example, let me just let me share my screen. I think that's makes it clear, I added here to the description I caught her don't have too many tabs open and it's the description, an example of UX tent that we generated now in release management. Can you folks see thanks?

C

Alright, the document yeah, so this was the original merge request, was to add the type drop-down to the release to edit release page and then, during this merge request. You see here that these settings are what this is nothing right if this would just follow up, not follow, but this would not be raised as an issue right now. It is merge. Request would be.

B

A UI polish in the.

C

Future but because while I was reviewing the Saito Nathan, this is this is wrong. This needs to be fixed, so we generated another issue, a follow-up for UX debt. So it is a UI polish. It's like a new wax bug right, but because we identified in a merger quest face during the development phase, it generates dissent and then we fix it during the milestone. So I think it really depends on the context and how we want to label and treat those things. But to me, as long as they are attracting the fix, you know, I.

B

Just want to read the definition: what's right, can you hover? Do you accept label again yeah and.

B

It was just written.

E

B

That makes sense now that I read it.

A

It's a discussion to move into like an issue or a llamar yeah like do we have any volunteers to start that, because yeah I feel like there's so much discussion happening like not only on the labels. I didn't.

C

Follow up with that, since I initiated in a special new X book.

C

A

Man, yeah I, think that also be useful not only for the product designers, but also for the product management department. Cuz I find myself often having that discussion with PMS like what does it exactly mean having that somewhere documented actually makes sense even earlier. So thanks a lot.

D

Is that I'll take the next point for PD and C is a progressive delivery and continuous integration I have introduced riding for both you exactly UI polish, as it like. A similar kind of like way as well. Yeah I'll describe is like different process, but the idea is that, with triage tracking reports, the product manager and the UX er are being reminded to triage the issues and assign basically a milestone and assign a severity and priority label to all issues and like initially it was just bugs.

D

Then you, except was introduced, like I, was not directly involved with that and what I've added, at least for CI and the product deliver. A progressive delivery group is adding a you, ik, UI polish, but specifically adding in heat maps, which makes it possible to see like hey how many issues are currently without a milestone. How many issues are currently without any severity labels, and if so, how?

D

Many issues are, for example, within the severity two and priority two like well part of the heat map, and that way you can get an overview of how well you're doing in your stage group I've. Yet, to make some improvements there, but for progressive delivery. This going very well and for see I am starting to start it up, so I'll be working with you. Vide vide got to get that going and apart from that, there's the standard process of suggesting at least one UX that and UI polish issue towards p.m.

D

and annex planning issue and the product management has already accepted that as like an effort and that they will work alongside to get that plant in and in that way we help out with the OPR related to you, accepting you white polish. So that's for CI MPD. It.

A

Is if anyone else on the school using in triage reports or anyone, anyone who is ignoring it because I know in Marcel's team some designers been like asking to how do you say, be removed from the notifications I get.

B

The try reports.

B

And you ignore.

A

B

A

Why is that? Because.

B

It was not clear right what yeah.

F

B

Am I supposed to do here? You know like sometimes I get them all, always all the time it was.

D

Just thrown on your roof, yeah and then I was like, but this needs to have some kind of function. So then I looked into it and it's like all right. There's about try edging alright, let's try these issues and then get them scheduled somehow.

F

So I have a question: who does the tragic happen? Like does do one of you take the task upon yourself or does it happen in a group in a meeting.

D

B

D

Happens: sorry go ahead, no.

B

No I mean we were just discussing like like the way that it's set up right now, at least for my, like the way that I get. It is there's an issue that gets created automatically, like my get locked, but.

B

Like stakeholder group and then you're supposed to go there and I see Queen easily. Do it? That's that's how it works right, Dimitri, yeah,.

D

Currently it is that way. I would say that there is like an improvement to be made there with like some kind of like a priority, matrix meeting or whiteboarding meeting, and then you know a sign those severity and and priority labels I think that's good, getting somehow a little bit closer to what Vienna is doing with, including them into a context and then looking at them, potentially together, I, don't know if you're doing that right Anna, but in the end it kind of serves the same goal of getting things scheduled right, one way or another.

D

C

I know from release management is that Jackie goes over. They stretch report I, get the the alerts, the notification, but by the time again, there's someone already did the best, so I never really have to look into anything. For example, the.

B

Last one, this one was triggered two days.

C

Ago the chat, and then there is this one bug that is an item that I just show you like follow-ups from when you accent so, if found in this year, right and Jack immediately schedule it and then I worked on it. So from my side, I ignore it because yeah.

D

I think I think it's important to look at those try to report. Similarly, as you have, for example, the stand stand up but like it is a tool for us to communicate, and you know do some backlog management while we like are not needing to always think of it ourselves, but it is not necessary to do it like it is a tool it's there to help us not for us to help them right, like that's the way, I look at it at least.

A

Interesting learnings here, yeah I'm curious to hear how this gonna be a IBM's gonna behave further with this try out reports and how like they're gonna, be prioritizing. Do you maybe like if you can even show us like a little yeah a little demo if you, if you will find that that works for the PM's, but yeah I understand it in some stage she looks is probably not needed. Like penny you're saying if check is following up with everything, that's just perfect.

A

Okay, all right um so I see our process. Part is empty. um Just like quick call out. Anyone wants to share any interesting process that folks tried or anything something interesting that works in a stage group doesn't seem like that. Alright, then, to cross stage- and the first item is mine. However, like I, see much more important items, so I won't spend time on this.

A

This is this was a follow up from our previous team call from the retro point that one mentioned about putting in one place all of the meetings that we are having as a team vehicle is going to be extremely helpful for you, so I'm gonna make sure that I merge that virtual quest soon and I'm also making the board where I would collect all of this type of issues. You know where I asked a team for input, so then you can go there and see.

A

Aha I replied here apply there, but then, for example, I didn't reply. There.

B

A

Just to make sure that we move on with some of the things faster that needs input and, of course, like pull around the red on this so but keep you posted I want to put something visual behind this word. So what's not supported, spend too much time and a quick note from myself: hey I've watched all of the uxk Cox video I really really enjoyed them. A few like I learned so much yeah, because some of the things I feel like it's really easy to keep when you're, not on stage group.

A

So it was very useful. I know that their team are there. You are also doing that. I haven't watched theirs though, but I know, I should and I'm curious in the team like to you. Do you watch other product designers, video? Maybe somebody watch the ones from deaf. Like you know, do you think this is gonna be helpful for us in the first place? Of course, this is a topic for retro, but just wanted to quickly ask you I I.

B

Did watch them all and I felt a little bit bad later, because I didn't mind where I mean like Dimitri's are like super like with the slides and stuff Hana's ones were like very I. Don't know like like presenting to an audience and mine were like oh yeah, here's what I'm working on you know. Oh I, see you later.

G

Rihanna's and they put the links to my issues in there, so I thought. Well, you know.

C

Feedback that mine was.

G

C

C

I think my honest opinion if this would be useful not just to us, but you know more broadly once we start doing this kick offs together with the ends, so that is like, which is the whole company like, and what I think the sheriff wasn't me, but whatever you meet, someone I also Jackie mentioned that she wants me to do together with her for the the company kick off the moss to kick off because yeah, then we can reference to a single thing and make sure that UX is included in the overall need, but yeah I watched it I love that Laurie's was like one and a half minutes.

G

And we don't do these in on New York's team, so it I think it's good for me to be able to do mine and put it with you guys's stuff as well, because otherwise we have a word. But nobody looks at the board about what we're up to.

A

Cool all right. Well, it sounds good. That's great I'm, happy that at least you know that we are coming and watching those as I said after we run the ones with PMS. Let's run a quick, read, travel create an issue, so we can compare the two ways to do that and see that's useful, because I can imagine that that takes time, that's like additional activity, so I don't want to ask to spend time on something that won't be valuable. However, I feel like that's going to be really interesting.

A

At least I feel the value already, but I hope I'm, not the only one really.

C

Just one thing is I I really like that we did the videos, but I personally still see the ballerinas just talking about it. Sometimes you know just say: yeah here's a list of the three issues that I'm working on and having them in the agenda or something so that we can not wait. You don't have to wait for the video, but you can have access or have a way to find it. You mentioned above like having the board or having something like that.

C

But yeah video is nice because it's a little available to everyone, but doesn't stop us from just.

E

Talking about it.

C

G

Wonder if we could just do a video of us talking about it and note the timestamps of each person's discussion piece, nice.

C

Like they work showcase.

A

Those are good proposals, I'll make sure that I document them and we collected together with the findings of the retro, and maybe we come up with a different approach.

A

Thanks for that, while I'm making a very safe comment body here, hi Anne over to you.

C

This one right yeah, so just a quick question if you guessed this before, but is anyone working on analytics, analytics components, data visualization anytime soon or you know, you have items in your backlog and I'm asking this because I have this test to identify the gitlab, UI components or at least some UI components to use in the director dashboard or the group level. Ci, CD, dashboard and I just want to know because I feel like I asked this before, but I. Don't really remember if anyone's working with analytics.

C

If not, it's also.

A

Fine, okay, yeah I actually think this is a great question for tomorrow. Well, if it's a different view with ops, but I know that not just when you go I think who is working in ops hmm somebody there yeah.

C

Another called me: we have monthly yeah data, visualization analytics circle and that make me go organizes and I know that is it create, oh, my god, which team whatever something they presented today this one like in generics analytic reports page. Let me just live here quickly.

C

He stops and it's like 90 percent, similar to what we trying to do on release management. The difference is that they want to have like a widget kind of a widget dashboard when the users and people can just stay on the slide file which data points they want to render in the dashboard view and but like for all data right, any any data points and for us it's really like related to environments and employment, etc.

C

In a dashboard view and I just wanted to know yeah if people are working on anything related because I think you'll be interesting to have conversations also with Jackie and allowing the blends, especially between us, because it's verifiable, easy everything's. The same.

A

Do you read you one over collage, your comment or I.

D

A

D

C

Then the next one, it's kind of like you meet he's already answering here, so we have this detached label, it's back from from the shadows and I just dropped here to here, for anything else is needed for my side or if there's anything that I can help with yeah.

D

Thanks thanks for that, you know this is an issue that recently got. You know, split off in terms of UX scope, so the engineering is going to work on improving when the detached label is shown at all. So I think that is that will improve the situation at least: buy buy, buy some and we'll kind of delay. The UX conversation a bit to a separate new focus focus issue. I saw that you left a lot of a lot of information there. Thank you for that in terms of like UX availability, this.

D

This is all bit like additional work. I want to get to, but there's more, you know more priority work for me. First, that needs to be done so I'm thankful this as being scoped off to it a separate issue, but I've made a comment inside that new issue that there's a lot of content to go through in the old one. So your content will not be forgotten and will be reviewed in that nation.

C

So I would say looking to the findings or and let the PM look into it, because all the answers for the problems, because I actually did a usability testing with this one. So there are video recordings there's the whole shebang related to yeah is about.

D

The meet actually also everything yeah I, don't want to make don't wanna, let that work go to waste and I know. There was some research on this, and thanks for putting in some details in there, there surely is important because will be so nice to just be able to. You know finish that confusion, because even though I was involved in implementing it even even to me, it still confuses it. Looking back at it like attach detach, they are like it's such a weird terminology being used there yeah.

C

And then from my science I did the whole. We we did the whole investigation and document documented everything, but then there were no proposals and no prototypes and no follow-up from all those issues. So I think it's also a good exercise and then I can definitely help you there, because it's better. If we have a discussion than if you have to watch six hours of user interviews, because I think that's the amount of people interviewing so yeah. Let me know.

A

It's definitely useful yeah, so.

F

A

You jumping in there as well and thanks Dimitri, for pushing this forward.

A

Okay, we have just few minutes left Laurie, the user research part is empty. Anyone wants to mention anything huge happenings around that I.

G

Got nothing other than we're using dovetail now for our tool, so everybody should have gotten an invite if I learned today, if you don't like hit the button to activate your invite it flips over to just a view, only account you've got like two weeks to do that. So, if you didn't activate it go and do that, if it still is like a viewer, account, I can change it. If that admin rights and we think you've got, you should have gotten an invite I hope at some point.

G

If you don't get one in the next week, let me know, and I can send you one from the system and if you've never used up tail before welcome I haven't either it's what we're using to capture note capture I, get either video to notes and our insights and our findings. So we don't write reports here. Instead we're very much more agile in how we present what we learn. So we're going to use that platform now moving forward to present all of that information. There's a ten minute video somewhere to watch.

G

That's what I did that's as far as I've gotten I need to dive into it more so if you get a chance to dive into it more and have, let me know we'll, learn together, Legos for everybody.

G

Okay, thank you.

A

You don't probably find it video and your email somewhere later. I can imagine, checked.

F

I, don't think I have it. We.

A

Can look into that with your after this meeting, yeah.

G

I didn't know where it was on her onboarding. So just let me know if you need anything I'll make sure that we follow this up.

A

All righty and well as a final final point, I actually just really wanted to share this I'm, not sure Laura. Maybe this is already being included into the job stupid Arnold that huge work that you are doing right now, but by your recommendation. I'm reading this book, that's by the way, actually so easy to read and so down to earth. Explanation of my jobs to be done, recommend it to everyone. Have it like on my iPad I, don't know it's just like a cheese go very fast and I didn't go too far.

A

Yet, but what I really liked and what makes me a lot of sense and like I, inserted this graphic of I, don't I, don't remember how they call it, but I think it's a jobs to be done. Grouping or something like that, and this is a nice visualization of how you visa visualize the whole, like user journey, with the jobs to be done from the beginning, to middle to an end and I thought.

A

It's really visual and easy to grasp, and probably a nice practice for us to try with mural with our PM's just wanted to share that yeah.

G

It's mapping the job, so I actually talked to Holly about this yesterday and her p.m. and Mike as well, because they had some questions about their jobs or their jobs too granular. Are they too high level and I suggested that maybe they map them out, because, if you're not sure, if you're at the right level to start with, try mapping it out at that level?

G

And if you find yourself missing some steps or missing some tools or missing some parts of that job, then you either need to go probably down in granularity to get closer to more detail. um If you find yourself, Matthew Under, the Sun, you might go one level in job detail, so my hopefully we'll meet on Friday I Monday was a holiday in Europe, so that was on me. I scheduled a follow-up on Monday, so it's scheduled for Friday.

G

I, really hope that the next hour will allow the group to get aligned on how we want to communicate granularity and altitude of jobs to be done, I'm so glad you're enjoying the book Nadya. It really is one of the best books that I have read on jobs. To be done, as it relates specifically to design in research, not just this 86 step process that this other guy came up with.

G

That's ridiculous and no one's ever gonna follow it's very consumable, very user friendly to read most of my stuff that some that jobs to be done, merge request came from the book, so I'm gonna need to really put his byline under there somewhere and I I. Think I might suggest it to the book club as well as their next book to leave, because it really is effortless to read and very very simple, and you can actually look at it and go. Oh that's something. I can do with my p.m.

G

or with my other designers and I keep mapping jobs out. We're gonna talk about that on Friday, because I think that's going to be something that will help help people to visualize what they're trying to capture in a statement as well as being able to pickup the user story, piece and task piece as well so yeah, because you kind of map out tasks like you know. You map out processes, but you don't think of it from a higher level. You point: okay, nice.

A

Yeah, looking forward to that yeah I'm.

G

Looking forward to discussing this.

A

More in the future, if anyone will have an X.

A

All right, I, don't want to make sure I want to make sure that I don't keep anyone over at the time. I know thanks a lot. Everyone for joining me today again welcome super nice to have you on the team thanks a lot for being so open to go through my torture of five activities. No, no I know everyone really like that from time to time, but yeah thanks a lot and yeah I have a good evening or day or whatever is the time they're you Jetson.