GitLab Digital Experience, 5 May 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Digital Experience Retro - May 5, 2022

Description

Digital Experience handbook page: https://about.gitlab.com/handbook/marketing/digital-experience/

A

Hi everyone uh welcome to digital experience team. uh This is our iteration retro video we'll go over what went well and what uh we can improve on from our last big project, which was released last last week, two weeks april 27th. um So this is kind of gonna be a longer retro. uh So we'll begin with the things uh that went well and I think barker has the first point: we launched a new freaking.

B

Site wow like come on, it's huge and it went off without a hitch like we launched it. Everything worked there's only a couple like small bugs. It was awesome. It's a tremendous achievement for the entire team, so yeah.

C

Yeah, I just had a point there too, like it's insane that this is what I expect from the team like when uh kimberly bolton asked. What is, can you give me some insight on what your um contingency plan is? I was like, oh maybe I should have thought of that, but I don't have one because I don't think we need it like. I just 100 had no doubt that this was gonna, go, how it went um and that just that sense is crazy, impressive. So it's it's the best feeling. um So thank you.

C

Oh, I had the next one um I saw so much kindness. I saw so much people giving the benefit of the doubt in the way of like when things weren't, where they needed to be. It was a collaborative opportunity to get them where they need to be. I saw in every every single corner of this project.

C

um Really it was just the kindness that blew me away like it was a positive approach. There's two ways: this could have gone like frustrated that you didn't get what you needed or that things were delayed or something might not have been understood. The way that you meant it to be understand, or it was okay. I see what we have. I know we need to get a little further.

C

Let's do this together, so I was just again so amazed and I think the opportunity for us is to just keep driving this like it's the cross-functional collaborations of muscle.

C

It was a muscle that had atrophied at gate, lab or just hadn't really been flexed and, like I've, just been using sort of like my hands to kind of like when two years ago, when I joined it, was like this, like people were doing lots of cool stuff, but apart, we've really forced it to here, and we have the opportunity now to go this way or go stronger and I would love to see us get stronger.

C

My third point I added, um I thought what went really well was being open to jam 3 joining our process. I also really appreciate how far they came to our process, um specifically like getting direct and honest feedback from adam. You know monica luke, the whole brand team, as well as um the product design team like it was always super clear, is wildly consistent. You know we were adam would send his notes to me. Jess would send our notes and I'd look at them be like. Oh, these are the same notes like th.

C

That was really easy and it wasn't ever. I was never worried that we weren't saying what we meant. You know I've seen that before, where everybody's being a little nice, nice, nice and it's like, but this is hurting progress, so I thought that went amazing.

C

Nathan you've got point four.

D

Yeah, I never thought I'd say this, because I don't like a lot of process, but I really like the daily stand-ups um I feel like they kept me accountable and, like I'd, look at what I said, I was gonna work on that day and then did I complete it and then what carries over anyway and it was nice seeing what everyone else was up to as well, and I think there's a lot of collaboration on on other people's posts about what was going on so yeah. I think I'm in favor of them.

D

I don't know this is something we want to roll out, but tyler doing that.

C

Did you like you like it through the way it was done through that uh geekbot? Is that specific yeah.

E

C

I'm gonna put that into action items.

E

I I love geek, but I I like stand-ups, I mean I I do stand-ups myself right like I have like. uh I keep like my notebook and I do like here's.

F

E

I did yesterday here's what I'm doing today and then like when I come back to my it just stays here and I like log on I just like see.

E

I have like a long, a running narrative right, which is really helpful for me for like me personally about my own work, but I think that the daily stand-ups for a team, like one you communicate out your narrative of like here's, what I've been working on, where I'm going and like what might be challenging or like where I might get blocked and then two you get visibility into other people's narratives and I think that's really helpful and I think that fostered a lot of the collaboration because we could like flag and adjust and like and um like.

E

I don't think we should do daily standups on zooms. That seems silly and superfluous and hard to collaborate hard to coordinate. um But geekbot is perfect because, like hop on it's on slack um and like it asks you the question, you don't even need to remember the things to ask, and it reminds you what you said yesterday, so I usually just sort of like go from there and it takes like five minutes. So I think, like you, know strong. Yes, I would love michael.

E

If we like you know we do the weeklies and, like I'm glad we or even like every other week. I think it's like right now. We have stuff like on the friday in the middle of an iteration and like I think that that is like it's just not enough for me right. I I even forget that we do when it comes up. I'm like oh yeah. I guess it's that day, huh like um I think that, like the the value of this goes up tremendously uh at the daily level.

C

That's really great feedback, because I had that, in my mind too, it's like every other friday like does this feel like more work to remember, whereas it's one of these illogical things where it's like well yeah, actually doing it every day, is less work, even though you're.

F

C

Every day, maybe we take a friday off, maybe it's like every day but friday. um Just because why not, but.

E

You can also tell the bot like I'm out or like, or you or use previous day's response is one of the default drop down options. So, if you're like stuck in a holding pattern, you like don't even need to type it out again sweet.

C

Okay, great feedback. Thank you. Yeah.

D

I was going to add on to that. We did daily stand-ups uh my previous position and I know for a while. There was like almost a bit of stress and that you always felt like you needed to have something, but as soon as you realize that it's okay to say, like I had a quiet day or I wasn't able to do everything, it makes daily stand-ups not as stressful, and I don't know just no obligations. I guess to complete, like a laundry list of things every day, 100 quantity over quality, yeah tyler.

D

Do you want to take the next one.

E

Yeah, um just I like shout outs to everyone who like joined the team, um like I don't even know who all joined the team and when because we were so busy in the middle of stuff that, like it just didn't like surface the way that normally new editions do- um and I think that like it's, I imagine that it's a unique challenge to like join the team, with a lot of like onboarding process in and of itself to do it remotely and to have like everyone who's already here being like.

E

Oh hey, like I'm super busy right now, like you know um so, like I, I know a lot of people who who joined in like I saw also doing like really critical stuff. um I for I, and I've actually forgotten, I'm so sorry. I forgot who did this, but someone like uh added like fixed the search bar in middleman, whoever you are like raise your hand, um because it was really good, because I like got a merge conflict on that file. I was like oh who fixed this.

E

I was like oh great, like someone who's like kind of new, um so great one great. Thank you for doing that, but two like multiple things like that, where I was just like: oh yeah, there's people here and they're really contributing, and then you know, of course I think, like miracle, I think you joined it like the day before the launch, but I think it's also great that you like were super self-sufficient, like I don't think like I, you know, I think you being able to like get started on your own.

E

While we were all like hey like we're doing something else for a couple days, can you give us a minute? um I think that's huge too, so just shouts to chefs to everyone um and yeah uh my gosh you're, not about coffee chats. I I agree like I feel like. I also feel like I. This could be in the like things to improve on thing but like I also wish that I knew like I had taken the time to like say hello to new folks like more personally than just now.

E

So you know like please like drop stuff on my calendar.

G

Awesome. Thank you.

A

I think I have the next one: um yeah release went great, um but so did after the release. You know we kept the momentum going up and we had a couple of different epics and I think barker led the charge on that and made sure that those were getting actioned. um So I'm I'm really pleased with that and keeping like we didn't just stop working, even though we had the day off on the friday. But after that we didn't just stop working.

A

So thanks to barker and the whole team, for you know, keeping the pace going.

A

I see tyler typing as he is.

E

Yeah you put yours in, and I just like- I uh michael I talked about this like last week or something about how awesome having a new layer of management has been and like again same thing of like wow, amazing job, doing it during a very like busy project.

E

um But I noticed the same thing where, like I think something we have struggled with for the last year of my recollection, is like a little bit of like delegation and coordination and like things coming up and then sort of like going out into the ether and like either people like superheroing them, or it's sort of like getting lost in the shuffle and like with all of the feedback and, like you know, things that needed to get fixed up and stuff. um I didn't see that happen.

E

The way that it could have happened without the folks like either like barker, getting like into the new management role or like justin, and feels like coming in, like I felt like I just like it just felt like there was so much more structure there to like help.

E

The ics do what they needed to do and like know where the priorities were, um and it like takes a whole set of considerations off of ic brains right where we're like not trying to figure out like we're not trying to suss out priorities like every single day, like, of course, we think about it. But now maybe more on that daily, we can say, like hey, like someone else knows the priorities, let me go ask them for a shortcut real fast. So um thank you to everyone joining that line of management.

C

Plus one um I added one more thing: just yesterday we had our first community contribution like someone on twitter added a small line of code to make the little scrolly thing uh on the home page animate a little bit- and I was just like I'm so excited about that, because it's little but like it starts things like when we're seeing these kind of things. If, if I have, I don't know in this parallel world where I would actually like be a hard ass about deadlines.

C

If I said this needs to be done in one hour and then you said, this dude gave us this code, I'm not going to do that in one hour. I'd be like great priority like I. I would love to have more and more and more community contributions, because I just think it's so core to who we are as git lab and I've wanted this for two years and because of the amazing work we did. It drew that attention. It's that pull of our core user.

C

We're excited to like write a tiny little bit of code like they. It's not just the fact that it was one css transition, it's that they looked at it and then they had a thought like they were inspired. They went. Oh, this is cool. You know it would make it cooler, that's amazing, so I I think that's just that's like the cool it made my week.

A

I think we can jump into things to improve on. I think parker's got the first point.

B

um Yeah on thursday, like at three after that crazy launch popped into slack, was like, oh, my god, the web id button like, let's fix that, and then I woke up friday morning. I was just like. Oh, I shouldn't have done that. That was bad because I tagged laura mateo and it was after hours for you. It was thursday evening you were out and done and we had friday off um I'm. So sorry, I felt really bad about that. I shouldn't have done that.

B

um I think, having a process for giving guidance on when there is an issue that does require after hours. Work would be awesome for as like management to like check yourself like okay. Is this critical enough to like start tagging, people and then also who you can call on during those off hours? um And what is you know so you're not just picking people by random? I guess that's all.

D

Yeah, I'm just gonna echo that, but I I think specifically there was a fastly blip that happened. I think a couple days after or a week after release, I know tyler jumped on it, but again it was like after hours and then it made me realize samus lauren like do we have a process for this like if the site goes down, god forbid, like at night, what's happening, is it the first person that jumps on slack finds that's responsible like yeah, I'm not sure tyler? I know you want to read it or continue.

E

We don't have a process um right, like I think it's like it's clear to me that there is, or my understanding is, there's no process right. Maybe there is one, but if there is we don't use it or it's not a clear process. um There are like support processes in the broader organization and like often like the like impact like like, like fastly like, like vastly, wouldn't really be us anyways, because, like we're, not the only people at the company that like use fastly and there's like an infra team- that's like on that.

E

So if fastly goes down like the infra team knows about it because, like like gitlab product stuff, gets served from there right um but like we don't we don't have a process for stuff. That is us. um We, it sort of just gets caught and like ad hoc routed, um I see that michael's not support michael has a no.

E

I fear that, like he doesn't want to go on call, um but like uh so like I basically my comment was going to be like I, I don't know if we need on call, it does seem like. Maybe we've hit a level of maturity where the expectation is that, like there is someone who has like domain expertise about the marketing site and like is available anytime, like other people at the company, need them to be available for um and like.

E

I would raise my hand to be part of an experiment of that, um because I think that, like on-call rotational hours actually match my sleep schedule really well. So, like that's cool, um but I I don't feel strongly about it other than like. If, if we do nothing about this, I think the answer will always be will continue to be that we only have an ad hoc process, and I think we just need to like understand like how important it is to have better than an ad hoc process.

E

It may not be important at all, and I feel like michael, is probably saying like in his next comment. That is not that important.

C

um No, I I agree. It's important. I guess like where my head goes. Is anybody gonna die no, um probably better to sleep, then uh I would rather see some kind of like alerting system so that we're aware. So it's not a surprise.

C

um The only reason I imagine we would ever need to hop on outside of regular hours if the site's down and we took it down, but usually, if the site's going to go down- and we took it down it's because we've done a thing and pushed it and it went down. So I wonder if maybe, instead of on like person, could we operationalize it and add some kind of documentation to the handbook that we can build upon? That's like usually if x is happening. This is the reason here.

C

Are the steps to rectify so we're, rather than us, being the solvers of, what's typically not overly complicated, we're giving people the tools to solve their own problem that way it takes the um effort off of us. What do you think there tyler.

E

um I think both an alerting system and a process require people like human intervention. um I don't like. I agree that that generally they're simple fix it like either.

E

It's like a complex fix that, like shouldn't, take us by surprise or like we would need days anyways right, like that's a catastrophic scenario but like just in that case yeah, maybe on called you know what four hours if something's, like you know, worked all the way down, um but for like in a learning system or process like people need to intervene, and if it's like, I think it's a fair assessment to say that our ecosystem of like projects are not straightforward and like are challenging to like keep all the threads together.

E

um The people most qualified to do that and intervene are on this team, and I would like I don't know I like it like. I don't know if it's sufficient to have a self-serve option for like the things we are primarily responsible for being like having downtime right beyond beyond, like small, like service blips of like third parties and stuff so um yeah like I I I would be it.

E

Obviously, it wouldn't cost us anything to start where you're suggesting michael right like it would be slightly better and that's iterative, um and I would just I would predict the future that it still would not be enough and that we would maybe find ourselves in this position again and asking like. Should someone be around to field the alerts.

C

Laura, I see your record. Can you speak to that.

A

Yeah um I I agree that you know on-call is great when um there's a lot at stake, so, like our large release, our ipo release, um maybe for those large releases, we do have some setup where um we're we're available for the evenings, the couple of days before and after a large release, um but otherwise I see a you know kind of a I'm worried about people abusing having access to us all the time.

A

um You know if people think that their thing is the most important thing and I'm getting pinged at midnight because because of whatever you know, um I I don't know that that's necessary um and maybe that's where just having the documentation for you know how to escalate. Something um might be helpful but yeah, maybe uh on.

C

A

Like such a great idea,.

C

Laura, I think that that nails it like uh tyler, you you're, also right, like we had an alerting system, would someone have to know? Maybe it's uh we can move on I'll, put it as an action item, but in my head the alerting system would be like it just posts, a digital experience channel so that it communicates like this is happening and we're aware and we're also not worried. You know just just so that people don't think they're like oh everything like we caught this thing and they don't know about it. It's like no.

C

We have visibility. We know that we know what's happening and we're on top of it um but yeah I'll add this is a great conversation. I'll add this to action items.

F

um I guess for mine I'll try to keep this brief. I feel like I could talk about this for a while, but um I'd love to see more, uh not like hard set focus but more of a mindset with like accessibility in mind um when we create things or or update things um as a team, I feel like we missed a lot in this big release and, honestly, I think that's just probably because of the the tight due date.

F

I don't think anyone probably went through anything with a screen reader and but now we have time to I'd love to um change the way. Maybe our definition of don is on some on some things, but um I know here at gitlab we're uh wcag.

F

Okay, I gotta know people say that with my wisconsin accents, what keg um 2.1 double a uh and like what the heck does that mean? There's a lot that goes into that um I created a little spreadsheet, there's a link there that has um the guidelines that fit for a and double a in that standard and like, admittedly, that stuff does not make sense. So each guideline has a link to the documentation of what it all means.

F

Admittedly, it's a lot of text and it also doesn't make sense, and um that sheet has a another tab with helpful links. My favorite links. I have these bookmarked. The first two are like aria label documentation.

F

So if you're building something say like breadcrumbs or a tab mechanism, they have like literally what you should do like make this div and give it a roll of tab panel, and um it's really really useful and we all have, I think, for the most part max and that's a simple command f5, to turn your voice over on there's also some tutorials in that sheet on how to use that, even on your. If you have an iphone um how to get that working.

F

But I know we have the dec x tools and google lighthouse available, but and they are really great tools to get started, but those tools, don't necessarily tell you everything. You need to know about your content if you're trying to portray something as a tab, axe doesn't know that, and I can't give you pointers really the only way to know if your content is being shared.

F

The way you want to to everyone is, if you roll up your sleeves and turn on that voiceover and give it a shot um so and like when it comes to accessibility.

F

Like I know when I first started, I just thought like: oh yeah, you just gotta, add alt tags on an image and you're done like no there's so much more. That goes into that, and it's definitely you're never going to get it.

F

100 perfect and everyone is probably on a different journey and learning what accessibility, accessible design or development is, and I think, as a team, we could really collaborate and and share what we know, um and so, if everyone loves this or likes a sheet, uh it would be great to maybe take a few pages every few months and audit that and make issues from that.

F

I'm happy to to use the sheet myself and record myself going through like the home page or something and like how I would use it if that's helpful, but all right, I talked a lot um laura. I saw you got a note on there.

A

uh Yeah, I we created an epic the other day or parker, created an epic and then mark, and I have been going through kind of chipping away at some of these um issues. I created empty issues just for each of the kind of page neighborhoods um to run acts on it and then do the fixes that it says. But, like you said, it's not comprehensive.

A

It's not going to be perfect, um but yeah we're trying to go back and and help fix some of that stuff, but definitely would love more eyes and screen readers on on that. I think tyler's in there next.

E

um I think uh I I think this is a huge opportunity for us to find improvements. I think also- um and it's not just accessibility too right. There are, like particular like um there are other web standards and conventions that uh we are in violation of that are not like legally binding.

E

The way that accessibility is um but are like conventionally wrong, um and I think I think, like the thing that would um part of, I think, the approach for accessibility and these other challenges that we face and, like things that we ought to correct, is um you know moving forward, since I think we'll probably have a little bit more like breathing room on on some of the deliverables and delivery timelines.

E

I think there's like this step of discovery, phase between design and engineering, where, like I feel bad when, like the requirements that I read or interpret, are like, like, I feel bad to say like saying no, especially when it's like okay, now, it's time for me to do so. It's like you know we kind of have to say like okay, the answer is like yes anyways, even if maybe the answer should be, let's find something else, and so um I I would just I would love to see.

E

I hope that moving forward, we have a little bit there's like something between like design engineering, where there's like a like, like a spike right like if you, if we do like agile terminology like a spike branch, other thing where we grab a design, we have our requirements. We do our best to be faithful to the thing and then we find because it's hard to anticipate all the time like, oh like like. Oh you want it to work.

E

This way turns out, there's like like there's, actually a limitation here hard to anticipate, but now that I've given like a couple hours on it, I can tell you and then we can find a solution that works for us um and we can like get to a better collaborative uh solution there. So- um and I think, except like this- goes accessibility and other stuff too,.

E

uh Lots of no vocalizations of people saying stuff.

C

Maybe I'll just uh share to wrap um this part, so we're establishing a legal requirement that we do meet um double a standards we currently do get sued, because we don't um the sad thing about the world we live in. Is we could um model out what makes us more money, fixing, accessibility or continuing to drive the improvements that we make and fixing accessibility would lose that doesn't help real people in their lived experience. So making this a priority is an important thing for us.

C

um I added to action items um nominating megan and lauren megan and laura to lead this effort, because from what I'm hearing, I think both of you sound well informed and also like passionate about it and just for what it's worth. I think um I think at two things regularly. I think accessibility is the thing that our generation of like digital makers, is going to look at when we're older and be so embarrassed about how we treated it.

C

And I also think that, like the generation of people in elementary school are going to look at people who don't know how to code like they look at cave people and be like what. So. I think those are kind of like related like understanding what living in the digital realm looks like and how to be um like inclusive.

C

Laura I see added or lauren, I see added a link there, so um let's just keep it moving, I'm looking at the time here, um I think we could have provided clear information on requirements. I hate the term requirements, it sounds so boring but um like- and I don't like the word- creative brief either but adam and I talked about it and like sometimes, let's just use the boring words because it gets across what we want.

C

It's almost like the day we released, I was like we should have a creative brief or like we should have a brief to give. You know when we're asking adam for illustrations on whatever it's like here's like here's, how much we want to skew to doing this and then like some brand, like just helping set up the people. We're asking things for- and I know adam has the start of some issues and then jam three gave us that google doc of requirements.

C

I think we could get that even um a little bit more better, a little more better. So I added that to action items to do.

C

B

Yeah, I just had a comment like how do we avoid this becoming extra work, um such as like some of our issue? Templates are very verbose, and sometimes it just feels like extra.

C

Work, um I I it would be a new issue template I, the term extra work. I feel like we're offloading the work to other people, so the work exists like it's there. The the clarity is needed. So by not having it sure we are not doing extra work, but we're making monica do extra work. So I think like can we meet in the middle like we could even do this collaboratively? I think that's how it'd be the strongest is hey. You know we're get. We need these illustrations.

C

Adam tells us like yeah, okay, uh vic's gonna be available, we take a stab at it and then we go like hey that. Can we collab on getting this to a place where we're both clear that that kind of starts? That's what drives this right. That's what starts that um cross-functional collaboration.

C

um Cool, I see some notes on four, so I just noticed I mean this could just be a personal thing. I just got a little squirrely when I saw a bunch of time off around the delivery date take time off and that's not what the sentiment is. It's just it just made me feel a little squirrely. um We've got this big thing.

C

um It got a little quiet uh that could also be a perception thing. Tyler. I saw your your comment like a lot of this conversation could be happening in zoom calls um again. I think it might just be the nature of working remotely like if we were in a place, you would see all the activity I just wanted to call it out, like I think, if we can increase the visibility of like everybody doing stuff, that energy feeds feeds our souls and like knowing you're in it with people.

C

um I don't know, there's just something there and again. It could just be me, so I just wanted to mention it.

E

You said no actually necessary, but, like it sounds like you still want us to do something, so I just like like do you want more in slack or or do you want no change at all? I guess like that. That's that's! What I want to clear up is like I.

C

E

C

Maybe no action, just um it's in your head now um that uh it's it's about visibility. It's about perception! It's about like.

C

When I know that I'm at like barely able to make it- and someone else is also there with me- um it just helps me and again that could just be a personal thing, but, like I really do mean no action like I just it's a recommendation that if we ever get in the again, which we will uh being able to look to your left and your right and know that like see that the people are there instead of having to take the take, the action uh to be like are you there um again is what it is, could be.

C

A uh feedback from one person.

G

um Maybe it'll.

C

There's other comments did anyone else want to jump in.

G

I want to just vocalize my point um that we had split up our slack channel into squad groups that maybe you weren't added to those groups inside slack, so.

C

Probably you didn't see.

G

A lot of a lot of the work for uh squad two um was happening in that channel.

C

Cool, well maybe that's just a visibility. Yeah.

G

It's a visibility.

C

um Tyler laura did you wanna um vocalize yours.

A

Sure, yeah yeah. I think that the pto wasn't didn't seem like a problem, but I was on the squad that I don't. I didn't notice anyone taking pto um so, but it seemed like all the work was really covered.

A

Well, we, you know we had check-ins and made sure that, like anyone who was on pto did they have work that needed to be completed and could someone else take it so, like the coverage, I think, went well um so there's that jess, oh um yeah, just I think it all went well in the end, I don't think anyone's pto really inhibited our progress and I think because we did do so much work. I know a lot of people were working overtime. This quarter that pto was kind of necessary, at least for me.

A

I felt like it so.

C

That's all yeah, I think it's definitely a great pto is is important. um I think for me, like the to put a sharp end on the point. It's like around the deadline, that's what caused me concern and um I think, out of when you're working on salary, there really isn't a concept of overtime because it it balances out, and here with unlimited pto.

C

I think it's pretty pretty easy enough to get into your like 9 to 5 40 hour punch the pay clock and if you are, I get notices from pto by roots, and you know that I'll get on you for not taking time off.

C

B

Yeah, I just put a comment in there about the pto roots. I love the um when you can task either a channel or a person for coverage, it's kind of annoying. Sometimes when you see like you know it ought to respond everywhere, but it it does really help. The reminder really helps.

B

Yeah, um I put a to do there for me to investigate how we can better have that communication for our contractor teammates, because they are not in pto routes, and so all we have is google calendar at this point.

C

Sweet nathan.

D

Yeah, um it's a tricky one, because I know we're kind of scrambling to get things done, but uh we didn't really follow our cutoff date um per time. We ended up, I think, merging it in with changes within like an hour, so I would prefer in the future. I know it's not always possible, but let it sit for a bit at least on, like a stable environment, on the review app without changes for like a couple days. um I think we got pretty lucky. I'm gonna be honest that nothing major came up.

D

I know that we've been working on it and we're always involved, but gotta be good to be lucky though nathan yeah, I don't know I've seen a lot of releases in the past and this one I was shocked by how smoothly it went, but I'm proud it did.

D

I just think one step we can make is just making sure we have a clear cutoff date.

D

um I'm not saying that we don't do the work. I'm just saying like totally.

C

D

C

We had in hindsight I was like cool. We had less than 24 hours of soft lunch, usually one a week.

C

Conscious of time, we got two more points here: tyler.

E

uh I think it's in this last retro, I just um are we splitting I, like it's cool, to see everyone's face. This feels too big for me, I I need smaller meetings. I think personally so like are.

F

E

Are we doing that uh in the in the future? I don't know yet cool okay. Well, I hope we do. I would you know toss my hat in for like smaller meeting sizes with with the groups.

C

We'll get that figured out jess.

A

um My point goes a little bit back to what you're talking about earlier, michael with setting up requirements up front, um but specifically, like you know, the brand team works one way the coffee team works one way jam. We worked on the way we work another way and I feel like there's a bit of chaotic chaos and like trying to figure out what the single source of truth was, because we never like really sat down and said: okay, we're going to use this drive for these assets and this stock.

A

For that thing, and so oftentimes there's like three different sets of things, and sometimes you didn't have access to the thing that you thought you needed. So I think just setting up those things in advance would really help us all like be on the same page and you know cause less like.

A

uh We do the same work over and over again again with the reasons.

C

Yeah I hear that I think uh I'll put it down into action items, but in the kickoff phase of a project it would be good to proactively say like how we work together ways of working to try and get that um tighter, and I also think that nature, that's the like training of the collaboration muscle, it's like the nature of doing it more. We learn how other people work and get closer so being proactive from the start and then continuing this interlock process. I think, will get so much better.

B

I uh I'm a strong opinion of git lab issues and mrs is the single source of truth. I see jess writing there. I say drop a link to that. Google drive in the get lab issue drop a link to the figma in the get lab issue, um but that will require the other people we work with outside git lab to adapt their processes. So um I can see how that could be challenging.

C

C

I get how like we will. I will continue needing to make things like that roadmap scan charts, because that's how executive leadership thinks but like when it comes to being in the work it's like. This is not helpful.

C

All right well we're over time um we've got some great action items. Anything we've missed anything on anyone's mind.

E

uh Logistics are we doing so we have off-site next week um and two questions. uh One. Are we doing sprint planning on monday? Still? Okay, we are all right, we'll.

C

Do it like a quarter quarter, q2 kickoff, sprint planning like we'll, keep it light. You know the sprint will be lighter because of off-site because of like upcoming time on all this kind of stuff. But um yes, yes and yes,.

E

And then um other than that personality assessment thing, which I still haven't gotten yeah.

C

So I'm glad everyone's here uh craig is doing that for me, so I'm giving him time to not bother him because he's got a thousand things to do. But if I don't hear uh from him by the end of today, I'll hit him up. Okay,.

E

Other than that is there anything that you want us to prep for or should we come like blank sleep.

C

um You'll hear from phil's of justin and lauren shortly on that.

E

H

Big smiles also uh just for visibility. I will be taking a week on july, going to texas for a family wedding, yeehaw.

A

Okay, stopping the record.