Hi Igor, thanks for the ping, I wasn't aware of the organization of data teams at Postman before.

As far as I understand it, Postman uses three different types of data teams

- a central one for limited context + as a plattform team

- an embedded project consultant team which get's embedded into the domain

- a distributed team to "fine tune inside the domain"

So in essence, they take all of the approaches above and use them together.

I only have a very limited context here, but from the first looks of the org chart they have there it seems to me that this structure creates a huge amount of communication and still has very unclear responsibility areas, so if you take a typical "team topologies" approach to this, you will notice there is a lot of "collaboration" going on which isn't something you should do in the long run.

Again, I only got limited context, but I don't see a benefit of using that structure over the combinations here. I find the CUTTING part very important and the hubs+spokes structure kind of tries to get around that.