What we’ve learned from our developer friends
The goal of DevOps is to change and improve the relationship of development and operations by advocating better communication and collaboration between these two business units—and to move faster (dare I say Agile). As we learned more about the DevOps way of working, our design team began to see and implement similar processes to improve communication and collaboration between different design disciplines, and to break down barriers with our development and offering management teams.
In this conversation, using our product as a case study, we will share how these practices have enabled us to overcome short- and long-term obstacles and helped prioritize common efforts in order to deliver meaningful experiences to our customers, and help our team become the well oiled machine it is today.
For over 2 years we have driven the early strategy, design and development of the user experience for the Availability Monitoring service integrated into IBM’s Bluemix Cloud platform. Throughout this time we have encountered and overcome communication, industry and market obstacles through the use—and persistence—of Design Thinking methods, open collaboration and ongoing user research. This cohesion between business goals and user needs allowed us to work with teams across time zones and take a product from conception to general availability in less than 1 year. We’ve failed, learned and failed again and have used those lessons to guide our product’s long-term vision and new differentiation efforts.
- DevOps best practices can be used by design to help breakdown barriers and increase efficiency
- Cross-discipline collaboration—between dev and design—early in the process leads to a more efficient workflow
- Design research helps keep egos, biases and assumptions away to make sure we all have the same understanding