742 Stack Overflow for Teams Reviews
active engagement; responsive team; patient regarding all the different questions (especially around governance, controls) and contractual agreements / negotiations Review collected by and hosted on G2.com.
I have to admit, that there wasn't really a whole lot that I didn't like. The contractual negotiations were frustrating at times but those normally are (at least the ones that I've participated in) Review collected by and hosted on G2.com.

It leverages the existing strengths of Stack Overflow for answering your own questions, but makes it available within a team. Review collected by and hosted on G2.com.
It would be nice to be able to scope a search within a tag.
We're still figuring out how to leverage SO for Teams to its fullest potential when it comes to our codebase. It'd be great to see prior art or how other teams do it. Review collected by and hosted on G2.com.
The way Q&A lets you start building up knowledge with minimal initial time investment Review collected by and hosted on G2.com.
Most of the features are focused on programming questions, and there are also a lot of non-programming questions. Review collected by and hosted on G2.com.
The product concept itself is useful and makes a lot of sense for knowledge sharing and management. Review collected by and hosted on G2.com.
Our support experience was not what we expected. Review collected by and hosted on G2.com.

Easy organisation of information. Easy to "ping" someone for more details. Ability to create Wikis on topics.
The ease of use after years of working as a community project helped to iron out many bugs from early on. I like that we can have a democracy of differing opinions or definitive answers in the same area. I like that you can edit your answer to show updates in processes, or what should be the correct answer.
I like that it gives the users the ability to self-govern. By removing that barrier, it would be possible for a setup-and-forget from the SysAdmin point of view by not being the sole person to moderate everything. Flagging helps, although I have not used it in practise. Review collected by and hosted on G2.com.
Cost. To use it as a non-profit is still quite pricey, so I can't turn my non-profit orgs to it.
Not open source - I can't install it on my own hardware if required. Review collected by and hosted on G2.com.

It's a central place for information with good search, the ability to ask people to answer, Slack integrations, reputation (always a bonus), and the ability to link to easily other documentation sources.
Being able to follow 'tags' for the terms that apply to your teams is very valuable, as well. You can link them to Slack channels (so they are automatically posted), or just receive emails when someone asks or answers questions.
Establishing reputation for your answers is also great - it provides incentive to provide good answers, ask high-quality questions, and edit answers or questions that need just a bit more clarification or adjustment.
The high quality search on Stack Overflow is nice, too. If you lack a central search mechanism, then Stack Overflow can be a nice bridge between different sources of documentation (whether static sites, wikis, tickets, etc). Review collected by and hosted on G2.com.
It's easy for things to get out-of-date, but linking to other documentation (where applicable) is a good way to solve for this. It's a bit tricky to ensure that you get adoption, but with the Slack integration, it's easier to nudge people toward asking a question from Slack on Stack Overflow.
When dealing with coworkers, 'down' voting an answer or question is... Tricky, at best. Review collected by and hosted on G2.com.
Builds on the very successful Stack Overflow Q&A model. It's a mature system that most developers are already familiar with. It also works well for non-developers as evidenced by hundreds of active Stack Exchange communities fielding questions from gardening to statistics to interpersonal skills. For a large team, SO for Teams might be the best way to share information. I'm particularly excited about articles, a new feature.
(Note: I may be given a $25 gift card for this reveiw: https://meta.stackoverflow.com/questions/401087/why-is-stack-overflow-sending-out-emails-paying-for-reviews-on-a-service) Review collected by and hosted on G2.com.
Teams really doesn't work without a large enough group of people participating. My guess is that as few as a half dozen committed contributors will be enough. (I'm basing this on several teams I've been part of as a former Stack Overflow employee, current moderator and community manager on another site.) The larger your team, the more likely you'll be to get enough interaction to keep people engaged. It's also important to insist people ask on SO for Teams and not just Slack or whatnot. Over time, your organization will build a corpus of answers that will really reduce time asking the same questions over and over again.
For organizations who don't get critical mass, Stack Overflow isn't the right tool. Google Docs or GitHub issues are still perfectly serviceable ways to share knowledge and you probably already have access to those tools. Documenting and knowledge transfer is hard work no matter what tool you use. Review collected by and hosted on G2.com.

I was able to keep the code/question open without having to worry about information/any internal documentation leaked to the public. I was also able to ask questions within the organization without the fear of being treated harshly for asking naive questions. This was important because within organization such treatment can be dealt seriously and encourages people to ask questions on this platform which satisfies the very reason this platform exists as well.
In addition I like the fact that important people within the organization was able to see my answers which helped me gain recognition Review collected by and hosted on G2.com.
Lack of community support initially when the product was new. Sometimes it would take a long time before we get one answer.
Organization friendly medals or badges were not there but would be nice for people to be recognized Review collected by and hosted on G2.com.
bi-weekly check-in and all the resources we have received on how to build the platform Review collected by and hosted on G2.com.
VC can't whitelist their portfolio companies domain, you need to single invite and then have them verify the domain. Review collected by and hosted on G2.com.