A couple of weeks ago, a tweet by Yesenia Perez-Cruz, Senior Designer at Vox Media, caught my eye. Her tweet posed what seemed like a simple question:
Usually, when these sorts of questions are posed on Twitter, there is an overwhelming variety of answers. While the answers varied, the majority who tackled the question proposed that the reason behind the lack of articles was due to the nature of the design/development process being sequential — work moves forwards not backwards. Pointing out that the process from a designer to developer is a linear process does a great job of answering Yesenia’s question… if the question was asked 10 years ago.
Today, I believe the answer is a little more complicated than this. According to the replies, some people, albeit the minority, also agree. These days, the web design process isn’t as linear as it used to be. Roles overlap and an openness to iterate frequently means that deliverables move forwards, backwards, diagonally and sideways during the life cycle of a project. In order to keep up with this, a team must communicate early and continue to communicate often. Essentially, the people in a team team need to work cohesively throughout the duration of the project instead of siloing themselves in their assigned roles.