Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Market Insights

  1. You are here:
  2. Handbook
  3. Marketing
  4. Brand and Product Marketing
  5. Product and Solution Marketing
  6. Market Insights

Market Insights at GitLab

Market Insights is a function of the Market Strategy & Insights team in Product Marketing.

What is the Market Insights Program?

We are a business partner who:

Questions We Seek to Answer:

Mission of the Program

To identify, qualify, and activate new avenues of pursuit and profitability for GitLab (range: 1-3 years)

Our big picture:

ELEVATE: We seek to grow our value proposition beyond benefits/features–or even value drivers + use cases–to enable our customers’ business outcomes

IDENTIFY & ARTICULATE: We look to leverage research & insights to identify blue ocean strategy opportunities

OPERATE: We will function as the company’s think tank, helping GitLab to become our customers’ recognized and essential catalyst for success

How Our Work Supports the Organization

Deliverables that feed into and/or support the needs of other GitLab functions:

How can Market Insights benefit your team?

Market Insights deliverables can be used to (and/or augment your efforts to):

Market Insights Responsibilities

The Market Insights Process & Potential Market Approaches

METHODOLOGY

  1. Research & Data Gathering: Collect information and data points, conduct and lead research, and build internal and external relationships to determine priorities and support the program.
  2. Analysis: Synthesize and correlate data to develop fresh perspectives and innovative concepts.
  3. Validation & Iteration: Incorporate feedback into insight, recommendations, and deliverables. Adjust research direction as necessary.
  4. Develop & Present Deliverables: Translate insights and recommendations into consumable publications.
  5. Create Insights & Recommendations: Distill insight into actionable ideas.


RESEARCH PROCESS:

  1. Topic identification (internally decided or by stakeholder request)
  2. Determine required business objective
    • Research–primary or secondary (technology/market/trend/topic/industry/vertical/solution or use case, user or persona, etc.)
    • Data review & interpretation with recommendations
    • Customer/prospect call participation
    • Event speaking
    • Thought leadership content creation/review
    • Other
  3. Articulate the WHY this deliverable is needed (problem statement). What is currently happening? What is the pain that is being experienced and who is experiencing it? Why now? What will happen if the status quo continues?
    • What is your business objective and underlying rationale for this research?
    • Define the questions that must be answered

Alternatively, is there an emerging technology or solution that we need to explore? What could the intersection of the tech/solution and the GitLab proposition be? Is this tech/solution being used (or could it be used) by our current customers or by potential, non-traditional GitLab users?

  1. Create the hypothesis - Develop an explanation, argument, or analytical supposition about the topic.
  2. Create the appropriate issue(s)/epic(s) and link to source materials and related issues.
  3. Data gathering from appropriate sources: Collect information and data points, conduct and lead research. Sources include but are not limited to:
    • Primary or secondary research (e.g. IDC or Forrester we commission)
    • Social media and SEM analytics (e.g. HackerNews, LinkedIn, internal reports from SEO/SEM team)
    • Mainstream media and industry articles / reporting (Wall Street Journal, Washington Post, New York Times, BBC News, DevOps.com, Government Executive Media Group publications, etc.)
    • Market growth statistics (from industry analysts, DevOps media sources)
    • Channel / partner input
    • Internal Sales trends & reports
    • Sales feedback and QBRs
    • Customer meetings, calls & Chorus, SFDC
    • Analyst publications, conversations & presentations (e.g. Gartner, Forrester, IDC, 451 Research, etc.)
    • Competitive intelligence reports
    • CAB (product & C-level) feedback
    • Peer review comments (e.g. G2)
    • Wider future market trends and tech & business-focused reports from industry leaders (e.g. Accenture, Deloitte, McKinsey, HBR, etc.)
    • Industry conferences
    • Internal collaborative issues / topic & research requests (Please share any interesting data sources, articles, etc. we'd find helpful in the #market-insights Slack channel.)
  4. Analyze data: Synthesize and correlate data to develop fresh perspectives and innovative concepts
    • Use tools from the Market Insights Tool Chest to process and analyze data, current conditions, forecasts, trends, etc. to develop strategic recommendations.
  5. Validate & Iterate: Incorporate feedback into insight, recommendations, and deliverables. Adjust research direction as necessary.
  6. Create Insights & Recommendations: Distill insight into actionable ideas and suggested activities.
  7. Develop & Present Deliverables: Translate insights and recommendations into consumable publications. Specific deliverables may include:
    • An Innovation Play
    • A business case/rationale for investment or course of action
    • A report or summary assessment
    • A discussion
    • A presentation, whitepaper, case study, sales enablement, or executive presentation
    • A speaking engagement
    • An analyst briefing

PROCESS FOR MARKET OBSERVATION OF INDUSTRY TRENDS & EVENTS:

  1. Identify an event (virtual, webinar, in-person) for attendance or an industry deliverable to consume.
  2. Register and attend or read/watch content piece.
  3. Take notes with appropriate screenshots. Insert links to relevant related content/sites.
  4. Add GitLab-relevant insights and recommendations.
  5. Download slides and/or deliverable to the Market Insights REPORTS & PUBS folder and post the notes in the NOTES folder. Make sure to link the replay and any login credentials in the top section of the notes document.
  6. Highlight any essential learnings on the Monthly Bulletin and inform stakeholders in the # market-insights slack channel of any action items.

GENERAL PROCESS FOR INNOVATION ACTIVATION:

What market approaches might GitLab take based on the identified opportunities?

After a topic has been researched (see "RESEARCH PROCESS") and a recommendation for the business has been identified, Market Insights will help the DRI and team with next steps for activating the recommendation. (See "POTENTIAL MARKET APPROACHES".)

Recommendations for potential market approaches based on the results of the data assessed fall on the following spectrum of activity, ranging from the easiest level of effort, Solution or Use Case Development, to Innovation Play/Campaign to Roadmap/Feature Development to Category Creation to finally the most difficult and investment-intensive, Market/Industry Repositioning.

Based on the most appropriate approach for the opportunity, Market Insights will provide activation assistance to ensure that recommendation activities are sufficiently ramped up and owned by the DRI/ stakeholder(s).

In certain cases, this may entail creating or supporting the development of a full business case for E-Group presentation and approvals. In other cases, some recommendations may initially be best activated in an experimental manner, allowing data to be collected that can serve as real-world proof points for further analysis and recommendation.

Based on business priorities and constraints including executive direction, level of effort, cost, time, and other factors, we may choose to:

BUYER PERSONA DEVELOPMENT PROCESS:

  1. Gather research requirements. Define anticipated usage of research deliverable (persona profile).
  2. Define the buyer journey for the persona and understand all of the corresponding organizational touchpoints.
  3. Define research factors/dimensions and obtain stakeholder buy-in.
  4. Perform a secondary research market analysis using: publicly available materials (Google search), analyst briefings/reports/primary research results, etc. to construct an initial understanding and framework of the identified persona and to identify what is missing to complete a full persona profile.
  5. Develop the survey research instrument. Review with stakeholders and the UX team to validate. If feasible, test externally in a small setting and iterate based on feedback. Use Qualtrics as the survey tool.
  6. Field the survey with internal and externally obtained target audiences. Use third party vendors to provide a blind experience, if possible.
  7. Perform analysis and synthesis of the survey responses.
  8. Using respondents and/or third party vendors, recruit for and plan the interview portion of the study.
  9. Conduct approximately (10-30) one-on-one interviews with a wide demographic of the targeted audience(s). Use Zoom and record the calls. Note: It is important to obtain written permission to record in advance from the participants. Email is sufficient; however, ensure a double opt-in and add a line in that confirmation that they "may withdraw their consent" by informing you via email "at any time."

Resources:

  1. Perform analysis and synthesis of the interviews.
  2. Optional: Conduct messaging research interviews to determine how specific personas relate to products/branding/messaging, validate research from the first round of interviews, and fill in any gaps.
  3. Create the persona profile.
  4. Execute an enablement plan:
    • Share via the Handbook
    • Share on Slack channels
    • Hold an enablement session for Marketing/Sales

BUYER PERSONA INTERVIEW OUTREACH:

Resources:

FOCUS GROUP (IN-PERSON) PROCESS

  1. Gather research requirements and determine objectives/topic of focus group.
  2. Determine audience.
  3. Create recruitment and incentive plan. Develop screener questions.
    • Recruitment sources may include:
    • Past conference attendees
    • Previous survey respondents who said they would participate in future research
    • Social media outreach
    • Booth visitors or general tradeshow attendees
  4. Select moderator and co-moderator/recorder.
  5. Coordinate video recording and logistics.
  6. Coordinate venue.
  7. Create discussion guide.
  8. Develop materials to review with participants.
  9. Execute recruitment plan. Collect the following info from recruits as we get volunteers:
    • Name
    • Organization
    • Title/Role (classify into Persona Group to attempt persona diversity)
    • Phone number
    • Email - Send confirmation email/text with logistics info - Send reminder (1) hour before session
  10. Conduct session. Ensure consent forms are signed, recorded, and stored.
    • If necessary, provide Uber gift cards ($10) to participants (send after the session)
    • Pick up drinks and light snacks to have in the room
    • Verify TV/monitor connections for room
    • Determine needed signage
    • Assign handlers/guides (if necessary)
    • Collect addresses and sizes for swag distribution Things to Bring:
    • Laptop with loaded presentation of materials with connection cords
    • Include swag photo slide - Business cards - Refreshments - Tabletop signs for names - Markers - Extra masks (optional) - Printed video recording consent forms

Sample agenda:

  1. Create transcripts (use the Rev tool).
  2. Moderator and co-moderator debrief.
  3. Create initial findings report and share with research team/internal stakeholders for feedback.
  4. Prepare final report and post to research issue. Notify stakeholders.

How to Engage with Market Insights

Market Insights OKRs

FY22 Q4 OKR: Enhance the Market Insights/Strategy Program to bring more Awareness to GitLab Product Positioning

  1. FY23 Q3 Market Insights OKR 1 - Research/Data Collection at GitLab Events
  2. FY23 Q3 Market Insights OKR 2 Buyer Persona Development v2
  3. FY23 Market Insights OKR 3 - Q3 Big Rock - Market Segmentation Research & ICP Development
  4. FY23 Q3 OKR 4 - Q3 Program Improvement - Continuing Development of Methodology/Processes

How We Measure Our Results

Resources

Market Insights Team

Open in Web IDE View source