Design processes, primarily tasked with better understanding problems, tend to value flexibility and experimentation. Development processes, primarily tasked with pushing features into production, tend to value rigidity and repetition. Ideally, both have the same goal – to improve experiences for users. However, even the most well-intentioned teams experience friction caused by the differences in approach between disciplines.
In this session we’ll look at sources of collaboration debt between design thinking and agile software development. Then, as a group, we’ll discuss ways to leverage tools such as design systems, automated testing, and in-person user validation as means to increase project velocity, reduce code churn, and improve user experiences. Along the way we’ll try to uncover ways to organize multi-disciplinary product teams to reduce project friction without reducing the unique value each discipline can bring to the table.