"For Tech oriented teams this is perfect"
What do you like best about Stack Overflow Internal?
I am a frequent user of Stackoverflow and have been for many years - so the whole experience of the Teams product is extremely familiar to me. The search functionality is really great and allows you to find the answers you really need. They also have a Slack app which makes the adoption of the product easier. We're slowly building our library of questions and it would be awesome to have some sort of CSV import
What do you dislike about Stack Overflow Internal?
Struggling to find things I don't like to be honest - it's a really simple application to use and through it behaving in the same way as the Stackoverflow site available to all it's really familiar. It would be great if we could import data into Stackoverflow Teams that we have in a spreadsheet - something like an import format where you can add a question, title, and an answer just to get it started off.
What problems is Stack Overflow Internal solving and how is that benefiting you?
A central repository of FAQ data that we get asked across the business. The search is accurate 99% of the time so there's no searching around in documents we have in various places. I found it easier to get adoption with the engineering team whereas the rest of the business doesn't use it as much - slowly chipping away at that!
For engineering - It's reduced the amount of time that we spend onboarding as new starts as they have a knowledge base available to them with FAQ's on setting up a dev environment, frequent questions that our users generate and loads more.
"Awesome knowledge base for our team"
What do you like best about Stack Overflow Internal?
Through the years we have had repetitive questions being asked in chats. Stack Overflow for Teams has allowed us to move those questions to Stack Overflow where our developer colleagues can first search for their issue before creating a new question.
What do you dislike about Stack Overflow Internal?
There's only one little minor thing that I'm missing from Stack Overflow for Teams, which is customization. It (currently) only allows for setting a single accent color in Light or Dark theme.
Recommendations to others considering Stack Overflow Internal:
The most difficult part of introducing Stack Overflow for Teams into the workflow of your developer teams will be buy-in and getting them to actually use it. My solution was to lead by example and redirect colleagues to Stack Overflow for Teams when they asked questions in our chat.
What problems is Stack Overflow Internal solving and how is that benefiting you?
Stack Overflow for Teams is for us a dedicated place for asking code-related questions. The discussions aren't muddied by other conversations in the same chats.
The fact that our developers can easily find existing questions has been the biggest benefit for us. Developers can search our Stack Overflow for Teams first to see if any of their colleagues have run into the same issue. It has also allowed for wider cooperation across teams. Before, developers might have asked the question within their team, not wanting to bother others in bigger group chats. When asking questions within Stack Overflow for Teams, more developers from other teams can also answer and share their insights.
"Beats archiving emails and then trying to search and find them"
What do you like best about Stack Overflow Internal?
- Instead of writing up answers for questions I get asked over and over, I can direct people to a Stack Overflow answer.
- It's much easier to search Stack Overflow than it is to search through emails or OneNote notes.
- their Stack Overflow answers will remain, preserving their knowledge
What do you dislike about Stack Overflow Internal?
- As the team admin, the 'Admin' tag is distracting and gives my answers extra, undue weight.
- Some have found it difficult to change their habits, and forget to use Stack Overflow.
What problems is Stack Overflow Internal solving and how is that benefiting you?
Onboarding new employees is much easier when they are able to search for answers to their questions. This saves supervisors' time as well. In general, the search function is easy to use.
"A Reliable and Familiar Resource For My Team"
What do you like best about Stack Overflow Internal?
I love the Stack Overflow format. Since my team and I work with about 10 different programming languages, this is a great way to document our findings and help each other solve problems.
What do you dislike about Stack Overflow Internal?
There really isn't much to dislike. The most difficult part is getting the buy-in from the rest of the team. We are trying to make it a habit to use it, so we will see how that goes!
Recommendations to others considering Stack Overflow Internal:
It's a must-have for development teams. Makes life easier :)
What problems is Stack Overflow Internal solving and how is that benefiting you?
Not only is it a great resource to help your team solve problems, but it is great to be able to look back at it to remember how I did things in a language I might not have used in a couple months. The fact that I can post a question and answer it myself before I even upload it is a huge advantage.
"Perfect workspace to manage common issues"
What do you like best about Stack Overflow Internal?
I always used StackOverflow to solve my coding issues, but I never thought to use it as a private space to share my knowledge on the projects I lead and push my collaborators to share theirs. It's a social network approach to company knowledge sharing. Whenever a collaborator asks for help, I always ask: did you search on our StackOverflow first? If not, do it! If yes, ask there for support!
What do you dislike about Stack Overflow Internal?
Nothing! It has everything I need to push knowledge sharing in my team.
What problems is Stack Overflow Internal solving and how is that benefiting you?
Dispersion of information. Multiple questions were repeated continuously. The lack of participation in common problems.
"Clean and familiar"
What do you like best about Stack Overflow Internal?
SO is a website most developers visit at least a couple of times a week, if not daily. So most of us are familiar with it, which is a huge plus for those not eager to use another tool for documentation. It's fast, easy to use, with a well-thought-out feedback system. And - it has a Slack integration :)
What do you dislike about Stack Overflow Internal?
The design is great for a large community or a big corporation, but for a small team, it feels a bit bloated. Also, the aforementioned Slack integration could be more helpful (most of the time, it directs you to the SO website :/).
What problems is Stack Overflow Internal solving and how is that benefiting you?
It is our knowledge base. With SO for Teams is much easier to write down bits and pieces we usually forget than with most of the tools we have used so far. And for us, ease of use is essential to keep the stuff up-to-date.
"Good for capturing knowledge within teams which would otherwise be lost in messaging systems"
What do you like best about Stack Overflow Internal?
The ease of use of the interface and integrations with messaging systems like Slack
What do you dislike about Stack Overflow Internal?
Inability to embed documents. The QA answer format does not lend itself to deeper topics
Recommendations to others considering Stack Overflow Internal:
Add Slack Integration. Start early so that the culture of adding and using SO doesn't have to be retrofit into your culture.
What problems is Stack Overflow Internal solving and how is that benefiting you?
Knowledge sharing within the team. We have discussions on Slack and move the conclusion as a QA to SO
"Motivates me to answer questions more when in Stack Overflow format"
What do you like best about Stack Overflow Internal?
It feels like I'm adding to knowledge that will be read and helpful to others in the future.
Fantastic that it's free, which is the reason we only adopted it now.
What do you dislike about Stack Overflow Internal?
It's not well integrated with any of the existing systems we use, so often people need to be reminded to use it for questions rather than just messaging the person directly.
The Microsoft Teams integration could use some improvement, especially the authentication stage.
What problems is Stack Overflow Internal solving and how is that benefiting you?
Saving knowledge to be used in the future. Write once, read many times.
"Easy to use and useful tool for sharing knowledge."
What do you like best about Stack Overflow Internal?
Since I am already familiar with using stack overflow, implementing this tool for internal purposes was very easy to use. We have been using this tool in our team within the last 3 weeks and so far it's been great.
What do you dislike about Stack Overflow Internal?
Adoption has been a little bit slow, some use the tool more often than others, hopefully, the adoption of the tool will increase when we have more information about different topics.
What problems is Stack Overflow Internal solving and how is that benefiting you?
Sharing information that use to be kept by one or few members is now being shared in a single location, using tags has allowed us to organize the information easily.
"SO for Teams is a great way to collaborate"
What do you like best about Stack Overflow Internal?
The Teams SO has been very handy for us; even though we are only a small team, we like to store the common developer "FAQs" on our Teams account so that when we have to do complex things again which aren't done frequently, or train new people up, there's a nice place to go where it's all in one place and others can then add to it later etc.
What do you dislike about Stack Overflow Internal?
There's not a lot I dislike really. It does the job well!
What problems is Stack Overflow Internal solving and how is that benefiting you?
No problems as such, but the benefits are that we have a centralised location to put a repository of knowledge and information for future use.
