SME Operations - Collaboration Project, Groups, Slack Channels
StackOverflow (TBD)
The preferred channel is our StackOverFlow for Teams via #cs-questions.
- Maintain List of SMEs (also in StackOverFlow) and SME Associates
Make sure that whoever is designated as an SME is listed as such in Stack Overflow. This will ensure that questions tagged with those relevant topics get routed to the right folks.
It should be part of the regular rigor that SMEs review questions in Slack (specifically #cs-questions) and Stack Overflow to ensure the answers are upvoted and relevant as new changes/features get released.
We can also use Stack Overflow for FAQs and Articles related to those particular areas.
TODO: Need to detail what exactly is the process to add SMEs to StackOverFlow
SME Google Groups
Each SA Area Lead should set up SA and CS SME Google Groups for calendars. Have also both SA program Leads owners also, as a backup in case SA Area Lead is OOO
Use list of SA SMEs and CS SMEs to form Groups
SME Area | SME Group |
---|---|
SME Area Leads Group | cs-sme-leaders sa-sme-leaders |
AI | sme-ai |
App Security | cs-sme-appsec sa-sme-appsec |
Dedicated | cs-sme-dedicated sa-sme-dedicated |
Plan | cs-sme-plan sa-sme-plan |
CICD/Runner | cs-sme-ci sa-sme-ci |
Metrics & Observability | cs-sme-metrics sa-sme-metrics |
Security | cs-sme-security sa-sme-security |
Support | cs-sme-support sa-sme-support |
SME Slack Channels
To facilitate effective communication and collaboration between Subject Matter Experts (SMEs) and the field teams, the following Slack channel structure is recommended:
SME Program Leadership Channel
Purpose: Async Coordination among SME Area Lead on any changes or decisions made concerning the SME program.
SME Area | Slack Channel That Currently Exists | Slack Channels Created to be used Going Forward |
---|---|---|
SME Program Leadership Channel | #sme-program-launch-planning |
#sme-program-leaders |
Channel for all SMEs in All Areas
Purpose: This is the main channel for all SME-related discussions and announcements. It serves as a central hub for:
- General SME program updates
- Cross-domain collaboration
- Sharing best practices and success stories
- Coordinating SME activities across different areas of expertise
SME Area | Slack Channel |
---|---|
All SMEs | cs-subject-matter-experts |
SME Area Slack Channels
Purpose: These channels are mainly for SME Program Leads, SME Area Leads, SMEs and SME Associates. They are used for:
- Asynchronous meetings
- Discussions on architectural challenges
- Competitive analysis
- Identifying and addressing enablement needs
SME Area | Slack Channel That Currently Exists | Slack Channels Created to be used Going Forward |
---|---|---|
AI | #sa-ai-sme-team #cs-sme-ai |
#sme-ai |
App Security & Compliance | #appsec-sme-team #cs-sme-security-compliance |
#sme-appsec |
Dedicated | #sme-dedicated | |
Plan | #cs-sme-plan | #sme-plan |
CICD/Runner | #cs-sme-ci | #sme-ci |
Metrics & Observability | #cs-sme-metrics | #sme-metrics |
SME Request Channels
Purpose: These channels are used for:
- Submitting SME requests for specific opportunities
- Coordinating SME involvement in customer engagements
- Tracking and managing SME requests
SME Area | Slack Channel |
---|---|
AI | #ai-sme-request |
App Security & Compliance | #appsec-sme-request |
Dedicated | #dedicated-sme-request |
Plan | #plan-sme-request |
CICD/Runner | |
Metrics & Observability |
SME Field Technical Channels
Purpose: These channels are open to all SMEs, Product Managers (PMs), and interested Solutions Architects (SAs) and Account Executives (AEs). They serve to:
- A place for team members supporting customer evaluations of GitLab features.
SME Area | Slack Channel That Currently Exists |
---|---|
AI | #ai-field-technical (may deprecate due to overlap with #sme-ai) |
App Security & Compliance | TBD |
Dedicated | TBD |
Plan | TBD |
CICD/Runner | TBD |
Metrics & Observability | TBD |
SME Collaboration Projects
Each SA Area Lead should set up SME Collaboration project (See App Security Example)
SME Area | Collaboration Project Link |
---|---|
AI | https://gitlab.com/gitlab-com/customer-success/subject-matter-experts/ai-sme |
App Security | App Security SME Project |
Dedicated | |
Plan | |
CICD/Runner | |
Metrics & Observability |
SME Metrics (TBD)
To effectively measure the impact and success of the SME program, we will track the following metrics:
- Technical Win Rate:
- Metric: Percentage of wins in opportunities with SME involvement
- Calculation: (Number of won opportunities with SME engagement / Total number of opportunities with SME engagement) * 100
- Goal: Increase win rate by 10% compared to baseline within 12 months
- Product Feedback Loop Effectiveness:
- Metric: Number of actionable feedback items provided to and received from product teams
- Calculation: Track feedback items submitted by SMEs and product updates based on SME input
- Goal: Implement at least 5 product improvements based on SME feedback per quarter
- Pipeline Growth:
- Metric: Percentage increase in pipeline value for opportunities with SME involvement
- Calculation: ((Current quarter pipeline with SME involvement - Previous quarter pipeline with SME involvement) / Previous quarter pipeline with SME involvement) * 100
- Goal: 15% quarter-over-quarter growth in pipeline value
- Opportunity Stage Progression:
- Metric: Percentage of opportunities moving from Stage 2 to Stage 3 and Stage 3 to Stage 4 with SME involvement
- Calculation: (Number of opportunities progressing to next stage / Total number of opportunities at current stage) * 100
- Goal: 25% improvement in stage progression rate compared to non-SME involved opportunities
- SME Engagement Efficiency:
- Metric: Average time to SME assignment and initial engagement
- Calculation: Sum of (SME assignment date - Request submission date) / Total number of SME requests
- Goal: Reduce average time to SME engagement by 20% within 6 months
- Customer Satisfaction:
- Metric: Net Promoter Score (NPS) for opportunities with SME involvement
- Calculation: Standard NPS calculation based on customer surveys
- Goal: Achieve and maintain an NPS of 50 or higher for SME-involved opportunities
- Knowledge Transfer Effectiveness:
- Metric: Number of SME-led training sessions and knowledge base articles created
- Calculation: Sum of training sessions conducted and articles published by SMEs
- Goal: Minimum of 4 training sessions and 10 knowledge base articles per SME per quarter
- Stack Overflow Engagement:
- Metric: Response rate and quality of SME answers on Stack Overflow
- Calculation: (Number of SME responses / Total number of relevant questions) * 100; Average upvotes per SME answer
- Goal: 90% response rate to relevant questions; Average of 5 upvotes per SME answer
Reporting and Analysis:
- Generate monthly reports on these metrics to track progress and identify trends
- Conduct quarterly reviews to assess SME program effectiveness and make necessary adjustments
- Use data visualization tools to create dashboards for easy monitoring of key metrics
By consistently tracking and analyzing these metrics, we can ensure the SME program’s continuous improvement and demonstrate its value to the organization.
New SME Area of Expertise Process
TBD - Define the process to determine whether a SME Area of Expertise should be established or not.
These are the differences between SMEs Areas of Interest and Formal SME Programs
SME Area of Interest | Formal SME Areas | |
---|---|---|
1. CICD/ Runners 2. Metrics & Observability 3. Embedded Systems |
1. AI 2. App Security 3. Dedicated 4. Plan |
|
Leadership Structure | No official SME Area Leader, or SMEs. Can be a pool of interested folks of SME Associates. One person driving program |
[x] SME Area Leads [x] SMEs [x] SME Associates |
Operations | [ ] Formal List of SA and CS SMEs [x] List of SME Associates or Interested Folks [ ] SME Google Groups [x] Slack Channels - General [ ] Slack Channel - Request a SME [ ] Collab Project [ ] StackOverFlow |
[x] Formal List of SA and CS SMEs [x] List of SME Associates [x] SME Google Groups [x] Slack Channels - General [x] Slack Channel - Request a SME [x] Collab Project [x] StackOverFlow |
Cadences | [ ] ARR Driver [ ] SME Area Leads Meetings [x] SME Area Pod Cadences [ ] PM/ SME Area Cadences [x] PM Roadmaps [x] Technical Skills Exchange Meetings can be in the form of trainings, async, office hours etc |
[x] ARR Driver [x] SME Area Leads Meetings [x] SME Area Pod Cadences [x] PM/ SME Area Cadences [x] PM Roadmaps [x] Technical Skills Exchange |
Process to Request a SME | No | Yes |
Customer Feedback Mechanisms | No | Yes (with Issue Boards etc) |
Engagement with PM | Some | Yes |
Once a SMEs Ares of Interest becomes a formal SME Programs These are the tasks needed to complete setup:
- Selection of SME Area Leads, SMEs
- Who decides on new SME Area
- Rollout to SA and CS Community
- Enrolling PMs
- Maintain List of SA SME Participants - Confirm List of SA SMEs and CS SMEs
- Maintain list of potential SMEs (SME Associates) as a pool for each area
- Create the necessary SME google groups for calendar purposes
- Set up Stack OverFlow with SMEs to answer questions.
- Set up SME Collaboration project
- Set up SME Google Groups
- Set up SME Slack Channels for all SME Areas
- Set up SME Slack Channels for SME Requests
- Update Handbook on SME Operations
6f6d0996
)