742 Stack Overflow for Teams Reviews
Majority (if not all) developers are familiar with Stack Overflow so getting them on board was easy and training wasn't really needed as they've had previous experience
Rather than the usual approach of Stack Overflow where you go to ask a question, we used Stack Overflow for Teams as a place to put answers first. For example, if you have an incident that you resolved (e.g. an application was displaying an error) and you resolve this then you would add this as a question and answer the question yourself. Next time this incident occurs someone can easily search the error message that is displayed and it will come up with the resolution that you gave previously.
Slack integration is great as well so can share questions/answers between the teams.
Ability to make tags and then create a wiki is very useful. Rather than having documents hanging all round the place with multiple versions the tag can be the place to look. If a user finds an answer but is unsure what application is about they can look at the attached wiki to find out more. Review collected by and hosted on G2.com.
Can't think of any negatives, it works as expected. All in all a good product! Review collected by and hosted on G2.com.
I love that this is a way to use a format that developers are already familiar with and now you can use it for your team. It is the best way to do living documentation that I have seen yet and I think it will be a key tool for us with onboarding. I also like that I can use it to help improve the transfer of knowledge and information within a team. This way instead of knowledge being moved from person to person it can move from person onto Stack Overflow and allow us to keep it and evolve it over time. Review collected by and hosted on G2.com.
That is is hard to get people to remember to use it. However, as the tool matures I am sure more integrations like Asana will come along. There could also be more resources to help people who aren't already familiar with Stack Overflow learn how to use it. This could really be helpful if they want to grow within organizations. Review collected by and hosted on G2.com.
I like the ability to flag a question to people within the organization, and a private place to ask questions that would otherwise be inappropriate for a platform like SO. Review collected by and hosted on G2.com.
I think the platform needs a fuller wiki, or way to organize questions into topics and practice areas beyond what is already available. We need a way for someone to curate pages of content, essentially. Review collected by and hosted on G2.com.
The ability to house organization-specific technical bugs and solutions is powerful. SO has always been amazing for diving into shared technical problems. But some issues we come across are so unique to our collection of tools and historic code, they felt out of place on a public SO thread. Review collected by and hosted on G2.com.
Not an indictment of the tool itself, but along with READMEs and wikis etc, it's yet another place to look for our company. Better to have too many than too few resources, but fragmentation is a challenge. And the challenge with SO is that it's further from the codebase compared to other locations. Review collected by and hosted on G2.com.
Stack Overflow Teams allows us to use the ubiquitous and easy-to-use Stack Overflow Q&A format to provide thorough well-researched answers to questions that our Support team (and other employees) have regarding our product. Additionally, it allows managers to monitor (and quantify) the contributions of employees to the shared knowledge base through the reputation system. We routinely set quarterly goals for reputation. Review collected by and hosted on G2.com.
Stack Overflow Teams is clearly being actively developed and tweaked to best meet the needs of its users. Just recently they updated the Slack integration to be inline with offerings from other companies. If you have a little patience for new functionality to land, there isn't much to dislike if you like Stack Overflow.
Probably the biggest lacking feature at this point is the lack of support on the Stack Exchange mobile app. Review collected by and hosted on G2.com.
One of the things that developers hate the most is to write documentation.
One of the things that developers like the most is to get a chance to show their knowledge and to teach others. Stackoverflow for teams takes advantage of these two characteristics and by gamification of the process makes the task fun to do and easy to share, maintain and search! Review collected by and hosted on G2.com.
I wish that reputation that was collected on this product would also reflect on Stackoverflow (the website), I think that it would encourage people to contribute even more! Review collected by and hosted on G2.com.
It is, very simply, a private Stack Overflow where I can ask and answer more specific questions about internal products that can't be discussed in a public setting. That alone is very valuable, but the additional notification features (especially the slack integration) sweeten the pot and make it easy to keep tabs on what is going on at our Q&A site. Review collected by and hosted on G2.com.
Would like to preface this by saying that these aren't dislikes with the product itself, but rather with how users interact with it.
Shares a similar problem-set as the public Stack Overflow. Teams users make many of the same mistakes in their first interactions that public users do. For example, I've observed several new teams users attempt to make meta tags for terms that aren't likely to be aggregated or searched on, which is also a common problem on the public site. This is also not necessarily a bad thing because we also have the public site to draw on for methodologies to remedy these problems (in this case, mentoring and discussion of what tags are for) but I could see things like this devaluing a particular team's store of questions and answers if the team site isn't well-curated by its members.
Also, after several months of using the product, we continue to experience difficulty with user adoption in our team. We have a handful of power users that ask and answer most of the questions. Other team members are open to contributing when prompted, but rarely do so of their own volition. Review collected by and hosted on G2.com.
The stack overflow style format is very good for turning questions into documentation by marking answers as approved/voting it as a good answer. It provides a source of truth for things that are too nebulous to document explicitly but often get asked over and over again, especially by new starters. Review collected by and hosted on G2.com.
Because most of the questions are asked by one department (sales) but they often need input from other departments (engineering/customer support) it requires a bit of discipline to make sure the people with the answers keep checking to see if there are things they could answer.
We mitigate this by having a slack channel that gets notified when a question is posted, for better visibility. Review collected by and hosted on G2.com.
People can get their questions to the right people much easier than having to ask around for someone with the right knowledge on the topic. Review collected by and hosted on G2.com.
Licenses are expensive and hard to justify for users that might not use the system very frequently Review collected by and hosted on G2.com.
I love that you get the familiar interface of Stack Overflow, though in a custom setting where the information is private & people are able to easily utilise the search function to find relevant topics. Review collected by and hosted on G2.com.
I don't like the per-user pricing model & think that the software should be geared to user brackets (i.e 10 users = $50/mo, 20 users = $100 /mo etc). Review collected by and hosted on G2.com.
