The Release stage includes all features that help you guarantee software delivery by automating the release and delivery of applications, shortening the delivery lifecycle, streamlining manual processes, and accelerating team velocity.
The Release UX team's goal is to enable these complex flows by providing the best experience in software delivery. Our design mission is bring to the forefront simple, clean ways to make GitLab the tool of choice for deploying where, when, and how users want to.
We divided the Release stage into dedicated experience groups to align with a similar split undertaken by our engineering and PM counterparts. In order to continously deliver a seamless user experience, we share responsibility in the overal vision, goals, and research initiatives related to overlapping features. The Progressive Delivery & Release Management UX teams work closely together and have shared coverage in the following areas:
We have different user types we consider in our experience design effort. Even when a user has the same title, their responsibilities may vary by organization size, department, org structure, and role. Here are some of the people we are serving:
The product vision for Release Management has become more focused on providing advanced administration capabilities for release coordination and deployment tracking in GitLab. This is to build on the data asset we have at GitLab that starts from users purchasing GitLab to build product fast in a continuously integrated way. We will expand this journey by helping them coordinate and deploy at scale.
Today, mono-repository projects deploying with Kubernetes are most able to take advantage of our offering. We are targeting customers needing to coordinate across many teams and groups to successfully deploy. Regulated industries are top benefactors of our offering.
We will commit to stay aligned on shared UX with the engineering groups as much as possible, being the conversation drivers with product managers and other counterparts.
The Release UX team is working together to uncover customers' core needs, what our users’ workflows look like, and defining how we can make tasks easier. Our strategy involves the following actions:
|Jobs to be done framework||Quarterly|
|UX Scorecards and recommendations||Quarterly|
|Opportunity canvas||Ad hoc|
|Stakeholder interviews||Ad hoc|
|User and customer interviews||Ad hoc|
Visit Verify & Release UX page to read about the department strategy.
In partnership with Product Managers, we participate in the heuristic evaluation of competitors focused on the user experience and feature set of their products. To ensure we maintain our ability to iterate quickly as a measure of efficiency, we rely on Product Managers to assess and identify missing features in our category epics, and translate them into the competitive landscape section of our product category pages.
As design practitioners, we help by analyzing the findings and gaining insights from the data collected to make informed UX decisions. We need the support of Product Managers and other strategic counterparts to better understand the business goals of the competitive analysis. Some of the reasons why we consider it important are to:
See all Release Management and Progressive Delivery JTBDs.
The following people are members of the Release Team:
The following members of other functional teams are our stable counterparts:
Our Release (CD) UX YouTube channel includes UX Scorecard walkthroughs, UX reviews, group feedback sessions, team meetings, and more.