The Field Enablement team's mission is to help customers successfully grow and evolve in their journey with GitLab to achieve positive business outcomes with effective enablement solutions aligned to Gitlab’s values. Want to communicate with us? Please Slack us at #field-enablement-team.
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.
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:
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 requestand
If 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 Enablement
FieldOps- label for issues that we want to expose to the VP of Field Operations; these will often mirror issues with the
FE:CS enablement- label for Field Enablement issues related to enabling Customer Success (CS) roles
FE:sales enablement- label for Field Enablement issues related to enabling Sales roles
FE:partner enablement- label for Field Enablement issues related to enabling Partners
field 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 Enablement
field 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 Feedback
vff::new- starting point for Value Framework feedback
vff::accepted- Value Framework feedback that will be actioned on
vff::deferred- Value Framework feedback that will be deferred until more information is gathered
vff::declined- Value Framework feedback that is declined (no action will be taken)
lxp- label for GitLab Learning Experience Platform
sales onboarding- label for issues related to sales/field onboarding
QBR- requests from Sales QBRs
sales enablement sessions- label for weekly virtual sales enablement series
sko- label for issues related to Sales Kick Off
status:plan- used in conjunction with sales enablement sessions to indicate when a session topic has been prioritized but not yet scheduled
status:scheduled- used in conjunction with sales enablement sessions to indicate when a session topic has been prioritized and scheduled
strategy- plans, methods, or series of maneuvers or stratagems for obtaining specific goals or results
FE status::triage- assigned to new requests before priority status is determined
FE status::wip- work in progress that has been accepted and assigned to a DRI
FE status::backlog- things in the queue not currently being worked
FE priority::new request- label for new requests that have not yet been prioritized
FE priority::1- work that directly supports an OKR
FE priority::2- work that does not directly support an OKR but has a large impact on the field team
FE priority::3- work that does not directly support an OKR and has a low to medium impact on the field