The goal of the Field Ops release schedule is to consolidate important, need-to-know Field Ops updates and deliver them on a predictable schedule to the GitLab Field team.
Because of the pace at GitLab, the Field team is often overwhelmed by the amount of information sent to them. A release schedule helps reduce confusion and increase engagement by consolidating the Field Ops-related updates and, thus, "lightening the load" on the Field team. It also allows the Field team to grow accustomed to receiving Field Ops updates at the same place and time. Furthermore, prioritization around release schedule themes and timelines allows Field Ops team to ship more purposefully in order to support more meaningful change and allow ample time for behavior changes.
The updates included in this process are strictly system/process/policy-based. Other announcements go through the normal Field Announcement Request process. The primary update types are related to Sales Ops, CS Ops, Channel Ops and Deal Desk. (Systems is a supplementary use case, but they are usually incorporated as a part of Ops updates.)
- Sales Ops is releasing ## system and process-related improvements today. Please see a summary of the changes and impacted teams below and see the [DATE Sales Ops Release eipc] for full details. Reach out in #sales-support with any questions.
- Change 1: [TITLE] (LINK TO EPIC)
- Who: (Which teams are impacted?)
- Why: (Why are we making this change? WIIFM?)
- Action: (What is the ask/next step that we're asking the audience to take?)
- Change 2: [TITLE] (LINK TO EIPC)
- Who: (Which teams are impacted?)
- Why: (Why are we making this change? WIIFM?)
- Action: (What is the ask/next step that we're asking the audience to take?)
- See the [Field Ops Changelog] for past changes.