Identifying opportunities for performance improvements in the SCM category

Background

In the GitLab SaaS Paid NPS: Q4 FY23 15% of detractors were dissatisfied with GitLab's performance. On the other hand, Gitlab is also associated with speed as was shown in Brand Q4 FY23 qualitative research study results

We can conclude that performance and speed is important to customers.

Purpose

The purpose of this issue is to collaborate as a team to identify opportunities for performance and workflow speed improvements in SCM, so that we can prioritize them appropriately.

Two types of performance opportunities

There are two types of opportunities that we should distinguish. Let's call them "interface performance" and "workflow speed".

• Interface performance: pure performance as a response time of specific web pages and other (user) interfaces
• Workflow speed: workflow speed as a sequence of steps need to achieve a bigger goal

Proposal for identifying web pages or other interfaces with performance issue

We should apply the RICE framework to identify opportunities as that makes them comparable and prioritizable.

Interface performance

Interface	current delay (number in sec and if it is perceived speed)	Idea for improvement	Reach (how often do users use the interface, how many users in percent of all are affected)	Impact (the improvement we think we can make in time in seconds and perceived speed)	Confidence that Reach, Impact and Effort are correct (a comment would probably be appropriate here)	Effort to implement the improvement

Workflow performance

Workflow (description)	current steps for workflow	Idea for improvement	Reach (how often do users use the workflow, how many users in percent of all are affected)	Impact (the improvement we think we can make)	Confidence that Reach, Impact and Effort are correct (a comment would probably be appropriate here)	Effort to implement the improvement