Design and deliver effective enablement solutions that grow field team members' and partners' expertise and confidence to drive efficient, predictable, and scalable growth for GitLab
You can find a read-out of Field Enablement team results by quarter – including overall team achievements, progress against OKRs and program-specific key accomplishments and results – in the Field Enabelement Quarterly Read-Out decks below:
Chat between David Somers (Sr. Director, Field Enablement) and Sid Sijbrandij (CEO)
Learn how Field Enablement takes a Handbook-first approach to interactive learning.
Inspired by The Advantage: Why Organizational Health Trumps Everything Else in Business by Patrick Lencioni
See our team mission in the Overview section.
On our best day, we show up with a positive attitude while demonstrating GitLab’s values along with the following behaviors to overcome the Five Dysfunctions:
See "How we do this" in the Overview section.
The below is a work in progress as we define success measures across each stage of the customer journey:
Activity does not equal Performance Knowledge does not equal Capability
Activity x Capability = Performance Knowledge x Practice = Capability
If you have a great training idea and/or enablement request, we'd love to hear it! Please make an enablement request by following this quick process:
FE priority::new request and FE status::triageFE priority::1FE priority::2FE priority::3FE status::wipFE status::backlogIf you have a Field Communications request (process change, announcement, etc.), please see the request process outlined here.
field enablement - issue initially created, used in templates, the starting point for any label that involved Field EnablementFieldOps - label for issues that we want to expose to the VP of Field Operations; these will often mirror issues with the FE priority::1 labelFE:CS enablement - label for Field Enablement issues related to enabling Customer Success (CS) rolesFE:sales enablement - label for Field Enablement issues related to enabling Sales rolesFE:partner enablement - label for Field Enablement issues related to enabling Partnersfield certification - label for issues related to /handbook/sales/training/field-certification/field communications - label for items that include work by/with the Field Communications team within Field Enablementfield events - label for Field Enablement-supported events (e.g. QBRs, SKO, President's Club, etc.)force management - label for issues related to Force Management engagement
vff - label for Value Framework Feedbackvff::new - starting point for Value Framework feedbackvff::accepted - Value Framework feedback that will be actioned onvff::deferred - Value Framework feedback that will be deferred until more information is gatheredvff::declined - Value Framework feedback that is declined (no action will be taken)lxp - label for GitLab Learning Experience Platformsales onboarding - label for issues related to sales/field onboardingQBR - requests from Sales QBRssales enablement sessions - label for weekly virtual sales enablement seriessko - label for issues related to Sales Kickoffstatus:plan - used in conjunction with sales enablement sessions to indicate when a session topic has been prioritized but not yet scheduledstatus:scheduled - used in conjunction with sales enablement sessions to indicate when a session topic has been prioritized and scheduledstrategy - plans, methods, or series of maneuvers or stratagems for obtaining specific goals or resultsFE status::triage - assigned to new requests before priority status is determinedFE status::wip - work in progress that has been accepted and assigned to a DRIFE status::backlog - things in the queue not currently being workedFE priority::new request - label for new requests that have not yet been prioritizedFE priority::1 - work that directly supports an OKRFE priority::2 - work that does not directly support an OKR but has a large impact on the field teamFE priority::3 - work that does not directly support an OKR and has a low to medium impact on the field