742 Stack Overflow for Teams Reviews
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. Review collected by and hosted on G2.com.
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. Review collected by and hosted on G2.com.
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. Review collected by and hosted on G2.com.
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. Review collected by and hosted on G2.com.
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. Review collected by and hosted on G2.com.
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. Review collected by and hosted on G2.com.
The Q&A format is much better than the Wiki format to internal knowledge alive. Especially tagging and comments are very usefull.
Searching ia a breaze. The editing interface is really easy to use.
And above all, it's now free for small teams. Review collected by and hosted on G2.com.
For a private Q&A Knowledge base keeping, the limits of public Q&A is crazy. Admins should be able to freely upvote or downvote or change Q&A owner.
Site administrators should be allowed to select or change accepted answers, to freely downvote or upvote questions and answers, including one's own Questions or Answers. Such feature is critical to draw users attention toward content. It's an integral part of public SO Experience: great questions or great answers have more points. As in a small private team we can't count on crowd to upvote or downvote the only alternative it to let curators do it, which could means site administrators in SO for Teams, but even allowing it for anybody would be better than current settings. In the current state of the product administrators can delete or edit questions or answers from others, and that's all, which is far from being enough.
Unavailability of these features - which looks rather arbitrary and dumb, a mere lack of thinking about the differences between a private Q&A with a handful of users and a public one - blocks our current SO for Teams from becoming the curated private Q&A site I expected at first. It makes it much less useful and much more frustrating than I expected.
Basically, I was willing to optimize the content of our SO for Team site for the benefit of our team (and as an old user of public SO I am a big promoter of Q&A format to keep internal knowledge)... but the current SO for Team didn't let me do it. I'm still hoping SO for Teams will eventually fix these issues (come on, it looks easy), but it was nearly enough to make me drop the use of SO for teams or review existing free Q&A engines (UI far from good enough when you are used to SO) . Basically what made me stick with SO for Teams and keep trying to make it useful is that it became free for less than 50 users. It's easier to explain to my boss that the expected benefit is not there when the product is free.
Also, administrators should also be able to offer bounties which makes much sense in a private Q&A. This would be a great tool to improve content and also to open new types of use (to focus users on most needed content).
A private Q&A teams should certainly not be a democracy, not if we want to keep a quality content in it.
Less critical: I would very much like the ability to clone content from public SO Q&A to private SO for Teams. Some internal Questions already have solution on public Stack Exchange and it would be really handy to cherry pick the usefull content from there (and eventually edit it afterward to make it fit better internal use). Of course I can already do that by copy pasting from public SE content, but it's awkward. Review collected by and hosted on G2.com.
The "private" StackOverflow, to be able to ask questions specific to an organization's environment and technical configuration is priceless. Review collected by and hosted on G2.com.
There needs some time for the teams to get used to posting questions and replying. Review collected by and hosted on G2.com.
Good platform for knowledge exchange inside a company or departement
Easy handling due to known platform Review collected by and hosted on G2.com.
The platform works quite nice, but everyone has to keep the discipline for a good content Review collected by and hosted on G2.com.
So for teams is a special tool to share knowledge across the organization. It uses a familiar QA mechanism and interface (literally every developer has seen the "normal" stack overflow and has had some experience with it), so it is immediate to grasp and use right away.
In our organization it is widely used both to provide technical guides and to collect all common blockers in a single place. Review collected by and hosted on G2.com.
There are no actual downsides since it is already a familiar tool for every developer who uses it; the only thing that can go wrong is organization-specific usage and conventions. If your moderators have a real hands-on experience and familiarity with the community practices used on the public Stack Overflow and try to apply them, I can't see any significant issue. Review collected by and hosted on G2.com.
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. Review collected by and hosted on G2.com.
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. Review collected by and hosted on G2.com.
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. Review collected by and hosted on G2.com.
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. Review collected by and hosted on G2.com.
The fact that I can ask a question about any part of my company's product or business and have it quickly answered by someone with intimate knowledge of that part of the business, as if by magic. It removes the work involved in finding out who the experts are in my company. Review collected by and hosted on G2.com.
It seems that there's a higher chance of duplicate questions/answers without the strict moderation on public SO. This may already exist, but it would be cool if there were a tool to identify parts of the business that often cause frustration and which would benefit from articles/content. Review collected by and hosted on G2.com.
