Knowledge sharing is critical for our teams to run effectively. Stack Overflow gives us a central place for staff to get answers to their questions.

As contractors, we need to be able to jump between projects quickly. This is just impossible without a good knowledge base.

It takes a while for the knowledge base to build up to a 'critical mass' before staff will start relying on it as THE place to look first. It is 'yet another' tool that staff need to be aware of when they start at the company.

Stack Overflow for Teams is helping our staff get the knowledge they need to become effective quickly when changing between projects.

The aspect I like the best, is being able to ask company/product specific questions that wouldnt make sense to post on the general StackOverflow site. For example, I would post a question like "why cant python access my google appengine sdk" on the general S.O. site. However, a question like "Please explain the flow between microservice A and microservice B" is much better suited for S.O. for Teams.

I havent found anything I "dislike" about using S.O. for Teams. Our company supports and encourages us to use it.

Another aspect I do enjoy is the ability to name a teammate who you feel might be able to answer the question. This allows me to pose a question, giving everyone in my company the benefit of seeing it and the solution, vs having it buried and forgotten in a Slack thread.

I've been a huge fan of StackOverflow for many years. It saves me lots and lots of time and allows me to give back and contribute in areas where I am an expert, or just to improve or clarify existing solutions. Even though I work hard to help others with questions the hive mind that is StackOverflow always gives me far more than I could ever contribute - the power of the many is amazing.

The Teams version is pretty much the same as the public offering but private. I love the fact that I only had to add my corporate email address to my existing long-lived StackOverflow account so that the experience is seamless. As a software developer, I am not a fan of documentation as people never read it, this is where StackOverflow rules - work out loud, work in public, get to a shared agreed common answer and then it lives forever for others to search, use, enhance. Genius.

Not a lot. I think the weak area is the comments - formatting them correctly and hailing others doesn't seem to work as I would like, maybe providing the full editor for comments would help encourage people to format their comments properly, not sure.

If you know what StackOverflow is and does and you use it regularly you understand the huge value. Just do it, it's great.

Knowledge sharing between product teams and establishing a knowledge base people can rely on - a huge improvement on a Teams channel where everything gets lost.

I like having one central place for all of our company's knowledge. Every question that our delivery teams have ends up in StackOverflow for Teams. The result is a vast searchable database of questions, tags, logs, errors, and stack traces that teams can use to troubleshoot their problems. Having all of this knowledge available is a massive time saver.

I don't particularly appreciate it when users paste in screenshots of logs or code, as this hinders searchability. It is also frustrating when answers become out of date or people don't fully document their solutions.

We use Stack Overflow for Teams for knowledge sharing and supporting delivery teams. The main benefit is a centralized place for questions and answers, as opposed to having these scattered across email and Slack threads.

Stack Overflow for Team it's an excellent tool for development teams as a knowledge base.

A centralized and intuitive tool like Stack Overflow for Teams will help you to share the knowledge and reduce the dependency on team members.

Highly recommended!

Nothing is coming to my mind now. Instead, I consider handy and intuitive tool. Most developers are already familiarized with Stack Overflow.

Having an updated knowledge base and sharing the knowledge that will reduce the dependency on team members.

We all know how helpful Stack Overflow is for programmers and engineers. Now you can use this same great tool to organize knowledge specific to your own company.

There isn't anything much to dislike. It takes time to build a good knowledge base, but once it is there, it is indispensable.

I would say go for it, it really is a great tool.

Stackoverflow for Teams allows us to organize all our institutional knowledge in one centralized location easily searched format.

Almost everyone is already familiar with the Stack Overflow interface, so there are no long learning curves. It is an excellent forum to ask and get answers, especially useful in a company like ours that is all remote.

Nothing to dislike about Stack Overflow, but it would be nice to have a tool or plugins that can search both SO and other internal company documentation (like Google Drive) from a single interface.

SO for Teams is our go-to tool, for technical answers, especially for onboarding new employees. Also, the repository for adding new information on technical questions so we do not have to reinvent the weel.

information is centralized in one place, so it's easier to know where to looking for and search is a lot more efficient than other tools we were using to register knowledge.

Also every developer is acquainted with SO and this makes a lot easier to new team members since there is virtually no learning curve to use the tool and since is so familiar more people were encouraged to record knowledge that was previously restricted to one person, since it works so well more people search there before asking on or slack channel.

The email with summary of what happened in the week in the company's SO is very helpful too.

I think it would be nice if if it were easier to visually distinguish when I'm searching on my company's SO or when I'm searching in the public SO.

One thing that you could improve would be the possibility to select the pre existing tags in the search box, instead of having to consult them in that menu on the left of the screen, it is difficult to notice that menu.

Not related with the product per se but this question here was confusing "What is your industry when using this product?".

Very easy to use since every developer is already familiar with SO.

before we had several places where knowledge was recorded, some of which had very bad search tools, the SO helped us to centralize this knowledge in one place, have standardized template for questions and made it easier to search for information.

We also started using the integration with Slack, and this allows us to know when there is a new question in the OS so that the questions do not go unanswered for a long time.

There are several things to like about Stack Overflow for Teams --

1. There is very little getting used to when it comes to Stack Overflow for Teams, as most devs are familiar with Stack Overflow.

2. The search functionality is so seamless and works well all the time.

3. Adding information to the knowledge base is very intuitive; when there is a doubt, ask questions; when an area is updated, make suggestions or revise answers.

As of now not much to dislike about Stack Overflow for Teams. There are products in Stack Overflow for Teams which we are not fully utilizing yet, like long-form articles, slack integration, and so on. will give them a try.

We are currently using it as a Q and A platform, hoping to extend it to the go-to knowledge base for all things tech in the team.

Stack Overflow is the first line of defense in protecting people's valuable time. Time is a limited resource; everyone admits that. Having a place where folks know they can conduct technical collaboration saves people time and builds community, especially when folks work virtually around the globe.

Since my company uses Microsoft Teams instead of Slack, some of the neat integration features take additional time to show up there, whereas slack has had them for months already.

Before introducing Stack Overflow in your community, be sure to pre-load as much content into the platform as possible and then upon release, make a big splash, have incentives ready to give people for participating right away.

We see a material reduction in context switching for our SMEs. Also, internally we have many different places to write documentation, and Stack Overflow provides an easily searchable way to link people to any platform by creating a question on stack to link-to any platform.