I'm trying to find an article that I read a while back which really resonated with me and I would like to share with my team.. But I can't remember how I came across it and I can't for the life of me find it! 🙃 It was about how Platform teams can sometimes wind up generating a lot of work for other teams (ie you all need to upgrade onto our latest platform offering, tweak your service configurations because of reason x) which goes against one of the core goals of a platform team of making things easier for their users.. If this sounds familiar, pls share the link!

I feel like this is a common story because it’s just like prioritizing documentation or technical debt, patches and upgrades and migrations take time away from features

That’s most articles. 😄 I can’t think off hand which it might be but if I come across in my never ending lists, I’ll share. 👍

yes this is definitely part of the overall story of why platform teams are valuable / what good platform teams should not do. But the article zoomed in on examples of work that a platform team can create for users (change your configuration so you can use this feature, approve this PR so we can upgrade you) and that's exactly the issue I'm seeing now.

This one perhaps @Kirstin Slevin? https://martinfowler.com/articles/platform-teams-stuff-done.html

it’s not that one either but that is an excellent article! I came across it a while back and it articulated some things I had been experiencing