• Lack of shared/standardized language across teams and development phases

• Informal Design System implementation and difficulty maintaining rules and updates

• Blurred responsibilities between disciplines

• Pushing off and forgetting design principles throughout development

A collaborative, living diagram to serve as a starting point for discussion to outline our design processes.

As we set up calls with different teams, this draft of the chart helped explain all the things we, as designers, were thinking about and how. Project managers and developers had their own opinions and ways of thinking about the process. While they found it informative to understand us, a different diagram would be need to be developed to represent the business and development needs that are subject to changing time frames and business needs.

In order to create long-lasting change, team buy-in is essential: across levels and across teams. Like most UX problems, it’s better to do research and collect more information before wire framing and designing a solution. Based on the feedback, this linear chart was a great starting point to describe a designer perspective, but in actuality, Product Manager, QA, Accessibility, and the Development Teams must be included to build a chart that more accurately describes and connects processes.