I've been a contributor on the public StackOverflow site for years, and I felt this could benefit companies internally for a long while. After my employer to adopted the product, I was happy to see that everything I liked about the public StackOverflow site (clear format, reputation points, voting, moderation) is available and just as helpful in the SO for Teams product. Developers got used to asking and searching on SO rather quickly - probably thanks to the familiar format and relatively friendly UX. The fear factor preventing most developers from actually contributing content online seems to be all but eliminated by the internal nature of SO for Teams. I and many others report a reduction in time wasted answering repeated questions or searching for past answers.

The only caveat is the price :) The per-user pricing model might be a bit steep for some companies. In our case, I think there's consensus that it's worth it, but that's a complex calculation to make. Also, the Search functionality can be slightly improved - as it sometimes misses a relevant answer.

Knowledge sharing across teams and sites was a challenging problem for us, with over 15 years of aggregated knowledge concentrating within specific teams or individuals. Newly onboarded developers, or even entire teams, waste much less time searching for solutions for problems ranging from technical issues with their local environment to best practices to design concepts.

Our development team uses Slack heavily but it was becoming difficult when a question was asked to make the proper answer clearly noted for everyone. Additionally it was very difficult for someone to come back and find the question and answer at a later date. If someone wasn't involved in the conversation or was a new hire forget about them even knowing where to look in Slack.

SO for Teams gives our team the ability to branch quickly from Slack into SO to record important questions/answers so that they're properly documented, a true answer is noted, and its easy to search/find later.

The Articles expansion was great for "non question" documentation.

No major complaints. Looking forward to feature expansion to get into some more wiki-light type documents which will really expand our ability to leverage the platform.

Able to more easily document and search/access team knowledge without having to rely on individuals asking possible repetitive questions.

I like that I can easily ask questions that are specific to my team and people in my team will get my question exactly. And it serves as a repository for previous questions that a normal chat-based help channel wouldn't have since previous questions would get lost. As a beginner or a person who has recently started on a project or a task, it is a useful resource since you don't have to continuously ask anyone. It's all just there. It's great.

It's a little difficult to get the correct formatting, the rules and norms for stack overflow (how to cite text sources and screenshots and how much information to include/exclude). But this is mostly because I am new to stack overflow and thus over time I am sure I will get a better understanding of these things.

Problems like technical glitches, version incompatibility, or questions regarding concepts to more experienced developers. Like for example, we used this as a private repository for questions regarding a course I was taking. If I ever had any questions regarding anything, I could simply ask and the course coordinators could answer my questions directly or other students could pitch in but this can be applicable to a lot of other scenarios.

As a senior software engineer, I often feel stuck in the process of training and onboarding and answering the same questions over and over. Filling out our internal knowledge base in SO for Teams has been an excellent way to reduce overhead and simplify the process. The search feature works very well for finding solutions. Also, tagging and assignments allow junior engineers to ping me on an item. The digest emails are also helpful as I can quickly see things I may have previously missed.

The only downside I can think of is how it's another tool in an already complete toolbox. As long as we continue to push new engineers towards it from our onboarding communications and integrate it with our chat software, it shouldn't be too hard of an obstacle to overcome. Further integration tools with our other software would also be helpful.

The product is good, but it is only as helpful as you make it. To benefit, knowledge holders must have buy-in to use the product to build an adequate knowledge base.

We're using SO for Teams as a tool to help with onboarding, training, and troubleshooting. If a new engineer has issues setting up their development environment, they are encouraged to ask it in SO for Teams instead of our chat software. That way, future engineers can also benefit from the answer via searching or browsing through tags. I've realized this helps me not have to repeat myself by answering the same question multiple times.

I always find solutions for a single problem in multiple ways and also top-rated solutions available on the top.

Some times more like solutions given below and also only questions available

Related some query qweb report odoo and the missing package of python for running odoo

You stay in your habits; developers are used to Stack Overflow, so that's easy for them to get involved.

It's not about Stack Overflow for team especially, but more to bring to life the whole process and make it used accross

Structure our technical knowledge, problems and post mortem analysis.

With Stack Overflow for Teams, we have a central repository of appropriately tagged questions and answers to which we can easily refer. Search, similar questions, and tagging makes it very easy to find what we need.

At this time, there has not been anything to dislike. The public Stack Overflow interface is well known, so transitioning to the Teams version had practically no additional learning curve.

Previously team members asked questions in Slack channels and direct messages. Questions and answers slowly disappeared into chat history, only to be asked again and again. The comprehensive search and tagging functions in Stack Overflow for Teams make it much easier to find what we need.

The ability to document company-specific processes and the ability to troubleshoot common development errors.

It takes a long time to delete the default Q&A posts (not sure if this will happen with questions we create). It would be nice if SO for teams would look different than regular SO. I want to choose a different theme for SO for Teams to tell them apart from each other.

We recently moved to Service Fabric for our jobs, and it's a lot of esoteric knowledge. It's nice to be able to ask questions and get them answered in a way that allows other members of the team to gain the same knowledge without needing to stop for a meeting.

The simplicity of the UI, it is also very familiar to most developers

There's no way to vet answers before they are posted and are viewable to everyone. This could lead to incorrect information being shared

Give it a trial!

It has proven especially useful with our newer developers, they now have a place where they can quickly find answers to business related questions.

It is also very useful for us to keep a log of our business knowledge to look back on.

We have seen less of the same mistakes.

A great and helpful community, features like upvotes and reputation points, moreover I can find a solution to my most of the issues faced here.

UX can be more user friendly

Sometimes few mostly asked questions remain unanswered

My issues were i get stuck are solved here once I ask it or many times its already asked,so its helpful for future reference too. Also the reputation points gives a healthy competition within teams