Natural way to create and organize a knowledge base - ask a question, get an answer, documented for posterity.

We are a small team but still have a lot of moving parts. All team members are so used to using the public StackOverFlow for day-to-day things that are in public domain. However, when there are questions on an internal library or on an error log, we had to resort to a wild goose chase on Slack. We started making documents called "cheat sheet", "troubleshoot" etc which had some success but lacked a way to search. That is when I came across StackOverFlow for teams, which was like God sent. It makes knowledge management simple and inviting. So, the question is Why did StackOverFlow not think of this before?

We love using Stackoverflow Teams as a communication tool between our support team and development teams. It keeps track of all the past questions the dev team has been asked and gets the conversations out of personal direct messages where no one gets to benefit from it.