CIOReview | | 19 JUNE 2022CXO INSIGHTSMost companies care about Customer Experience (CX) for their end consumers and make every effort to improve it. But what about the Developer Experience (DX)? In IT, we often claim that we have the customer in mind when we offer self-service or online services to them. But surprisingly we very often forget that the people who build these services are also customers to other services and teams. I see that a lot of companies expect to solve this with the move to the cloud and the use of portals and services from cloud providers. Unfortunately, the number of growing services and the speed of innovation of cloud providers can lead to a complete information overload and distract developers. . Furthermore, not everything that is used is 100% seamlessly integrated from Day 1. This is one of the reasons why we see a rise of enabling or platform teams in many organizations, especially when they transition into self-organized autonomous teams where teams have now more responsibilities. The platform teams are often responsible to provide a great Developer Experience inside the company and to create the foundation others can build on. This becomes especially important when you grow your engineering teams.How does good Developer Experience look like?This will differ from company to company but for me there are few important things to consider:- Reduction of cognitive load for the teams.- Self-service and autonomy remain key principles- Adoption is not forced1. Reduction of cognitive load for the teamsA key driver to improve Developer Experience is to reduce the cognitive load of the developer teams. Many teams have transitioned into DevOps teams over the last years. They took over more and more responsibilities and integrated new knowledge into their team. This causes a lot of context switching due to different tools and processes for the teams. This is often visible when teams have to do unplanned work (e.g .during incident troubleshooting, introduction of new standards and processes).. A good Developer Experience would reduce this "noise" for the teams.2. Self-service and autonomy remain key principlesOne often misunderstood part of Developer Experience is that it is not equal with giving away responsibility or ownership to another group. Instead, the goal of a good DX is to have all services which a team needs available via self-service and ideally as an API. This gives teams the opportunity to still have autonomy around their service/product. In an ideal world you would make sure that a team needs as few interactions as possible outside their main responsibility.DEVELOPER EXPERIENCE IS MORE IMPORTANT THAN YOU THINKBy Christian Rudolph, Head of DevOps, TUIChristian Rudolph
< Page 9 | Page 11 >