Slab Knowledge Base vs. Stack Overflow for Teams

It's perfect for us to update processes that we use daily at Curri. This is a very important piece of our business because being a start-up, things are always changing. I'd say it's pretty appropriate for all needs related to a knowledge base.

Incentivized

In my opinion, Stack Overflow for Teams is well suited for an organization that is on a hiring spree for the engineering teams. The reason for it is because instead of catering to doubts of new joinees individually, they can be asked to refer to the Stack Overflow and hence will save a lot of time for both new joiners as well as the existing employees.

Incentivized

• Organization
• Training
• Sharing information
• Linking documents
• Easy access to company material

Incentivized

• Sharing technical solutions to problems we encounter in our internal development environment.
• Sharing best practices we find in external resources.
• Discussions on design patterns and conventions we can use in our projects.

Incentivized

• Sometimes the search doesn't want to pull up what I've entered, even though when I find what I'm looking for, it's named exactly what I was searching for.

Incentivized

• I would recommend an increased engineering focus on the Microsoft Teams integration.
• It would be nice to make more medals.
• Easier ways to earn points.

Incentivized

Most of the systems I have used in the past that house knowledge feel clunky and difficult to navigate. They are not easily modified and are not easy to access when you are working directly with a customer. They do not feel linear and sometimes feel overwhelming when you are trying to learn new processes. Overall, I've never used a KB that I felt did a great job at housing the information I would need to refresh and train. Slab is easy to navigate, easy to use and overall very seamless in delivering information. I never feel overwhelmed and the simplicity in it's layout allows users to access information without feeling discouraged trying to locate it

Incentivized

It's easier to use Stack Overflow for Teams Q&A to maintain our knowledge base over time, over the Confluence wikis that we also maintain. You don't need to bother about folders, filenames, templates - just ask a question and answer it or get it answered. It feels less formal, so developers feel more free to add content.

Incentivized

• Positive impact in keeping all departments in sync
• Positive impact on finding who owns a particular territory
• Positive impact making and retrieving templates

Incentivized

• It makes the search for answers more efficient, so devs can focus in more important things.
• Knowledge is not lost, even if people leave the company.

Incentivized