The separation between the public and the team network is advantageous. The fact that in the team, we usually work with the same technologies and projects, and we go through the same problems, having a separate platform for that makes the diagnosis a lot faster. Also, because we know each other in most cases, the discussion is more fluent, and threads become more explicit.

I can't find anything that I dislike about StackOverFlow Teams. Even in the public channel, it was the tool that saved my life most of the time on the bug resolution process.

Maybe if we add a private discussion tool for a more fluid process

The team is made for our school. We use it to ask questions about our projects in general or about the school process. There are always students that worked before you on some problem, so you either find solutions to a similar issue, or you ask about it, and they help you. I realized that I was going a lot faster using this tool.

The best thing about Stack Overflow is that we can quickly post our problem or query and found an instant solution from strangers. Also, we can ask our questions in images format.

sometimes a community becomes slow by which we don't get a response at a proper time, and second its good if this platform also uses an audio chat

I would surely recommend to learners if they got stuck in any of their projects so they can ask on Stackoverflow and can get the appropriate answer.

Asking experts for the better solution

As a tech guy I am using stack overflow for years now. I really appreciate the power of finding good answers to difficult questions. With stack overflow for teams I can now use this power even for our internal knowledge management. People from all departments can contribute their knowledge which is a big win for our teams since it reduces the number of distractions that experts get when someone wants to know something from them. Another very positive fact is, that knowledge is peristent and searchable which is a big win over knowledge that just sits in the head of some experts. Everybody can search for solutions and finds them as soon as there is a certaincritical mass of posts.

It would be nice if i could integrate questions of a certain topic (tag) into existing Wiki/Confluence pages. For example it would be nice to have a RSS feed per tag. This could be integrated into the documentation of our services.

We want to create a persistent knowledge base that helps to distribute knowledge without friction to everyone that needs it. We also want to reduce knowledge bottle necks. We realized that as soon as there is a certain amount of questions and answers, the system is used more frequently as it provides real value from this point on.

Upvoting each other's posts to increase collaboration throughout the company. The best part about this platform for me is the gamification aspect. It is amazing to see the whole company reputation going up as we collaborate with each other. I really enjoy the fact that you can place bounties on people's posts to increase the likelihood of it being answered. Now when people ping me on teams I can easily direct them to a stack overflow post instead of simply asking it.

I think it's weird that when a poster marks a post as the right answer, the answer with the most upvotes is still on top. I would rather have it that if the poster marks the message as correct it is now the top answer. Visually this make more sense for me due to that fact that it is more right. Why would an answer not selected as right be up top? That doesn't make much sense to me. However, I understand the need for the voting system to be in place so users can collectively agree on the best answer.

I would highly recommend it.

A single place where all answers to questions can be found instead of siloed answers. Stack overflow integration with teams is nice because this is mostly where I do my day-to-day work. I don't have to leave teams to go to another site. It is also nice that users can comment directly on the posts. I can use teams functionality to use i.

I love that the Stack Overflow interface for teams is exactly the way I expect it to look from years of experience using it for personal projects and work. Everything is exactly where I expect it to be and nothing is out of place. The same highly effective voting system helps separate good answers from mediocre or "poor" answers, and the points system gamifies work just enough to be valuable, without encouraging poor contributions.

The only thing I don't love about SO for teams is that it's sometimes easy to end up in the "primary" Stack Overflow interface/main page. On more than one occasion, I have mistakenly started drafting a question with some sensitive, company-specific information and nearly published it to the public Stack Overflow knowledge base. This is, obviously, a bad thing. I'd like to see the interface do a better job of making it clear when the user switches between the private and public spaces, though the ability to do so relatively seamlessly is wonderful.

We're solving an incredible number of problems. The biggest, in my estimation, is that questions that were often answered in direct messages or in public channels on Slack now are being posted to Stack Overflow, and then are well documented for other users at the company to find. This format works far better than something like a wiki (read Confluence or similar) type knowledge base, since not all questions are truly "FAQs" and parsing through a knowledge base is much more cumbersome than individual pages for individual questions.

A Private SO instance has been great for our new-ish remote org. It enables easy async communication, as well as excellent search. In the past, we never really had a central place for tech/business questions outside of other tools. My most liked feature is tags, which allow teams to focus on questions directed at them or their product.

There isn't much to dislike about the private instance. My one primary feedback would be more distinction between subject matter experts vs. watching a tag.

The main problem being a central place for questions and answers. We've relied on our chat programs too much, as well as other solutions that not many people use (like confluence). They have always been clunky, and answers get lost over time. It's been easy to onboard people and get them to use this tool, as well as create collections and search for old answers.

Our knowledge base was pretty fragmented before. Most people relied on Slack to find solutions to a problem - and if they didn't find one from searching thousands of messages, they'd post in a Slack channel and wait for someone with the right expertise to respond. That puts a lot of pressure on certain people, and in a lot of cases, questions are answered multiple times over a year or two. Stack Overflow for Teams has optimized this all for us! Stack Overflow has always been great at providing excellent search results for a query - it's how most of us became professional engineers. That's no different here!

The only thing that's been a downside is that we've had to change our habits to stop posting questions to Slack. Being able to direct questions to specific people is a big help.

Fragmented knowledge, Slack was relied on (aside from a wiki that got stale pretty quickly and was hard to search). Stack Overflow really shines with search & being able to find solutions quickly.

Sharing your knowledge inside your company with the familiarity of Stack Overflow is the best. The question and answer format let you share knowledge way better than wiki or other doc formats.

Nothing so far. The experience is excellent.

Brag about your points in Stack Overflow for Teams. That increases the usage :)

Instead of searching through Slack to find problems and solutions people have already experienced, we can easily find them here.

* Familiar interface to the public Stack Overflow sites

* Integrates with Slack to notify the team of new questions

* Questions and answers are retained for future reference

* Questions can be tagged to make them more searchable

* Stack Overflow allows images, code snippets, and other formatting that help present questions and answers clearly

* As you type, Stack Overflow suggests possible similar questions/answers to prevent repeating questions

* Minor thing, but it adds an unavoidable validation check before you can post a question whether you mean to use Stack Overflow (public) or Stack Overflow for Teams

If you like Stack Overflow and you have a team that will commit to using it (as opposed to asking questions through other channels), Stack Overflow for Teams may be a great option for you.

* Asking/answering team-specific questions

* Find answers to common questions that other teammates have encountered

Having an internal SO to ask specific questions about your business code or processes where your colleagues can see it and they should have the context as opposed to public SO. Also useful as internal documentation as you can ask a question and answer it yourself all in one action.

The tagging system so far is annoying compared to public SO. It will register tags that we've used in our SO instance but marks them as a red colour like they're invalid. It would be nice if we could assign a short description like other popular tags from the main SO site.

Documenting expected behaviour of our large systems and asking for help when things aren't working as intended.