Stack Overflow for Teams

Everything you love about Stack Overflow in a private space.

get it
#4 Product of the WeekMay 03, 2018
+1

Stack Overflow for Teams is a private, secure home for your team’s questions and answers. No more digging through stale wikis and lost emails—give your team back the time it needs to build better products.

Around the web

Reviews

  • Pros: 

    Better documentation & collaboration is cheaper in the long run!

    Cons: 

    If you succeed you will graduate to Enterprise (good problems)

    Their enterprise product has been a huge hit with big companies, having that community power to do better long term documentation and historical knowledge repository at your fingertips for a smaller team is a big win for startups.

    Julie Fredrickson has used this product for one week.
  • Cameron Alexandercreator of things, indie hacker, etc
    Pros: 

    Helps with onboarding and saves time answering questions multiple time

    Cons: 

    People have to actually use it for it to be useful, so you have to get your whole team on board

    I was skeptical at first, but SO for Teams has become a great way to document things about your team's process and decisions that would otherwise go undocumented.

    Cameron Alexander has used this product for one week.

Discussion

You need to become a Contributor to join the discussion - Find out how.
J.J. Fliegelman@jdotjdotf · CTO, WayUp
We've been using this in the beta and it's been the best thing ever--I cannot overstate how immediately and dramatically it changed how knowledge is shared and memorialized among our engineering team. It works for both small teams (5-10) and large ones (hundreds). I'm thinking of rolling it out to the whole company if we can find a good way to separate different types of knowledge (technical v non-technical, etc.) Every CTO I've shown this to has also understood the value of the product immediately. It's far better than a wiki, which takes time to write, makes guesses about what people will need to know, and gets stale over time. This stays as up-to-date, relevant, and useful as the regular Stack Overflow, without any extra effort. The only tough part here is to get people out of the habit of asking in Slack and instead get them to ask in Stack Overflow--but that's not too difficult to solve since most developers are used to asking in Stack Overflow anyway. And, if you wanted to take it a step farther and be really clever, you could write a slackbot to recognize questions and encourage the person to move it to Stack Overflow instead. (Also, just from a vanity perspective, it is incredibly cool to see WayUp's logo inside Stack Overflow itself.)
willcoleMaker@willcole · VP of Product at Stack Overflow
@jdotjdotf Glad you're having a good experience with Teams at WayUp. A couple of notes: 1. You can have multiple teams, and have individuals be members of multiple teams. 2. Hear you on Slack. We're working on more integrations to migrate question content from chat products to create Q&A artifacts on Teams. 3. We've had a surprising number of teams report back to us that they've invited PMs, designers, marketing etc... into their teams to great success.
J.J. Fliegelman@jdotjdotf · CTO, WayUp
@willcole I have no doubt you could get marketing, design in there with no problem. I have a separate use case I'm thinking about where you'd need to limit who has access to certain information that would be present—but multiple teams might be the answer there. Happy to discuss if you're interested to hear about it
Toon Verbeek@verbeektoon · Indie hacker, dev turned product manager
@jdotjdotf Hey! It's really cool to see that you're thinking about rolling a Q&A-like knowledge base for your entire company, not just development. I've been working on something that does exactly that! Would love to have a chat sometime to understand your specific needs. Would you be up for that? Thanks!
Ryan HooverPro@rrhoover · Founder, Product Hunt
I can see this being particularly useful for bigger teams with more mature products. In all the smaller startups I've worked in, I've found it difficult to maintain and up-to-date internal wiki (which it sounds like this replaces). I'm curious what type of companies and use cases you're seeing so far, @spolksy and @willcole?
Joel SpolskyMaker@spolsky · CEO and Co-founder, Stack Overflow
@spolsky @willcole @rrhoover The big problem with a wiki is that you have to tell people to "write documentation" which is homework they don't want to do. They either write too little (because it's homework) or too much (because they don't know when to stop or what information needs to be included) and then the Wiki is a useless artifact which rots quickly. Whereas, with Q&A, you only have to "document" or write things because one of your teammates has an immediate question and an immediate need -- and then you stop writing the minute they say "OK, I get it!" So now you've created exactly the right amount of documentation, and it's stored in a Question / Answer format which is perfect for searching later. I think that even smaller companies (5-25 developers) have a lot of Q&A going on in chat and email, where it's lost to posterity. So at least if you direct your Q&A through Stack Overflow for Teams, it'll be there forever. Our own internal Team already has hundreds of questions that have become invaluable to new developers.
willcoleMaker@willcole · VP of Product at Stack Overflow
@spolksy @rrhoover Also, for big teams who want more control (on prem self hosted), we have Stack Overflow Enterprise (https://stackoverflow.com/enterp...). The risk for small teams is that things happen infrequently (even if important) and no one notices. We're making sure this works for small teams by integrating Teams notifications with the SO Public system, and we support tag watching (email and Slack notifications). Additionally you can @mention team members to direct questions to an individual, something that wouldn't work on the public site and helps small teams stay more connected.
Maxim ZubarevHunter@mxmzb · I build things, too.
You guys know how StackOverflow works. Same thing for your company issues. This just got me way more excited than it probably should have.
Emanuele Ricci@stermi · I get excited about bleeding edge tech
Seems cool but I feel that SO should also have a 1 free plan (with upgrade) for really small teams (like Slacks)
Joshua PinterPro@joshuapinter · Product at CNTRAL. Maker of ntwrk.
@stermi I was thinking about this, too, but I think the true value of this private SO for Teams is for larger teams. For a team of 10, I think a well-curated Wiki still makes the most sense. But for large development groups and organizations, like an Amazon, this can be extremely valuable.
Emanuele Ricci@stermi · I get excited about bleeding edge tech
@joshuapinter if it's a team of developers I cannot see a better tool than SO (every dev is used and know SO). It also would be cool (I didn't read all the features) if I can create an internal question that is also posted on SO and the answer (approved on SO) would be also added on my private SO
willcoleMaker@willcole · VP of Product at Stack Overflow
@stermi Up to 10 users it's a flat $10/mo. The $5/user/mo only kicks in after that.
Alex Bogdanovski@albogdano · Created Para BaaS https://paraio.com
@stermi I think going with one of the open source SO clones would be a better choice for small teams. The thing is, very few of these clones actually support the 'teams' functionality, i.e. an isolated space for questions and answers. Scoold is one of them (https://scoold.com).
Amie Chen@amiechen01 · UI Designer/Developer. Love making stuff
I think this is a really smart move and is solving a real problem! Many companies I have worked for before were trying to solve this exact problem internally, by rolling out things their own. It's a common hackweek project, let's just put it that way :). Awesome job and can't wait to try it