A lot of developer experience teams I meet with talk about wanting to promote best practices and guide and coach teams at the same time as they're building internal infrastructure-insured services. A lot of these leaders get a little bit stuck on the first part the enabling part the consulting part if you will. We actually interestingly we've been working on a new video based training for our academy which is about effective enabling teams where we talk a lot about some patterns and the patterns so one key thing that we've observed in organizations is that creating enabling teams is hard because leadership doesn't necessarily see what is this going to be the value of this enabling team.
Manuel Pais delves into one of the concepts covered in his book “Team Topologies”: platform and enabling work. Manuel shares how he views the strategy behind when and how to invest in platform or enabling work. This conversation also goes into each type of work in more detail, covering topics such as measuring cognitive load and where platform engineering may be heading in the future.
- (2:13) How enabling teams and platform teams are different
- (10:28) What it looks like for a team to own both platform and enabling work
- (17:04) How to deliver enabling work in an organization
- (22:28) Whether enabling teams should be temporary
- (30:10) Platform team anti-patterns
- (47:10) Measuring cognitive load