Community vs Team

My last topic on the subject - promised.
This is also inspired on the topic #250 "Visual Basic Community"

In #250, @KathleenDollard is looking for the VB community.
In this thread I am looking for the VB Team.

I am working in a very small company (my own company), and I always worked in very small companies.
So I have difficulties understanding how big companies like Microsoft work.
In a small company, you deliver a product. If something is not working 100%, you have to fix it. No excuse that it is someone elses job - the customer buys 1 product and doesn't care that it consist of different (even external) parts. For the customer it's just 1 product. But I already learned that it doesn't work this way at Microsoft.

As I get the answers in several threads, there is no such thing as a VB team; there is a VB _language_ team, and a visual studio team. This covers the compiler and the editor.
What I am still missing is the VB content team (who makes the VB content, like templates, example projects, documentation), the VB support team (who talks with the users) and the VB Promotion Team (that tells everyone how awesome VB is).

In this thread I'd like to meet the people behind VB, what they do in the team, what they want for VB and how they see the communication between the VB community and the VB team(s).
What I also like to learn in this thread is how the different teams work together, or are they working in tiny islands (as it seems to be: "This is not a VB issue, this is an editor issue, please try there and there")

How can we learn from each other and how can the community support the team(s) / the team(s) support the community?