Hey folks, what do you think about dedicated DevEx & Infra PE teams? We have this split for quite a while, and though especially DevEx is not mainly doing "typical" DevEx platform engineering, I struggle a lot with this decision. For me, DevEx is a cross-cutting concern, that needs to be present in every capability / "sub-platform" that is provided. I feel it's not natural and efficient to go through another team to speak to your "customers", i.e. the devs, while implementing the stuff they use. What do you think, and what are your experiences with this? 🤔

Why dont you set up a meeting about that? I would be happy to discuss

@Mehmet Yildiz Thank you for the offer, will get back to you after PlatformCon, busy times at the moment 😉

Hey Dirk. A couple things I thought about after our call. While you can distribute DevEx responsibilities across teams (perhaps something like a regular working group of product managers), someone still needs to be responsible for relevant reports to help senior leadership stay in the loop, help communication approaches stay in sync, ensure statistical rigor, and other cross-cutting concerns. Also, we didn't discuss team foci, so ignore if you're already aware of this. A common antipattern is to focus platform teams around tools instead of users. AirBnB restructured their teams around developer persona workflows, and saw double-digit YOY improvements for 2+ years, aligning with DORA's 2023 findings that Teams prioritizing user needs achieve 40% higher organizational performance.