PART I: TEAM UPDATES
(Scott) Hey Daniel! Hey Eric!
(Everyone) Hello!
(Scott) Welcome back, Eric.
(Eric) Thanks so much. Yeah, it’s great to be here.
(Scott) Hi, Virginia.
(Virginia) Hello!
(Scott) Alright. Let’s… Let’s kick off.
I wanted to start out with some reminders.
First, we have a book club coming up on Inspired in 4 weeks on August 7th.
I just reread it myself, it’s um… It’s a good read, it’s highly aligned with how… I think about Product Management and does a good job of explaining why some of these things are important that I also believe to be important. So, it’s nice to have another voice explaining all of that.
So, please do read that. I think I’m gonna… update the new hire onboarding doc and ask all new hires to read this as well so that… Everybody in the team is on the same page
with respect to this book.
Let’s see. Reminder B, remember there’s this interview spreadsheet CS and Sales have populated that with the number of customer contacts for meetings. Please do follow up on that. I want to ensure goodwill with that team and and follow up promptly with meetings with these customers so that that team can see that we’re taking advantage of it.
Third reminder, we’ve got a little engagement survey. I’m gonna run this once a month in Q3 just to take a pulse given all the change going on. Please do take a minute to fill it out, it’s five (5)…, you know, quick questions and then one free forumwhere you can share whatever feedback you have.
Fabian, I didn’t receive it.
(Fabian) I’m pretty sure I went through my emails…
(Scott) OK.
(Fabian) Maybe it’s on my end but I’m happy to fill it out …but I haven’t…
(Scott) You didn’t get it. Need to get it to you.
Alright. I will um… I’ll ask Jessica to resent that to you. Anybody else in the same condition where you did not receive it?
(Katrina) I don’t recall but is there way to put the link to the survey in the agenda?
(Scott) Well, it’s personal. It’s umm.. It’s tied back to your User ID so we can track which team you are on and that kind of thing, I do believe it’s anonymous but… nevertheless everyone has their own custom ID so I’ll ask Jessica to send it to Fabian and Karina.
Anybody else?
(A male employee) I just… I hadn’t seen it, Scott but I searched my email real quick and it looks like that’s the title of the email so if you just search for that in your Gmail
you should be able to find it if you got it.
(Scott) ‘Pulse Survey’. Anybody else didn’t get it please ping me.
Alright.
Next reminder. We need… We have a goal of at least three customer interviews per PM. There’s an OKR issue out there. If you have it updated lately, please do so. And… remember we have three weeks until Q2 to hit our goal, so please do invest the time to get those set up and get at least 3 done if you haven’t already.
PART II: HIRING UPDATES
(Scott) Alright, some team updates.
We hired a couple more PM so we got a good rhythm going on hiring. We hired Gabe Weaver, but we have a really strong candidate for that 4th slot so we’re gonna target Gabe for our 3rd Manage PM. That team is to be defined but bottom line we’re gonna have a 3rd group in the manage area and Gabe will lead that.
And then Dov Hershkovitz, we just hired him as the API monitoring, he’s got a great background in monitoring and has most recently been at Elastic.
So thank you to everyone who’s been involved in the hiring loop.
I know it’s taking a lot of energy from everybody.
PART III: DISCUSSION ABOUT THE UPDATES TO THE HANDBOOK
(Scott) There were a number of changes. But, before, the handbook basically read that internal feedback is worth ten times more than external feedback. And I understand why we want internal feedback. Because of dogfooding and using our own product.
It’s… It’s a great channel for feedback. But I think it was sending the message that
customers weren’t nearly as important as internal opinion and both Christy and I
want to move off of that position, like, we should be customer first and treat our own teams as a customer but let’s… I don’t want people to interpret that our own internal opinion is worth 10 times more than a customer’s opinion if that makes sense, so it was mostly language wherever that showed up in the handbook.
PART IV: TRAINING PLAN
(Scott) Customer training, Discovery training’s coming soon. Sarah O’Donnell and her team, we’re gonna do a bunch of… sort of quick videos on a variety of customer discovery topics. Super excited for that.
They should start dropping any day now I think, starting this week.
Description is on our team page as well.
PART V: A TEAM MAMBER HAS A QUESTION
(Katrina) Hey Scott, this is Katrina, just want to add to that if you don’t mind.
(Scott) Yup.
(Katrina) I think this has always been a challenge in Product even before I joined Gitlab. For many people, how to get there on some of this terminology when those of us have deep technical background.
My thought would be is there a way that you can start sharing, you know, or applauding
good examples of this so that the product team can start to kind of ruminate on this and develop that skill if we’re not there yet.
(Scott) I’ll check those out. I’ll look through
for some other examples. Thank you for the suggestion.

Leave a comment