Most developers have experience of recording and accessing information about development decisions, gotchas, etc via a wiki page. However, my own experience of working with wikis is that capturing information ecomes too much like homework and that very soon the wiki goes out of date, despite everyone’s best intentions. Also, the information recorded is what one person thinks other people will need to know, which is often not what they actually need when the actual problem.

Stack Overflow for Teams provides the ability to organise knowledge in a way that corresponds to how humans best gain knowledge: through the asking and answering of questions. One does not have to wade through someone else's braindump in a wiki page looking for relevant information. Rather, the information contained in Stack Overflow for Teams in targeted to specific needs.

This not to say that SO for Teams obviates the need for a wiki. Rather, it complements a wiki.

The main downside to using Stack Overflow for Teams is getting people to remember to use it to ask questions. But this is something that can be overcome by training and reference to questions that have been previously answered via SO.

I would suggest starting small with adding a few questions, answering them, and then getting feedback from the team.

Above all, Stack Overflow for Teams has been a good tool for onboarding new developers. Before asking another team member a question they can check whether it has already been asked in Stack Overflow. This reduces the cost of onboarding new developers in terms of the time needed from other developers.

Further, a benefit of using Stack Overflow for Teams is the ability to build up an answer that reflects the understanding of the whole team.

Automatically structured content makes browsing content easy and fun. All is well organized. Gamification is fun.

Best Q/A cannot be easily exported to other document management systems to create well-written how-tos or procedures. Sometimes it is cumbersome to read all the answers and the question because they are not been thought to be "published" but just written to quickly have an answer to an issue.

The ability to accept multiple answers because they are equally valid.

Two kinds of problems:

1) The classic problem Stackoverflow solves: posting a technical question to receive a technical answer from experts, regarding the dev teams.

2) A place to discuss open questions in the company or team that are difficult to solve or need many points of view, not only from a technical point of view. By using all the answers we can reach a consensus or a solution in less time. Since these questions are hard to solve, they may stay there for a long time and thus a structured approach helps to remind you about unanswered topics that probably deserve a proper solution.

In this case, having the ability to accept multiple answers can aid to build a valid position to solve the big question because it is rare that a single answer can solve it all.

I like being able to seek support and help others within my organization in a way that I have used - Stackoverflow.

Fortunately, I don't have anything I actually dislike about using Stackoverflow for Teams

It is the proven tool for one-stop place to report and help other team members with issues within your organization. In addition, these issues are super easy to find.

Previously issues reported by developers were getting lost in the various tools used. With Stackoverflow for Teams all is now in one place and super easy to find.

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

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

Yes I recommend. Especially because you don't have to alter the questions unlike putting it in public domain you would rather do it within the org without altering any part of the question. This tool can also be used to create a team specific question that can be answered by geographically distributed teams. In situations where some tools are internal, we can follow topics around those tools and can be informed about questions/topics around those tools.

The questions which are domain specific or organization specific were easily answered as the questions stayed within the org and not exposed to public. This is important as people answer known problems and how they can be addressed with the tools that the organization uses