Customer Training Roadmap
Our focus is to build a world class customer training experience focused on our Enterprise customers. By creating a foundation of consistent training materials and formatting, we will empower the CE org to better serve our Enterprise customer base and our customers to see the most value out of Sourcegraph.
: Expansion
Coming out of , the team accomplished:
- Shipped and enabled Sourcegraph 101, 102, and Admin webinars (all available on GitHub)
- Shipped Batch Changes and Code Insights webinars (available on GitHub)
- Partially shipped dev onboarding webinar (available on GitHub)
- Delivered 3 customer trainings
- Delivered 4 Office Hours trainings (Looker Dashboards, Managed Instances, Extensions, Authz/N. Available in Google Drive.)
- Collaborated with customer to ship public LMS 101 content (currently in staging; working with them to move to production and Marek to create videos; videos available in Google Drive)
- Created three Comms Templates (config review, new customer kickoff, PoC slack announcement, available in GitHub)
Going in to , the team will be focused on expanding the training library as well as increasing the number of video offerings, due to CE and customer request.
-
Offering video content
- What: We’ll build modular video units to cover the LMS versions of Sourcegraph 101, 102, and the Admin webinar.
- Why: Modular video content is a consistent request from customers and from CEs, and having modular content will allow targeted sharing of appropriate videos as part of the onboarding and enablement journey for the customer.
- Business Outcome: CEs will have both sync and async training available for customers for all three required training units; we should no longer be blocked on enablement due to a lack of resources for these three trainings.
-
Use case based webinars
- What: We’ll complete the shipping and enablement of the New Developer Onboarding webinar in both lesson plan and LMS form. Additionally, two new use case webinars will be shipped, selection TBD based on CE feedback.
- Why: Use cases remain key to selling Sourcegraph and to making it clear to devs how Sourcegraph fits into their daily workflow. Orienting around those use cases benefits customers and the CEs.
- How: Each of the three use case webinars will have at minimum a lesson plan and an LMS form. Stretch goals include video content for the units.
- Business Impact: 100% of CE team is enabled on 3 new webinars.
-
Public webinars
- What: We’ll lead, in partnership with Marketing and Engineering, three public webinars. The first, on VSCode, is scheduled. The other two (Autoindexing, and a TBD topic) have not yet been scheduled.
- Why: Having CE-delivered content for public audiences serves as a lead gen tool in alignment with other peer companies. Additionally, building out a library of recorded video content will allow that content to be leveraged by CE if needed.
- How: Partner with Marketing to deliver the webinars, guided by their knowledge of best practices.
- Business Impact: 3 webinars delivered and analyzed for trends and efficacy as a driver of sales conversations.
-
Evaluate impact
- What: We’ll attempt to establish more concrete metrics around the success or failure of the CTE program.
- Why: was focused on establishing something that could be evaluated; now that there’s baseline content, is focused on evaluating efficacy and iterating.
- How: Build CE-targeted survey to evaluate impact of program, deliver at beginning and end of quarter and compare results. Additionally, work with CE to build a post-webinar, customer-facing survey to be delivered via Zoom’s survey functionality.
- Business Impact: Survey completed with at least 70% CE participation, allowing for confirmation of whether there is improvement in efficacy, understanding, etc. throughout the quarter as a result of CTE efforts.
Additional projects
- Complete public ship of 101 and 102 Trailhead units
- Create internal training on GraphQL for the CEs, per their request
- Continue with Office Hours program
: Foundations
was focused on building a strong foundation for our future work. We focused on standardizing training content and flow, standardizing content location for greater discoverability, and producing template content for the CEs to leverage.
-
Standardizing customer training
-
What: We built and delivered standardized Sourcegraph 101, 102, and admin webinar trainings, and enabling the CE team on them, similar to previous work on Demo Flows. We also begin work on use case-oriented trainings, though this may extend into ; initial use case focus is Code Security.
-
Why: We can’t iteratively measure the impact of our work if each CE is training on completely different cadences and with completely different materials. Additionally, without training templates, CEs were forced to reinvent the wheel each time they onboard a new customer. Additionally, we wanted to bring use cases into our customer training and success model in the same way they exist in the pre-sales model.
-
How: We established a shared training repository in GitHub, a template for training materials to follow, and then transfer existing 101, 102, and admin training concepts floating around the team into standard flows. The team has beene trained on how to deliver these trainings using a train the trainer model.
-
/: Customer Onboarding Experience
/ will be focused on continuing to build upon the foundation set in , expanding to the full onboarding experience of customers post-sale closing. We’ll focus on the 90 days after a sale is closed and providing collateral and training as needed based on feedback from the customer’s usage. This collateral and training content will be used by the CE team to continue enabling their customers.
-
Create initial 90 day customer enablement onboarding plan
- What: We’ll be building a standard plan of onboarding a customer post-sale close to include which trainings to deliver in which order and use-case specific training
- Why: There is not currently a standardized onboarding experience for customers. While trainings have existed for Sourcegraph 101, 102, admin, etc: These have not been formally presented in a roll-out plan for a customer to adopt and be officially “onboarded” and move into a more “ongoing” status. Standardizing this process gives a more clear picture of “onboarding” versus “ongoing” and lays a plan out to the customer to achieve their kick-off goals.
- How: Collaborating with CE management, the CTE team will introduce an enablement plan template that outlines the trainings and outcomes expected for a 90 day roll out plan to a customer.
- Measure of Success: Creation of 90 day enablement training plan. Train CE team (train the trainer) on utilizing this enablement plan with their customers.
-
Create collateral and training for ongoing customer enablement
- What: We’ll be building a process for reporting and feedback on training and webinars, enabling CEs to provide CTE with methods to request collateral and determine training opportunities
- Why: Post onboarding, CEs need to ensure their customers are continuing to onboard developers by providing training based on usage data and feedback from the customers. This feedback will influence the CTE team priorities on enhancing existing training and collateral, as well as creating new training and collateral when required.
- How: Collateral and training will be made and updated as needed to support ongoing and customer-usage based training needs through an established feedback mechanism from CE to CTE.
- Measure of Success: CEs are enabled to know which training exists, how to gather and provide feedback on trainings, and when to utilize trainings based on customer feedback and usage data. CTE measures feedback and effectiveness of the trainings.