I do dislike tree-based organisation, but I can’t imagine the Wiki approach, because each article needs a unique name. That works fine for documenting real-world distinct things. But in a company, the only real distinct things with names are projects/products, and you do not want just one Wiki page per project.
I guess, for a project “Foo”, you could have pages named “Foo: Finances”, “Foo: Customers”, “Foo: Code”, but unless you make those understandable without context, that’s kind of a tree structure again.
I do dislike tree-based organisation, but I can’t imagine the Wiki approach, because each article needs a unique name. That works fine for documenting real-world distinct things. But in a company, the only real distinct things with names are projects/products, and you do not want just one Wiki page per project.
I guess, for a project “Foo”, you could have pages named “Foo: Finances”, “Foo: Customers”, “Foo: Code”, but unless you make those understandable without context, that’s kind of a tree structure again.
Ha, I wish projects and products would be real distinct things in my company. They split and merge. Their scope changes or is not clearly defined.