Initial draft of Ride Alongs - Exposing New SA's to Common Scenarios
Why is this change being made?
As the solutions architecture organization grows, we want to learn from one another.
- https://poffey21-master-patch-42173.about.gitlab-review.app/handbook/customer-success/solutions-architects/processes/activity-capture/activity-desc/#description-for-enterprise-and-commercial-sa-activity-type
- https://poffey21-master-patch-42173.about.gitlab-review.app/handbook/customer-success/solutions-architects/sa-practices/ride-alongs/
Related Issue for Adding to Troops: https://gitlab.com/gitlab-com/sales-team/field-operations/customer-success-operations/-/issues/1854
Author Checklist
-
Provided a concise title for this Merge Request (MR) -
Added a description to this MR explaining the reasons for the proposed change, per say why, not just what - Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
-
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
Maintained by
section on the page being edited - If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR - If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.
Edited by Tim Poffenbarger