I get notified over slack so I can reply fast. That also means my colleagues reply to me faster.

Nothing, really. It's a complete solution that allows us to be more productive while using an interface we're already used to. Please don't change that! :)

Stop using GitHub wiki, Confluence, and other documentation tools for your code questions. If you do that you'll end up with different sources of truth. StackOverflow is the best one we've tried so far mainly because (1) it's lightweight, (2) you already use it regularly, (3) you can easily search questions, and (4) you get notified over Slack or email, as you like.

Problems that are confidential, private, or too specific to our company. These are addressed via SO for teams.

Similarity with regular stackoverflow, juggling between public and teams Q&A is great

It can be abused to serve as documentation. But that is more a training problem than a solution issue

Sharing company wide knowledge on shared infrastructure

Resolve minor issues which affect only a subset of people

Share meaningful knowledge about niche problems

StackOverflow is immediately familiar to any programmer, so it's a great format for capturing internal knowledge. Additionally, the question-and-answer format causes people to document bits of information that might not otherwise make it into more formal documents.

Because StackExchange/StackOverflow are more commonly used by programmers, non-programmers may not be as accustomed to the format.

We have a lot of obscure internal knowledge that is difficult to capture and share. Because we are disciplined about asking questions in Stack Overflow instead of in Slack DMs, we are able to document this knowledge for others going forward.

Intelligent search experience makes the perfect condition for smooth workflows and assisting the colleagues when they are in the challenge and need some help. The keywords catch is incredibly useful and the system let's to track all the articles that might interest you based on your previous searches.

The recommendations can be improved based on your search and in the meantime, more interactive bot can be implemented in the website to help with real time-assistance.

I'm solving support-related issues, and reading through the articles/questions that have been posted by my colleagues eases the process of not referring to escalating the issue once you have all the answers located with the keywords. Also, the voting is really awesome, so you can know how legit/valid is the article. The benefits are to decrease the case-solving lifetime, also not to use the senior agents but instead looking through the previously asked and submitted questions.

The Q&A search capabilities are invaluable, with a supported workflow for SMEs and moderators.

There are many opportunities to improve the slack plugin to make the integration more seamless with my company's collaboration workflows. Dashboard and metrics capabilities could also be improved.

Hold a pilot and judge value for yourself.

For a large, globally distributed company like ours a platform like Stack Overflow is invaluable to breakdown silos and provide a place for developers to asynchronously help each other while reducing overhead.

Stack Overflow is a great and exceptional tool for Teams as it provides immediate solutions and help and is easy to navigate and use.

I believe there's not a significant thing that I dislike about Stack Overflow.

Using Stack Overview is quite helpful as it contains some valuable information and is a great resource when investigating difficult issues.

Tagging and search, and the moderation options

Hardly anything, but somewhat clearer branding to distinguish it from 'normal' StackOverflow would help for me

Discussion forums for university courses are usually a mess; StackOverflow is much better organized.

With Stack Overflow for Teams, users can share knowledge about anything related to the group, be it a company, a school, a group of enthusiasts, etc. It allows for more "personal" and direct Q&A since it's not public and all users are on the same team.

There's not much to dislike in Stack Overflow for Teams if you like Stack Overflow. SO for Teams is a private version of Stack Overflow that you can share with a specific group.

On Stack Overflow for Teams, my colleagues and I can Q&A about anything company-related, which allows for more in-depth knowledge sharing between us.

A tool that I'm very familiar with is now also an everyday tool in my organization-specific engineering efforts. I love being able to share and ask questions of my colleagues in a format that encourages teamwork.

While gamification can be fun, it's not a perfect fit for Etsy. The group is less competitive and more about growing and sharing.

If you have engineers and want a familiar tool to share information, SO is a fantastic solution.

We have a vast array of documentation that quickly goes out of date. SO for Teams turns documentation into a living knowledge base that ebbs and flows with the organiztion.

Connect with colleagues from different areas of the company that you would otherwise never do. I have already exchanged with a least a dozen colleagues from other departments because of it. So one could say this is also an excellent networking platform.

The strength of Stack is on the questions and answers and the reputation system. That helps to surface the most relevant content to the top and rewards the users (especially the reputation hunters!) for keeping the content neat and up to date. It takes the burden out of the shoulders of the SMEs with the knowledge reuse. It is straightforward to find colleagues willing to help with any topic by clicking on the "top users" for any tag. Very nice to create custom feeds about the topics (tags) that you work. The search capabilities are also very flexible. You can customize the search results to your needs.

No ABAP syntax highlight support - which is essential for our company

MS Teams integration only connects to one single MS Teams Team

The Slack integration currently allows external Slack users to use /stack search command even without having a user on the instance.

It is not possible to filter the data by anything else other than time intervals on the dashboards.

I know all these points are being looked at by Stack :)

As any project, you need to have great executive engagement and support. In Stack Overflow for Teams this is especially important. We've seen that it is especially motivating when the company leadership uses the solution to answer questions the employees might have about different internal company topics. This really drives the adoption and engagement of the tool, so pick good executive sponsors. Also, it positively impacts the company culture, but changing behaviors is not easy. People tend to fall back to the lowest denominator of collaboration which is emails quite often.

Find where to or to whom to ask a question. This isn't easy in several scenarios for big companies where several different tools are used that can support Q&As. With the increase of Stack adoption in the company, we expect to see a slight decrease in the number of meetings as the information should flow more freely and be more easily accessible inside the company.