Patch Management In Networks With 10 Computers

I have installed WSUS and, at first, was organizing the groups by department.  I soon realized that this was pointless and remembered the KISS (keep it simple stupid) principal.  I run a small network, but with multiple locations.  I mainly need to ensure that computers are updated and keep the management of it simple but effective.

I now maintain just three groups.

1. Servers:  I want to control what is installed on these machines. 
2. Testing: In a small network this includes some PCs that are in main production and I.T. PCs.
3. Production: All other PCs are lumped into the Production group. 

If I have the luxury of a testing PC it has a place in the testing group.  If I lack a good test bed, usually the case in a small network, I can solve this problem by including IT and a sampling of production PCs (i.e. one sales pc) into the testing group.  I can see what the real-world effects of the patches are before rolling them out company wide.  Worst case scenario is that I have one sales pc down, not all of them.