Interesting article, however if I may point out a few remarks. Conflict isn't necessarily coming to a common understanding of the choices made in the course of a project. Conflict comes and does emerge, when the different participants within a Design Process have different view points, expectations, and even experiences weighing in on what they think the solution should move towards. And invariably in this process the diverging ideas will come at times to a common ground, where there is a notion of a solution needing to be a compromise, whereas sometimes that conflict remains itself within the process, since those different strategies are part of the iteration cycle. They are documented, and eventually revisited, and considered as part of an MVP, or even something that loses pertinence as users/clients provide further insight into a product/solution. This article also gives the impression that the Design Process is solely driven by Design Professionals, which isn't really the case. The team efforts are a convergence of Design professionals, but also Product Ownership/Management, Development Peers, Customer Support Professionals, Sales, Researchers, the list goes on. While conflict can indeed exist within Design teams, to reduce the conflict that can be manifested in the Design Process solely to those professionals, is a myopic view of the Design Process itself. Conflict can ultimately be a powerful catalyst to seek further insight, not just for the product itself being devised, but also for the understanding of the peers who are embarking on the Product Design journey.

Written by

I’m a Design Professional. I’ve been Designing Products since 2001. http://canhenha.myportfolio.com

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store