 All right, the church bells are ringing at least here as I live next to a church Welcome to October 1 and welcome to the product functional group of date And I have a lot to share today, but I want to keep it short. So I'm gonna get started right away If I can move to my next slide, there we go so recently I sent out a product survey and the reason for that There are various reasons for that I got a bunch of feedback from different people and it gave me the impression that We need to work on our communication within product and other teams So I figured well if I just send a survey I get a lot of voices from a lot of people and then we can Probably look through that so that I did and today I will present you the results and conclusions and actions we took First off everything that I will talk about regarding the survey you can find at this link handbook product and survey Everything is summarized there and every question. I didn't don't answer in this presentation We've answered there at least most of them think the best method. So first quantitative outcomes there were 64 responses, but 40 from sales sales was the primary target group so that is very good to see and I asked the number of questions. It's but there were four core questions The first was what is the best-selling feature of good lab and most people commented about CI being integrated with SCM and then directly followed Having a single application for the entire life shot, which I guess you could combine together and over for people that said well Just see SCM and then over a number of other responses, but this is a pretty uniform Response the second one what feature change our customers most excited about and Interesting here with quite a large majority security features were mentioned as number one second to net at the shared second place were Everything related to project management. So issues portfolio management and CI third Kubernetes with much less votes and then almost every other feature was mentioned here as well, which I thought was Quite fun. So customers care about all of the things we're building and then What are we not working on today that we should be spending more time on I asked and The plurality of people said we should do more in terms of issues more to compete with tools like Jira Second people said more in the core part of good lab SCM code review HA was a number of time and again here almost every other feature was mentioned as well I'm getting back to this these answers in a bit And then I asked like what should we not be doing? Or what are we doing and it should we be doing and Luckily here, there was no consensus. So there's not one thing that we're clearly doing wrong But there were a lot of interesting opinions of a lot of people said well We shouldn't spend time working on things that have a clear established market leader currently So I spent less time on X where X is like your security tools or anything else. There were a lot of things mentioned here The interesting figures, of course, that's how get lab started right when get lab started There were already established competitors both this SCM and NCI and look at where we are now So that's what I would say to those people A few people said we should stop doing more breath and some people said we should stop adding features to core and starter And I'm happy to go into detail with that those things at another time or with those people in particular But to come to the conclusions and to the most important parts I what I see is that there's a lack of insight in what we're building The number one people think people said about what should we do be doing more of we are not is issues of project management We're investing a lot of time in that So why do people say that it's because We're not aware what we're building To a lot of people gave me feedback in between the several different Questions is that it's unclear on how we make decisions and third is we're not consistent in giving feedback and Now I'm going to walk through those three and tell you how I have addressed them how we are addressing them within product and engineering So first off, there's a lack of insight in what we're building The first thing we did is I we created within project team Separate direction pages for each of the devops each for the categories so each for the devop life cycle stages So if you go to direction slash manage direction slash plan, etc You'll find a single page with the vision for that particular part of kid lab So if you were to go to direction slash plan, you'll find exactly how we are competing with tools like zero We also made it and this is Already for a while, but we keep improving his page We make it very easy to find which PM is responsible for what and we keep simplifying this page to make it very transparent and easy Define that on our product handbook categories And the next thing we're going to do is we're going to do FG use per product category So that means that we'll have one for Manage we'll have one for plan and we have one for create so that we don't have overlapping content But also we actually talk about all of the content rather than me summarizing Everything here in one color for is it which doesn't make any sense, right? I'm already over time and I haven't even addressed any features in kid lab So this was the first action on both improving the insight in what we're building To it's unclear how we make decisions This is a very fair point and I get this a lot and what I used to do is I would address it here in a functional group of dates And I would give you a vague answer because there is no hard and fast answer that covers the entire product However, there is a hard and fast answer for what each individual product manager does And what I asked every product manager to do and they have done so is to actually edit that To their direction page. So if you go to the direction slash manage, you'll find their prioritization process and it'll say how Jeremy makes his decision how he prioritizes things And that goes for every p.m. So for every category every depth of state you'll find it there And then the third one is that and this is more an observation that I made we're not consistent in giving feedback and What I noticed is that some people sent a whole bunch of feedback at once for instance It had the top 10 list But then if I were to go into the top 10 list into the issues I there were no Salesforce links Some people would tell pms directly and that's always fine um But some people would only add a Salesforce link and nothing else and feel Yeah, not not happy that Maybe they added the Salesforce link and there were thousands and thousands of seats for that particular feature And it was not recognized by the product manager. So that's a problem. It's a problem that goes many many directions um And I think that's something we have to continuously work on but the first thing is If you want to give feedback, you're not sure or you feel like you're not being heard immediately contact the product manager or me like Our number one job is dealing with feedback and making that it do something great right and building something that our customers want The second tip is we have to maintain a single social truth If you have any feedback and you know where the issue is Throw it in the issue If you don't know where the issue is just ping the product manager and they'll point you in the right direction Or they will do it for you And third is let's keep it up because We do get a lot of feedback which i'm very appreciative of and I love to get it in any way shape or form So please giving us feedback. Um, don't wait for me to ask you don't wait for another survey to come by Just keep giving feedback and so far it's been amazing I think this is the one strength of kid lap because we're so so transparent We can process a lot of feedback and we can do a lot with that So Eight minutes not as not in five minutes But that's what I wanted to share for today Let me know if you have any questions and for the time that there is no questions I will go through this list, but you can speak up or add them to chat whatever you want No questions at all about any of the product can be about anything doesn't have to be about this can be comment concern criticism I will walk to my things at least Oh Simon says Can you see us getting closer to microsoft tech wise? um That is a great question That's also a ginormous question because microsoft is a many billion dollar company That buys a billion dollar companies. So will we get closer? I think in terms of like our DevOps product versus their DevOps, right? I think we're ahead. I think we're ahead in terms of usability I think we're ahead in terms of features. They do offer a number of very interesting things In particular for microsoft platforms Um, do we want to get closer to that? Yes, absolutely Hey job I think we've lost him Microsoft microsoft question break took him off Just to say that and then I'll give you some more time there. I see there's bill. You've got a question about PIV and cac. Can you even elaborate what you mean by those? The best time for the power to go out. Oh my Hi Was my last word microsoft because that's just beautifully poetic So job, so I think um, the question was in terms of Partnership I suppose so not are we getting closer in terms of feature parity But are we going to get closer in terms of building upon microsoft technologies? Yeah, I mean in terms of Building for their platforms or at least allowing for instance you to run windows runners these kind of things Okay, um, I'm not going to say the m word again because apparently the power in my house will go down if I if I say so Simon the answer is we do want to support the platforms better. Um, it's not something I think we're going to do in the next Quarter or so but in general it's a huge market So we do want to be close to microsoft in that sense I hope that answered your question because my power went out a number of times while you even while you asked it I missed all the other questions from chat because your zoom chat gets wiped So if anyone could copy paste them back into the chat, I would much appreciate them Thank you very much Simon Will this be a recurring survey from joe? Yes Uh, I'm not sure about the frequency at first. I thought I would do it every month. I'm worried that Um, it will get stale that people answer the same question who are stopped answering Uh, but yes, that's my intent. I also hope to streamline it a bit And I would do quite some effort Melissa says thumbs up to fees code plus extension by fatty. Yes I highly highly recommend you try it out fatty made an incredible extension for official studio codes Um, it's really really good. And I think it's the best way to Today use if you use an external id and not the key lips with ID Um bill Duncan s. What is the support for? Piv is a cac authentication in 11.4 I will defer to that to jeremy who I'm sure will leave something in the chat What other customer information would you find useful to be added to the issue as john woods user account product purchase growth potential Yes to all of that today we can do that without making an issue confidential That's why victor started looking into confidential issues. We're also looking into integrating sales force more closely or doing something similar Um, every all information is useful. Um, just be aware that for now We only have sales force links because all issues are public And the trade off is too painful, right? We can't make issues confidential because then people can't contribute anymore Um, you can also always just share it directly with the product manager And they should reach out to you as well the way if they can't access the sales force links John may ask what do you think of microsoft's new offering as a competitor? Um, yeah, it's actually interesting So they did rename an existing product So they had vsts, which admittedly is a terrible name and as your dev ops is a much better name So they renamed it and they reskinned it. So it's essentially a rebranding So it's the same competitor as we had before and they added a few bells and whistles to it Um, which are very interesting I think there's one thing one notable thing is that we don't do is they offer runners for mac and windows So you don't have to set up your own and you could do that with github now set up your own But we don't offer them out of the box and I even give three minutes for that That's very powerful. I think that's very great. And I'm we're looking into ways to to compete better with that John woods. What other? It's the same same question. That's great And lucas says, yeah, I was sad. We don't have macOS runners. Uh, yeah But we do plan to do that. Like we know that there's a big market. It's uh, It's a it's a challenge to do Sorry, our pms balancing breath and depth over the next year. Well, I'd actually added that to my slide here It's a balance. I think that In 2018 we've been very very aggressively pursuing breath. I think that in 2019 um One thing we're trying to avoid is to a yo-yo, right? We don't want to go breath depth breath depth and they get like Tick tock kind of situation. We don't want to do that. I think what we're now learning is we're Going balancing a little bit more towards depth Um, whereas before maybe it was 80 20. Maybe we'll now be 50 50. Don't bring me on those numbers. They are Made up, but we I do see in our plans that we are doing a little bit more depth, especially for q4 If I look at what the teams are doing, it's all like Stuff that customers really want depth that customers are looking for Uh, we're quite quite laser focused on that. So I'm very proud of that I'm really looking forward to see like the outcome of q4 Um, so the last release that we'll be working on will be January 22nd. So Yeah, that's it will be very good to see. I'm very very excited about that Uh, any more questions before my power goes out again Sorry, why is kid lap 12 march 22nd? Um, so there's a number of reasons uh, To give you the straight answer. I um, figured we should have a major release No, the reason for for march 22nd is One we want to have major releases Frequently enough so that we have opportunities to have major releases where we can deprecate things where the migration can be a little bit harder Uh, second reason is it's a great marketing opportunity So you want to don't want to have a marketing opportunity in like a vacation Like we always see a huge drop in user activity around the holidays in december. Um, so you don't want to do it there And then I don't I prefer to not go into the um X point y and it wears y has uh multiple digits So 11.10 is not a very beautiful version of it because it gets confusing with 11.1 so March 22nd would mean it would follow 11.8 which gives us a margin of one release if Things are on fire and also march is a reasonably nice time to do a major release on this Adam Olson asked another baby. No No Not yet John Wood says we do have to be careful because major releases really scare enterprise customers and they require additional testing. Yeah, it's completely fair john woods. Um, I would say That's why we are spending we're doing eight releases that are not Major releases before doing a major release But like we have to be able to move quickly So that's that's why we do it and in general get labs major release. Especially if you look at like last two They've not been very heavy Upgrades they've not been very very hot and I don't well. I won't I won't make any promises about this one Sorry, what do your emoji mean on their biggest concern? Also, I think emoji plural should be emoji, but the world is a piece of me Um, so there's my major concerns are the first one is train that's on fire is velocity um, I think that's Our biggest advantage that we have a high velocity. We should maintain that. How do we do that shipping small small changes not Putting a lot of weight in our roadmap Um, and just keeping everything going as we've always had. Uh, that's a challenge. The second one is mobile Mobile is a huge market. It's nowadays bigger than desktop software markets. Um, and we're not doing that much yet They're generally github is pretty good for mobile and rci is very flexible So like it cannot accommodate perfectly and there's many customers of ours that have almost only or mostly mobile locations Um, but we can be more proactive about it. So that's that's my concern And our last concern is a little loop. Uh, and it stands for a search I we don't have elastic search running on github with com. That's a big concern to me. Um, because if we don't Dog food or things or drink around champagne Um, that means that we generally are less aware of the good and the bad of it And we're not we don't spend a lot of time Luckily victor spent a lot of time indexing what what needs to be done to get it running on github.com And it's it is a work in progress but it definitely is a concern of mine and I think our biggest competitor In terms of big scm player github they do search extremely well So we really need to level up our game there. Uh, but it's it's going to be Some hard work in the in the coming months to achieve that Looker says so we could use victor instead of elastic search if the index everything that's true But victor has a very cute little son. So he would only work eight hours a day five days a week and We wouldn't have searched or something at the time any other questions Is this a just probably a record for a month of power outages during a call Um, is there any priority making open source projects more discoverable? Yeah, we're actually doing a whole bunch of things there I i'm going to defer to I don't know if andres is on but i'm sure jeremy is to Share some some issues about that, but we have some nice Uh epics about that and i'm such backup generator in your future Well, I have my internet working on a ups So like the internet doesn't go down but my monitor goes down and my microphone goes down So that's that's the problem so all right um Simon says have we got any new plans for picking up community contributions more quickly? I have a call with a customer about this tomorrow um well, I I think Having our community is one of the greatest things about working for git lab, right? Like it's one of our Biggest strengths as well that we have this amazing community So I believe we measure how long we take with community contribution with people dedicated to this. So we are you know We fully intend to be as fast as possible I don't know about actual concrete things we're doing today that would make a difference converted yesterday, but I'm I'm sure that there is something Maybe eric can come from this You might hear baby crying in background, which is a reality being dead and david shared A link to a merge request On git lab to come add community contributions to product priority. There we go That's very good I'm excited Oh, I should have added this to my functional group of days All right, anything else give you five seconds to chance. You can also speak up Did you notice that I added my background? I made it git lab orange goes from git lab orange to white All right. Thanks everybody. See y'all in the deem call