UX Research: Obtaining telemetry data from self-managed instances

What’s this issue all about?

Obtaining telemetry data from self-managed instances

Who do you want to learn from?

Non-Public Sector, self-managed users who have switched telemetry data off. The target user is likely an administrator of a GitLab instance, but also be aware of the fact that they may be instrumenting commands from higher up in their food chain rather than making the decisions themselves.

What questions are you trying to answer?

Core questions

• Why are many of our self-managed instances (excluding public sector customers) opting out of telemetry data?
• What % of our self-managed instances have telemetry data switched on vs off?

Supporting questions

• What typically drives the decision to opt-out of telemetry data?
  • Does the decision to opt-out of telemetry data result from any restrictions or company policies?
• Do users understand the benefits of GitLab collecting telemetry data?
  • How can we communicate this better?
• How can GitLab resolve concerns around usage data collection?
• What conditions would GitLab need to fulfill, in order to encourage these users to opt-in to telemetry data?

What assumptions do you have?

None right now.

What decisions will you make based on the research findings?

It entirely depends on what we find.

What's the latest milestone that the research will still be useful to you?

12.3

cc @katokpara