Refer to https://about.gitlab.com/direction/create/design_management/ for the Design Management vision <details><summary>Old content</summary> Stage Label: ~"devops:create" | Category Label: ~"design management" | Maturity: [**n/a**](https://about.gitlab.com/handbook/product/categories/maturity) | [Issue list](https://gitlab.com/groups/gitlab-org/-/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name%5B%5D=design%20management) <!-- [Documentation]() --> ## Description We want to make UX Designers first-class users within GitLab and support their workflows as good as any product can. We are planning a competitive analysis of source control tools for designers. It’s more than version control really. When exploring the scope of this capability, we should think about multiple aspects that are relevant for an improved flow for designers. * Better asset management * Support further file format previews * Integrated graphic discussion * Version-controlled design files with visual diffs * Further quality of life improvements ## What's next & why Design management MVC: designer/developer collaboration https://gitlab.com/groups/gitlab-org/-/epics/660 Make collaboration between designers, developers and product managers on issues easier and more structured. Issues are where the details of each iteration are resolved and discussed, creating a single source of truth for what should be built. Currently designs are added to discussions and the issue description, but there is no easy way to give feedback on points of interest, or track the evolution of the designs. This iteration should make it possible for designers to upload a _design_ consisting of multiple _screens_ (a screen is a single image file). Discussions can be had on the design as a whole, or on points of interest on specific screens. When a new version of the design is ready, the designer should be able to upload a new set of screens. ## Competitive landscape https://docs.google.com/document/d/12o6h6Fm7bAjhW5AK1r-PNhvn0QrQwZncorYNia12e3Q/edit ## Analyst landscape We do not currently engage with analysts in this area. ## Top Customer Success/Sales issue(s) <!-- These can be sourced from the CS/Sales top issue labels when available, internal surveys, or from your conversations with them.--> ## Top user issue(s) <!-- This is probably the top popular issue from the category (i.e. the one with the most thumbs-up), but you may have a different item coming out of customer calls.--> ## Top internal customer issue(s) <!-- These are sourced from internal customers wanting to [dogfood](https://about.gitlab.com/handbook/product/#dogfood-everything) the product.--> ## Top Vision Item(s) <!-- What's the most important thing to move your vision forward?--> </details>