Workshops

Common workshop topics include:

• DevOps Automation
• Portfolio and Project Management
• Security
• Advanced CI/CD

These sessions accelerate customer comfort and awareness while helping to refine and reduce technical evaluation requirements. Workshops often minimize or eliminate the need for extensive POVs and can lead directly to technical wins.

Technical Requirements

Each workshop requires:

• A dedicated GitLab instance for attendees to use during exercises
• Pre-configured class projects
• Setup of issue tracking workflows
• Additional environment preparation specific to the workshop topic

For more information, review the Hands-On Workshop Tools and Resources handbook page.

Capacity and Format

To ensure optimal experience:

• Attendance is limited to 200 or fewer participants
• This limit enables:
  • Stable working environments for all attendees
  • Timely responses to questions and issues
  • Effective hands-on guidance

Key Benefits

The workshop approach delivers multiple strategic advantages in the pre-sales process:

• Dramatically accelerates customer comfort and awareness with GitLab’s extensive feature set through direct, hands-on experience
• Substantially reduces or completely eliminates the requirement for time-consuming and resource-intensive POVs
• Provides technical teams with immediate, practical experience in applying GitLab to their specific use cases
• Often catalyzes technical wins by demonstrating clear value alignment with customer needs
• Creates an interactive environment for deep engagement with technical stakeholders
• Builds confidence in GitLab’s capabilities through guided, hands-on exploration

Audience

Workshops are strategically designed to engage a diverse technical audience, typically including:

• Software Developers and Engineering Teams: Those directly responsible for code development and deployment
• DevOps Practitioners: Professionals focused on streamlining development and operational processes
• Security Professionals: Team members responsible for application and infrastructure security
• Operations Team Members: Staff managing infrastructure and deployment environments
• Quality Assurance Engineers: Those responsible for testing and quality processes
• Platform Engineers: Professionals designing and maintaining development platforms
• Technical Architects: Those making technical decisions about tool adoption and integration

Workshop Format

Structure

1. Customer Background Discussion and Context Setting

   • In-depth exploration of the customer’s current technical landscape
   • Detailed discussion of challenges and pain points driving GitLab evaluation
   • Establishment of specific workshop objectives and success criteria
   • Understanding of customer’s existing toolchain and integration requirements
   • Review of current development processes and desired improvements

2. Comprehensive Demonstration Phase

   • Strategic showcase of GitLab capabilities aligned with customer needs
   • Live demonstration of relevant workflows and integrations
   • Real-world examples of how GitLab addresses specific customer challenges
   • Illustration of best practices and recommended approaches
   • Interactive Q&A to address specific technical questions

3. Guided Hands-on Portion

   • Step-by-step walkthrough of key GitLab features and functionality
   • Practical exercises designed to reinforce learning objectives
   • Direct assistance with configuration and setup
   • Collaborative problem-solving sessions
   • Real-time feedback and guidance from GitLab experts

4. Independent Hands-on Labs

   • Self-directed exploration of GitLab features
   • Application of learned concepts to customer-specific scenarios
   • Opportunity for deep-dive into areas of particular interest
   • Practice with advanced features and integrations
   • Freedom to experiment with different configurations and approaches

Delivery Options

The workshop format offers flexible delivery options to accommodate various customer needs:

In-Person Sessions:

• Direct, face-to-face interaction with GitLab experts
• Immediate assistance with technical questions
• Enhanced collaboration opportunities
• Stronger relationship building
• Easier handling of complex technical discussions

Remote Delivery via Zoom:

• Broader accessibility for geographically dispersed teams
• Recording capabilities for future reference
• Screen sharing for detailed technical demonstrations
• Breakout rooms for focused discussions
• Chat functionality for resource sharing and quick questions

Duration and Timing:

• Typical length: 2-4 hours, allowing for comprehensive coverage
• Strategic breaks to maintain engagement
• Flexible scheduling to accommodate different time zones
• Optional follow-up sessions for advanced topics
• Built-in buffer time for extended discussions

Workshops vs Demonstrations

Understanding the distinct characteristics of workshops and demonstrations is crucial for effective pre-sales engagement:

Workshop Preparation Best Practices

Essential Preparation Steps

1. Comprehensive Dry Runs

   • Execute multiple complete rehearsals of the workshop content
   • Practice handling various technical scenarios and potential issues
   • Prepare detailed verbal explanations for complex concepts
   • Anticipate and prepare for common customer questions
   • Document potential technical challenges and their solutions
   • Test all demonstrations in multiple environments
   • Verify all links, codes, and access requirements
   • Practice recovery procedures for potential technical issues

2. Interactive Engagement Strategies

   • Implement regular checkpoints for participant questions
   • Create natural breaks in content for discussion
   • Prepare discovery questions to gather valuable customer insight
   • Design interactive elements to maintain engagement
   • Plan for different learning styles and technical levels
   • Create opportunities for peer-to-peer learning
   • Develop contingency plans for low participation

3. Resource Management and Organization

   • Prepare comprehensive resource documentation
   • Create easily accessible link repositories
   • Organize session registration processes
   • Document all required project materials
   • Prepare backup copies of essential resources
   • Create clear instruction sets for all activities
   • Maintain updated reference materials

4. Structured Delivery Framework

   • Develop clear, step-by-step instruction sets
   • Create visual aids for complex concepts
   • Implement consistent progress tracking methods
   • Follow established presentation best practices
   • Maintain clear communication protocols
   • Create detailed session timelines
   • Prepare transition strategies between sections

Companion Role and Responsibilities

A dedicated workshop companion serves as a crucial support resource, responsible for:

Technical Support:

• Maintaining comprehensive knowledge of workshop content
• Managing Learn Labs session access and technical issues
• Providing real-time troubleshooting assistance
• Monitoring participant progress and identifying struggles
• Managing technical infrastructure during the session

Communication Support:

• Managing question queues and discussion threads
• Sharing resources and links in chat
• Documenting key discussion points
• Capturing follow-up items and action points
• Facilitating breakout sessions when needed

Documentation:

• Maintaining detailed session notes
• Recording key technical questions and answers
• Documenting customer-specific requirements
• Capturing feedback and improvement suggestions
• Creating summary reports post-workshop

Backup Coverage:

• Being prepared to take over presentation if needed
• Managing technical difficulties
• Handling unexpected situations
• Providing additional examples or explanations
• Supporting individual participants as needed

Success Metrics and Evaluation

Workshops can be evaluated based on several key success indicators:

Immediate Outcomes:

• Reduction or elimination of POV requirements
• Achievement of technical acceptance
• Positive participant feedback
• Increased understanding of GitLab capabilities
• Clarification of technical requirements

Long-term Impact:

• Acceleration of sales cycle
• Increased GitLab adoption rates
• Improved customer satisfaction
• Reduced implementation time
• Enhanced customer relationship development

Measurement Methods:

• Participant surveys and feedback forms
• Technical requirement resolution tracking
• Sales cycle duration analysis
• Implementation success metrics
• Customer satisfaction assessments

View page source - Edit this page - please contribute.