People think that hierarchies are the correct way to structure information. In many cases, that makes sense at first. But soon enough, you realize some things d

People think that hierarchies are the correct way to structure information. In many cases, that makes sense at first. But soon enough, you realize some things don't fit into one place, or there are two or more competing ways of building a hierarchy. At that point people spend a lot of time arguing which hierarchical way of storing documentation is better. You have long conversation about in which folder a document should be housed. You end up with a lot of non-productive conversation. Forget hierarchies. Build a graph. Create "indices" which link to docs, which link to other docs. Create one or a few places to enter the graph (think the old Yahoo directory). Hyperlink, hyperlink, hyperlink. You can create a hiercharchy if you wish to, and you can also effortlessly structure docs in all other ways. Restructure links as it make sense. More links == more discoverability. You can do this in pretty much any tool. Wiki. Google Docs. Notion. Quip. etc... If the tool forces you to have a hierarchy of folders, create one, but don't spend ANY time deciding if it is a good one. People will find documents via the links not by traversing the hierarchy.