Software Updates Management

Question

I'm trying to plan for Software Updates. I've got the Software Update Point all setup, configured and testing fine. I'm looking to find out what's the best way to manage the organization of the updates themselves.
How do you guys group/deploy them, do you make folders for organizational purposes, and if so, what sorts of structures do you use?
Do you separate them out by product, or deploy in large groups based on other properties?

Answer 1

I understand. I knew about the folders being purely organizational, not not functional, I think it helps sooth the organization freak inside. I think my biggest concern was the size of the Software Update Package. I think that I had an irrational
fear that the wrong updates would get installed on the wrong products if they were deployed in chucks, but I guess the WUA handles that part. I just have one last question. I'm pretty sure I know the answer, but, when a client downloads the updates, does it
download the whole software update package to update from, or does it only download the updates from the package?
It only downloads the update content that it requires.