I suppose the 'thing' being prestigious to write is a differentiator, here. Put that team on AdWords with principal expectations for each of them and it's probably dysfunctional.

I wrote a golang WaitableBool struct for my team's code. I tried to submit it to the company's internal 'contrib' library, but golang-team rejected it. I pointed out that the company's C++ and Java versions of the struct were used in >150,000 places. Clearly there was demand and the Golang version would become widely-used. They argued that all Golang coders should always remember details of channel syntax and be happy to read five lines of boilerplate instead of "value.waitUntilTrue()".

I think their team was too senior. None of them were willing to add breadth to the standard library, despite massive code duplication within the company. They need a junior team member who can get promoted for growing and maintaining the standard library. We all need that.

[0] https://pkg.go.dev/math