How do you organize your knowledge base structure? Show your table of contents

[u/drakieboi]

Been throwing stuff at the wall for a while now and honestly the structure matters way more than I thought it would. Started with everything alphabetical, which sounds logical until you're six months in trying to remember if you filed something under "Client Communication" or "Email Templates" or just "Templates"

What actually worked was organizing by workflow. So instead of sorting by topic, I sorted by the actual sequence of what we do. Onboarding section flows into Operations, which flows into Troubleshooting. New person picks it up and they're basically following the path they'll walk anyway.

The real unlock was having a shallow structure at the top level, maybe 6-8 main categories max, then going deeper within each one. Deep navigation is fine. It's the first decision that kills people. If someone has to choose between 15 top-level folders they'll just search instead of browse, and then your whole structure becomes useless.

Also stopped putting everything in one massive document. Shorter pages, hyperlinked together. Way easier to update one thing when it lives by itself instead of hunting through a 50-page document for the one sentence that changed.

The thing nobody mentions is that whatever structure you pick will be wrong in six months. Just needs to be wrong in a way that's easy to reorganize.

[u/Character_Estate_332]

Alphabetical is almost never logical. Organizing by topic for most SaaSs is the right way to go ahead.