Ask HN: What's the best way to manage institutional knowledge in tech companies?

While Jira helps document discussions on issues and features long term, information on old obscure bugs, debugging processes, admin, customer relationships, and special tools/processes tend to be left undocumented (probably buried in email, slack or in-person meetings). This issue is often worse for support and other business teams.

What are some good practices to avoid this? What can help reduce friction in documenting this institutional knowledge? How can we make institutional knowledge more accessible within the company?