To be a recognized partner who contributes to field & partner business outcomes. We inspire our field and partners to achieve high levels of success through the acquisition and application of knowledge, skills and behaviors - at scale - that improve productivity and accelerate customer outcomes & growth.
We envision a Field organization that has easy and intuitive access to the information and resources needed to sell effectively, and that is inspired and motivated to be a part of the GitLab team through experiences that drive meaningful connections and engagement.
Review the Field Enablement FY24 Quarterly Deliverables deck.
| Name | Title | Role |
|---|---|---|
| Ali Shahrazad | Sr. Director, Field Enablement | Mgr |
| Kelley Shirazi | Director, Global Sales and Customer Success Enablement | Mgr |
| Monica Gomez | Director, Enablement Operations | Mgr |
| Steve Wilson | Sr. Manager, Product Enablenent | IC |
| Emelie Rodriguez | Staff Program Manager, GTM Enablement | IC |
| Shannon Thompson | Sr. Field Communications Manager | IC |
| Pallavi Daliparthi | Staff Program Manager, Customer Success / Solutions Architect Enablement | IC |
| Cristian Enache | Staff Program Manager, EMEA Field Enablement | IC |
| Jess Stetson | Staff Program Manager, AMER Field Enablement | IC |
| John Blevins | Sr. Program Manager, Onboarding & Continuing Education | IC |
| Joshua Jones | Sr. Program Manager, Partner Enablement | IC |
| Omnia Radwan | Associate Program Manager, Customer Success / Solutions Architect Enablement | IC |
| Tess Dutton | Program Manager, Field Enablement Content | IC |
| Emily Hiett | Field Communications Manager | IC |
The Field Enablement and Communications teams track and measure success in three main areas:
When considering how to engage with the Field Enablement team, stakeholders should take into account the following questions:
The answer to the above questions will dictate how the Enablement team triages requests across three primary issue templates:
The Field Announcement request issue gathers requests from DRIs/stakeholders across the business to launch or announce something to the Field team – either the full team or a large segment of it. Segment-specific communications are currently out of scope and will require an Field Enablement request flow. Requesters / DRIs should open an issue using this template to track:
The issue template includes questions and instructions to assist the Enablement team in determining if the announcement requires a Field Comms-only or Field Comms and Enablement motion. Please complete the required sections of the issue template in full, providing as much detail as possible. Note that ALL questions must be answered prior to Field Enablement triaging your request.
Once the request has been triaged by Field Communications, the team will collaborate with you to clarify any outstanding details and define a launch plan. If a Field Comms and Enablement motion is required, Field Enablement will open a Field Enablement issue (below) to scope enablement-related activities and deliverables.
The Field Enablement request issue gathers ad-hoc enablement requests from DRIs/stakeholders across the business. Requesters / DRIs should open an issue using this template to track:
The issue template includes questions and instructions to scope the intended audience(s) for the enablement activities, learning objectives and priority. It also includes questions to determine if Field Communications activities are also required. Please complete the required sections of the issue template in full, providing as much detail as possible. Note that ALL questions must be answered prior to Field Enablement triaging your request.
Once the request has been triaged by Field Enablement program managers (PM), the PM will conduct any additional exploration with the requester/DRI to determine a workback plan.
For larger, more complex initiatives that involve go-to-market (GTM), cross-functional alignment, Field Enablement has created the GTM Enablement Process.
This process outlines a prescriptive process, timeline, bill of materials and DRIs for Field Enablement, Partner Enablement, Field Comms and Partner Comms for high-, medium- and low-complexity initiatives.
If Field Enablement determines that your initiative requires a GTM Enablement Process, the Field Enablement team will open an issue and populate the appropriate deliverables and due dates. DRIs/Stakeholders will be added to the issue to provide input, answer questions and review.
To reach the Field Enablement team on Slack, use #field-enablement-team
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 accreditation - 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 QBRsFE: Revenue Programs - label for issues related to Field Enablement-led pipeline growth & acceleration programssales 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 fieldac11808a)
