Redesign Duo Chat Welcome Screen for IDE and Web Contexts

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Background

Currently, GitLab Duo Chat's welcome screen focuses only on Q&A product questions. To better serve our users across different environments (IDE vs gitlab.com), we need to create welcome screens that highlight the most relevant capabilities for each environment.

Objectives

• Create distinct, environment-specific welcome screens for IDE and gitlab.com
  • This scope does not include contextualized page specific buttons
• Increase discovery and user engagement with Gitlab Duo features

Environment-Specific Feature Analysis

IDE Environment

Primary User Context:

• Active development
• Code understanding and modification
• Testing
• Debugging

Recommended Features to Highlight:

1. Code Explanation
   • Example button: "Explain this code block"
   • Value prop: Instant understanding of complex code
2. Test Generation
   • Example button: "Generate tests for this code"
   • Value prop: Accelerate test coverage
3. Code Suggestions
   • Example button: "Help me complete this function"
   • Value prop: Speed up development
4. Code Refactoring
   • Example button: "Refactor this code"
   • Value prop: Improve code quality
5. Fix Code
   • Example button: "Help fix this bug"
   • Value prop: Quick problem resolution

gitlab.com Environment

Primary User Context:

• Project management
• Code review
• CI/CD pipeline management
• Security analysis
• Collaboration

Recommended Features to Highlight:

1. Merge Request Assistance
   • Example button: "Summarize this merge request"
   • Value prop: Quick context on changes
2. CI/CD Support
   • Example button: "Analyze pipeline failure"
   • Value prop: Fast issue resolution
3. Security Insights
   • Example button: "Explain this vulnerability"
   • Value prop: Better security understanding
4. Issue Management
   • Example button: "Generate issue description"
   • Value prop: Faster issue creation
5. Discussion Summary
   • Example button: "Summarize this discussion"
   • Value prop: Quick catch-up on conversations

Copy Testing Plan

Phase 1: Button Copy Variations

Without the proper context, some buttons may not work. Additionally, the unpredictability of outputs requires testing our way into the correct copy.

1. Action-oriented vs Question-based

   Example for Code Explanation:
   - Action: "Explain this code"
   - Question: "What does this code do?"

2. Value-focused vs Task-focused

   Example for Test Generation:
   - Value: "Boost test coverage"
   - Task: "Generate unit tests"

3. Casual vs Professional tone

   Example for Merge Request Summary:
   - Casual: "Break down this MR for me"
   - Professional: "Summarize merge request changes"

Phase 2: Welcome Message Variations

Explore different welcome messages:

1. Capability-focused

   "Welcome! I can help you with code, testing, and deployment. What would you like to do?"

2. Context-aware

   IDE: "Ready to help you write and understand code. Choose an option below:"
   Web: "Let's make your GitLab workflow smoother. What do you need help with?"

3. Benefit-oriented

   "Save time and improve code quality with these tools:"

Success Metrics

• Increase in feature adoption rates
• Time to first meaningful interaction

Next Steps Checklist

• Create test variations for copy in IDE and Web welcome screens focused on Duo's features
• Test responses and review in IDE and Web
• Select copy that provides that helps user get to their solution the fastest
• Document opportunities for dynamic, contextualized buttons for a future release
• Review with design & PM team for feedback
• Implement changes