[jhchen]

This post makes some salient points about the challenges of team knowledge sharing:

- Tree structure is too strict for cross departmental content ex sales to customer success handoff - should that be under sales or customer success?

- The right answer can be found in multiple tools - companies are not going to ditch Google Sheets / Excel for Notion tables

- A common source of truth needs to take into account the variability in skill - some users are going to be heavier users or more technical than others

- Collaboration needs to be as good as Google Docs or else people will just use Google Docs

It looks like the author is envisioning a new solution with Dokkument but if you want an existing one, take a look at https://slab.com. It’s designed to focus on team knowledge sharing while recognizing that it will be part of the productivity stack. For example, there is have a Content Map feature that shows a bird’s eye view of the entire information topology (with filters and drill down possible) and even mass reorganize from there. Integrations are first class with search retrieving results from other tools and rich linking that will preview external content. Knowledge sharing used to be an afterthought for a lot of teams but with the world going remote it’s exciting to see the innovation and prioritization pick up in this space.

Disclosure: I am a co-founder of Slab

[bad_username]

Some friendly criticism. I was curious how slab topics work but could not find the details after a minute of trying to click and scroll around. The marketing bit about topics does not link anywhere. I finally made some progress by scrolling to the bottom, going to the support section, and searching for "topic". I had to scroll past results that described how to reorganize topics, assign permissions, until I arrived at the basics of topic usage. Even that did not provide an insight about how topics are different from regular tags, and I still am not sure what the difference is. So a "features" or "concepts" page would be nice, and even better if it was the main page. (I am an engineer.)