In the fast-paced digital world, where technology is constantly evolving, the collaboration between design and engineering teams has become more crucial than ever. The creation of seamless digital products that provide meaningful experiences to users requires a harmonious partnership between these two disciplines. However, the traditional approach of treating design and engineering as separate processes has proven to be ineffective and inefficient.

The Outdated Workflow: A Barrier to Productivity

The traditional waterfall model, which emphasizes a linear progression from design to development, has long been the standard approach in many organizations. Designers would create static prototypes using tools like Adobe Illustrator or Sketch, while engineers would implement the desired features based on these designs. This division of labor often leads to a slow and isolated workflow, resulting in subpar digital products that take a long time to build.

The design handover, a supposed "magic moment" where design finishes and engineering begins, is the root cause of many collaboration problems within product teams. The design process, which begins before the specifics of what is being built are known, is detached from the complexities of the systems that developers create. As a result, crucial design decisions may be missed, and early decisions that could improve the project's outcome are harder to make.

Flattening Waterfalls: A Shift in Workflow

To overcome the challenges posed by the traditional workflow, organizations need to adopt a more collaborative and iterative approach. By flattening the waterfalls and embracing a continuous flow, designers and engineers can work together from the beginning to the end of a project. This tighter feedback loop allows for a more agile and efficient workflow, where design and engineering processes are seen as complementary and interdependent.

Treating the digital product itself as the true design product is a fundamental principle in this new workflow. Rather than perfecting every design detail in static design tools, designers should focus on creating real components in code. This shift in mindset acknowledges that modern applications are too complex to simulate in traditional design tools and encourages a design-driven engineering culture.

Operating Like an Open Source Project

To further enhance collaboration within product teams, organizations should adopt an open-source mindset when it comes to their design systems. Instead of creating isolated design system teams, the maintenance and collaboration around the design system should be open and accessible to all. This means prioritizing the documentation, workflows, and tooling needed to accept contributions from across the organization.

By operating like an open-source project, organizations can foster a culture of shared practices, where design decisions are made collectively and knowledge is shared between designers and engineers. This collaborative approach not only speeds up the production process but also empowers teams to work faster and better around the creation of digital products.

Increasing Visibility through Automation

Automation plays a vital role in bridging the gap between design and engineering teams. By automating manual tasks and implementing continuous deployment workflows, organizations can increase visibility and make work accessible across the entire team. For example, setting up a system where pull requests are automatically deployed and posted to a communication platform like Slack allows designers to stay up-to-date with the latest developments in the codebase.

Design teams can also benefit from adopting automation in their workflows. By automating the creation of design elements that are consumed by code, designers can focus more on questioning, ideating, and communicating intent through their design tools. This not only saves time but also ensures that design decisions are grounded in the realities of the medium they are designing for.

Planning Like a Farmer: Embracing Agility

Agile processes such as Scrum and sprints have become popular frameworks for managing projects, but they often fall short in making teams work faster and better. The obsession with fixed delivery dates and detailed estimations can hinder collaboration and flexibility within product teams. Instead, organizations should embrace a "plan like a farmer" mentality, where they have a long-term perspective but plan only for the next day.

This agile and collaborative workflow allows teams to sense and respond to changes more effectively, steering them towards healthier outcomes. Rather than focusing on estimation, planning, and scoping, teams can invest their energy in creating meaningful digital products. By embracing uncertainty and adapting to reality, organizations can achieve greater speed, efficiency, and collaboration within their product teams.

Conclusion

In today's digital landscape, the collaboration between design and engineering teams is critical to the success of any digital product. By breaking away from the outdated workflow and adopting a more collaborative and iterative approach, organizations can create seamless digital experiences that make sense for users. Flattening waterfalls, making code the true design product, operating like an open-source project, increasing visibility through automation, and planning like a farmer are key principles that promote collaboration and productivity within product teams. By embracing these principles, organizations can redefine the way they build digital products and deliver exceptional experiences to their users.