5 Reasons you DevEx journey will fail
Any type of transformation is hard but developer experience touches so many parts of an organization that it can be even more challenging. Its one of the reasons why so many big project fail… but they don’t have too. I have helped many organizations with just this problem.
Did you realize that over 300 billion dollars of aggregate GDP is lost every year due to developer productivity and process issues? Or that over 50% of organizations developers only spend about 30-40% of their time actually writing code?
This has led to 58% of software engineering leaders reporting that developer experience is critical to an organization’s C-suite. With this being such a focus area, let's talk about five ways you can totally screw this up… if youre not careful.
Here are the 5 key reasons why a lot of developer experience efforts fail
There is no easy button
There is a lack of product thinking across the organization
It requires a new way of thinking about problems
Cultural shift are needed to enable change
You can actually make your developer experience worse
Want to learn more of the details? Watch the video below.
If you like our content, it would be great if you consider subscribing. Its totally free, unless you want to chip in, and it really helps us out.
I usually think in my mind - when the process and tooling folks arrive at the scene then be very very very cautious... And the whole "internal Dev platform" and "DevX" has already attracted many in huge swathes. As you mention in this video the stats are staggering so even if someone claims for marketing that their <thing> saves a company 10% of that wasted time.. That's huge. 😅
So predicting we will soon have consulting and certifications specifically for IDP and DevX cropping up in huge numbers soon. And that is 6th reason DevX will fail.