this is the uh weekly product marketing meeting for april 12th so not a ton on the agenda today uh so the one bullet point i have here is have you all seen the timeline for sales plays uh so i put a link i am not to this issue and uh so the the intention behind this one issue i believe was to coordinate across across gtm motions to have a unified timeline but if i am if i'm correct so so ideally this is this is what i would like to see that i don't think we've totally
seen altogether i think we're getting there as far as go to market motions in general and sales plays in particular but ideally for example um if somebody signs you up for a deadline ideally they are a due date ideally they ask you and they say hey can you deliver thing x by this date and then you would say yes i can i i commit to doing that date i don't think that that happened in this case which is why i wanted to raise it the entire group where i think that's maybe some depending on which
go go-to-market team you're on i think that maybe some folks were aware yes that was a date and we discussed it as a team and we committed to it but i wanted to kind of raise it to the whole group to say uh hey if you have not like look at the date look at the stuff that's due for your go to market team if you have not committed to that date um you know leave a comment on the issue uh honestly kind of even just evaluating it too i i'm kind of thinking to myself
i don't i don't necessarily know who would be the dri for these dates and i i think it should be us and i think it i think it's probably you cindy does that sound right to you that like um should be by each team lead for each of the gtm motions i think pmm needs to look at it and make sure it makes sense and if it doesn't have a conversation in the team meetings but i think the dri for the schedule and the work plan is the whoever's leading each of them the gtm motions
so do we do we need this issue then yeah i think it helps keep us it gives us something to for visibility i didn't realize the dates of uh hitops and the platform so that's good you know yeah and even if we end up landing a play in a different week it's good to know what the ballpark is like what the sort of expectations are that have been set we we haven't actually in our team fully committed to uh you know a gantt chart that's going to land in that first week in june with the
sales play but could we sure i mean it's a couple months from now we could do that it's just good to know what the expectations are and maybe when we gant it out we're actually a week early or late or something like that i'm kind of surprised why the platform is so late it seems like we ought to be able to pull that in closer yeah well we've been having some discussions on that we're gonna have some more this week but um i i dropped a comment into the uh platform channel on friday about that
there was um [Music] there was some discussion about whether a devops platform how much a devops platform sales play was needed right now or certainly the campaign so my my suggestion was just like let's finish the sales play let's give sales something that they need when they want to sell the value of a single app because we know they're going to want to do that but everything else might wind up tabled so i don't understand it seems like that was i thought that was i mean that's the key to our message that was a big
brand launch why would we not follow that with a camera well the question is like is is there a product campaign based on there there was there were there was some conflating of the brand message and the um and the um the gtm motion and that was confusing to a lot of people including some of us i think myself certainly being one of them and uh and brian actually did some work on separating those as well so i by my belief that i could be wrong and this is being recorded so don't quote me on
this although i i guess it's quotable now um is that there were some folks who were thinking that there would be a campaign around the brand message that was going to come out of our team which doesn't really make sense because it's a brand campaign and um i i wasn't in all of the meetings but there were some talks that um our team lead zach had had with others and it looks like there wasn't a whole lot of appetite from sales for where we were headed on the campaign side so i yeah yeah maybe i
was going to say on that topic brian do you mind linking your mr in the agenda and actually do you mind just sharing screen for a moment and kind of showing it to the team and then we can encourage encourage this kind of team to review it and then share it with some broader folks as well let's see here now we've got a a series of other changes to the use case page aka the go to market strategy page that are not in what you're looking at right now in this branch just because we started
working them separately but yeah you can see we actually felt the need to go to the trouble of having a section that specs out the differences between the brand messaging and the use case and i think that's useful to do if not for anything else then for future reference or for folks who are not inside of our conversations every day we've got individuals like val who are inside of both conversations the brand messaging and the go to market team but a number of folks who are only on one side of the other so it's useful
for us internally but i think going forward would be even more useful to separate those out i will link to it in the agenda but that's just to show that we've started working on it we're going to pass this around uh some more william and cormac and i have particularly contributed but we also are feeding into this conversations with you know becky and zach and a lot of other folks from one or the other side of this so a lot of other threads have been sort of woven together there and as far as not needing
a sales play i think what we really needed was to flesh out a little bit more of the use case and we're still doing that so we're going to sew that patient up this week and then the more sort of needed yeah this is definitely an open patient still but the more needed uh play it felt like was one of the competitive plays and so that's our next decision as a team is which of those competitive plays to focus on to cindy's question there just wasn't a real practical demand for a devops platform sales play
so long as the use case itself was was fleshed out obviously that's our our key differentiator and it's it's underwriting almost every conversation we have but that doesn't mean it needs a play per se and the the so far uh what's been discussed for the the competitive play next would be either some sort of github takeout or potentially um something agile related because um that's being recorded because there are some things coming up um in the uh in the coming weeks that that will uh that will probably help with that and also increase interest in
that but there's also possibility i saw something mentioned in one of the meetings last week said that that may feed into the premium to ultimate story in which case that if that's being handled elsewhere then that could free us up to work on one of the uh the more direct uh takeouts yeah cool and uh so there's there's an mr there that um this has a little section what's the difference between the you know uh devops platform as a use case for using gitlab and open devops platform which is our brand message and uh probably
right now it has a certain opinion but uh obviously you know looping in uh the the brand folks and todd and the org to to kind of come up with a sharp way to articulate this to alleviate some of that confusion so uh samia looks like you had a question about launching a sales play yeah and perhaps cindy can help me with this um so the mr that william linked in the second point um calls for launching the sales player on a specific date i'd like to understand what entitles launching the sales play is it
just having all your sales playbook assets together do a sales enablement during that week um and you know make sure that sales is equipped to go and sell or is there something else i mean do we have like a set of things that we definitely need to have when we say that we're launching the sales play i i've linked to your definition of a sales play over here as well um so is that the bomb that we need to go with when we say we're going to be launching the sales play in a specific week
well that i mean it's a very good point because each sales play is going to be a little bit different in terms of like for instance you're going you're going to be doing some enablement for the sdrs whereas the ci one is not because it's an expand and the sdrs aren't really involved so it's more of an fyi for them um so very good question maybe i need to add a checklist of like launch readiness or something yeah i think i think that would be useful just so that everybody in the or also knows what
we actually mean by uh launching the sales play and also looking at david somers note in the uh gtm motions um channel where he said that we don't have i think it was last week sometime that we don't have a clarity on um where we're going with the sales play launch right uh we haven't reached a reconciliation on uh what we want to call as a sales play or a sales playbook so this was probably before your discussions with david subsequently you've had some discussions with him because i saw some threads around that but uh
i just want to make sure that we're all on the same page uh when we say that this is what we're going to be doing when we are going to launch a sales play yeah and it may be tough so we used to do this we used to launch go to markets we use a smart sheet and we call it we had a minor and a major launch and they all had different items and you could pick and choose what would make up the launch so i don't ever think it's going to be a one-to-one
relationship um but we also don't have a main checklist like that so maybe that's a good thing um and i did not like using smartsheets by the way um yeah i would say let's have an mr template yeah with the checklist and so you've got an actual mr for the actual launch and it would have a checklist of things yeah that makes sense actually and uh another follow-on question on that related to sdr enablement and sdr related material like the outreach sequence and so on um the feedback that i got from elsa was that normally
what they do is they take what we provide them as a part of assets and sales playbooks and so on and they would create their own you know outreach sequences um in your sales play definition we do have an sdr outreach sequence as a bullet point so um maybe elsa came from a regional point of view where you know in every region they probably modified based on what the requirement is for the region uh but who would be a global counterpart so to say or a leader for sdr enablement that we can talk to and
make sure that we we kind of give them what they actually require um so there's there's two to loop in so one is uh hannah who leads the entire sdr globally i believe yeah um and then the other one is chris wang who is uh specifically responsible for sdr enablement okay um there's also actually he's supposed to there's there's another um maybe it's smb enablement um o'nell told me to work with someone i think her name is melissa no that's not right kelly okay there's a kelly that does enablement for the smb so i get
i how much she has to do with the sdrs i'm not sure it's k-e-l-l-e-y um maybe on the checklist i have a list of names of who to contact too yeah i was just going to say i think that the um the idea behind launching the sales play uh is that one it's probably uh somers's calendar that's that's the big constraint in the sense that we don't want to say like hey we're going to ship these three things and then enable sales all of them all in the same week so that's probably the major constraint
uh and then the the secondary constraint would be is if there are any associated marketing campaigns that need to be executed in conjunction with that sales play then those similarly need to be on a calendar and so i think that's the intention behind this issue that i linked in particular is that uh from the perspective of marketing campaigns they need to know what date sales players are going to hit um so and then maybe there's a few others so cindy are you taking an action item to create an mr to kind of stub out that
checklist yep awesome thank you um just to close out on that so cindy will you be reaching out to hannah kelly and mr program christopher um if you need it done quickly go ahead and do that and then lets you and i reconcile to fold in what you learn into the the overall mr i this needs to be pretty collaborative so what i'm going to do is i'll come up with a boilerplate for a checklist and then i think everybody's going to have to weigh in on it to add to it and flush it out
a bit sounds good i'll uh try to async reach out to the three of them and then maybe later this week try to schedule some time with them um if you're able to i'll keep you in sync so if you're able to reach out to them earlier that's fine as well okay what i'd probably do is just ping them on the mr and ask them to weigh in on the mr for me but you might want to talk to him specifically about your campaign yeah i'll do that okay cool uh then uh 14.0 is coming
up which is very exciting and typically on a major uh release and you know in terms of semantic versioning where uh you know we're revving from 13 dot something to 14.0 we tend to uh do a little bit more there tends to be we did tend to try to do some type of press announcement because the we'll get some good press coverage usually with our media partners uh and so the um the question would be uh how about if brian owns that 14.0 launch and sami it sounds like maybe you were on the docket for
it but that's uh that works out for you it's pushed we added a launch in there and that's that's right so do we need to uh is there a link to the yeah the release post managers let's just take is this page up to date with the latest uh let me see if i can is this one here yeah is this is this accurate uh we have a may and then 14.00 in june or is this out of date that's accurate okay cool then for 14.0 so samia looks like you are currently slotted for 1312
in may does that still work for you yeah that works for me okay and then parker if we move brian here onto 14-0 does that work for you um yeah that's that's fine i don't know pretty flexible there these are um yeah that's fine okay cool and then maybe we can look at the rotation and add add some other folks for the upcoming ones okay would i so i would be are you you were after me so i would flip-flop with brian i would be august 22nd i think so unless you want to take july
which that's cool no i think yeah i don't think either way matters i just saw that you were on for um july so yeah i guess either one of those swaps is fine with me you've got wedding stuff parker do you need to oh oh yeah that when it's your not your wedding necessarily but ones that you're in oh that's so that's the end of this month um luckily okay so yeah that one is in the into april so it'll be the end of this month when i'm headed to new orleans so when is your
wedding do you know that um it is april of next year okay actually it'll be the day after we release on april 22nd it'll be a get lab release day and then parker marriage day that's exciting uh i just realized does 14-3 overlap contribute ooh no contributes on the ninth right i could be that's a good thing to ask though while we're on the topic we had it we had a launch i think in cape town and a bunch of people just sat in the corner and knocked out the release post while we were there
so contribute is the 19th through 24th so yeah we've got the release right in the middle of it okay although it'll be easy for easy to track down anyone who hasn't pushed something that's not true they put that drink with an umbrella down we got to push this mr exactly there's a uh there's a breaking changes blog in the works and i'm gonna do a version 13 year in review uh in the weeks leading up to 14.0 but is there anything that was already like special and in the works for 14.00 samira parker that you'd
heard of nothing really okay uh darren on the runner team might have something let me double check on that and i'll follow up with you i'm going to take a note to remember to do that great yeah i was going to say if across the team if you all could um as you sync with your kind of pm counterparts query into that for like kind of what what are they planning for 14.0 and um and then brian it might even be able to be good for you to uh sync with the new to see kind
of if if he has anything that's um in mind yeah last year we recorded cindy that was you uh last year and and that was scott right i think who recorded a video for 13.00 yeah that was all we did in 12.0 we actually produced like a little show it was like a 30 or 45 minute show with a sid ama and a bunch of other stuff but i don't know if there's anything special in the works for 14.00 we should do something there's usually pr so you need to coordinate with natasha and see what
the plan is well and and with the the new brand messaging there's probably i i think we have enough of uh we have enough runway i think to ramp up something that supports that too yeah and brian i would think it's uh it's your launch so what do you what do you think should be a part of it like plan the uh planning activities that's right do awesome need to open an mr to switch or were you planning on that or what uh yeah actually parker could you open an mr to that page yeah i'm
happy to and that way we can and there's no one else that needs to be swapped right sorry just me and brian simon still stays 13 12. okay all right but we can i mean we can fill out oh yeah i guess i mean who's volunteering for the 22nd i was like okay we might as well put someone in there in october while i'm in here yeah because september that one's the one that'll overlap with contribute yeah throw me in there if i i'm up next anyway because i just did 1310 so if if i'm
not going to be able to make it then i'll take it from your car oh that's that's fair yeah well hopefully you can yeah i don't know yeah i may not get i don't know if i'll get a vaccine by that so if i do get then maybe i otherwise i wouldn't yeah i wonder if gitlab so gitlab said they'll help reimburse right is there a way that you could find one that maybe isn't waiting for um you know the government to come around and have it to you other ways that you could go and
find one and get reimbursed by gitlab maybe no it's it's not about the cost it's just that they're not giving anybody below 45 years right availability okay yeah alrighty well we got our fingers crossed me too there is a 0.6 which is that the gc deck is next monday uh so i will share this that um ty and tracy and i and todd have had a little bit of conversation on the way we format this um and for this next coming gc we'll we will kind of keep to our like the format that we've always
had which is basically any anything that you shipped kind of like we're gonna have a slide and the goal is for that slide to have all of this stuff um my so this might be a good topic for a discussion my opinion on that format is that i don't like it and the reason why is because it's a heavy emphasis on um activities and and not results and so i would love to see a shift in the way that we do group conversation from outputs to outcomes uh and and so this would like i would
love to see something like these are the outcomes the results that we're aiming for like let's say for example in our gtm motions um or otherwise for like other projects that we're on these are the these are the outcomes we're aiming for and then uh and then how we're tracking to those so that that's what i would love to see for a group conversation but i thought i would um for this next gc same as always kind of like do the same thing we've always done add all of your links to the deck um please
do that asap i think that one of the reasons i don't like the old format is because there's always a scramble and you have to go and it's kind of like logging your work twice but the sooner you can add your stuff to that deck then the better it makes it on fern who will be kind of has to make a video for that gc so please get your stuff into him so he has it early but uh on the topic kind of shipping out the format any kind of thoughts on that from the team
how do you measure like for customer meetings how do we measure outcomes for that when um they may not be known for a while right so my my thought is that um we probably wouldn't necessarily we wouldn't just report on the the meetings that we attended um so i think it's okay look so for example for this next gc i think it's okay to say like here are a bunch of customer meetings we attended um and i think that's okay to report that but i think what might be ideal would be um to ask the
question like why do we attend those meetings right like what's the result that we're we're trying to enact and then um how do we know if we achieve that result or not and so the idea would be um that that's that's what we would report on that's what we would kind of share with the with the organization is that like here's a result that we're tracking to or here's you know here's uh and we could talk about like these are activities that we did to in order to achieve that result but it's just a shift
kind of from we're we're doing this activity because an activity we do um to this is the result we're trying to drive and the activities that we perform may change i i agree with your with your direction not just not sure how we measure because like the the gtm motions why you know we're dumping a ton of time and energy into those what are the intended outcomes and how do you measure them today it seems like our intended outcome would be you know if you took each of the gtm motions they've each got a target
of what they're planning on on growing revenue wise but that's not going to be achieved for six months at least so how do you measure you almost have to like say this is what our intent is we'll tell you what we actually achieved six months from now yeah so what i what i would love to see and i don't i don't know how um much each team has has delved into this um but i ideally within the the structure of like you have a go to market motion and that go to market motion is comprised
of some set of marketing activities so some set of campaigns and some set of sales plays uh and then for each of those campaigns and sales plays then we would have you know outcomes that were we're driving towards and so what would be really cool is if for this even for this one is if we even started to make that shift although this is not like a a requirement for this one like let's just do the same thing we've always done it's next monday do what's familiar but in my mind it would be great to
say like here are these three go to market motion this is what pmm team and tmm team are spending a huge amount of time on um and these are the results we're aiming to drive this is this is and so you're sharing the the predictor this is like this is what we're trying to go and achieve and then uh then yeah over the coming months we would be able to report against that that sounds like a good slide for you to create william i'm i'm totally up for it and my only um my only cop
out there is i'm uh i'm a little bit kind of like behind the um like i don't even think i've attended each i have not yet been to like a devops platform stand-up even uh so some of the i'm kind of like uh you know i think i was out of office for a week and then i was like cmo shadow for two weeks and so that last week was kind of my first week poking into this stuff um so i'm happy to kind of own that and then that's why i said like i probably
won't have it for this monday but um that's that's a really good thing in general for for me to just put it to do to myself that like uh you know have some kind of overview on how all the motions are measuring success which candidly cindy that's kind of what i said in the meeting to uh todd and tracy and ty was um i really think it's that's what i told them i said i think it's our responsibility to create the gc slide um i don't think we should just always bump this down to our
teams as their responsibility to go and make the slide i like the idea of hey anybody on the team could add things they want visibility for so to your point tracy if you wanted visibility for let's say hey look at all these kind of sales meetings i went to uh i think that that's good to at to have is like anything that you all care about and that you wanted to surface i think that's good to have that channel but um that was kind of my point is that like hey i think it's the management
team's job to create the gc deck so uh making it to do myself cool uh elita you've got point seven here um yeah i just wanna say thanks to everyone for jumping in and helping me out with the um partner versus uh competitor exercise very very helpful um so as i mentioned that's gonna kind of be the starting point for us to decide um well no i think william i think we're deciding to keep even if we tag someone as a partner we're gonna still keep a competitive page right i haven't read your notes in
the issue yet so that is a great question uh actually i think that this definitely bears worth talking about um even on youtube i suppose for anybody in the world that would watch this video uh but um so there's a few there's a few bits of nuance so one is that we we have a delimiter on is another vendor are they a technology partner or aren't they or even we could even just say generally like are they a partner or are they not a partner that list exists and there are criteria for being an official
partner and you know some some companies our partners and some companies aren't um now some of the some of the nuance comes in like well what if somebody's let's say like a potential partner or what if there's somebody's somebody that we may want to partner with in the future and some of our capabilities overlap but some of them don't and so what message do we put up about them on our website so for example on a comparison page where we compare git lab with other devops tools as the thing that we say about that tool
it's not going to hinder let's say the work of our alliance's team to try to try to create a partnership that we don't yet have so i think that's some of the nuance that we need to navigate um i did open an issue uh where i think i tagged the whole team on i think the the team you should have gotten a notification and then i think what do we tag elita we tagged uh my onc and um dunk and some other folks but the the i kind of had like three there's i i think
in my head there are three basic options maybe there are more but there there's basically for any vendor out there where they are a partner or potential partner and also they have some type of capability that overlaps with gitlab we could have only a devops comparison page we could have only a partner page or we could have both um so there's some discussion of like kind of what's the what's the strategy there um i think that we end up having both but you know that's just a a thing to kind of get alignment on i
think yeah i haven't um gone into the issue to add my um kind of thoughts yet i'll do that today if the team decides and and we all you know are aligned to having both i'm okay with that just because that's what we all want but my personal perspective i think when we look at devops tools and how many competitors we cover um i think it for me i feel like we should narrow the list down and this is one of the ways that i can do that um but again whatever we decide i'm on
board with yeah well i'm sorry i was just going to say elita i think you are the dri so you should you should take the input of everybody else and ideally make a call that kind of weighs the trade-offs of of you know what we need to weigh um but to your point about tiering the you know um the idea would be maybe if somebody if somebody if a partner or somebody's a partner maybe they fall into a different tier that is uh that's that makes sense that that's maybe part of the conversation as well
what were you thinking cormac i was just going to say plus one to pairing that list down i think there are some folks i imagine it's the same for everyone but um certainly within the agile like plan space there are some competitors there where it probably doesn't make sense like at least you know i mean atlassian does a lot of things but like trello from atlassian like trello is not really a com if someone is considering trello they're probably not considering gitlab uh for that for that specific use case um they could be they could
be using trello with other things and then um there could be a multi-vendor solution they're comparing against us but you know there there are some cases where if we if we needed to trim that list down we could probably do so without doing a disservice to customers yeah agreed yeah i mean we're you know the roi is tough right with the with the the state of 10 now i think we'd have a much better time keeping it up to date and maintaining it and a much more focused list if you would if you will um
yeah yeah that's that's very much true on the scm side i mean i i added to the list a whole bunch of folks everyone who hosts snippets is not is not a competitor you know yeah and one one bit of nuance that i might suggest is that for that section of our website is not i don't i don't think the intention is strictly to show like competitors um in in a kind of like competitive sense although i think i so for example going back to your point about like a tool like trello um it seems
reasonable that folks that are users prospects customers of gitlab would say okay well gitlab has these issue boards um when when could i use issue boards and when could i use trello could i use them together would i use them for different reasons that seems like that would be helpful information to our customer base um now what i really like elita is your proposal of like tiering these where there are some tools that are probably more important to our user base that like for those kind of tools it's it's more important to those users and
those prospects those customers that that there's some kind of like how do i understand this tool versus git lab and those are the ones where we focus on energy and effort so maybe a tool like trello just says something very lightweight or nothing at all because it's it's not something that our users would care as much about but um that's kind of my thought on it is that if there was a if there was a user and they're trying to think well when would i use gitlab and when would i use tool x it's probably
helpful to have some type of web information about that well that one to that point william i think if we had those kind of qualitative context pages you were talking about then that would be wonderful for trello because i think you know trello is one of those things that people just spin up everywhere and there will there will be questions about that if i think right now the the thing that's a little weird is if we're scoring against them it's it's it's a weird because then it is a you know direct it doesn't give you
any extra context and it could confuse things so if we did have that how does this fit into this world view that would also be um you know would also be easier on our partners i think that would be useful information what is this yeah yeah go ahead message thinking was if you look at it and break it into two parts you've got how do we compare on scope and how do we compare on capabilities and you might give everyone a comparison on scope and not everyone a comparison on capabilities so scope would be important
to show you know we do all this they only do this part or they do all this too but to understand how they can fit from a scope standpoint and then from a capability standpoint maybe with a partner you decide you don't want to go down that path or maybe you do go down that path and you say and they have this capability that we don't have that compliments us and that's why they're a partner so i had the scoring thing um can get so complex here's what i was thinking and you guys tell me
if you agree or disagree um so parker myself and ryan we had a call last week um with hey what was the guy's name from forrester uh chris condo recon right we had a great conversation the idea is that we start having these monthly sync calls where i ask them specific questions uh competitive related um questions i was thinking the next call we have that i bring this to the table and ask them their perspective and their opinion on what do they think we should consider what should be the factors we consider we should consider
in scoring ourselves against other competitors so what do you think about that so uh i would just i'll i'll say this and elita you and i've talked about this at nauseam and so it like you and i have had 50 conversations about this but i realized like the rest of the team has not uh so my strong extremely strong stance is that the current graphic that we have on those devops tools pages is really really bad it is negative on several several fronts um so trying to the reason why is to your point cindy it
it scores capabilities of every single tool on that list and it treats them all as though their platform so you look at the page and you would say for example like trello you would be like trello is not a devops platform but we score it like we give it like zero for ci or something it's just really goofy and so the reason why it's bad is because like we lose credibility because anybody who looks at that page is like does gitlab even understand what trello is like why are they even scoring trello on ci yeah
it's um it makes us lose credibility it causes frustration with um partners or potential partners right as our alliances team is share with us hey so and so wants to partner with gitlab but we have this page where we like really really misrepresent their tool so we're not being fair i don't i don't feel like it's in line with gitlab's values of uh transparency it's not very transparent it's it's um it's very very like marketing kind of um dishonest almost it's kind of i don't want to overstate it but i really really dislike the chronographic
yeah we've talked about it and i agree when i brought this up um to leadership i think one of the things that that leadership really likes about the format of the infographic is that they feel someone can quickly look at it and immediately say oh jenkins is not a player in xyz space you know they're they're a ci cd player whatever right so i think that was one of the the reasons why um leadership would like us to continue down the path with these current infographics right then they should give well to do it right
i think i think like if that's the case then yeah we just well uh elita i really like your proposal so so um i don't know elita would you be able to just link your issue or your um plan you have like a and i know most of the team has waited on that plan but it'd be great to just have a link in the agenda and one of the things i really like in your scope of issues is your uh your kind of proposal for for an augment to the current graphic the current graphic
treats everybody like they're all a platform play and it's kind of dishonest and it's kind of you know not credible and then it scores everybody like that but that's kind of goofy um what leadership or like todd in particular what todd likes about the graphic is that it tells our platform story and that's true it would be great to tell our platform story but the there's a graphic that you propose a leader that's really cool i like because it shows okay git lab is a devops platform and this tool does this one thing nobody is
going to be offended by having that's true that is true it's transparent it's credible if we just have a visual representation of gitlab what's the difference between git lab and trello well git lab does all this stuff including issue boards and trello does like issue boards right or you know kanban boards um and that's one difference and that alone just having that credibly represented tells our platform story and um helps our users right they would look at it and be like well what's the difference between 11 trello oh well this is one major difference so
i like how cindy said it's like scope so if you just show the scope you don't have to have to score on scope um but then potentially a score would be on like let's say capabilities maybe where uh on the specific bits of functionality where gitlab and uh whatever tool overlap like how are they how do they how do they compare yeah and so i know we i don't want to take up too much more time on this william i know we have other things to to to talk about really quick before we move on
i wanted to get the team the way and i think most of you kind of weighed in on a k call but for those of you who were not on the kick call so i kind of had i threw one option out there hey we you know we talked to some analysts and said hey we're doing the scoring can you kind of help us out guide us here right i don't know what they would say but i would my recommendation is that we ask the second option is do we just ask for money to hire
a third-party firm to come in and do it and i know we talked about this on a cad call and everyone gave their opinion but for those of you who were not on the call can you share your thoughts what do you yeah or nay do you think that's something we should do or not you should i think it's also important to point out that you that right now it would be a voluntary thing um and like my point on the call was that i don't if it's voluntary i don't think it'll get done um
i i i think with third parties so it do you mean just a third party to come in and get it done or a third party to come in and put their stamp of approval on it like we were doing yeah third party to actually do the research and the scoring and all of that for us i i think that the that would certainly add to credibility but i think that it can also go stale unless we're engaged in a long-term partnership and um when we since being recorded when we worked with another vendor there
were there were thoughts that you know there could be business considerations at some point that could affect that um that you know if our relationship with that party changes at any point then what happens to do they do they own that data uh do we have the right to update that data as soon as we update it do we lose the credibility that we gain so that that's something we'd need to lock in something long-term if we were to do that it also we would have to figure out where the marketing in that goes as
well um because i mean it is also a marketing tool and if so if a third party controls that then we lose the ability we'd have to market around it yeah okay i will i will say this i i think that um if we had tiered you know comparison pages and it wasn't like 80 tools plus or however many are on there and every single quarter this entire team and all of tmm and like you know as many resources possible needs to go and update all 80 tools every quarter that seems uh i don't think
i just don't want to sign up for that but if we have a tiered list of tools and we say like there's tier one and maybe even like a tier two it it it feels to me like a pretty reasonable ass like i would make this ask of the team to say like as part of your quarterly goals as a product marketing manager you would update you know one to three tools each quarter to kind of keep it fresh does that seem like a reasonable ask i think so i think so but i don't want
to speak for it it's not something that i relish but i think yeah but if we know it's coming it's not like you know last time it was all hands on deck for you know two days and and i think if we know it's coming then you know we'll we'll all have moments when we can two days two days yeah mine was more it was like two months yeah yeah like so like i don't see this yeah that's my input but yeah yeah basically i thought that a lot tiger last time was a pretty big
debacle of a mismanagement of resources but my thought is as a product marketer you want to be an sme on the top competitors for your solutions that you own right or the products that you own but we only have one product so in this case for the solutions that you own um you know a core a core competency for any pmm would be to be a competitive subject matter expert on the top competitors in their space and so if you're if you're doing that that kind of bit of research anyway or for that matter it
could be it could be like because you have a task to go and like update some set of pages or just to even to check in on them then it's a reason to go and check in on them and um that's kind of my thought there is that for 80 tools is too much but it but um alita i think and i could we could ask this of tai as well to say like hey we think a core competency for a tmm is to be an sme on the top one to three tools for their
space and that they should keep fresh on that information on like a quarterly basis and then one of the outcomes of keeping fresh on that would be like maybe an update to a web page that feels like a very fair and a reasonable and a scalable ask here's another thought too is if if we do break it into scope versus capabilities the scope part of it it shouldn't change too much from quarter to quarter right that's absolutely more stable capabilities might but if you say if you tier that capabilities part and say you know top
three competitors or something and then give the uh give the ability for them to um open an mr and suggest changes if there's something on there that's not accurate but i do think you still have to figure out you probably don't want the detailed comparison on ones that you're trying to partner and if we limit it to say top three that our our our pm our pm counterparts should be deeply involved with that same sort of research already yep so in fact they might even have it on their vision page yeah and so i think
that that you know if i you know if i if i called up gabe and said gabe let's talk about i don't know i'm trying to think base camp like yeah i haven't looked at base camp but i guarantee he's looked at azure boards and you know that sort of thing so i think i think that's uh that if we limit it that could be easier than we think cool well elita has a plan in there there's a specific issue for the partner stuff you can weigh in on and some of these other things as
they crop up we can log issues for them and uh thank you all for a great meeting and happy monday yeah happy week everybody fingers crossed for zombies vaccine [Music]
