At the beginning of the year I was tasked with getting with a handful of our departments to discuss how to store our project documentatation that allowed for company wide searching to find them. Sharepoint was our proposed solution and we ended up with a folder structure to represent the desired taxonomy with a list of standard attributes. We were fortunate that installing MOSS 2007 was in the works anyways so all we had to do was wait. Well, we finally have it installed and running and some people here are getting familiar with it by creating 'My Sites'.

Getting back to my original task, I now am charged with setting up a Sharepoint Site for one of the departments to see how we should roll it out with the rest them. In that meeting where I was given those marching orders, we discussed having a site at the company level (Level 1) which already exists, then creating a site below that called R&D (Level 2) that will have other sibling sites at some point in time for Admin, Marketing etc. Below the R&D site will be the departments I mentioned such as QA, Development etc. QA is the one I was charged with setting up as a test.

I took a step back and asked, why did we assume that we are creating all of these sub-sites? Our initial requirement was to store project documentation that can be searched upon by those within the organization. It seems that we can meet this requirement as well by having a document library or libraries at the company level and place our documents there vs. pushing out all of these sites with their own document libraries.

My question to the forum is this: Given my situation, what is the suggested route to take an why?