In my experience it's useful for teams to share some "culture" -- some shared expectations so not everything has to be communicated explicitly.
On the other hand, it's kind of useful that different teams have different cultures and some between-teams attrition goes on in meetings related to larger projects. Think "marketers versus engineers". It's important that these mutually contradicting views clash!
Also: I've had the bad experience of the buddy-chuminess of team culture gradually drift into flirting and then into unsustainable sexual tension, complete with big fight and months of really bad communication. But note this: we've been able to work through all that storm, and now we're on pretty good speaking and collaboration terms. This only worked because we were cogs in a seven-ish-cog-machine and the machine could grind on with insufficient lubrication between two cogs. (This is a bad analogy because it seems that the more cogs the better, but there's a sweet spot...)
In my experience it's useful for teams to share some "culture" -- some shared expectations so not everything has to be communicated explicitly.
On the other hand, it's kind of useful that different teams have different cultures and some between-teams attrition goes on in meetings related to larger projects. Think "marketers versus engineers". It's important that these mutually contradicting views clash!
Also: I've had the bad experience of the buddy-chuminess of team culture gradually drift into flirting and then into unsustainable sexual tension, complete with big fight and months of really bad communication. But note this: we've been able to work through all that storm, and now we're on pretty good speaking and collaboration terms. This only worked because we were cogs in a seven-ish-cog-machine and the machine could grind on with insufficient lubrication between two cogs. (This is a bad analogy because it seems that the more cogs the better, but there's a sweet spot...)