I've long advocated a simple learning approach to note-taking: don't engineer your organization system from the outset (wiki/labels/etc), just dump your thought

I've long advocated a simple learning approach to note-taking: don't engineer your organization system from the outset (wiki/labels/etc), just dump your thoughts to disk/paper first. Then learn from how you actually use that information (rather than how you imagine you would use it). Your use patterns will provide hints as to the correct organizational method. Then you can start specializing. For instance if your notes are most once-off, there’s no need to organize them. If they’re for writing, you may elect to coalesce and rewrite them into coherent topics. If they’re for to do lists, you can reorganize them using bullet journal methods. If the network is important, then consider a wiki. This same principle applies in data engineering. If the data's use-patterns are not yet established, don't create a complex anticipatory architecture that may be underused or ill-fitted. Learn from how the users use the data, then create the appropriate architecture. Otherwise you'd end up with an over-engineered system that soon gets abandoned due to friction.