Commit edddc16c authored by William Chia's avatar William Chia
Browse files

Product Marketing to Strategic Marketing

parent c76623b4
......@@ -270,24 +270,24 @@
/sites/handbook/source/handbook/marketing/events/ @Emily @Lconway @melsmo
/sites/handbook/source/handbook/marketing/localization/ @erica @lblanchard
/sites/handbook/source/handbook/marketing/marketing-operations/ @sdaily @EWhelchel @tbarr @rkohnke
/sites/handbook/source/handbook/marketing/product-marketing/ @kuthiala @johnjeremiah @dangordon @williamchia
/sites/handbook/source/handbook/marketing/product-marketing/analyst-relations/ @cfletcher1 @rragozzine
/sites/handbook/source/handbook/marketing/product-marketing/competitive/ @kuthiala @mskumar
/sites/handbook/source/handbook/marketing/product-marketing/customer-reference-program/ @cfletcher1 @FionaOKeeffe @jlparker
/sites/handbook/source/handbook/marketing/product-marketing/demo/ @dangordon
/sites/handbook/source/handbook/marketing/product-marketing/mrnci/ @cfletcher1
/sites/handbook/source/handbook/marketing/product-marketing/partner-marketing/ @TinaS
/sites/handbook/source/handbook/marketing/strategic-marketing/ @kuthiala @johnjeremiah @dangordon @williamchia
/sites/handbook/source/handbook/marketing/strategic-marketing/analyst-relations/ @cfletcher1 @rragozzine
/sites/handbook/source/handbook/marketing/strategic-marketing/competitive/ @kuthiala @mskumar
/sites/handbook/source/handbook/marketing/strategic-marketing/customer-reference-program/ @cfletcher1 @FionaOKeeffe @jlparker
/sites/handbook/source/handbook/marketing/strategic-marketing/demo/ @dangordon
/sites/handbook/source/handbook/marketing/strategic-marketing/mrnci/ @cfletcher1
/sites/handbook/source/handbook/marketing/strategic-marketing/partner-marketing/ @TinaS
/sites/handbook/source/handbook/use-cases/ @kuthiala @johnjeremiah @williamchia
/sites/handbook/source/handbook/marketing/product-marketing/usecase-gtm/ @johnjeremiah @dangordon
/sites/handbook/source/handbook/marketing/product-marketing/pmmteam/ @johnjeremiah @williamchia
/sites/handbook/source/handbook/marketing/product-marketing/public-sector-gtm/ @traci @johnjeremiah
/sites/handbook/source/handbook/marketing/product-marketing/usecase-gtm/version-control-collaboration/ @warias
/sites/handbook/source/handbook/marketing/product-marketing/usecase-gtm/ci/ @parker_ennis @iganbaruch
/sites/handbook/source/handbook/marketing/product-marketing/usecase-gtm/devsecops/ @cblake @fjdiaz
/sites/handbook/source/handbook/marketing/product-marketing/usecase-gtm/simplify-devops/ @supadhyaya @dangordon
/sites/handbook/source/handbook/marketing/product-marketing/usecase-gtm/gitops/ @williamchia @csaavedra1
/sites/handbook/source/handbook/marketing/product-marketing/sales-resources/ @johnjeremiah @williamchia @dcsomers
/sites/handbook/source/handbook/marketing/product-marketing/technical-marketing/ @dangordon
/sites/handbook/source/handbook/marketing/strategic-marketing/usecase-gtm/ @johnjeremiah @dangordon
/sites/handbook/source/handbook/marketing/strategic-marketing/pmmteam/ @johnjeremiah @williamchia
/sites/handbook/source/handbook/marketing/strategic-marketing/public-sector-gtm/ @traci @johnjeremiah
/sites/handbook/source/handbook/marketing/strategic-marketing/usecase-gtm/version-control-collaboration/ @warias
/sites/handbook/source/handbook/marketing/strategic-marketing/usecase-gtm/ci/ @parker_ennis @iganbaruch
/sites/handbook/source/handbook/marketing/strategic-marketing/usecase-gtm/devsecops/ @cblake @fjdiaz
/sites/handbook/source/handbook/marketing/strategic-marketing/usecase-gtm/simplify-devops/ @supadhyaya @dangordon
/sites/handbook/source/handbook/marketing/strategic-marketing/usecase-gtm/gitops/ @williamchia @csaavedra1
/sites/handbook/source/handbook/marketing/strategic-marketing/sales-resources/ @johnjeremiah @williamchia @dcsomers
/sites/handbook/source/handbook/marketing/strategic-marketing/technical-marketing/ @dangordon
/sites/handbook/source/handbook/marketing/project-management-guidelines/ @johnjeremiah @dplanella @jgragnola
/sites/handbook/source/handbook/marketing/readmes/ @dmurph
/sites/handbook/source/handbook/marketing/revenue-marketing/ @EWhelchel
......
......@@ -85,7 +85,7 @@ customer_study_content:
- |
Hotjar wanted to stay away from solutions where they had to host the source code management and their own workflows. Now, their teams are able to focus on their priority tasks and the main line of business, instead of trying to figure out why [Git repositories](/blog/2019/10/28/optimize-gitops-workflow/) are down. With GitLab, Hotjar is able to see which updates are in the planning process. “It was definitely something that was impressive. During the trial I think there were two releases. So we got issues that we were finding during the trial fixed in the releases that came out during the trial,” Pinho said.
- |
GitLab projects connect to their [AWS EKS cluster](/handbook/marketing/product-marketing/technical-marketing/howto/eks-cluster-for-demo.html), the tests run within the cluster using Kubernetes Operator, it reports back with coverage results, then artifacts are uploaded to AWS ECR/S3. Review environments spin up inside the EKS cluster during review. After the merge, artifacts are deployed again to the EKS to the production environment. “We went from the deployment itself to production that in our old system was taking something like eight minutes and is now gone down to something like four, so half the time to deploy. Within the whole incident resolution scheme, this sounds like very little, but it still impacts things across the board,” Pinho said. Developers are saving time and effort by making use of standalone review-environments instead of in-the-loop shared staging environments, which create bottlenecks.
GitLab projects connect to their [AWS EKS cluster](/handbook/marketing/strategic-marketing/technical-marketing/howto/eks-cluster-for-demo.html), the tests run within the cluster using Kubernetes Operator, it reports back with coverage results, then artifacts are uploaded to AWS ECR/S3. Review environments spin up inside the EKS cluster during review. After the merge, artifacts are deployed again to the EKS to the production environment. “We went from the deployment itself to production that in our old system was taking something like eight minutes and is now gone down to something like four, so half the time to deploy. Within the whole incident resolution scheme, this sounds like very little, but it still impacts things across the board,” Pinho said. Developers are saving time and effort by making use of standalone review-environments instead of in-the-loop shared staging environments, which create bottlenecks.
- |
Hotjar’s remote culture continues to thrive. “Most people are online at the same time, you can expect an MR to be reviewed within hours or minutes, and be able to jump on a video call together to debug issues, discuss projects, etc. We definitely don’t suffer from the usual pains of fully remote offices where any query will only be answered by the next morning,” Pinho said.
- |
......
......@@ -28,12 +28,12 @@
- avoid: EE
use_instead: Subscribers or paid users
reason: |
[EE is a distribution](/handbook/marketing/product-marketing/tiers/#history-of-ce-and-ee-distributions) and not all people who use EE pay us.
[EE is a distribution](/handbook/marketing/strategic-marketing/tiers/#history-of-ce-and-ee-distributions) and not all people who use EE pay us.
 
- avoid: CE
use_instead: Core users
reason: |
[CE is a distribution](/handbook/marketing/product-marketing/tiers/#history-of-ce-and-ee-distributions) and many Core users use EE.
[CE is a distribution](/handbook/marketing/strategic-marketing/tiers/#history-of-ce-and-ee-distributions) and many Core users use EE.
 
- avoid: Hi guys
use_instead:
......
......@@ -128,7 +128,7 @@ pages:
- starting at $20k/year for 10 users, with tiered pricing for lower per-user cost for larger organizations
* Jenkins X
- Free (and Open Source)
- But Total Cost of Ownership has cost (see [Pinterest anecdote](/handbook/marketing/product-marketing/customer-reference-program/#deliver-value-faster))
- But Total Cost of Ownership has cost (see [Pinterest anecdote](/handbook/marketing/strategic-marketing/customer-reference-program/#deliver-value-faster))
 
## Is Jenkin Really Free?
Here are some additional cost that should be considered for Jenkins users:
......
......@@ -53,7 +53,7 @@
use_case: ci
stage: Manage, Verify, Package, Release
category: Audit Events, Compliance Management, CI, Code Quality, Code Testing and Coverage, Web Performance, Usability Testing, Accessibility Testing, Merge Trains, Package Registry, Container Registry, Dependency Proxy, Review Apps
link: https://about.gitlab.com/handbook/marketing/product-marketing/usecase-gtm/ci/
link: https://about.gitlab.com/handbook/marketing/strategic-marketing/usecase-gtm/ci/
embedded_link:
gated_link:
short_description: The CI Resource page
......@@ -67,7 +67,7 @@
use_case: ci
stage: Manage, Verify, Package, Release
category: Audit Events, Compliance Management, CI, Code Quality, Code Testing and Coverage, Web Performance, Usability Testing, Accessibility Testing, Merge Trains, Package Registry, Container Registry, Dependency Proxy, Review Apps
link: https://about.gitlab.com/handbook/marketing/product-marketing/usecase-gtm/ci/message-house
link: https://about.gitlab.com/handbook/marketing/strategic-marketing/usecase-gtm/ci/message-house
embedded_link:
gated_link:
short_description: The CI messaging and positioning
......@@ -81,7 +81,7 @@
use_case: ci
stage: Manage, Verify, Package, Release
category: Audit Events, Compliance Management, CI, Code Quality, Code Testing and Coverage, Web Performance, Usability Testing, Accessibility Testing, Merge Trains, Package Registry, Container Registry, Dependency Proxy, Review Apps
link: https://about.gitlab.com/handbook/marketing/product-marketing/usecase-gtm/ci/#customer-facing-slides
link: https://about.gitlab.com/handbook/marketing/strategic-marketing/usecase-gtm/ci/#customer-facing-slides
embedded_link:
gated_link:
short_description: The CI Customer presentation
......@@ -104,7 +104,7 @@
use_case: devsecops
stage: Manage, Secure,
category: Audit Events, Compliance Management, SAST, DAST, Dependency Scanning, Container Scanning, License Complience,
link: https://about.gitlab.com/handbook/marketing/product-marketing/usecase-gtm/devsecops/
link: https://about.gitlab.com/handbook/marketing/strategic-marketing/usecase-gtm/devsecops/
embedded_link:
gated_link:
short_description: The DevSecOps Resource page
......@@ -118,7 +118,7 @@
use_case: devsecops
stage: Manage, Secure,
category: Audit Events, Compliance Management, SAST, DAST, Dependency Scanning, Container Scanning, License Complience,
link: https://about.gitlab.com/handbook/marketing/product-marketing/usecase-gtm/devsecops/message-house
link: https://about.gitlab.com/handbook/marketing/strategic-marketing/usecase-gtm/devsecops/message-house
embedded_link:
gated_link:
short_description: DevSecOps messaging and postioning
......@@ -154,7 +154,7 @@
use_case: vcc
stage: create, package,secure,plan, manage
category: Source Code management, Code Review, Wiki, Static Site Editor, Web IDE Live Preview, Snippets, Design Management, Issue Tracking, Compliance Management, Code Analytics, Jupyter Notebooks, Git LFS, SAST
link: https://about.gitlab.com/handbook/marketing/product-marketing/usecase-gtm/version-control-collaboration/
link: https://about.gitlab.com/handbook/marketing/strategic-marketing/usecase-gtm/version-control-collaboration/
embedded_link:
gated_link:
short_description: The Version Control and Collaboration Resource page
......@@ -168,7 +168,7 @@
use_case: vcc
stage: create, package,secure,plan, manage
category: Source Code management, Code Review, Wiki, Static Site Editor, Web IDE Live Preview, Snippets, Design Management, Issue Tracking, Compliance Management, Code Analytics, Jupyter Notebooks, Git LFS, SAST
link: https://about.gitlab.com/handbook/marketing/product-marketing/usecase-gtm/version-control-collaboration/message-house/
link: https://about.gitlab.com/handbook/marketing/strategic-marketing/usecase-gtm/version-control-collaboration/message-house/
embedded_link:
gated_link:
short_description: The Version Control and Collaboration mesaging and positioning
......@@ -182,7 +182,7 @@
use_case: vcc
stage: create, package,secure,plan, manage
category: Source Code management, Code Review, Wiki, Static Site Editor, Web IDE Live Preview, Snippets, Design Management, Issue Tracking, Compliance Management, Code Analytics, Jupyter Notebooks, Git LFS, SAST
link: https://about.gitlab.com/handbook/marketing/product-marketing/usecase-gtm/version-control-collaboration/#customer-facing-slides
link: https://about.gitlab.com/handbook/marketing/strategic-marketing/usecase-gtm/version-control-collaboration/#customer-facing-slides
embedded_link:
gated_link:
short_description: The Version Control and Collaboration Customer slides
......@@ -247,6 +247,9 @@
- sources: /handbook/product/pricing
target: /handbook/ceo/pricing/
comp_op: ^~
- sources: /handbook/marketing/product-marketing/
target: /handbook/marketing/strategic-marketing/
comp_op: '~'
- sources: /integrations/
target: /partners/integrate/
comp_op: '~'
......@@ -594,7 +597,7 @@
target: /stages-devops-lifecycle/secure/
comp_op: '='
- sources: /handbook/sales/demo/
target: /handbook/marketing/product-marketing/sales-resources/#demos
target: /handbook/marketing/strategic-marketing/sales-resources/#demos
comp_op: '='
- sources: /deploy
target: /stage-devops-lifecycle/deploy-targets/
......@@ -665,7 +668,7 @@
- sources: /handbook/sales-training/
target: /handbook/sales/training/
comp_op: '='
- sources: /handbook/marketing/product-marketing/enablement/
- sources: /handbook/marketing/strategic-marketing/enablement/
target: /handbook/sales/training/sales-enablement-sessions/
comp_op: '='
- sources: /handbook/sales-process/account_management/
......@@ -2465,7 +2468,7 @@
- sources:
- /compete
- /compete/
target: /handbook/marketing/product-marketing/competitive/compete/
target: /handbook/marketing/strategic-marketing/competitive/compete/
comp_op: '='
- sources:
- /handbook/business-ops/it-help
......@@ -3365,12 +3368,12 @@
target: /job-families/product/pricing/
comp_op: '='
- sources:
- /devops-tools/azure-devops/decision-kit.html
- /devops-tools/azure-devops/decision-kit.html
target: /devops-tools/azure-devops-vs-gitlab/decision-kit/
comp_op: '='
- sources:
- /devops-tools/azure-devops/content/evaluation-questions.html
- /devops-tools/azure-devops/content/evaluation-questions/
- /devops-tools/azure-devops/content/evaluation-questions.html
- /devops-tools/azure-devops/content/evaluation-questions/
- /devops-tools/azure_devops/Azure-Questions-Concerns.html
target: /devops-tools/azure-devops-vs-gitlab/evaluation-questions/
comp_op: '='
......@@ -3384,14 +3387,14 @@
- /devops-tools/azure-devops/content/continuous-delivery.html
- /devops-tools/azure-devops/content/continuous-delivery/
- /devops-tools/azure_devops/AzureDevOps-CD.html
target: /devops-tools/azure-devops-vs-gitlab/continuous-delivery/
comp_op: '='
target: /devops-tools/azure-devops-vs-gitlab/continuous-delivery/
comp_op: '='
- sources:
- /devops-tools/azure-devops/content/devsecops.html
- /devops-tools/azure-devops/content/devsecops/
- /devops-tools/azure-devops/content/devsecops/
- /devops-tools/azure_devops/AzureDevOps-DevSecOps.html
target: /devops-tools/azure-devops-vs-gitlab/devsecops/
comp_op: '='
target: /devops-tools/azure-devops-vs-gitlab/devsecops/
comp_op: '='
- sources:
- /devops-tools/azure-devops/content/version-control.html
- /devops-tools/azure-devops/content/version-control/
......@@ -3400,29 +3403,29 @@
comp_op: '='
- sources:
- /devops-tools/azure-devops/content/licensing.html
- /devops-tools/azure-devops/content/licensing/
target: /devops-tools/azure-devops-vs-gitlab/licensing/
- /devops-tools/azure-devops/content/licensing/
target: /devops-tools/azure-devops-vs-gitlab/licensing/
comp_op: '='
- sources:
- /devops-tools/azure-devops/content/business-decision-makers.html
- /devops-tools/azure-devops/content/business-decision-makers/
- /devops-tools/azure_devops/AzureDevOps-BDM.html
target: /devops-tools/azure-devops-vs-gitlab/business-decision-makers/
comp_op: '='
comp_op: '='
- sources:
- /devops-tools/azure-devops/content/news.html
- /devops-tools/azure-devops/content/news/
- /devops-tools/azure-devops/content/news/
- /devops-tools/azure_devops/AzureDevOps-News-Markers.html
target: /devops-tools/azure-devops-vs-gitlab/news/
target: /devops-tools/azure-devops-vs-gitlab/news/
comp_op: '='
- sources:
- /devops-tools/azure-devops/content/comparison-methodology.html
- /devops-tools/azure-devops/content/comparison-methodology/
- /devops-tools/azure-devops/content/comparison-methodology/
- /devops-tools/azure_devops/comparison-methodology.html
target: /devops-tools/azure-devops-vs-gitlab/comparison-methodology/
target: /devops-tools/azure-devops-vs-gitlab/comparison-methodology/
comp_op: '='
- sources:
- /devops-tools/bitbucket/decision-kit.html
- /devops-tools/bitbucket/decision-kit.html
target: /devops-tools/bitbucket-vs-gitlab/decision-kit/
comp_op: '='
- sources:
......@@ -3451,7 +3454,7 @@
target: /devops-tools/bitbucket-vs-gitlab/atlassian-pricing/
comp_op: '='
- sources:
- /devops-tools/github/decision-kit.html
- /devops-tools/github/decision-kit.html
target: /devops-tools/github-vs-gitlab/decision-kit/
comp_op: '='
- sources:
......@@ -3523,7 +3526,7 @@
target: /devops-tools/github-vs-gitlab/business-decision-makers/
comp_op: '='
- sources:
- /devops-tools/jenkins/decision-kit.html
- /devops-tools/jenkins/decision-kit.html
target: /devops-tools/jenkins-vs-gitlab/decision-kit/
comp_op: '='
- sources:
......@@ -3557,7 +3560,7 @@
target: /devops-tools/jenkins-vs-gitlab/news/
comp_op: '='
- sources:
- /devops-tools/jfrog/decision-kit.html
- /devops-tools/jfrog/decision-kit.html
target: /devops-tools/jfrog-vs-gitlab/decision-kit/
comp_op: '='
- sources:
......@@ -3575,7 +3578,7 @@
- /devops-tools/jfrog/content/jfrog-pricing/
target: /devops-tools/jfrog-vs-gitlab/jfrog-pricing/
comp_op: '='
- sources:
- sources:
- /solutions/version-control
- /solutions/version-control/
target: /solutions/benefits-of-using-version-control/
......
......@@ -1784,8 +1784,8 @@
- Strategic Marketing
- Technical Marketing
expertise: |
<li><a href="/handbook/marketing/product-marketing/technical-marketing/">Technical Marketing, CI</a></li>
<li><a href="/handbook/marketing/product-marketing/technical-marketing/">Technical Marketing, CI/CD (acting)</a></li>
<li><a href="/handbook/marketing/strategic-marketing/technical-marketing/">Technical Marketing, CI</a></li>
<li><a href="/handbook/marketing/strategic-marketing/technical-marketing/">Technical Marketing, CI/CD (acting)</a></li>
story: |
Itzik joins GitLab with a background in Technical Marketing, Demo Solutions, Product Management, and Technical enablement.
He brings strong capabilities to bridge gaps between business and technology, increase customer satisfaction, and customer business results.
......@@ -4570,8 +4570,8 @@
- Configure Group
- Merge Request buddy
expertise: |
<li><a href="/handbook/marketing/product-marketing/pmmteam/">Product Marketing, Cloud Native</a></li>
<li><a href="/handbook/marketing/product-marketing/pmmteam/">Product Marketing, GitOps</a></li>
<li><a href="/handbook/marketing/strategic-marketing/pmmteam/">Product Marketing, Cloud Native</a></li>
<li><a href="/handbook/marketing/strategic-marketing/pmmteam/">Product Marketing, GitOps</a></li>
<li><a href="/company/culture/inclusion/">GitLab Diversity, Inclusion & Belonging Advisory Group</a> member</li>
<li><a href="/handbook/people-group/general-onboarding/mr-buddies/">Merge Request buddy</a></li>
story: |
......@@ -5940,14 +5940,14 @@
- Marketing
- Strategic Marketing
expertise: |
<li><a href="/handbook/marketing/product-marketing/">Strategic Marketing</a></li>
<li><a href="/handbook/marketing/strategic-marketing/">Strategic Marketing</a></li>
<li><a href="/handbook/marketing/pmmteam/">Product Marketing</a></li>
<li><a href="/handbook/marketing/product-marketing/technical-marketing/">Technical Marketing</a></li>
<li><a href="/handbook/marketing/product-marketing/mrnci/">Market Research and Customer Insights</a></li>
<li><a href="/handbook/marketing/product-marketing/analyst-relations/">Analyst Relations</a></li>
<li><a href="/handbook/marketing/product-marketing/customer-reference-program/">Customer References</a></li>
<li><a href="/handbook/marketing/product-marketing/partner-marketing/">Partner and Channel Marketing</a></li>
<li><a href="/handbook/marketing/product-marketing/competitive/">Competitive Intelligence</a></li>
<li><a href="/handbook/marketing/strategic-marketing/technical-marketing/">Technical Marketing</a></li>
<li><a href="/handbook/marketing/strategic-marketing/mrnci/">Market Research and Customer Insights</a></li>
<li><a href="/handbook/marketing/strategic-marketing/analyst-relations/">Analyst Relations</a></li>
<li><a href="/handbook/marketing/strategic-marketing/customer-reference-program/">Customer References</a></li>
<li><a href="/handbook/marketing/strategic-marketing/partner-marketing/">Partner and Channel Marketing</a></li>
<li><a href="/handbook/marketing/strategic-marketing/competitive/">Competitive Intelligence</a></li>
<li><a href="/handbook/sales/training/">Sales and Partner Enablement</a></li>
story: |
 
......@@ -7763,7 +7763,7 @@
- Strategic Marketing
- Product Marketing
expertise: |
<li><a href="/handbook/marketing/product-marketing/pmmteam/">Product Marketing, DevSecOps</a></li>
<li><a href="/handbook/marketing/strategic-marketing/pmmteam/">Product Marketing, DevSecOps</a></li>
story: |
Cindy loves to garden, kayak, explore the outdoors, and travel. She enjoys architecture, history, and all kinds of crafts. A wannabe teacher, she loves to use relatable, every day experiences to explain complex security topics. Ask her about perimeter security and 'when pigs fly' or smart phones relative to integrated DevSecOps.
 
......@@ -11572,8 +11572,8 @@
- Strategic Marketing
- Technical Marketing
expertise: |
<li><a href="/handbook/marketing/product-marketing/technical-marketing/">Technical Marketing, Agile</a></li>
<li><a href="/handbook/marketing/product-marketing/technical-marketing/">Technical Marketing, SCM (acting)</a></li>
<li><a href="/handbook/marketing/strategic-marketing/technical-marketing/">Technical Marketing, Agile</a></li>
<li><a href="/handbook/marketing/strategic-marketing/technical-marketing/">Technical Marketing, SCM (acting)</a></li>
story: |
Tye joins GitLab with a background in product marketing, solution architecture, business analytics and customer marketing.
Tye loves to golf and travel with his family of three.
......@@ -16061,8 +16061,8 @@
- Strategic Marketing
- Product Marketing
expertise: |
<li><a href="/handbook/marketing/product-marketing/pmmteam/">Product Marketing, Agile</a></li>
<li><a href="/handbook/marketing/product-marketing/pmmteam/">Product Marketing, SCM</a></li>
<li><a href="/handbook/marketing/strategic-marketing/pmmteam/">Product Marketing, Agile</a></li>
<li><a href="/handbook/marketing/strategic-marketing/pmmteam/">Product Marketing, SCM</a></li>
story: |
Brian is a longtime open source contributor who lives GitLab's mission that "everyone can contribute." He's been a leader in the open science community since helping start it in the 1990s. As a former frontend web developer, Brian endured the early years before git and agile, then happily joined those revolutions while consulting for clients in science, technology, government, media, and marketing.
 
......@@ -17639,7 +17639,7 @@
- Strategic Marketing
- Product Marketing
expertise: |
<li><a href="/handbook/marketing/product-marketing/pmmteam/">Product Marketing, Regulated Industries/Public Sector</a></li>
<li><a href="/handbook/marketing/strategic-marketing/pmmteam/">Product Marketing, Regulated Industries/Public Sector</a></li>
<li><a href="https://about.gitlab.com/company/culture/inclusion/">GitLab Diversity, Inclusion & Belonging Advisory Group</a> member</li>
story: |
Traci loves to travel, particularly places with great cuisine and wines, and gets especially excited about opportunities to learn about other cultures, people, and traditions. As a technology go-to-market strategist, she specializes in bringing teams together to execute innovative ways to approach industry challenges. After working in tech and consulting for over two decades, she sees team potential outside of traditional methods and practices. When she isn't teaching her five grown children how to ‘adult’, she dreams of a professional career as a beach critic and sand goddess.
......@@ -20595,7 +20595,7 @@
- Strategic Marketing
- Product Marketing
expertise: |
<li><a href="/handbook/marketing/product-marketing/pmmteam/">Product Marketing, Agile</a></li>
<li><a href="/handbook/marketing/strategic-marketing/pmmteam/">Product Marketing, Agile</a></li>
story: |
Cormac is a former industry analyst who made the jump to Product Marketing and never looked back. He lived in Southern California long enough to hug Mr. T twice and use the word "stoked" to describe how he feels about the team at Gitlab. When he's not punching keys, Cormac is probably riding a bike or hanging with his fantastic wife and epic dogs.
 
......@@ -20617,7 +20617,7 @@
- Product Marketing
- Ops Section
expertise: |
<li><a href="/handbook/marketing/product-marketing/pmmteam/">Product Marketing, Simplify DevOps</a></li>
<li><a href="/handbook/marketing/strategic-marketing/pmmteam/">Product Marketing, Simplify DevOps</a></li>
story: |
Prior to GitLab, Saumya has played multiple roles across Product Management, Marketing & Consulting at VMware, Micro Focus & HP. In her spare time, Saumya loves working out (including Crossfit, Boxing & Yoga) & doodling - sometimes a combination of the two.
remote_story: |
......@@ -20848,8 +20848,8 @@
- Strategic Marketing
- Technical Marketing
expertise: |
<li><a href="/handbook/marketing/product-marketing/technical-marketing/">Technical Marketing, DevSecOps</a></li>
<li><a href="/handbook/marketing/product-marketing/technical-marketing/">Technical Marketing, GitOps (acting)</a></li>
<li><a href="/handbook/marketing/strategic-marketing/technical-marketing/">Technical Marketing, DevSecOps</a></li>
<li><a href="/handbook/marketing/strategic-marketing/technical-marketing/">Technical Marketing, GitOps (acting)</a></li>
story: |
I'm a Technical Marketing Manager at Gitlab. Keeping Austin Weird 🌵 one cold-brew at a time.
 
......@@ -20869,7 +20869,7 @@
- Strategic Marketing
- Technical Marketing
expertise: |
<li><a href="/handbook/marketing/product-marketing/technical-marketing/">Technical Marketing, SCM</a></li>
<li><a href="/handbook/marketing/strategic-marketing/technical-marketing/">Technical Marketing, SCM</a></li>
story: |
Passionate about applied R&D, hackathons, programming, storytelling and marketing.
 
......@@ -20890,7 +20890,7 @@
- Strategic Marketing
- Technical Marketing
expertise: |
<li><a href="/handbook/marketing/product-marketing/technical-marketing/">Technical Marketing, GitOps/IaC</a></li>
<li><a href="/handbook/marketing/strategic-marketing/technical-marketing/">Technical Marketing, GitOps/IaC</a></li>
story: |
Cesar joins GitLab with a background in operations, development, consulting, technical pre-sales, competitive sales, and technical product marketing. Cesar loves to travel and play and watch good quality soccer.
 
......@@ -23060,8 +23060,8 @@
- CI/CD
- Ops Product Marketing Counterpart
expertise: |
<li><a href="/handbook/marketing/product-marketing/pmmteam/">Product Marketing, CI</a></li>
<li><a href="/handbook/marketing/product-marketing/pmmteam/">Product Marketing, CD</a></li>
<li><a href="/handbook/marketing/strategic-marketing/pmmteam/">Product Marketing, CI</a></li>
<li><a href="/handbook/marketing/strategic-marketing/pmmteam/">Product Marketing, CD</a></li>
story: |
Parker loves all things open source and has a passion for injecting positivity into the workplace. He's delighted to be a part of GitLab after working in the DevOps space for several years across multiple different roles. He enjoys rooting for NC State, banging on the drums, gaming, and traveling with his partner to see live music in his free time!
 
......@@ -36,7 +36,7 @@ with the details of the category can understand what is being discussed. -->
 
#### Target Audience
<!--
List the personas (https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas#user-personas) involved in this category.
List the personas (https://about.gitlab.com/handbook/marketing/strategic-marketing/roles-personas#user-personas) involved in this category.
 
Look for differences in user's goals or uses that would affect their use of the product. Separate users and customers into different types based on those differences that make a difference.
-->
......
......@@ -6,7 +6,7 @@ module Lint
'/handbook/engineering/projects',
'/handbook/product/product-categories',
'/handbook/business-ops/order-processing',
'/handbook/marketing/product-marketing/competitive/compete',
'/handbook/marketing/strategic-marketing/competitive/compete',
'/handbook/hiring/charts/sales'
].freeze
 
......
......@@ -25,11 +25,11 @@ If you create a merge request during a period where there is an issue in master
 
Once the issue in master is fixed, you can solve this by using terminal to merge the latest version of master into your branch (which you can find in your [merge request](https://docs.gitlab.com/ee/user/project/merge_requests/)).
 
For those who primarily use Web IDE to interface with GitLab, it can feel foreign to engage [locally](/handbook/marketing/product-marketing/getting-started/102/). Before diving in deeper, be sure to read our [_GitLab 101 – a primer for the non-technical_](/blog/2019/08/02/gitlab-for-the-non-technical/) blog post.
For those who primarily use Web IDE to interface with GitLab, it can feel foreign to engage [locally](/handbook/marketing/strategic-marketing/getting-started/102/). Before diving in deeper, be sure to read our [_GitLab 101 – a primer for the non-technical_](/blog/2019/08/02/gitlab-for-the-non-technical/) blog post.
 
The process is fairly straightforward once you have completed the [necessary steps listed in the GitLab Handbook to edit locally](/handbook/git-page-update/).
 
Once you are properly equipped to edit locally, open a [terminal window](/handbook/marketing/product-marketing/getting-started/102/#a-little-terminal-time) and execute the following.
Once you are properly equipped to edit locally, open a [terminal window](/handbook/marketing/strategic-marketing/getting-started/102/#a-little-terminal-time) and execute the following.
 
1. Navigate to the appropriate project. If you've cloned the project to your root directory, try `cd www-gitlab-com`
1. `git checkout master`
......
......@@ -119,7 +119,7 @@ The process is comprised of four key stages:
1. What we reimplement in GitLab
1. What we discard/EOL
1. What is critical for user migration
1. Target [product tiers](/handbook/marketing/product-marketing/tiers/) in GitLab
1. Target [product tiers](/handbook/marketing/strategic-marketing/tiers/) in GitLab
1. Barriers for implementation
1. Deal Milestones:
1. We aim to set 3 milestones at 2, 4 and 6 months from joining GitLab, to provide a concise set of goals which should cover the bulk of our product interest in the target company
......
......@@ -69,7 +69,7 @@ Much of the data within and supporting the Customer Segmentation Dashboard is [O
 
### Key Terms
 
1. [Product Category, Product Tier, Delivery](https://about.gitlab.com/handbook/marketing/product-marketing/tiers/#overview)
1. [Product Category, Product Tier, Delivery](https://about.gitlab.com/handbook/marketing/strategic-marketing/tiers/#overview)
1. [Sales Segment](https://about.gitlab.com/handbook/sales/field-operations/gtm-resources/#segmentation)
1. [Account Owner Team](https://about.gitlab.com/handbook/sales/#initial-account-owner---based-on-segment)
1. [Territory](https://about.gitlab.com/handbook/sales/territories/#territories)
......
......@@ -15,7 +15,7 @@ title: "Product Geolocation Analysis"
 
Understanding where your product is used around the world is an important step towards developing a more complete understanding of your customers, your product's global reach, and related location insights.
 
Currently, the majority of GitLab's customers choose to [download, install, and host a GitLab self-managed instance](/handbook/marketing/product-marketing/dot-com-vs-self-managed/#why-you-probably-want-gitlabcom), which is why we are [focused heavily on delivering a great self-managed customer experience](/direction/#strategic-challenges).
Currently, the majority of GitLab's customers choose to [download, install, and host a GitLab self-managed instance](/handbook/marketing/strategic-marketing/dot-com-vs-self-managed/#why-you-probably-want-gitlabcom), which is why we are [focused heavily on delivering a great self-managed customer experience](/direction/#strategic-challenges).
 
To make the right data-driven decisions on the self-managed product lifecycle and what features to invest in, [our self-managed customers](/is-it-any-good/) sends GitLab a weekly [usage ping](/handbook/customer-success/tam/usage-ping-faq/) at an instance-level by [enabling usage ping on their self-managed instance](https://docs.gitlab.com/ee/user/admin_area/settings/usage_statistics.html#instance-level-statistics) or by sharing the values with our Customer Success team.
 
......@@ -70,7 +70,7 @@ Some data supporting Product Geolocation Analysis is classified as [Orange](/han
- [Instance](https://docs.gitlab.com/ee/development/product_analytics/event_dictionary.html)
- Instance User Count - the total number of users on an instance
- [Paid User](/handbook/product/performance-indicators/#paid-user)
- [Product Tier](/handbook/marketing/product-marketing/tiers/#overview)
- [Product Tier](/handbook/marketing/strategic-marketing/tiers/#overview)
- [Usage Ping](https://docs.gitlab.com/ee/development/product_analytics/event_dictionary.html)
- [Version](/handbook/sales/process/version-check/#what-is-the-functionality-of-the-gitlab-version-check)
 
......
......@@ -55,7 +55,7 @@ Some data supporting MAU/TMAU/Section MAU/SMAU/GMAU/AMAU Analysis is classified
- [Instance](https://docs.gitlab.com/ee/development/telemetry/event_dictionary.html)
- Instance User Count - the total number of users on an instance
- [Paid User](/handbook/product/performance-indicators/#paid-user)
- [Product Tier](/handbook/marketing/product-marketing/tiers/#overview)
- [Product Tier](/handbook/marketing/strategic-marketing/tiers/#overview)
- [Usage Ping](https://docs.gitlab.com/ee/development/telemetry/event_dictionary.html)
- [Version](/handbook/sales/process/version-check/#what-is-the-functionality-of-the-gitlab-version-check)
 
......
......@@ -136,7 +136,7 @@ The snippet called `feature_usage_this_agg_period_and_growth(feature)` ([SQL sou
 
This snippet can be used with the date-range and aggregation filters. It has been used in several dashboards, one of them is the [Secure Metrics dashboard](https://app.periscopedata.com/app/gitlab/410654/Secure-Metrics)
 
We are planning to build a second snippet to report on the adoption rate per [product tier](/handbook/marketing/product-marketing/tiers/). This snippet will allow to easily calculate among the instances that send us usage pings in a given period, the number of instances that use a specific feature.
We are planning to build a second snippet to report on the adoption rate per [product tier](/handbook/marketing/strategic-marketing/tiers/). This snippet will allow to easily calculate among the instances that send us usage pings in a given period, the number of instances that use a specific feature.
 
###### Examples
 
......
......@@ -29,7 +29,7 @@ Make sure to save these credentials as distinct from your regular GitLab credent
- [renew subscription quote](/handbook/sales/field-operations/sales-operations/deal-desk/#renew-subscription-quote)
- [Quote Approval instruction](/handbook/business-ops/order-processing/#how-to-submit-a-quote-for-discount-and-payment-term-approval)
- [Good resource of helpful links from TAMs](https://gitlab.com/gitlab-com/account-management/commercial/triage/blob/master/LINKS.md)
- [How GitLab.com Subscriptions Work](/handbook/marketing/product-marketing/enablement/dotcom-subscriptions/)
- [How GitLab.com Subscriptions Work](/handbook/marketing/strategic-marketing/enablement/dotcom-subscriptions/)
 
## Important Links for Customers and Prospects
 
......
......@@ -463,7 +463,7 @@ Since GitLab is an open core project, we'll always create much more value then w
These straightforward ways are not possible for the following reasons:
 
1. Scope: charging more for adoption would hurt the adoption of GitLab for the whole lifecycle. In January 2018, version control is 10 times more popular than the next feature (CI). We need the features to spread organically, so people can create more value with GitLab. People are much more willing to pay when they are already using a part of the lifecycle.
1. Size: many other software companies limit the maximum amount of users in certain [tiers](/handbook/marketing/product-marketing/tiers/). For GitLab, we can't do this because we [promise the open source version won't contain artificial restrictions](/company/stewardship/#promises). We can do it in our proprietary tiers, but this doesn't seem symmetrical. It also feels unfair, if you have to pay more simply by being a bit larger then the limit.
1. Size: many other software companies limit the maximum amount of users in certain [tiers](/handbook/marketing/strategic-marketing/tiers/). For GitLab, we can't do this because we [promise the open source version won't contain artificial restrictions](/company/stewardship/#promises). We can do it in our proprietary tiers, but this doesn't seem symmetrical. It also feels unfair, if you have to pay more simply by being a bit larger then the limit.
 
So we're left with charging for features.
We can't charge for each feature separately, since that is unwieldy for the customer.
......@@ -480,7 +480,7 @@ To simplify the above, we base our feature groupings on champion position (see b
## Buyer-Based-Open-Core
 
We make feature tiering decisions based on: **"Who cares most about the feature"**.
Our [four tiers](#four-tiers) are differentiated based on [the buyer persona](/handbook/marketing/product-marketing/roles-personas/#buyer-personas) or IC who buys GitLab, from individual contributor, to manager, to director, to executive. Every person in the company [is on the same tier](/handbook/ceo/pricing/#multiple-plans-for-one-customer), even if they don't use all the features.
Our [four tiers](#four-tiers) are differentiated based on [the buyer persona](/handbook/marketing/strategic-marketing/roles-personas/#buyer-personas) or IC who buys GitLab, from individual contributor, to manager, to director, to executive. Every person in the company [is on the same tier](/handbook/ceo/pricing/#multiple-plans-for-one-customer), even if they don't use all the features.
The feature is put in the plan based on what champion is most likely to **care** about it.
Buyers make sense, since a higher-cost plan needs a higher-placed buyer.
 
......
......@@ -755,9 +755,9 @@ If a term is ambiguous don't use it, for example our [hiring definitions](/handb
 
Make sure that projects and working groups have clear and direct names. Prefer "CI Spend Reduction Working Group" to "Project Raven Working Group".
 
Make sure that people can infer as much as possible from the word, for example our [subscription options](/handbook/marketing/product-marketing/tiers/) allow you to know if someone if using self-managed or GitLab.com.
Make sure that people can infer as much as possible from the word, for example our [subscription options](/handbook/marketing/strategic-marketing/tiers/) allow you to know if someone if using self-managed or GitLab.com.
 
Make sure terms don't overlap without clearly defining how and why, for example see our [tier definitions](/handbook/marketing/product-marketing/tiers/#definitions).
Make sure terms don't overlap without clearly defining how and why, for example see our [tier definitions](/handbook/marketing/strategic-marketing/tiers/#definitions).
 
Keep terms to one or at most two words to prevent people from introducing ambiguity by shortening a term. When using two words make the first word unique because people tend to drop the second word more often.
 
......
......@@ -69,7 +69,7 @@ When the demo systems team was established in October 2019, we created a prelimi
<tr>
<td>FY21-Q2</td>
<td><a href="https://gitlab.com/gitlab-com/customer-success/demo-systems/demo-feature-requests/demosys-okrs/-/issues/1">demosys-okrs#1</a></td>
<td>Add generated sample data to Demo Data Designer with <a href="/handbook/marketing/product-marketing/roles-personas/">Marketing personas</a></td>
<td>Add generated sample data to Demo Data Designer with <a href="/handbook/marketing/strategic-marketing/roles-personas/">Marketing personas</a></td>
</tr>
<tr>
<td>FY21-Q2</td>
......
......@@ -159,7 +159,7 @@ Customer Success team members maintain a [FAQ](/handbook/customer-success/faq) t
* [Client Use Cases](/handbook/use-cases/)
* [Proof of Value Guidelines](/handbook/sales/POV/)
* [Account Planning Template for Large/Strategic Accounts](https://docs.google.com/presentation/d/1yQ6W7I30I4gW5Vi-TURIz8ZxnmL88uksCl0u9oyRrew/edit?ts=58b89146#slide=id.g1c9fcf1d5b_0_24))
* [Sales Demo](/handbook/marketing/product-marketing/demo/)
* [Sales Demo](/handbook/marketing/strategic-marketing/demo/)
* [Sales Development Group Handbook](/handbook/marketing/marketing-sales-development/sdr/)
* [With Whom to Talk to Ask Questions or Give Feedback on a GitLab feature](/handbook/product/product-categories/#devops-stages)
* [CEO Preferences when speaking with prospects and customers](/handbook/ceo/#sales-meetings)
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment