Why we exist
To guide the intention of GitLab’s initial impact. Our goal is to continually shift perception by delivering positive experiences at velocity.
Where we're going
A future where everyone can contribute, consumers become contributors and we greatly increase the rate of human progress.
What we do
Create tools and processes that unlock GitLab team members and users to deliver results.
Contribute and execute on the strategy for the marketing site.
View long-term goals here: https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/foundations-agenda/
|Team Member||Role||Contact Info|
|Michael Preuss||Senior Manager, Digital Experience||- Email: email@example.com
- GitLab: @mpreuss22
- Slack: @mpreuss22
- ReadMe: michael-preuss
|Lauren Barker||Senior Full Stack Developer||- Email: firstname.lastname@example.org
- GitLab: @laurenbarker
- Slack: @lbarker
- ReadMe: lauren-barker
|Brandon Lyon||Frontend Engineer||- Email: email@example.com
- GitLab: @brandon_lyon
- Slack: @Brandon Lyon
- ReadMe: brandon-lyon
|Tyler Williams||Website Full Stack Developer||- Email: firstname.lastname@example.org
- GitLab: @tywilliams
- Slack: @Tyler Williams
- ReadMe: tyler-williams
|Laura Duggan||Frontend Engineer||- Email: email@example.com
- GitLab: @lduggan
- Slack: @Laura Duggan
- ReadMe: laura-duggan
|Stephen McGuinness||Design System Lead (Contract)||- GitLab: @smcguinness1
- Slack: @Stephen McGuinness
|Jessica Halloran||UX Designer (Contract)||- GitLab: @jhalloran
- Slack: @jhalloran
|Tina Lise Ng||UX Designer (Contract)||- GitLab: @Tinaliseng
- Slack: @Tina Lise Ng
|Javier Garcia||Frontend Engineer (Contract)||- GitLab: @jgarc257
- Slack: @Javi
|Sanmi Ayotunde||Frontend Engineer (Contract)||- GitLab: @sanmiayotunde
- Slack: @sanmiayotunde
- ReadMe: sanmiayotunde
Specific targets can be found here
Metric: Inbound marketing qualified leads.
There are many other digital marketing metrics we track for the website. These include pageviews, unique visitors, time on site, and conversion metrics for key funnels. These detailed metrics are leading indicators for the health of our North Start metric, and are internal to GitLab.
See Where should content go? to learn which web property is the most appropriate place to put different types of content. To learn what section of the website different content belongs see definitions.
The website does not include - The Docs:
docs.gitlab.com - The GitLab.com product:
gitlab.com - The Handbook:
about.gitlab.com/handbook - The blog:
We collaboratively define OKRs as a team with cross functional partners in advance of each quarter. Once OKR candidates are complete the Growth Marketing Leads review and submit for ratification.
Key Result: During Q3 FY21, we made the decision to move forward with a 3rd party CMS (content management system) for the GitLab marketing website. A vendor selection process was completed, and the decision is to implement NetlifyCMS.
Link To Slack Working Group: #wg_mktg-cms
Key Result: During Q3 FY21, we will invest in planning, designing, and building a design system for our Marketing site. The Marketing Design System will increase our efficiency and make it easier for everyone to contribute.
Link To Slack Working Group: #wg_mktg-design-system
Our goal is to deliver a release every 2 weeks. Our release day is always a Wednesday. We can push MRs at any time but for collaborative work initiates we plan a package for delivery to ensure we're improving our customer's experience rapidly.
For FY21 Q4 we have 2 sprint cycles running which start on alternate weeks.
Before a sprint starts, our team aligns on what will be delivered during the sprint. We identify issues that need to be written, write them, then add them to our boards. We weight these issues and target delivering 10 weight points per sprint.
This is the template we use for Sprint Planning
Sprint Retros allow us to reflect on what went well and what we can to do continuously improve our process.
This is the template we use for Sprint Retros
Marketing Design System Sprint Planning and Retros
CMS Sprint Planning and Retros
We use issue weight to plan and manage our work. Team members are not held to weights, they’re simply a planning and learning tool. Digital Experience weights are based on the following point scale: 1pt = .5 day
@digital-experience use this handle in any channel to mention every member of our team.