Draft: First draft of common scenarios strategy page linking to proposed highspot pitches for CSM/CSE

Why is this change being made?

Adding a new handbook page to the CSM section. Handbook can be starting point for understanding what common customer problems/questions are. HB should document common scenarios ie “Customer is migrating from a different CI/CD tool and need best practice guidance on code review etc” and we could link to specific pitches for that scenario.

Identify common scenarios/topics/questions that would lead to recommending the HS resources. We come up with scenarios for enablement and include enablement resources through Highspot. This would help the CSM org overall too.

This will be something we can send AE’s to as well, they can get an idea of how CSE’s engage.

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, and the content is SAFE
• 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
  • The when to get approval handbook section explains the workflow in more detail
• 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.

---