There is never enough time, money or personnel to monitor every possible security hole or potential misuse. Besides, in one-person shops, you don't want to come across as the thought police.
So, once again, do whats possible and document what you do and why. Law drives corporate policy. For example, the company I work for is controlled by state privacy law, a contract with a principal government entity, and HIPAA.
We have an acceptable use policy and I enforce it. Everyone sings a piece of paper saying the acknowledge a) they have no privacy in the work place and b) they can be monitored at will, for any reason or none. No one can add, change or remove anything on company computers, periods. If you install something, sorry, it now belongs to the the company.
We use ISA on all principal servers, and XP's own firewall on all XP boxes. I keep the ISA logs on all servers forever (or at least until I run out of disk space and have to move logs to tape). I check ISA traffic logs weekly and send department heads regular reports of where their staff hang out when they should be working.
We use no filtering at all - having to explain what you do on the computer to your boss is enough to keep people in line. We have no trouble with liquor, guns, ammo, porn, gambling, shopping and the like - it gets nipped in the bud pretty quick.
As the I.T. manager, I make it public knowledge that I look at all this stuff, and I subject myself to peer review, too.
If anything questionable appears in a log file, three people are immediately notified: a staff member's immediate supervisor, the HR manager, and my boss, the executive director. I will not subject any employee's email, web use and files to a detailed probe unless the HR manager tells me to ask our executive director. We do all this in writing and document what we do and why we do it.
As for spot monitoring, I put a hub between the inside NIC on our firewall and the switch that brings the network together. I use the Debian Linux-based Remote Exploit Toolkit, and EtherAPE to see instantaneous network traffic (inbound, outbound and combined). I know exactly where people are hanging out; if I have questions about why I go ask "Why are you on Ebay, net radio, or whatever?"
In summary:
1. Have a policy. Know why it exists, especially the law behind it.
2. Educate staff about what is expected of them.
3. Keep key decision makers in the loop about what you see.
4. Be personally accountable. The I.T. manager is NEVER above the law they enforce.
5. Document, document, document what you do and why you do it.
My 2 cents worth.