The new DX Core 4 framework has been a critical tool for our customers leading Developer Experience initiatives. We recently spoke with one of them, and their results are incredible: ?? A 40-point improvement in their DX score after implementing Okteto. ? 8 hours saved per developer—every single week. That’s the power of better development workflows. When platform teams invest in Developer Experience, the impact scales across the entire organization: faster delivery, happier developers, and real business value. #DeveloperExperience #DX #PlatformEngineering #Productivity #DevEx
The best way to gain executive sponsorship for your developer experience and/or platform engineering initiatives is to use language your leadership understands. Leadership doesn't care about technical debt, developer happiness, or developer efficiency (some do, but most don't). Leadership cares about how your program will help them achieve their personal and company goals. So, it's key to frame the value of your initiatives using that language. DevX and PlatEng programs save organizations much time, which means three essential things: 1. You save them money (by reducing the need for team expansion) 2. You deliver projects faster (by removing friction) 3. You can deliver more projects (by enabling self-service and reducing rework) It is very important to use this language when discussing the results (actual or potential) of developer experience and platform engineering initiatives with your leadership team. It could be the difference between getting that budget or not. If you need proof points, the DX Core framework that DX recently released is a good way to start moving in this direction.